Fitnescity Health Platform Evolution

Snapshot

Role: Engineering Manager

Sanitized: Yes

Context

Fitnescity operates a multi-surface experience where users discover tests, schedule appointments, and receive results while operations teams coordinate provider workflows.

Challenge

The product needed consistent architecture across marketing, booking, and results delivery while reducing manual operational overhead.

Constraints

• Healthcare-adjacent workflows requiring cautious handling of sensitive result data.
• Fast delivery expectations across public and internal products at the same time.
• Partner-driven result ingestion with heterogeneous input quality.

Architecture

A composable web stack connected CMS-driven presentation, transactional workflows, and asynchronous result ingestion pipelines.

Frontend

• Next.js public site optimized for SEO and Core Web Vitals.
• Customer and admin portals covering discovery, scheduling, verification, and results views.

Backend

• Node.js and NestJS services for orchestration and business workflows.
• PostgreSQL-backed operational data with background processing.

Integrations

• AWS-based messaging and event orchestration using SQS and EventBridge.
• S3-based result file intake from external lab partner channels.
• Automated extraction modules feeding structured data into admin review flows.

Data Flow

• Partner files are synced into S3.
• Extraction services convert raw files into structured records.
• Operations validates results in admin workflows before customer publishing.

Execution

Responsibilities

• Owned architecture and delivery across public website, customer portal, and admin tooling.
• Built the public web experience in Next.js 15 with a Strapi-backed content model for non-engineering publishing.
• Led internal workflow improvements for scheduling support, notifications, and operations coordination.

Delivery

• Improved public page performance from roughly 50-level baseline scores to high-80s range on most pages via targeted optimization.
• Unified user and operations journeys across discovery, scheduling, and results.
• Introduced automation around result ingestion and verification handoffs to reduce manual effort.

Outcomes

• Faster publishing and iteration for marketing and product stakeholders.
• More reliable and auditable result delivery workflows for internal teams.
• Higher-quality user experience across critical conversion and engagement paths.

Leadership

• Managed scope across multiple product surfaces without splitting ownership.
• Balanced product delivery speed with operational reliability concerns.
• Drove architecture decisions that were understandable by engineering and business stakeholders.

Lessons

Lessons are intentionally omitted in the public sanitized narrative.