Builder - Staff Product Designer
Santa Clara · San Francisco
On-siteLead & above
Job details
- Santa Clara · San Francisco
- On-site
- Full-time · Lead & above
- Product & Design
- Posted 1 month ago
Sponsorship history
Past filings by Reevo in public government data. Not a promise of sponsorship.
- Filed 2 H-1B LCAs in FY2025
Full job description
About us:
At Reevo, we're reimagining the entire revenue stack from the ground up, and we're doing it with speed. We're building software that orchestrates every go-to-market motion, enabling B2B teams to operate faster, smarter, and more collaboratively. By combining automation, intelligence, and a radically intuitive interface, we're helping companies unlock new levels of productivity and growth across marketing, sales, ops, and customer success teams.
If you're excited about working on a product that reshapes how revenue teams work and being surrounded by curious, driven teammates, you'll feel right at home here. From day one, you'll get real ownership, real mentorship, and real impact. Our team of 100+ builders has over 30 exits under their belt, so you'll be in good company, and working alongside the best!
The Role:
We're looking for a Staff Product Designer to own a major surface of Reevo end to end and to raise the bar for how the whole team works.
You'll work from our San Francisco or Santa Clara office alongside the engineers and product managers you build with, take the hardest and least-defined problems on the roadmap, and turn them into product bets that ship. Nobody hands you a spec here, and nobody is waiting on one from you. You lead with a solution — a design, a prototype, something people can react to. You own your work from idea through production.
The product designer role is changing fast across the industry, and we're looking for someone on the leading edge of it. Our designers prototype in code, command agents, and ship their own front-end work. Figma is for lightweight mockups, exploring divergent directions quickly, polishing little details, whiteboarding, and vision work; production work happens in the codebase. You work in the codebase through agents, owning the decision and proving it with something running.
What You Will Do:
Own the problem, not the screen: Take ambiguous, high-stakes areas of the product and decide what should exist. Own the workflow, the information architecture, and the bet — across a domain or, at times, the product end to end. You'll make those calls fast and on minimal information rather than waiting for certainty, and you'll bring a direction rather than a list of open questions.
Ship in code: Prototype in our playground, work in the codebase, and ship the surface-level UX you own — styling, states, alignment, polish — without waiting on a front-end specialist. You'll do it through agents, and when the output isn't good enough you'll work with engineering to improve how we build our experiences rather than patching the one screen.
Ship fast, then iterate: We learn by putting real work in front of real customers quickly and sharpening it from there. Be clear about the bet you're making and the signal that will tell you whether you were right — then ship it, watch what happens, and improve it. The first version is where the learning starts, not where the project ends.
