A complete application in a minute
Tailored resume and cover letter, ready to send.
ABC Legal Services in the United States seeks a Technical Product Owner to own the backlog for the Service of Process platform, ensuring delivery aligns with SAFe cadences across engineering, operations and product teams.
The role requires turning priorities into precise requirements, managing dependencies, and coordinating releases with CTO and product managers to support a complex, enterprise-grade service.
ABC Legal Services is proud to be the national leader in service of process. We are a team of 1000 and growing with offices in Los Angeles, Oklahoma City, Phoenix, Brooklyn, Chicago, Washington DC, and more. Seattle is our home and headquarters.
We've been successful in this unique business for over 30 years, and we continue to advance our technology and business processes to remain years ahead of what our competition is able to offer. Our focus is to expand our technology lead, acquire and integrate less efficient competitors, and tap into new segments through an integrated inbound marketing and sales approach.
ABC Legal is hiring a Technical Product Owner to own the backlog and the delivery sequence for part of our Service of Process platform, and to keep work moving cleanly across a large engineering organization.
ABC Legal is a tech-forward, tech-enabled legal services business: we use technology to power a core operational service, not the other way around. Your area is one or more of our Service of Process products: the mobile app process servers use in the field, the customer-facing web portal, the enterprise APIs our largest clients integrate with, and the proprietary platform that powers job assignment, routing, task management, and evidence chain.
This is a SAFe Product Owner role with a technical program management core. Business-facing Product Managers own customer and market discovery, positioning and launch. You take their priorities and turn them into requirements, sequenced backlogs and releases that engineering can build and operations can absorb. You own the backlog, the dependencies between teams, release quality and the post-release check that what shipped works.
You will report directly to our CTO and work closely with Engineering, Operations, and the business-facing Product Managers. We will teach you the domain. We are not going to teach you the craft: we expect you already know how to write precise requirements, run a scaled agile cadence and hold a date across teams you do not manage.
Most product roles are software all the way down. This one is not. Every job we run is a physical-world logistics problem, getting a real person to a real address at a time they will actually be there, wrapped in a legal evidentiary standard that decides whether the work counts at all.
The platform has to serve a distributed field workforce, demanding enterprise legal customers, an internal operations organization of hundreds, and a court system that changes its rules by county. A change in one system can produce a defective proof of service weeks later, in a different system, in front of a judge. Sequencing and dependencies are the job, not an afterthought.
We are also further into production AI than almost anyone in this industry: dozens of AI agents run live today across service validation, document handling, evidence review, and operational decision support. You will help decide where that belongs in the product, and where it does not.
Own the backlog for your area of the Service of Process platform. Depending on your background, that is likely to center on the enterprise side: the APIs and integrations our largest clients build against, and the platform behind job assignment, routing, task management, and evidence chain, with surface area across the customer web portal and field mobile app.
Take priorities from the business-facing Product Managers and turn them into crisp problem statements, requirements, success criteria and edge cases. Court rules vary by jurisdiction, and requirements must reflect that instead of discovering it in QA.
Break features into stories that fit an iteration. Accept or reject work against acceptance criteria and the Definition of Done.
Set and defend the priority order within your area: what gets built, what waits, and what we stop doing. Explain the reasoning to an engineer, an operations leader and the executive team in terms each cares about.
Plan and run your area through the SAFe cadence: iteration planning, quarterly PI Planning, system demos, and Inspect & Adapt.
Sequence work across the teams and systems it touches. A single change can touch the field mobile app, a document template and a rules store. Order the pieces so they land correctly, and hold the dependencies.
Name prerequisites before work starts, and catch collisions between initiatives while a fix is still a conversation and not a rebuild.
Maintain a rolling plan that survives contact with reality: sequenced, tied to business outcomes, and revised openly when the evidence changes.
Give the executive team a clear read on status, risk and trade-offs, including the bad news, early.
Work with engineering to keep current the picture of which systems a change to