Senior Product Scientist Relationships

## About Deeply We are a customer-obsessed company. Everything we build starts with listening to couples — what they're struggling with, what they've tried, why it didn't work. That obsession is the seed of everything. Couples know something is wrong but don't know what to do. Therapy has a 6-week waitlist and costs $200/session. Self-help books diagnose but don't prescribe. We're building a shared system for couples who are willing to do the work — a place where both partners can see each other, communicate honestly, and resolve the issues that actually matter. Today that means: helping couples name what's really going on in their relationship, work through issues together across multiple conversations, send each other structured questions and reflections, and build a shared home where each partner can see how the other is doing and what needs attention next. AI handles the cognitive labor — translating, structuring, guiding — so couples can focus on the relational labor of showing up for each other. We didn't design this in a vacuum. Every feature traces back to a customer conversation, a pattern across interviews, and a theory about why relationships get stuck. That's how we work, and that's who we're looking for. ## The Role You own the pipeline from customer insight to product design. This is the core of the job: - Talk to customers — hear how couples experience conflict, repair, and follow-through - Find the patterns — synthesize across conversations to see what's really happening - Form a theory — name why the pattern exists, grounded in psychology and first principles - Turn theory into a hypothesis — "if we build X, couples will experience Y" - Render the hypothesis as a design — mockups, prototypes, flows that make the idea tangible This is the work. You're the person who sits with a stack of interview transcripts and comes out the other side with a product idea that's grounded in real evidence — and a mockup that shows exactly how it should feel. You'll work directly with the founder to shape what Deeply becomes. ## If you can also build it — even better We use AI tools (Claude Code) to go from design to working product fast. If you can code, or are eager to learn with AI-assisted tools, that's a meaningful bonus. But it's not the filter. The filter is whether you can do the insight-to-design work that makes the right thing get built. ## You're right for this if - You're obsessed with relationships. Not as a job — as a genuine curiosity. You think about why couples get stuck, why repair is so hard, why people who love each other still can't resolve a $40 argument about groceries. You read about attachment, communication, behavioral patterns — not because someone assigned it, but because you can't stop. This is non-negotiable. - You're obsessed with design. You see a confusing product and can't help but sketch how it should work. You think in flows, states, and moments — not features. You can turn an abstract idea into a mockup that makes someone say "yes, that's exactly what I meant." - You turn customer evidence into product thinking. You don't design from assumptions. You start with what people actually said, find the pattern underneath, name the principle, and then — only then — propose what to build. You can trace any design decision back to a real conversation. ## What this is NOT - A traditional PM role where you write PRDs and hand them to engineering - A pure engineering role where someone else decides what to build - A role where you design in a vacuum without customer evidence - A role where you wait for perfect requirements before starting ## What we bring - A validated product thesis with real customer data — not a pivot-hunting startup - A working theory-to-artifact process: raw interviews → pattern synthesis → theory → hypothesis → design → specification - A founder who will partner with you on customer research and product strategy - A collaborative, high-trust working relationship — this is a partner role, not a task-taker role - The chance to shape a product category (bilateral relationship tools) from the ground floor ## To apply Tell us about your relationship experience. And tell us about a time you talked to users and turned what you learned into a product decision. What did you hear? What pattern did you see? What theory did you form about why? And what did you design because of it? Show us the pipeline — that's the job.