Product Manager

Location: Remote (select states)
Candidates must currently reside in one of the following states:
Alabama, Florida, Georgia, Michigan, Mississippi, Missouri, North Carolina, Oklahoma, Tennessee, Texas, or Virginia.

Position Overview

The Product Manager owns end-to-end prioritization, scoping, and delivery for a core area of the company's platform. This role sets the standard for what "ready for engineering" means, drives the backlog from ambiguous business requests to buildable, well-defined work, and keeps engineering, client services, and business stakeholders genuinely aligned rather than working around each other. The role partners closely with engineering, client services, marketing, sales, and operations to identify priorities, scope solutions, and keep delivery moving without sacrificing quality.

Key Responsibilities

Product & Conversion Ownership

• Own backlog health and refinement — tickets arrive at planning with clear acceptance criteria, right-sized scope, and no ambiguity left for the room to untangle live.
• Prioritize the team backlog by balancing client/business requests against technical debt and platform health, and make tradeoffs explicit to stakeholders rather than implicit.
• Partner with client services and business stakeholders in analyzing requests, client feedback, and operational pain points to identify and prioritize opportunities.
• Track outstanding requests proactively — nothing sits blocked on an external party without a named owner and a follow-up cadence.

Requirements & Specification

• Translate business ideas into clear technical requirements — most requests arrive as a business problem, not a deliverable, and it's in this role to determine what's actually needed and who else needs to weigh in.
• Write and maintain requirements, acceptance criteria, and edge cases precise enough that engineering can build against them without re-litigating scope in every meeting.
• Support engineering by clarifying open questions, unblocking ambiguous requirements, and making scope decisions when tradeoffs arise mid-build.

Process & Standards

• Define and continuously improve how refinement, sprint planning, and stakeholder acceptance work for the team, fitting the team's size and delivery cadence.
• Maintain consistency in how tickets are written, scoped, and tracked across the backlog, so quality doesn't depend on who happened to write a given ticket.
• Partner with engineering to keep documentation and decision records accurate as systems evolve, so past decisions don't need to be re-derived from scratch.

Cross-Functional Collaboration

• Collaborate with leadership and stakeholders across engineering, client services, marketing, sales, and operations to align priorities with business rules, compliance needs, and support workflows.
• Facilitate cross-functional decisions that don't belong to any single team — surfacing who needs to weigh in (legal/compliance, engineering feasibility, business priority) before a direction is chosen.
• Represent the user/client perspective in cross-functional discussions, surfacing risks and identifying opportunities to improve product and client experience.

Scope & Leadership

• Serve as a primary point of contact and decision-maker for prioritization and scoping questions across the team.
• Operate as a peer and partner to engineering — holding the line on scope and quality while staying genuinely collaborative when priorities shift or new information surfaces.
• Champion a culture of clear communication and evidence-based decision making, bringing data and stakeholder input into planning rather than relying on whoever asked most recently or loudest.

Additional Responsibilities 

• Perform other related duties, ad hoc tasks, and special projects as assigned to support departmental and organizational goals.

Required Qualifications

• 3+ years of product management experience, ideally in a B2B SaaS, CRM, or insurance/fintech environment.
• Demonstrated ability to run backlog refinement and sprint planning with engineering teams.
• Strong written communication — able to turn a messy conversation into a clean, unambiguous story.
• Experience working directly with client-facing teams (sales, client services, support) on external integration or feature requests.
• Familiarity with Jira or a comparable tool for backlog/sprint management.
• Comfortable pushing back on both engineering and stakeholders when scope or requirements aren't ready.

Applicant information collected during the hiring process will be used solely to assess qualifications, verify eligibility for employment, and make hiring decisions. Applicant data will be stored securely and retained only for as long as necessary to complete the recruitment process and meet legal, regulatory, and record‑keeping requirements, after which it will be deleted or anonymized in accordance with our data retention policies.