Job Title Senior Product Manager
Department Product
Reports To Chief Product Officer (CPO)
Location Remote (US-based)
FLSA Status Exempt
Position Summary
The Senior Product Manager owns product initiatives end to end: from understanding the customer problem and making the case for solving it, through shaping and defining the solution with engineering and design, to release and the measured result. This is a fully remote role for a product manager who thinks in customer outcomes and commercial numbers, brings a point of view about what to build and what not to build, and can defend it with evidence.
Assembly is an AI-native product organization. We expect product managers to use AI as a core part of how they research, write, prototype, decide and learn, and to bring judgment about where AI belongs in the product experience and where it does not. The work is discovery-heavy, moves very quickly, and is ideal for people who have strong ability to identify customer and commercial value, define problems tightly, finish what they start, and hold us to the outcome. We love working in product, and we want someone who does too.
This is a senior individual contributor role with significant scope and autonomy. It does not manage people. We are rethinking what the role of product management looks like during a period of constant change in how software gets built, and we want someone who wants to make that journey with us: a product person who is defined by the outcomes they own rather than by the traditional tasks and boundaries of the role, and who is comfortable when those boundaries move.
Essential Job Functions
Discovery and Customer Understanding
· Stay close to customers. Spend regular, protected time with customers and the teams who serve them. Observe how they work, understand the problem behind the request, and know the difference between what customers ask for and what they need.
· Define the problem before the solution. Write the problem statement, the target user, how they solve the problem today, the expected outcome and how it will be measured, before any solution is designed.
· Ground decisions in evidence. Combine customer research, usage and adoption data, support and sales signals, and market and competitive context into a clear view of where value lies. Make a reasoned argument with imperfect data rather than waiting for perfect data.
Strategy and Prioritization
· Own the business case. Build the business case for what we should work on next: the customer value, the commercial impact, the cost, and why it comes before the alternatives. Bring the recommendation; defend it; adjust it when the evidence changes.
· Prioritize against a number, not a backlog. Understand which commercial outcome your work is meant to move (adoption, retention, expansion, satisfaction) and prioritize against it. Say no, or not yet, to good ideas that do not serve it.
· Work ahead of the build. Keep a roadmap that runs well ahead of the build, so that work is understood and defined before it is scheduled, and keep it current as priorities and learning change.
Solutioning and Definition
· Shape the solution with engineering and design. Explore the solution with the technical lead and the designer as peers, before requirements are finalized. Bring the customer problem and the constraints; let the solution be shaped together.
· Define to a standard. Produce a feature definition that states the problem, the outcome, the scope (what is in and what is out), how success will be verified, and what is deliberately left open. Know what clear enough to build means for the engineer who will pick it up.
· Write the stories. Decompose the defined solution into stories with testable acceptance criteria, sized so the team can build and release them incrementally. Write them yourself; own their quality.
AI-Native Practice
· Work as an AI-native product manager. Use Claude and modern AI tools as core parts of your practice: to synthesize research, draft and pressure-test requirements, decompose work, generate test criteria, analyze data and feedback, and build clickable prototypes that go in front of customers in days.
· Improve how we work, not just what we build. Our development lifecycle runs on AI-native workflows and shared skills that encode how we discover, define, decompose and test. Treat those as product too: notice where they produce weak output or slow the team down, iterate on them, and contribute new ones. Continual improvement in the way we work is part of the job, not a side project.
· Bring judgment about AI in the product. Develop judgment about where no interface is needed at all and an agentic experience that does the work on the user's behalf serves them better, where AI adds value inside the experience, and where a conventional interface still serves best. Design for trust: users should understand what the system did and retain control over decisions that matter.
· Own the quality of AI output. Understand what AI-generated output a professional user will accept, how it is verified, and how quality is measured over time. Treat accuracy and trust as product requirements.
Delivery and Outcomes
· Stay with the work through the build. Be reachable to the team during the build for intent and acceptance questions. Handle scope changes deliberately and route them through the definition, not around it.
· Decide when it is done. Review delivered work against acceptance criteria and the customer outcome as a hard gate. Declare a feature finished as an explicit decision, checked against what it was supposed to do, not implied by a count of closed stories.
· Read the result and act on it. After release, read adoption, usage, satisfaction and business results against the measure set at the start. Decide whether to iterate, expand or stop, and feed what was learned back into the roadmap. Release is not the finish line.
· Enable the organization. Supply what go-to-market, customer success and support need to sell, launch and support the work: the value, the change, the known limits.
Leadership and Influence
· Bring energy, and bring it kindly. We have a lot to do and we like doing it. Show up with enthusiasm for the work and for the people doing it alongside you, treat colleagues and customers with generosity and respect, and be someone others want in the room when the problem is hard. Ambition and a sense of fun are not in tension here.
· Operate at every altitude. Move between executive conversations about strategy and outcomes and detailed work with engineers on a story's acceptance criteria, and be credible in both.
· Lead through conviction and evidence. Bring a clear point of view, challenge weak assumptions, and hold the line on outcomes while staying pragmatic about technical and business constraints.
· Raise the bar and help redefine it. Model the practice for other product managers: how to define problems, build cases, work with engineering as a partner, and use AI well. At the same time, treat the shape of the role itself as something we are designing. Try new ways of working, drop the ones that do not earn their place, and help the team see what a product person owns when AI and engineering can do more of what the role used to.
Minimum Position Qualifications
· Significant product management experience with a track record of owning products or initiatives end to end, from problem definition through release and measured outcomes
· Demonstrated ability to build and win a business case for what to build, and to say no to good ideas in favor of better ones
· Experience shipping products that customers paid for and continued to use, and the ability to describe the results in both the customer's terms and the business's numbers
· An AI-native working style: you already use AI as a core part of how you research, write, prototype, analyze and decide, and you have considered opinions about where it helps and where it gets in the way
· Experience defining or shipping AI-driven product experiences, with a practical understanding of what makes AI output trustworthy to a professional user
· Direct experience running customer discovery: interviews, workflow observation, prototype testing, and translating what you learn into definition
· Experience working with engineering as a partner in shaping solutions, and a clear sense of what a story must contain before a developer can build it
· Strong systems thinking and comfort with complex, workflow-heavy software used to run a business
· Strong data fluency: able to build an argument from behavioral, commercial and qualitative evidence, and honest about its limits
· Strong written communication: definitions, cases and decisions that others can act on without a meeting
· Genuine interest in how the product management role is changing, and a willingness to work outside its traditional boundaries rather than defend them
· Positive energy and a collaborative, generous way of working with colleagues and customers; passion for the product and a sense of fun about ambitious work
· Experience in legal, professional services or another vertical where the software runs the customer's business is a strong plus
What Success Looks Like
• Every initiative you own has a clear problem statement, an outcome measure and a business case that the organization understands and has agreed to.
• You are close enough to customers to see the important problems before they arrive as requests, and you can say what is and is not worth building next in your area.
• Engineering and design describe you as a partner who brings the problem and shapes the solution with them, and whose stories are ready to build.
• You have helped change how product management is practiced here, and you can point to something the team does differently because of you.
• Work you own reaches customers in increments, is judged against the outcome it was defined for, and is iterated or stopped on evidence rather than left as shipped.
• Your use of AI in the work is visible in the speed and quality of your discovery, definition and analysis, and other product managers learn from how you do it.
• The commercial number your work is meant to move is moving, and you can explain why.
When you’re considering a new job, it’s normal to have questions. Here are a few things we get asked all of the time:
1. I'm tired of the daily commute. Where are you located?
Assembly Software is a fully remote company. We work across time zones and connect through Teams, so you can build your career from wherever you do your best work: home office, favorite coffee shop, or yes, in your PJs if that's your vibe.
2. What makes Assembly Software different?
Our people. We're a fast growing SaaS company and the leading provider of case management solutions for personal injury and legal firms. Through our three brands, Neos, Needles, and TrialWorks, we serve over 2,500 law firms and 40,000+ users, the largest user base in the industry. Backed by Ridge Road Partners since 2017, we combine decades of legal tech expertise with a scrappy, entrepreneurial energy. We move fast, we care about the product, and we have fun doing it. Our sales team also enjoys uncapped commission with built in accelerators, so top performers are rewarded for their impact.
3. What's the benefits package like?
Competitive and comprehensive. You'll have access to:
- Medical, dental, and vision plans
- Short and long term disability coverage
- Supplemental insurance options
- 401(k)
- Flexible time off
- Paid parental leave
- An Employee Assistance Program
We invest in our people because we know our results depend on them. When you do great work here, you'll be recognized and rewarded for it.
Assembly Software provides equal employment opportunities to all employees and applicants for employment and prohibits discrimination and harassment of any type without regard to race, color, religion, age, sex, national origin, disability status, genetics, protected veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by federal, state or local laws.