Product Manager

Audicus•New York, NY

7d•$100,000 - $130,000•Hybrid

About The Position

You'll own how product and engineering work gets planned, committed, and delivered at Audicus. Requests come in from every corner of the business — marketing, sales, customer experience, operations, our clinical team, B2B partners. Your job is to turn that stream into an organized, committed roadmap: scope the requests, break them into the tickets that actually get them built, sequence the work into sprints, and hold everyone — stakeholders and engineers alike — to the plan. When priorities genuinely shift, you make the trade-offs visible so decisions get made with eyes open rather than scope creeping in sideways. This is a delivery and execution role, not a product-strategy role — at least to start. You'll work directly with the COO, who currently leads the product function, and as our product organization matures there is real room to grow into roadmap ownership and strategy — shaping what we build, not just how it gets delivered. But the first job is to be the person who makes the machine run: the most organized person in the building, the one who sees the shortest path from A to B and keeps twelve workstreams moving without dropping any of them.

Requirements

2–4+ years in product management, technical program management, project management, or a comparable execution-heavy role — ideally somewhere with real operational complexity.
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).

Nice To Haves

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.

Responsibilities

Run product intake: work with stakeholders across our DTC, B2B, marketing, and operations teams 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.
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.