We're hiring the founding technical builder for one of our portfolio companies. We're not naming it publicly, but shortlisted applicants get the full picture, including the company, the first build, and where this goes long-term, before committing to anything.
You will be building systems for established companies with the purpose of increasing profit margins and efficiency. Real workflows, real users, revenue-relevant systems from week one, and as the first technical hire you'll set the standards everything after you is built on.
You build fast with AI, but you don't trust what it writes blindly. You own the system end to end, not just one slice of it.
Give you a clear thesis and access, and you come back with working software and a list of decisions you made along the way. If it's broken you fix it. If it's unclear you ask. Nobody needs to chase you.
You were probably a developer (2+ years) before going deep on AI, and you're now dangerously fast with tools like Claude Code and Cursor, without ever trusting their output blindly.
Systems you've built run in production for real businesses. You've watched them break, fixed them, and hardened them. You know the difference between a demo and something a company depends on.
Rebuilding community templates and tutorial automations is not the same as designing a system. This role starts where the templates run out.
Impressive demos don't count. If nothing you've built has survived real users, real data, and real failure modes, you'll be out of your depth here.
We bring the thesis and the scope takes shape together, but from there you're expected to move. If you need a complete spec before you can start, this will frustrate you.
Fill in the form below. It takes about 10 minutes, and the Loom is the part that decides.