Lead Engineer

The roleAs Lead Engineer, you're the senior technical presence on client builds. Co-founders stay close on scope, client relationships, and strategy — you drive the work from kickoff to production. You'll spend 60–70% of your time coding and the rest reviewing pull requests, orchestrating AI coding agents, breaking work into Linear issues, and keeping other developers unblocked.You make the architecture calls. Auth, data modeling, deployment topology, integration patterns. We trust your judgment, and we expect you to tell us when we're about to do something dumb. As we grow into more enterprise work, you'll also help us shape how we hire, how we run sprints, and how we use agentic workflows to ship faster than a traditional dev shop.This isn't a role where you own a slice of a massive codebase. You own the whole build.What you'd actually do→Own delivery end-to-end on most active client projects — scope, architecture, shipping, and production stability→Code 60–70% of the time; the rest is PR review, agent orchestration, Linear issue management, and keeping the team unblocked→Make the architecture decisions: auth, data model, deployment, integration patterns→Sit in on key client conversations to make sure the build matches the scope→Help shape how we hire and operate as we scale our delivery teamYou probably fit ifYou've been the senior or lead engineer at a small product team, consultancy, or growing company — not a slice of a 10,000-engineer org. You've shipped end-to-end and you know what that actually requires. You're already using Claude Code or a comparable AI coding agent daily, and you have real opinions about how to use them well. You're fluent in Next.js, React, TypeScript, and Supabase or a comparable Postgres-backed stack. Vercel is your default deploy target. You can take a Figma file or a rough spec and turn it into clean, polished product without pixel-by-pixel direction. You care about client outcomes more than pristine code — shipping a working dashboard on Friday beats refactoring forever.You probably don't fit ifYour experience is primarily at a large org where you owned one service in a massive system. We need range, not depth in a single domain. You want a roadmap-meeting culture or someone handing you tickets. You're skeptical of AI-assisted development or think it's a fad. You need a fully specced PRD before you can start — a lot of our work begins as a Loom and a Slack thread.