Our hiring partner is hiring their first engineer.
The founder has already built the foundation himself using AI coding tools: a data layer that pulls Klaviyo data for every client into the company’s own Supabase database (so the team can query it in ways the platform’s native API doesn’t allow), a set of AI skills and workflows the team uses instead of building reports by hand, and a diagnostics tool made of agents that continuously QA client accounts and flag what’s broken. On top of that sit early products that are somewhere between prototype and solid foundation.
It works and it’s validated. But it was built by one person, and it’s reached a level of disorganization that isn’t sustainable as the company scales. The products need to be rebuilt with scale in mind, and the whole system needs an engineer who owns it.
That’s where you come in. You’ll own the architecture end to end: auditing what exists, deciding what stays and what gets rebuilt, and turning it into a fully maintained codebase with clear guidelines. You’ll pair closely with the founder, who leads on product while you lead on development, iterating on agency workflows and products with feedback that comes directly from clients. And you’ll build agentic flows across nearly every area of the business, from account diagnostics to go-to-market, which today are all built and maintained by the founder alone.
This is a lead role, not a founding-engineer-in-name-only role: you set the technical direction and standards for everything that gets built, and as the engineering function grows, you’ll be the one shaping it.