One platform. Every side of care.

The public commerce site was only one part of the frontend domain. Patients and clinicians had their own portals, while the team used Strapi to manage content. Changes needed to fit those connected surfaces and the APIs behind them.

My role covered frontend architecture, implementation, testing, release, and ongoing maintenance. I worked alongside backend engineers and the CTO. I usually received Figma designs and sometimes designed interfaces myself; responsibility continued after the interface reached production.

Commerce, checkout, payments, and clinic booking were examples inside a broader product. Patient and clinician workflows also connected messaging, appointments, results, prescriptions, registration, and consent with the platform’s services.

The frontend had to translate those workflows into responsive interfaces and integrate with existing APIs. My contribution included implementation and production support across that domain, without treating frontend ownership as ownership of every backend service.

Testing and observability were part of delivery: Playwright and Cucumber supported end-to-end verification, while Sentry supported production issue investigation. Routine AWS work involved services including DynamoDB, Cognito, Amplify, and Secrets Manager.

The engineering record includes platform modernization and CMS migration work. Continuity mattered: product behavior, integrations, and release workflows needed attention alongside library or infrastructure changes. No conversion, revenue, or patient-outcome improvement is claimed here.

My TBD Health role ran from November 2022 to January 2026. I then continued as frontend domain owner during the Wisp transition until July 2026, under the Senior Frontend Engineer (Contract) role recorded in my résumé.

That chapter included documenting system architecture, product behavior, deployments, integrations, and operating procedures, as well as route preservation and login handoff. A product is easier to inherit when its behavior and operational knowledge travel with its code.

The public evidence includes the role and scope record, résumé, a static restoration of the January 2026 public website, and selected interface captures collected in October 2026. Clinician evidence consists of three empty-state crops. The cinematic building is an illustration around these captured interfaces. Employer repositories, credentials, patient records, internal URLs, and private partner details are excluded.