Care1

Scaling a Healthcare Platform from Team Formation to Production Pilot

I served as an engineering leader and architecture co-designer, helping scale the development organization while guiding the platform from development into a production pilot.

Business problem

Care1 needed a scalable healthcare platform capable of supporting clinical workflows. The organization had to grow its engineering capacity, establish a sound technical architecture, and demonstrate that the product could operate successfully in real clinics before broader rollout.

Architecture

flowchart LR
  Clinics[Clinic workflows] --> Services[Platform services]
  Services --> SQS[Amazon SQS events]
  SQS --> Workers[Event-driven workers]
  Workers --> Data[Clinical data stores]
  Workers --> Pilot[Two-clinic production pilot]

Technologies

AWS cloud architecture
Event-driven systems
Amazon SQS
Clinical workflow platforms
Team scaling and mentoring practices

Challenges

Growing engineering capacity from a small team while delivery continued.
Designing for a two-clinic pilot without painting the architecture into a corner for later clinics.
Balancing immediate pilot requirements with longer-term multi-clinic scale.
Establishing technical direction and mentoring while co-owning architecture decisions.

Decisions

Helped grow the software team from 4 to 8 engineers.
Co-designed the system architecture with another senior engineer.
Adopted an event-driven architecture using AWS services, including Amazon SQS.
Provided technical direction, mentoring, and delivery leadership as the team and product expanded.
Balanced immediate pilot requirements with an architecture intended to support additional clinics later.

Results

Doubled the engineering team from 4 to 8 developers.
Successfully launched and supported a production pilot across two clinics.
Validated the platform in a real clinical environment.
Established an architectural foundation designed for onboarding additional clinics.
Reduced scaling risk by separating workflows through an event-driven design.

Lessons learned

Team formation and architecture must advance together—capacity without a scalable design stalls pilots.
Event-driven boundaries reduce coupling when clinical workflows need to grow clinic by clinic.
Production pilots are the real validation gate for healthcare platform architecture.