01
Join your team
A senior engineer inside your team. I work in your codebase, standups and code reviews, and stay long enough to own a real part of the product. Under the hood: Laravel, Node.js, Python or AWS.
Full-time or long contract
Health products fail in two places: the query is too slow when the waiting room is full, and the wrong person can open a chart. I work on both.
The shape is usually Laravel, a relational database, and role checks at the edge of every record. A nurse, a doctor, and a billing clerk do not share one login.
I do not invent a compliance badge. I encrypt what should be encrypted, log access, and keep the path a reviewer can follow.
What this includes
- •Patient, appointment, and staff models with permissions that match the clinic, not a single admin flag.
- •Access logs for who opened a record and when.
- •Indexes and cache so a chart opens without a spinner.
- •A path for lab orders or results when that is part of the workflow.
What you leave with
- •A chart the right role can open, and the wrong role cannot.
- •A schedule that does not double-book under two clicks.
- •Notes another engineer can audit without a walkthrough.
How it starts
We start from one clinic workflow: open a chart, book a slot, or post a result. That slice ships before we widen the product.
When to use it
Use this when your product holds patient or clinic data and the current build is a form on top of a shared table.
Engagement
Ways to work together
02
Work solely for your company
A dedicated engineer for one company. I take the product from planning to the live version: backend, data, hosting and screens, with your product as my focus.
Dedicated contract
03
One project
A clearly defined build, then a clean handover: an MVP, taking an AI-built prototype (Lovable, Bolt, Cursor) to production, a migration, or an AI feature. Get in touch to discuss scope and pricing.
Fixed-scope project