The posting
THE ROLE You'll own the path from "we need this" to "it shipped" at Audicus — defining what gets built, and then running the machine that builds it.
Both halves are the job from day one. Requests come in from every corner of the business — marketing, sales, customer experience, operations, our clinical team, B2B partners — and they arrive as problems and wishes, not specs. Your first job is to turn them into well-defined work: ask the questions that surface what's actually needed, figure out the best path from Point A to Point B, and decide what the tickets should say before anyone writes code.
Your second job is to deliver what you've defined: break the work into epics and tickets, sequence it into sprints, hold everyone — stakeholders and engineers alike — to the plan, and make trade-offs visible when priorities genuinely shift, so decisions get made with eyes open rather than scope creeping in sideways. We need someone who finds satisfaction in the follow-through, not just the framing.
The year ahead includes new product initiatives across our consumer and B2B lines, so there's real definition work from the start. You'll work directly with the COO, who leads the product function and owns the roadmap — you'll be the person who makes each item on it concrete, built, and shipped.
What You'll Do Run product intake: work with stakeholders across our DTC, retail, and B2B lines to capture requests, ask the questions that turn a wish into a scoped piece of work, and slot it into the roadmap at the right level of commitment — from major projects down to keep-the-lights-on maintenance. Define scope: for each initiative, work out requirements with stakeholders, pressure-test the approach with engineering, and settle the best path from A to B — what we're building, what we're explicitly not, and in what order. Decompose scoped projects into epics and child tickets in Jira, with owners, estimates, review steps, and dates the team commits to. Design and run the sprint cadence across our engineering team (mobile, web, backend). Keep the timeline honest: track delivery against committed baselines, surface slips early, unblock the team, and escalate when needed. Run our change-request process so mid-flight scope changes carry a visible cost in time and resources, and stakeholders make informed trade-offs instead of informal asks. Own the planning system itself — Jira plus our internal capacity and timeline dashboards — and keep it the single source of truth for project status. Report on the numbers that matter: on-time delivery, sprint predictability, capacity utilization. Give leadership a status view they trust without having to ask. Partner with the COO and our product designer on new product initiatives — discovery, requirements, and development plans for the things we're building next.
What Success Looks Like Within six months: stakeholders know where their requests stand without chasing anyone, engineers work from tickets that are scoped before the sprint starts, committed dates hold or slip visibly with a reason attached, leadership reads project status from one view — and at least one meaningful initiative has gone from loosely-stated need to shipped product with your fingerprints on its definition.
What We're Looking For 3–5+ years in product management or a comparable role — including real experience taking a product from concept to launch, not only operating a process someone else defined. Scoping judgment: you can take a vague ask, figure out what's actually needed, and draw the line between what gets built now, later, and never — and defend that line. Exceptional organization. You're the person who makes chaos legible, and it bothers you when a plan lives in someone's head instead of a system. You learn systems fast. You should expect to be fluent in our Jira setup, data pipelines, and internal tooling within weeks, not months. Sequencing instinct: you see dependencies and the shortest path from A to B, and you notice when a plan has one hidden in it. Comfortable holding the line with senior stakeholders. Saying "yes, and here's what it costs" is the job. A clear, concise writer — tickets, requirements, and status updates that people actually read. Technical fluency without an engineering background: you can follow an architecture conversation, read a data model, and earn engineers' trust that your tickets make sense. You don't need to have written production code. Working knowledge of Jira (or a comparable tool at depth). Bonus: comfortable in spreadsheets and light scripting with AI tools like Claude. You don't need to write code yourself — you need to know how to get it written and verify it works.
Salary Range: $120k-150k - commensurate with experience and location
Location: NY, NY (Hybrid or US remote)
Benefits: Medical, Dental, Vision Insurance (Aetna), 401K, Flexible PTO policy, Commuter Benefits, Additional Wellness Perks, Parental Leave Policy
FLSA Status: Exempt – This position is not eligible for overtime pay and is expected to fulfill the responsibilities of the role regardless of hours worked.
