Senior Product Manager - Audio Interface Hardware & Software

Department: Product Management   

Reports to: Director of Product Management (Hardware)

Location: Scotts Valley, CA or Remote (United States)

We are hiring for a Senior Product Manager.  This is a dual-mandate role, and both halves are equally weighted. Roughly half your time is spent as the Product Owner of a dedicated Agile software team — you own its backlog, write its specifications, and are accountable for what it ships and when. The other half is spent as the Senior Product Manager for a line of professional audio interface hardware — you own the roadmap, the business case, and the launch.

These are not two jobs bolted together. The software team you run exists largely to support the hardware you define, so the person in this seat is the single point where hardware requirements become software commitments with real dates attached. We are looking for someone who is as comfortable ranking a sprint backlog and reproducing a driver bug on a nightly build as they are presenting a BOM cost trade-off to leadership.

We are open to candidates in the United States.  Candidates located in commutable distance to our HQ, Scotts Valley, CA are a plus.

Responsibilities

Product Owner for an Agile software team (~50%)

• Backlog and sprint ownership — You are the single accountable owner of one scrum team's backlog: you rank it, keep it groomed, and decide what enters a sprint. Ambiguous or under-specified work stops with you, not the engineers. You run the product side of two-week sprints — planning, mid-sprint review, refinement, demo — and partner with the Scrum Master and Engineering Manager on capacity and sprint goals that survive contact with parallel initiatives.
• Specifications and acceptance criteria — Translate hardware and business requirements into written software specifications detailed enough for an engineer to build from and QA to test against, decomposed into initiatives, epics, and sprint-ready stories. Every spec goes to the software architect and QA leads before development starts, and every story has agreed-upon acceptance criteria. This is a requirement, not a nice-to-have.
• Software delivery schedules tied to hardware milestones — Given a hardware ship date, work with the Project Manager to determine what part of the software stack must deliver which functionality and by when, across application, driver, firmware, and DSP disciplines. Publish and defend feature-complete, beta, release-candidate, and release-to-marketing dates.
• Bug triage and release management — Own defect priority: write reproducible bug reports yourself, decide what blocks a beta or release, and make the go/no-go call with QA and engineering. Own the release plan and its artifacts — release notes, known-issues lists, compatibility test matrices, and documentation handoffs to Customer Care and Technical Publications.
• Prioritization and instrumentation — Maintain an explicit, defensible method (e.g. WSJF) for weighing stability, performance, tech debt, and customer-care-driven fixes against new feature work. Define the analytics events and reporting needed to know whether a feature is actually being adopted, act on what the data shows, and work with the Data team to keep that pipeline scalable for future releases.

Senior Product Manager, audio interface hardware (~50%)

• Product requirements — Author complete requirement sets spanning hardware, mechanical, electrical and audio specification, connectivity, driver support, software behavior, packaging, and documentation.
• Supply, lifecycle, and vendor management — Track component lifecycle and last-time-buy exposure, drive cost-down opportunities, and plan transitions before availability forces them. Manage the product relationship with silicon and driver vendors, technology partners, and contract manufacturers, including requirements, schedules, and license terms.
• Customer discovery and go-to-market — Run research with working professionals and enthusiasts, and own the activation and onboarding funnel — where new users get lost or disengage, and how you fix it. Partner with commercial, marketing, sales, and operations on SKU structure, pricing, bundling, launch readiness, channel and inventory planning, and EOL execution.

Qualifications

• Demonstrated Product Owner experience on a scrum team — not "worked with Agile teams," but personally owned a backlog, has written the stories, run the ceremonies, and been accountable for the release. Expect to be asked for specifics.
• Technical fluency sufficient to hold your own with systems engineers: operating-system-level device drivers, firmware, installers and software deployment, high-speed c