Frontend Engineer
I build interfaces and the systems behind them - from enterprise frontend architecture to products I ship solo.
About
2+
Years of professional experience
I like structure - holding a high bar in code review, setting conventions, being the person a team leans on when frontend architecture gets messy. I'm just as comfortable working alone: picking a problem apart, building the pieces that matter, and shipping without waiting on anyone else's opinion. Mostly I'm just curious about how things work under the surface, and I'd rather rebuild the wrong abstraction than live with it.
Stack
What I build with.
Selected work
A few things I've built recently.
How I work
A few things I hold to.
Curious by default
Using something without understanding what it's actually doing underneath eventually catches up with you. I'd rather go one layer deeper than ship on faith that it just works.
Boundaries over trust
Constraints should be structural, not conventions people have to remember - a build that physically can't ship the wrong credential beats a comment asking nicely not to.
Cut friction that doesn't earn its place
Every sign-up, setting, and extra step is a tax on someone finishing the thing they came to do. If it isn't load-bearing, it goes.
Rebuild rather than live with it
A wrong abstraction doesn't get more right the longer it sits there. I'd rather redo the piece that's bothering me than work around it indefinitely.
Get in touch