My story
I started in enterprise software engineering over a decade ago and have stayed close to the metal: APIs, databases, background jobs, and the user interfaces that consume them. Most of my work has been in regulated life-sciences environments, where consistency, audit trails, and predictable behaviour matter more than novelty.
I went deep on full-stack .NET — C#, ASP.NET Core, EF Core — and at the same time stayed current on the frontend with React and Angular. I've owned reporting pipelines, long-running workflows, identity integrations, and operator UIs that real teams use every day.
I spent 2.5 years onsite in Canada, working directly with business stakeholders, downstream consumers, and QA. That changed how I write software: I now plan for the production support story before I open the editor.
Working style
I default to small, vertical slices behind feature flags, idempotent handlers, and structured logs with correlation IDs. I prefer one obvious solution over three clever ones, and I write code reviews assuming the next reader will be a junior engineer joining the team in six months.
Engineering values
- Stakeholder clarity before architecture choices.
- Idempotency and observability as first-class design inputs.
- Honest estimates. Honest post-mortems.
- AI as a force multiplier — never as a substitute for review.
Career highlights
- Designed and delivered enterprise reporting and workflow platforms.
- Owned background-job pipelines with retry-safe, auditable transitions.
- Mentored engineers through code reviews, pairing, and design discussions.
- Worked onsite in Canada with business and downstream stakeholders.