Lead Engineer, Growth

Alt is unlocking the value of alternative assets, starting with the $5 B trading-card market. We let collectors buy, sell, vault, and finance their cards in one place and we are backed by leaders at Stripe, Coinbase, Seven Seven Six, and pro athletes like Tom Brady and Giannis Antetokounmpo. Our next frontier is real-time pricing at scale—the Alt Value that powers every trade, loan, and product on the platform.

The Role

You are our founding Growth Engineer, and you turn today's experiments into instrumented, repeatable systems across both sides of the marketplace — sellers and buyers. Attribution that we trust. A submission funnel we can measure step by step. Lifecycle messaging that is an owned system rather than a stack of per-campaign setups. Channels we can scale on purpose instead of by accident.

The metric you own: unique submissions. It is our north star, the whole company watches it, and you'll be held to it with the same weekly-reported discipline we hold marketing to.

It's a technical owner who understands growth levers and can build them — thinks like a PM, builds like an engineer. You'll partner directly with our founder and our Head of Marketing, own the funnel end to end, and the ceiling here is running the growth function. The people who are great at this have stepped back from a backlog before, instrumented a funnel nobody had instrumented, found the real blocker, and gone after it without being asked.

What You'll Own

The activation funnel. Rebuild the submission funnel end to end, instrument every step, and run a real experimentation loop on it — A/B testing, and re-engagement for the users who exit without submitting. Today a drop-off is an anecdote. It should be a number with a name on it.

Acquisition channels that actually acquire. Work out which channels bring in real users on both sides — lifecycle, SEO, AEO, paid, mobile ads — and build the machinery to scale the ones that work. That includes agentic optimization: how Alt ranks and shows up in ChatGPT, Claude, Gemini, and other assistants. That surface is new for everyone. It's yours.

The data and attribution foundation. This is the unlock for everything else. Stand up clean attribution, consolidate our product analytics into a single source of truth, and modernize the messaging and deep-linking stack so we can finally tell what moved the needle. Until this is right, every other result is contestable.

Lifecycle infrastructure. Turn push, in-app, email, and SMS into an owned, instrumented system rather than per-campaign setups — including SMS opt-in compliance, which is not optional and not glamorous.

Marketplace balance. Watch the balance across bidders, buyers, and sellers, and build growth into whichever side is weak. A marketplace that grows one side only doesn't grow.

How You'll Use AI Here

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.