Growth Engineer

We built Overmind, the world's first AI-driven simulation of infrastructure changes. Our simulations are used when making changes to the massive, complex infrastructures that support some of the world's most trusted companies (e.g. Dropbox) and are backed by some of the most successful early-stage investors in the world including Renegade Partners, with Four Rivers, Operator Collective, Dan Scheinman, and Walter Kortschak

Building Overmind taught us how difficult it is for teams to understand and approve changes to complex systems. Coding agents have made that problem much broader, and we're launching a new product to tackle it. Agents can now produce the implementation, but people are still responsible for deciding what should be built and whether the result matches what they agreed.

We built Until for that job. Until is the outer loop for coding agents: teams agree on a Plan, an agent implements it, and Until checks the result against the agreement until every material difference has been resolved or acknowledged.

The product is already in the hands of private beta users. We now need someone to get Until into developers' hands and discover how it grows.

The role

You will own growth for Until end to end, from technical content and outbound through activation, paid conversion, and retained usage.

This is our first dedicated GTM hire for Until. You will not inherit a mature pipeline, a finished playbook, an agency, or a team to delegate to. You will decide what to try, execute it yourself, measure whether it worked, and build systems around the things that compound.

The work spans growth engineering, product-led growth, technical marketing, early sales, partnerships, and developer advocacy. The exact channel does not matter. Increasing meaningful, retained use of Until does.

What you'll do

• Define and execute Until's growth strategy across product-led growth, content, outbound, partnerships, communities, and events.
• Own the journey from first contact through activation, paid conversion, and retention. Instrument the funnel so we understand who adopts Until, why they convert, and why they stay.
• Run growth experiments every week. Ship quickly, measure honestly, expand what works, and stop what does not.
• Write and publish technical content that software engineers respect: examples, documentation, articles, launch posts, videos, and social content.
• Build demos, lightweight integrations, MCP examples, and small tools that make Until easier to understand and adopt.
• Find relevant developers, teams, creators, and partners; contact them directly and move each promising conversation toward a concrete result.
• Bring developer feedback, objections, usage patterns, and ecosystem changes back into product and positioning decisions.
• Work with the founder and product team to sharpen our ideal customer profile, messaging, packaging, and the product journey from free use to a paid team.

Most importantly, you'll measure which of the above do the most to move the needle for the product, and double down on that

Who you are

• You've shipped enough using AI to get frustrated. You've gone beyond "build me a dashboard" and have worked hard to have AI deliver something in the way

  you

  intended it. This could be as a professional software engineer, or it could be vibe coding a side project
• You have personally helped something grow and can explain what you did, how you measured it, and what changed. That evidence may come from a job, startup, community, open-source project, or something you built yourself.
• You communicate clearly and can earn credibility with software engineers in writing and conversation.
• You work autonomously: you research unfamiliar problems, form opinions, make reversible decisions, and execute without waiting for a detailed brief or a team to delegate to.
• You already live within commuting distance of San Francisco, or have a concrete relocation plan that will let you work from our San Francisco office four days a week by your agreed start date. We are hiring on a short timeline, so we cannot accommodate an open-ended relocation plan.

You will be stronger in some parts of this role than others. We care that you can learn and execute across the range, not that you have already mastered every channel.

We care more about evidence than job titles or years of experience. Show us what you built, published, grew, sold, automated, or learned.

Useful experience

None of this is required, but it may help you get started faster.

• Developer tools, infrastructure, open source, MCP, or AI products
• Working as a founder, early employee, or autonomous operator in an early-stage company
• Public technical work such as writing, demos, videos, talks, integrations, or open-source contributions

How we'll measure the role

Your primary outcome is sustainable growth in retained, paying use of Until. Free users matter when they activate, return, and demonstrate a credible path towards becoming paying teams. A large free user base that never converts is not success.

We will track activation, free-to-paid conversion, weekly active teams, paid retention, revenue, qualified developer conversations, experiments shipped, and the contribution of each acquisition channel.

You will work with the founders, product, and engineering teams to improve our ideal customer profile, messaging, pricing and packaging, conversion journey, and the instrumentation behind these measures.

What you can expect

• Work directly with the founders and the engineers building Until.
• Own decisions as well as execution.
• Work with coding agents every day and burn a lot of tokens.
• Ship experiments without waiting for a large approval process.
• Get direct access to product usage, developers, customers, and the reasoning behind the product.
• Receive a competitive salary and meaningful equity.
• Help define both the growth playbook and the future team around it.

How we hire

1. Tell us about yourself and the work you are proud of.Send links, explain your personal contribution and what happened after you shipped it.
2. Try the product.Use the plugin before we speak. Come prepared to discuss what you understood, where you got stuck, and how you would introduce Until to another developer. We care about demonstrated curiosity.

3. Speak with

   us. We will discuss your work, how you operate, and what you want to own.
4. Complete a bounded paid practical project.The exercise will take no more than four hours. We will agree the scope, time limit, and payment before you begin. You will work on an Until growth problem that combines technical execution with distribution-for example, building a small demo or integration and creating the content and launch plan needed to get it used.
5. References and offer.We will move quickly and tell you where you stand throughout the process.