Product Manager II - API Platform

What You'll Do:

• Backlog & Delivery Execution: Own day-to-day backlog management and sprint coordination for assigned workstreams, ensuring engineering always has a clear, prioritized queue of well-scoped issues with acceptance criteria — so nothing ships ambiguous and nothing stalls waiting on product.
  

• Customer & Stakeholder Translation: Synthesize feedback from beta customers, partners, and internal teams into actionable, well-scoped issues that connect user pain to product change. Escalate architectural or strategic decisions to the Senior PM with context, not just questions.

• Cross-Functional Coordination: Lead standups, refinements, and implementation syncs across Engineering, Design, Support, and Go-to-Market — producing clear outcomes and owners from every meeting so momentum doesn't depend on follow-up threads.

• Product Quality & Acceptance: Perform product acceptance testing alongside QA before releases ship, ensuring what we deliver matches what we spec'd and what customers actually need.

• Specs & Documentation: Draft and maintain product specifications, business rules, user flows, and use cases that serve as the source of truth for features in development — plus contribute to release notes and internal enablement materials that keep the rest of the org informed.

• Beta Program & Partner Enablement: Support the management of external beta programs and partner relationships, synthesizing feedback loops into prioritized action so early adopters see their input reflected in the product.

• Launch Readiness: Coordinate cross-functionally to ensure smooth product launches — the right teams have the right context at the right time, and nothing surprises Support or Sales on release day.

What You Need:

• 2–5 years of product management or closely adjacent experience (technical PM, solutions engineering, product ops, technical program management) in SaaS.

• Comfortable with technical concepts: APIs, OAuth, webhooks, data pipelines, or similar. You don't need to write code, but you need to read a ticket from engineering and understand what's being built.

• Hands-on experience using AI tools (e.g., Claude, Cursor, ChatGPT) to build coded prototypes, automate processes, or develop internal skills and workflows. You don't need to be an engineer, but you should be using AI to extend what you can do.

• Experience working within Agile/Scrum delivery frameworks and managing a product backlog.

• Strong written communication — you can draft a clear spec, a concise status update, and a customer-facing release note without heavy editing.

• Demonstrated ability to independently run meetings, synthesize competing inputs, and drive to decisions.

• Analytical and data-informed — you use evidence (customer feedback, usage data, support trends) to support prioritization, not just intuition.

• Comfortable operating in ambiguity and shifting priorities while keeping business outcomes in focus.

Nice To Have:

• Experience in Legal Tech, Law Firm Operations, or a regulated industry where compliance and data governance matter.

• Familiarity with workflow automation platforms or integration tooling.

• You've shipped something where the user was a developer or integrator — and you understand how that changes the way you write specs, define success, and gather feedback.

• Experience supporting or participating in beta programs, customer advisory boards, or partner onboarding.

• B.S. or M.S. in business, engineering, computer science, information systems, or a related field — or equivalent direct work experience.

What Success Looks Like:

• Within 30 days: Comfortable navigating the LOIS platform, API architecture, and team tooling. Sitting in on all key ceremonies and beginning to independently drive at least one workstream.

• Within 90 days: Independently running meetings, triaging beta feedback, and filing well-scoped issues without review. Engineering teammates trust you to bring them clear requirements.

• Within 6 months: Owning a product area (e.g., LOIS Workflows) with increasing autonomy over roadmap input, stakeholder communication, and launch coordination.