Senior Product Owner - Software Development

Leidos

22h

About The Position

The Defense Sector at Leidos is seeking a Senior Product Owner to work closely with software development teams, customers, and other product stakeholders to define and deliver high-quality software capabilities. This role is responsible for translating customer needs into clear, actionable product requirements, including user stories, rules, and acceptance criteria that enable efficient development and predictable software behavior. The ideal candidate combines strong communication skills, structured logical thinking, and experience working in Agile software development environments. This position requires someone who can operate effectively between technical teams and external stakeholders—balancing priorities, managing expectations, and ensuring that product requirements are clearly defined and understood. This role often requires navigating competing priorities and making difficult trade-off decisions to ensure the most valuable capabilities are delivered efficiently.

Requirements

US Citizen with at least an active Secret security clearance is required to be considered.
A Bachelor’s degree with 12+ years of experience or a Master’s degree with 10+ years of experience. Additional experience may be considered in lieu of a degree.
Exceptional written and verbal communication skills.
Ability to write clear, structured product requirements and logical rules.
Strong analytical mindset capable of defining system behavior and edge cases.
Experience working with software development teams in Agile environments.
Familiarity with JIRA, Confluence, sprint planning, and backlog management.
Understanding of the Product Owner role in Agile workflows.
Strong organizational skills with the ability to manage multiple initiatives simultaneously.
Comfortable operating in fast-moving environments requiring frequent context switching.
Demonstrated ability to take ownership of problems and drive them to resolution.

Nice To Haves

Prior experience working with the U.S. military, preferably the U.S. Air Force.
Familiarity with operational or command-and-control systems.
Experience with the C2IMERA application.
While this is not a software engineering role, technical familiarity is highly beneficial.
Experience with or exposure to: Git or source control systems Model-based systems engineering tools (PlantUML or similar) Behavior-driven development frameworks such as Gherkin or Cucumber API-based software architectures Microservices and distributed systems Relational databases and data modeling Interface definition and system integration documentation
Logical, structured thinking
Attention to detail
Strong ownership mentality
Ability to mediate between stakeholders
Comfort being the decision maker when tradeoffs are required
Professional demeanor when interacting with customers and leadership

Responsibilities

Translate customer needs and operational concepts into well-defined user stories, rules, and acceptance criteria.
Develop clear requirement logic using structured rules and defined system behavior, ensuring minimal ambiguity.
Identify and document expected behavior for edge cases and boundary conditions to prevent gaps in system behavior.
Maintain and prioritize product backlogs across multiple epics and feature areas.
Work with development teams to refine stories and ensure they are ready for sprint planning.
Serve as the primary interface between customers, product leadership, and development teams.
Communicate requirements clearly in both written and verbal form.
Facilitate conversations between stakeholders when priorities or expectations conflict.
Manage trade-offs between customer requests and technical constraints, working to find the most effective solution.
Participate in Agile ceremonies including backlog refinement, sprint planning, sprint reviews, and retrospectives.
Maintain artifacts and documentation in JIRA and Confluence.
Ensure development teams have the information necessary to deliver high-quality work during each sprint.
Coordinate across multiple epics and development efforts simultaneously.
Manage frequent context switching across product areas and priorities.
Support development teams before, during, and after implementation to ensure requirements remain clear and achievable.