Lead Design Builder

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:

Get to a clickable prototype of a new flow in a day — real card data, simulated model output, testable interactions — so the team argues about a real thing instead of a doc

Write a Claude skill that holds your surface's written bar , so every frame gets checked against it before it reaches review, and the bar stops depending on who's in the room

Mine CX tickets and session replays at volume to find the pattern you'd never catch by hand — the phrasing that precedes an abandoned submission, the screen people revisit three times before they bail

Turn a customer call into a synthesis the team can act on the same afternoon , not a deck three weeks later

Generate and kill twenty directions before you commit to one, and be able to say what each one taught you

Put a prototype in front of actual high-value sellers and come to roadmap planning with behavioral data — "version B moved stated acceptance likelihood, here's the prototype, here's the number"

And have a view on the other side of it: where AI output is actively wrong for this work, and what you refuse to hand to a model. We ask.

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

Relentless curiosity about users. This is the first bar. Not "I read the research" — you go and get it.

You've made ambiguity tractable, more than once. Not a UI problem with a brief attached: a genuinely open problem, where you had to decide what the problem even was before anyone could work on it. You can tell us how you structured the chaos, what you chose not to solve, and how you knew when you had clarity.

Articulation as part of your craft. You can state a problem so cleanly that the room aligns before a single mock exists, and defend a trade-off to an engineer, a founder, and a customer in their own languages. If we ask "what were you actually solving?" about your best work, the answer arrives in one sentence, not a walkthrough.

Influence without authority. You've changed what a company built through the quality of your reasoning: reframed a roadmap, killed a bad direction, gotten engineers to fight for your design's details.

Founding, first, or early designer experience — or you've built something of your own. You know what it costs to own an outcome end to end.

You've shipped things you conceived , not just executed from someone else's spec, and you can narrate the problem-framing behind your best work unprompted.

A portfolio organized around problems and outcomes, not screens. You talk about your work quantitatively: what moved, what you killed, what you learned.

You prototype in code, or in code-adjacent tools, as a thinking medium. AI is already how you work. You can name the last thing you built with Claude, Cursor, Lovable, v0, or Figma Make — and what it got wrong. We'll ask you to show us, so bring something real.

Bonus: marketplace or two-sided experience; high-consideration or financial products where trust was the conversion problem; consumer products with a passionate community; 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 sell. Every round assumes you've used the product, and we expect your point of view to sharpen as you go. For this role, pay attention to the submission, offer, and auction surfaces — those are the ones you'd own

1. Recruiter screen— 30 minutes The surfaces you own today and the metric you move. Why Alt. How AI actually shows up in your workflow. We'll answer your questions and talk comp.

2. Hiring manager with Vijay, Head of Design — 60 minutes, Google Meet. How you frame problems. Bring an open problem you had to define before anyone could work on it, and be ready on what you chose not to solve. Two or three pieces organized around problems and outcomes, not screens. Bring the numbers: what moved, what you killed, what you learned. We'll push back on at least one decision on purpose.

3. Leore, our founder and CEO — 45 minutes. Everyone who joins Alt meets Leore, and he's in design loops daily, so this is a working conversation. Bring a point of view on a marketplace surface you'd go after first and why.

4. Reference check(s) — 15 minutes with a former manager or close cross-functional partner.