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
Platform Refactor
A major part of the work 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 without making the app harder to understand.
Challenges
The most complex part was expanding the product model from individual care workflows into agency and supervisor workflows without making the experience feel heavier for caregivers or careseekers.
What I Learned
This project sharpened my ability to balance careful platform architecture with founder-speed product iteration, especially around payments, permissions, and scheduling workflows.