What I am looking for next.
I am looking for a senior engineering role where I own the system end to end. Senior Engineer, Staff Engineer, Technical Lead, or a tier-3 escalation engineering seat where the difficult problems actually land. I prefer remote, but I am open to hybrid for the right team.
Where I do my best work
- Production platforms with paying customers. Teams that take uptime, performance, and clear service-level commitments seriously. A real on-call rotation, honest post-mortems, and a culture that treats reliability as a product feature, not an afterthought.
- Regulated and compliance-heavy environments. ISO, GDPR, NDPR, SOC 2, CASA. I have shipped under these regimes and I would rather have the compliance conversation early, while it is cheap, than at audit time when it is not.
- Architecture and platform work. Breaking a hard product idea into services and contracts. Choosing the data store, the queue, the deployment topology. Picking the trade-offs and writing them down so the team can disagree with my reasoning, not guess at it.
- Infrastructure and developer experience. CI/CD, containerization, observability, the local dev loop. The layer that decides whether shipping is a calm thirty minutes or a panicked afternoon.
- Tier-3 and escalation engineering. The tickets that bounce off the rest of the team. I read the logs, reproduce the bug, ship the patch, and write the runbook so it never lands on anyone else again.
- Teams treating AI as a serious tool. Groups using coding models for actual leverage, not theatre. I have opinions about how to keep the output reviewable, the system coherent, and the engineer in charge.
What I bring
- Architectural judgment. Seven plus years of shipping production systems. I usually know which corners are safe to cut and which ones quietly cost six months later. I sketch, I prototype, I write design docs, I argue the trade-offs in public.
- Project ownership. Scope to ship to support, with the difficult conversations included. I have led products from blank page through launch and the first months of real traffic. I raise risks early rather than perform confidence and miss a deadline.
- Technical leadership. I mentor, I review, I pair. I write the documentation nobody else wants to. I leave teams more capable than I found them.
- Calm under outage. Production failures do not rattle me. Logs, metrics, traces, a clear incident timeline, and a short note afterwards so the same fire does not start twice.
- Stack flexibility. I have shipped production code in several languages across several runtimes, on AWS and bare Linux. I pick up whatever your team has chosen and contribute on day one, not month three.
- AI as a teammate, not a crutch. I use modern coding models to move faster on the work that deserves to move faster, and I know where they embarrass themselves. The judgment stays human.