Growth Engineer

Responsibilities

• Own the funnel end to end. Website, signup, onboarding, activation, expansion. You decide what to fix first, you fix it and you report on whether the number moved.
• Build the website like a product. Landing pages, pricing, programmatic SEO pages, interactive demos, the docs entry points. Ship, measure, iterate. No waiting on an agency.
• Make onboarding take minutes. Own the signup and first-run experience for Weave and the Weave Router: connecting a repo, installing the router, getting to the first insight a team actually cares about. Find where people drop off and fix it in the product code.
• Run the experimentation engine. Build the A/B testing, feature-flag and event-tracking infrastructure, then use it. Real hypotheses, clean experiments, honest readouts. Kill what doesn't work, double down on what does.
• Build the growth data stack. Attribution, product-qualified lead scoring, CRM sync. Sales should know which self-serve teams are ready for a conversation before those teams do.
• Automate lifecycle. Email and in-product sequences triggered off what a team actually does in Weave, from signup to activation to expansion.
• Partner across the team. Product engineering on in-product surfaces, our Founding Marketer on launches and content, our Founding GTM Engineer and AEs on the handoff from self-serve to sales.
• Be flexible: some days you're rewriting a signup flow in React, others you're building a programmatic SEO pipeline, debugging attribution or pulling the numbers on last week's experiment. We're inventing the function as we go.

Must-Have

• You're an engineer first. You've shipped production code across the stack and you still write it every week. You can build the experiment, not just propose it.
• You've grown something and can show us the receipts. A funnel you owned, a signup flow you rebuilt, a programmatic SEO play that worked. Not "we grew while I was there." You know which of your changes moved the number and why.
• You think in funnels and cohorts. You're fluent in SQL and product analytics, you know the difference between a metric that moves and a metric that matters, and you design experiments that can actually fail.
• You have product taste. Growth at Weave means making the product easier to want, not adding dark patterns. You can tell the difference and you'll push back when we can't.
• You move fast and own outcomes. You don't wait for a brief. You find the biggest leak in the funnel, fix it and report on what happened.
• You care about developer tools. Our users are engineers. You know what they read, what they trust and what makes them close the tab.
• This role is 5 days in office in SF

Nice-to-Have

Why Join

About the interview