2026-05-06
Why I'm open to anywhere
Three years of federal .NET in Ottawa, three languages, two passports — and an aversion to ruling cities out before the role fits.
I was born in Cancún, México on a January morning in 2003 and moved to Canada in 2013. Two passports — Canadian and Spanish — three languages, no real attachment to a single skyline. Which is to say: I'm not filtering my next role by city.
What three years of government work taught me
Government work taught me to ship cleanly the first time. WCAG-compliant HTML, accessibility audits, peer code review on every PR, Azure DevOps pipelines that don't tolerate flakiness — when your users include people on slow connections in northern communities and screen-reader users applying for benefits, you stop cutting corners.
After three years inside Service Canada writing C# and .NET MVC for federal platforms, the discipline is permanent. What's changing is the scale of problem I'm chasing.
What I want next
A smaller team, a faster product loop, more of the frontend stack I've been sharpening on the side — Angular, React, the things I build in personal projects like Crittr (Blazor WASM + ASP.NET Core, currently adding LLM-powered features) and the SignalR + OpenAI work I did for Swipe & Decide Cards at JacHacks 2025.
Specifically:
- Full Stack or .NET-leaning role — strongest in C# / .NET 8, but always growing on the JS / TS side (Angular, React, Next.js).
- Permanent, fixed-term contract, or contract-to-hire — open to all.
- Remote, hybrid, or on-site.
Where
Anywhere the role fits. Some places land more naturally — bilingual or trilingual cities like Montréal, Madrid, Mexico City, Barcelona, Toronto — but that's a tilt, not a filter. If your team is in Halifax or Helsinki and the work is right, I'll move.
If that sounds like your team, say hi. I read every email.