Lead Engineer, Growth

We don't want to hear that you use Claude every day. Everyone does. We want to know what you've built with it. Concretely, in this role:

Own agentic search visibility as an engineering problem : instrument how Alt gets represented in ChatGPT, Claude, and Gemini answers, build the harness that measures it across a set of real collector queries, and treat the results as a channel with a dashboard rather than a guess

Stand up an agent that reads the funnel — event stream, attribution tables, experiment results — and hands you the ranked list of steps where users are leaking, with a hypothesis attached to each

Use models to generate and QA lifecycle content at variant scale — dozens of push, email, and SMS variants per test, screened for compliance and tone before a human reads them, so experiment velocity stops being bottlenecked on copy

Put an MCP server over product analytics and attribution so "which channel produced last week's submissions" is a sentence, not another one-off query and a Slack thread

Use Claude Code or Cursor as the default way you rebuild the funnel instrumentation or migrate the analytics stack, not as autocomplete

If you've built agents, wired up connectors, written skills or MCP servers, or shipped internal tooling your team actually depends on — lead with that. Name the artifact, not the tool.

5+ years of engineering experience with strong backend (Python, Postgres, AWS or similar) and frontend (React, React Native, JavaScript/TypeScript) chops. This seat is genuinely both.

A track record of owning growth systems or product features from design to production. Design doc to shipped, not a ticket you closed.

Fluency with growth tooling and analytics — experimentation and A/B frameworks, product analytics (PostHog, Amplitude, or similar), attribution (AppsFlyer or similar), and lifecycle platforms.

A sharp instinct for funnels and instrumentation , and the patience to turn messy data into clean, trustworthy signal. Most of the first six months is this.

Comfort owning a north-star metric. You've held a number publicly, weekly, and you know what it feels like when it doesn't move.

Strong collaboration and communication. You write great docs, ask smart questions, and give thoughtful feedback.

Bonus: familiarity with the collectibles space or alternative asset marketplaces. You collect, or you have a view on where this market is going.

We'll be specific so you can prepare. Before any of it: download the app, put a card up, make a bid, and try selling. Every round assumes you've used the product, and we expect your point of view to sharpen as you go. For this role in particular, pay attention to where the submission flow made you hesitate — we will ask.

1. Recruiter screen — 25 minutes, Google Meet. Come ready to talk about the metric you own today and how you're performing against it, why Alt specifically, and how you're actually using AI. We'll align on comp and answer your questions

2. Hiring manager Interview— 45 minutes, Google Meet. Be ready to go deep on a growth system you owned end to end: what the funnel looked like, what you instrumented, what you changed, and what the number did. Bring the numbers.

3. Technical screen — 60 minutes. A hands-on working session. Think out loud.

4. Architecture and system design — 60 minutes. Design instrumentation and attribution under real constraints. We'll push back on at least one of your choices on purpose — how you take that matters as much as the design.

5. Culture interview — 30 minutes. How you work with the people on the other side of the funnel: marketing, product, design.

6. Leore, our founder and CEO — 30 minutes. Everyone who joins Alt meets Leore. Come with a point of view on what you'd go after first on unique submissions.

7. Reference check(s) — 15 minutes with a former manager(s).