Work
Every link below opens something real and running. Nothing here is a mockup or a repo with a README.
Capabilities
4+ years across web, backend, automation and mobile.
Typed end to end. Server components, real loading and error states, motion that respects prefers-reduced-motion.
Schema first. Row-level security, migrations that are reviewed rather than generated, and business rules kept out of the controllers.
Model-agnostic by default. Structured output over prompt-and-hope, with the expensive calls cached and the failures visible.
Submitted to the App Store and Google Play — store listings, age ratings and CI builds included, not just a running prototype.
Deploy on push, migrations gated, errors reported. The unglamorous half that decides whether anything stays up.
Background
Promoted to lead team coordination and project management while building high-impact applications. Overseeing development processes and ensuring project delivery excellence through full-stack development expertise.
Full-stack Developer
Leading development of enterprise applications using AngularJS, Node.js, and Express. Implemented responsive designs and RESTful APIs.
Part-time Backend Developer
Developed scalable backend services with Node.js and PostgreSQL. Focused on performance optimization and security.
Full-stack Developer Intern
Built SPA applications using Vue.js and Ruby on Rails. Collaborated on GraphQL API development.
What I fix
If one of these sounds like your week, that is the conversation to have.
How I work
The reason small projects go wrong is almost never the technology. It is an open-ended scope nobody agreed on.
A conversation, not a questionnaire. I want to know which task eats the most hours and what happens when it is done badly. Often the thing worth building is not the thing you first asked for.
You get the number and what is included in writing, up front. No hourly surprises, and no starting work before we both agree what done looks like.
The first version solves one workflow end to end. You use it with real data before we widen it — that is what stops a project turning into six months of guessing.
Documentation, access, and a walkthrough. If you want me on retainer afterwards that is a choice, not a dependency I engineered in.
Contact
No pitch deck needed. A few sentences about what is eating your week is enough for me to tell you whether it is worth automating — and if it is not, I will say so.
