Responsibility & architecture
Technical Lead for the platform connecting scientific, regulatory and market-access workflows.
Constraints
An initial request, expert availability and milestone delivery need to remain understandable across a multi-step engagement.
Explicit workflow boundaries
React and TypeScript support the product interface; an Express API and Firebase support requests, bookings and operational workflows.
Engineering tradeoff: Shared infrastructure simplifies integration, while workflow-specific validation still needs to live close to each operation.
Check booking availability
The booking service checks availability and existing reservations before creating a booking.
Engineering tradeoff: A check before a write does not establish atomic protection against simultaneous reservations. Concurrency requires separate verification.
Architecture overview based on implementation scope. The tradeoffs describe engineering considerations, not measured outcomes.
Delivery context
The public product presents ProovIntake, ProovMatch, ProovModels and ProovOS. No certification, regulatory approval or market-access outcome is implied by the software workflow.
The challenge
HealthTech teams need to coordinate scientific evidence, regulatory preparation and market access across several specialists. ProovLab organizes this journey through intake, expert matching, deliverables and progress tracking.
Technical scope
I lead the technical work on ProovLab. The React, TypeScript and Vite frontend connects to a Node.js/Express API backed by Firebase. Backend services cover expert availability, bookings, documents and reports; booking creation checks expert availability and existing reservations before recording a request.
Platform scope
ProovIntake, ProovMatch, ProovModels and ProovOS organize the journey from an initial request to expert-supported deliverables and milestone tracking. The platform covers scientific evidence, regulatory planning and market-access preparation.