About This Project
Worked as the primary frontend engineer on a scheduling platform for caregivers, careseekers, and agencies. I led implementation of Stripe subscription and payment systems, improved frontend architecture and design consistency, and contributed backend endpoints and platform architecture decisions. I also helped design and implement a large-scale refactor introducing agency accounts, supervisor roles, and multi-seat subscription support across the platform, while staying close to founder priorities during launch and post-launch iteration.
Role
I worked as a fractional product engineer with a heavy frontend focus, but contributed across product architecture, backend endpoints, payments, design system consistency, and implementation planning for larger platform changes.
What I Worked On
Primary frontend engineering across core scheduling and booking workflows
Stripe subscription and payment infrastructure
Frontend architecture improvements and design system consistency
Backend endpoints and full-stack architecture decisions
Agency accounts, supervisor roles, and multi-seat subscription support
Launch and post-launch product iteration with a small founder-led team
Accomplishments
Helped move the platform through launch and post-launch iteration
Created stronger foundations for subscription billing and agency workflows
Improved product consistency across important care scheduling flows
Supported founder-led product decisions with practical engineering tradeoffs
Challenges & Learnings
The most complex part of this work was on the development side: layering agency and supervisor workflows into an app originally built around caregiver and careseeker interactions without turning the codebase into a tangle of one-off paths. I needed to reuse parts of the existing scheduling experience where it made sense, while still making supervisor mode feel intuitive for a new user role with different responsibilities.
A major part of the refactor was preparing the product for more complex care-provider organizations. That meant thinking through how agency accounts, supervisors, seats, permissions, subscriptions, and caregiver workflows should fit together while still preserving the simplicity of the existing app.
The hardest product and architecture decision was finding the right balance between moving quickly and designing the system cleanly enough that it could scale into a core part of the platform or be rolled back if the use case did not gain traction. This project sharpened my ability to avoid both overengineering and short-term hacks, especially when shipping quickly inside an early-stage product.
I also learned a lot about balancing founder-speed iteration with careful platform architecture around payments, permissions, and scheduling workflows, where small decisions can have a large downstream impact on the user experience.