hire me

The condensed version of how I work, what I value, and what kind of team gets the best out of me.

my core values

Before we work together, you should know what I actually value and how I operate. These aren't posters on a wall — they're how I make decisions when nobody's watching.

First principles

"It works, leave it" isn't good enough. I trace things to the root before I trust them.

Curiosity & growth

I go deep because I need to know exactly how stuff works — not because a ticket told me to.

Sharpen against the best

I want to be the least experienced person on the team. I'm pulled forward by cracked developers who are better than me — I'd rather be catching up than coasting.

Founder energy

Startups are my natural habitat — small teams, high ownership, no bureaucracy. The intensity and the hours aren't a con for me; they're a pro.

not on my resume

The thing a resume can't show: I think a developer should go deep with the tools they use every day — and spend real time optimizing how they work.

It took me two attempts over almost a year to move fully from VS Code to a Neovim/Tmux/Wezterm setup I built by hand. I like being blazingly fast and I love minimal tools — so once Vim motions clicked, Neovim/Tmux was inevitable. The payoff was real (ssh into prod, right logs in seconds), but the point is the conviction: go deep, remove friction, invest unreasonable time in the tools you live in.

neovim config →watch the workflow →

we'd be a fit if…

The kind of team where I do my best work.

[✓]You're a lean team that ships fast — ownership over process, quality over bureaucracy.

[✓]You're open to new technology and better approaches, not locked into legacy habits.

[✓]You hire for capability and give it real autonomy, rather than staffing a role to execute instructions.

[✓]You treat tools, resources, and work-life flexibility as inputs to good engineering, not perks.

[✓]You value first-principles engineering over resume-driven hype.

If that sounds like your team, let's talk [e].