Full-stack engineering
TypeScript, Go, Python. End-to-end ownership from schema to shipped product. Comfortable as the only engineer or as a senior IC in a larger team.
I write code for the same reason I ran a 14-person student council: I like turning ambiguous goals into shipped things. Most of my work sits at the intersection of backend systems, developer tooling, and the messy human coordination that makes either of them succeed.
Before going independent I led platform teams across two startups and chaired the technical faculty's student board for three terms. The pattern is consistent — small groups, real ownership, fewer meetings.
TypeScript, Go, Python. End-to-end ownership from schema to shipped product. Comfortable as the only engineer or as a senior IC in a larger team.
Fractional engineering management and tech lead engagements. Hiring loops, architectural review, on-call hygiene, postmortems that change behavior.
Internal tooling, CI pipelines, codebase migrations, and the unglamorous infrastructure that makes a team three times faster.
Independent reviews of codebases, designs, and team practices. Written report, ranked findings, and an actionable plan.
Replaced a 7-year-old Rails monolith with a service-oriented platform handling 40k daily shipments. Cut average dispatch latency from 900ms to 110ms.
Designed and shipped a self-serve onboarding that moved activation from 38% to 71% in two quarters. Owned the surface end-to-end.
Ingested and normalized 14 disparate trial-data sources for a Phase-II oncology study. Audit-grade lineage, zero rejected submissions.
Five roles, two startups, one student council. Each one taught me a different thing about shipping under pressure.