Product Manager
This is not a role where every project arrives with a defined product, backlog, technical architecture, or implementation plan.
What to know going in
This is not a role where every project arrives with a defined product, backlog, technical architecture, or implementation plan.
Some workstreams will begin with questions like: What problem are we actually trying to solve? Which HHS Divisions need this capability? Should this be a shared enterprise service or a Division-specific solution? What already exists? What should we standardize? What should we build? And what should happen first?
Others will involve existing applications that already have users and stakeholders and need to move quickly through feature development, integration, launch, adoption, and ongoing improvement.
You’ll need to be comfortable operating at both levels.
At the enterprise level, you may work with architects, engineers, platform owners, and HHS stakeholders to understand how platforms; identify opportunities for shared services and tenant integration; define priorities and adoption strategies; and translate technical possibilities and constraints into decisions leaders can act on.
At the product level, you’ll work closely with designers, researchers, and engineers to turn user and operational needs into working software. Current and emerging application work may include enterprise mentoring, security tooling and analytics, employee onboarding, and other internal digital services.
Across both areas, speed matters. You should be comfortable learning enough to act, showing early work, testing assumptions, and refining the approach as the team learns rather than waiting for perfect information before moving forward.
What you’ll do
What we’re looking for
Basic qualifications
Posted November 1, 2026