I was the first employee, founding engineer, and later lead engineer at Kinetic, a venture studio that builds and runs its own products. Now I'm figuring out what's next :)
brooklyn, ny
the studio
to write · alex
What Kinetic was and what your seat in it actually consisted of. What a venture studio meant day to day, and what "first employee and founding engineer" looked like in practice. Keep specifics inside the ledger.
approved: "first employee and founding engineer" (R-001) · "through august 2026" (R-002)
the winners
to write · alex
ProveIt and PayMe in your own words: what you proposed, what you built, what the numbers mean. Keep the honesty caveat somewhere: company outcomes, run rates from snapshots, not realized revenue, not things you did alone.
approved wordings: proposed and co-built ProveIt's initial product in two weeks (R-037) · $3.0M annualized subscription run rate, 40,000+ active subscriptions (R-038) · 4,485 negotiations for 4,018 users, $844K provider-reported first-year savings, $1.39M over full terms (R-032) · helped build and scale PayMe to a $9.3M annualized net revenue run rate (R-036)
the team
to write · alex
The hiring work: what you owned, what thirteen hiring decisions taught you, and why that work was less visible than the products. This section feeds the thesis.
approved: directly hired and onboarded four engineers; participated in hiring all 13 people added to Kinetic's team, including non-engineering roles (R-009)
the thesis
to write · alex
Why hiring, in your own words. What you believe breaks in technical hiring, what Hiring Theory is testing, and what would make you wrong. No claims needed here; this one is pure conviction.
work · professional
work · projects
work · next
tokens burned
193.5B tokens · 1,265,468 requests · $201.5K · data through 2026-08-28 · current period in orange · full breakdown →
first employee, founding engineer & later lead engineer, kinetic · figuring out what's next
linkedin · github
© Alex Neyman