Skip to content

Resume

Product engineer in New York. Most of what’s on my GitHub started as friction in my own app. I follow the thread until I understand what’s wrong, file the PR upstream, and keep a patch around so my projects aren’t waiting on review.

Give me a real problem and time to read the source and I’ll ship the fix. That’s how I got 29 PRs merged upstream to expo, Convex, better-auth, shadcn/ui, bun, napi-rs, fumadocs, Astro compiler-rs, and TanStack.

Selected projects

Full project list →

Open source

29 PRs merged across 10 upstream repos: expo/expo (8), shadcn-ui/ui (5), get-convex/better-auth (5), better-auth/better-auth (3), fuma-nama/fumadocs (2), withastro/compiler-rs (2), and 4 more across napi-rs, bun, App-Store-Connect-CLI, and TanStack/db. 6 open across 5 repos. Plus a public patches repo (113 patch files for Bun, npm, and pnpm) so my projects and anyone else hitting the same bug can ship while the upstream PR is in review.

Full contributions list →

Background

Started freelancing in 2013. Reverse engineering APIs, scraping large datasets, pentesting, learning by doing. A few of those scraper bots and automation tools cleared six figures a year before I moved on.

What I’m looking for

I ship a lot. Been solo my whole career, so every project is end-to-end. Most of my team engineering experience comes from contributing upstream and getting feedback from core maintainers on my PRs. What I haven’t done is sit inside an engineering org with code review, on-call, and sprint cycles. I want that next. Specifically, I want to work next to people who are better than me so I get better faster. Every time a maintainer has pushed back on one of my PRs or refactored something I wrote, I’ve come away a better engineer for it. I want those conversations happening every day instead of once a month. Developer tools, devex, mobile, or AI tooling are where my habits would add up fastest.

Education

B.S. Computer Science, Long Island University, 2016