Software Product Manager

Job description

Job responsibilities

• Own the EW Mission Applications product roadmap: what is committed, what is queued, what we declined and why — published and current enough that program management and engineering leads both plan against it
• Run a single intake path for product requirements from programs, customers, partners, and internal teams, and give every request a scoped, sized answer: accept, defer, or decline, with a reason
• Define operator capabilities before design and engineering start — the problem, the workflow, and the acceptance criteria that QA builds integration coverage against
• Deconflict competing program demands on shared engineering teams using a written, defensible prioritization framework
• Represent EW Mission Applications in the recurring device API review: bring the integration needs, justify the priority, agree the build order with embedded engineering, and track requests through to delivery
• Partner with UI design on operator workflows and with QA on test coverage, owning the requirement behind both
• Turn recurring field issues from our mission software engineering team into roadmap items and test coverage on a standing cadence
• Track delivery commitments against actuals and publish the results, so our estimates improve and our release commitments earn credibility

Job requirements

• 5+ years in software product management, technical product ownership, or a closely related role
• Direct ownership of a product roadmap, including the authority and the track record to decline work
• Demonstrated ability to write requirements and acceptance criteria that engineering and test executed against
• Strong written and verbal communication skills — you'll be writing the roadmap, running prioritization calls, and briefing leadership
• Experience owning a software product surface that depended on hardware or firmware built by a team you did not control
• Experience deconflicting priorities across concurrent customers or programs competing for the same engineering capacity
• Ability to read and navigate codebases and API surfaces: you don't need to write production code, but you need to understand what is changing and what it costs
• Comfortable operating with incomplete information and requirements that move