Senior Product Builder

About Deeply

Deeply is building a relationship workspace for couples.

Most relationship tools are designed for isolated moments: resolve a conflict, complete an exercise, read advice, or attend therapy. But relationships are ongoing systems. Couples need help not only understanding one another in difficult moments, but also carrying what matters forward and staying connected over time.

Our product helps both partners:

• share their perspectives privately
• develop a fair shared understanding
• turn that understanding into meaningful next steps
• maintain continuity around important topics, goals, and commitments
• reflect, revise, and make progress together over time

We are still early. We are not simply implementing a settled product roadmap. We are discovering the right product model, interaction system, and recurring loop for an entirely new category.

We are looking for a Founding Product Builder to help turn that thesis into a product couples genuinely value and repeatedly use.

The role

This is not a conventional product manager, product designer, or software engineer role.

It is an end-to-end product creation role.

You will take important, ambiguous customer problems and move fluidly across:

> Customer insight → product model → UX flow → prototype → implementation → release → learning → iteration
>

You might spend one day analyzing user sessions and reconsidering the product architecture. The next day, you might prototype a new interaction, modify the underlying data model, implement the experience, and put it in front of couples.

You will not receive a finished specification and simply execute it. You will help determine what should be built, why it should work, how it should feel, and whether it is producing the intended outcome.

The central question for this role is not:

> “Can you build what has already been defined?”
>

It is:

> “Can you help us repeatedly turn uncertainty into a better product?”
>

What you will own

You will own meaningful product problems from beginning to end.

Depending on your strengths and the company’s needs, this may include:

Product discovery and judgment

• Participate directly in customer interviews and design-partner sessions.
• Synthesize qualitative feedback and behavioral evidence.
• Distinguish customer problems from requested features.
• Form product hypotheses and identify the fastest useful way to test them.
• Challenge the framing of a problem when the proposed solution is addressing the wrong thing.
• Help determine what not to build.

Product and systems architecture

• Define the concepts, objects, states, and relationships underlying the product.
• Reason across customer behavior, product loops, interaction models, and system architecture.
• Simplify the product when concepts or workflows become unnecessarily complex.
• Decide which elements should persist over time and which should remain temporary.
• Translate evolving product ideas into coherent technical and experience models.

Interaction and experience design

• Design end-to-end user flows rather than isolated screens.
• Create prototypes quickly enough to support real learning.
• Develop interfaces that make complex relationship workflows feel clear, natural, and emotionally appropriate.
• Write or refine product language where words are part of the interaction.
• Identify missing states, confusing transitions, and unintended user expectations.
• Use AI-assisted design tools without outsourcing judgment to them.

Engineering and implementation

• Build and ship production software.
• Work across the stack as necessary to deliver a complete experience.
• Use AI coding tools extensively while maintaining a clear understanding of the resulting system.
• Make pragmatic decisions about what to hardcode, generalize, test, or defer.
• Add instrumentation so that we can understand real product behavior.
• Identify technical, security, privacy, and reliability risks early.
• Know when a decision requires deeper specialist review.

Learning and iteration

• Put work in front of real users early.
• Observe where people become confused, disengage, or behave differently than expected.
• Evaluate whether a feature is producing the intended customer outcome.
• Revise the product based on evidence rather than attachment to the original solution.
• Close the loop between what we build and what we learn.

What makes someone strong in this role

You do not need to be equally exceptional at product management, design, and engineering.

You should have one area of real depth, strong competence across adjacent areas, and the ability to integrate them into a coherent product outcome.

You are likely a strong fit when you demonstrate several of the following:

• You have personally taken products or important features from ambiguity to production.
• You are a strong software builder who also has meaningful product and UX judgment.
• You are a product designer who can implement production-quality experiences.
• You are a founder, early employee, or independent builder who has owned the complete product loop.
• You simplify difficult product problems rather than merely organizing their complexity.
• You can move comfortably between customer needs, interaction flows, data models, and implementation details.
• You prototype and ship quickly without confusing output volume with progress.
• You understand the systems you build, including code produced with AI assistance.
• You can explain your assumptions, tradeoffs, risks, and decisions clearly.
• You seek contradictory evidence rather than defending your first idea.
• You make progress without requiring detailed task decomposition.
• You know where your judgment is strong and when to involve a specialist.
• You care about the quality of the whole product, not only your functional contribution.

We care more about demonstrated capability than conventional credentials, titles, or years of experience.

What this role is not

This is probably not the right role for someone who primarily wants to:

• receive detailed specifications and implement them
• own only frontend, backend, design, or product documentation
• manage a process without directly creating the product
• produce polished artifacts without validating their underlying assumptions
• avoid customer conversations
• work within rigid functional boundaries
• generate large amounts of AI-assisted output without deeply understanding or evaluating it

Breadth alone is also insufficient.

We are not looking for someone who knows a little about many disciplines but cannot produce strong outcomes in any of them. The ideal builder combines range with craft, judgment, and accountability.

How we work

We believe AI changes the minimum team required to build an ambitious software product.

A small number of strong builders can now accomplish work that previously required a larger functional organization. This allows us to keep the connection between product thinking, experience design, and implementation unusually tight.

Our operating principle is:

> Keep product conception and expression unified. Add specialist review before adding specialist ownership.
>

The core builder moves quickly across disciplines, while experienced specialists help critique the work and identify blind spots.

This may include:

• senior product-design critique
• architecture and engineering review
• relationship-domain and safety expertise
• direct customer observation
• product analytics and behavioral evidence

Production may be integrated, but judgment should remain distributed.

We expect collaborators to challenge one another candidly, make assumptions explicit, document important decisions, and remain open to changing the product when reality contradicts us.

What success could look like

During your first several months, you may help us:

• turn customer research into a clearer product thesis
• simplify the product’s conceptual architecture
• design and ship new end-to-end relationship workflows
• improve the transition from one-time activities to ongoing value
• create more intuitive systems for shared artifacts and next steps
• increase the percentage of couples who reach a meaningful outcome
• improve repeat engagement without relying on superficial gamification
• establish product and technical foundations that other builders can extend
• create a faster, more disciplined build-test-learn loop

We will evaluate this role primarily by outcomes such as:

• the quality of product decisions
• the speed at which important assumptions are tested
• improvements in customer comprehension and behavior
• the coherence and maintainability of the system
• the ability to take ownership without creating organizational dependency
• how much less uncertain the company becomes because of your work

Success is not measured by the number of tickets completed, screens designed, or lines of code written.

Why join

This is an opportunity to help define both a new product category and a new way of building a company.

You will have significant influence over:

• the core product thesis
• the product and technical architecture
• how AI is used throughout the development process
• the quality bar for the customer experience
• the company’s early operating model
• the team we build around the product

You will work on a meaningful human problem with difficult product, interaction, technical, and emotional dimensions.

The product is early enough that foundational contributions will matter. It is also developed enough that you will be working with real systems, real users, and concrete product questions rather than only abstract ideas.

The ideal person is excited by the opportunity to make something real, confront ambiguity directly, and help determine what the company becomes.

How to apply

Please send us a short introduction and examples of work that demonstrate how you build.

We are especially interested in seeing:

• a product or feature you personally took from problem to production
• the specific decisions you owned
• how you approached product, design, and engineering tradeoffs
• how you used customer evidence
• what you built directly
• what changed after launch
• what you would do differently now

A working product, prototype, repository, case study, or thoughtful written walkthrough is more useful than a polished résumé alone.

Tell us what you are unusually good at, where you rely on others, and why this way of building is compelling to you.