Sr. Project Coordinator - Product Owner Job

Job Related Statistics

• Responsible for acting as Product Owner for larger, more complex projects with high value to the organization
• Job Duties/Responsibilities may include but not limited to:
• Responsible for maximizing the value of the product and the work of the Development Team
• Responsible for acting as Product Owner for larger, more complex projects with high value to the organization
• Responsible for creating, maintaining and prioritizing the Product Backlog according to business value for the life of the project
• Communicate Product Backlog priorities to the team.
• Act as the key decision-maker regarding what features the product will have
• Responsible for the vision of what is to be built, and conveying that vision to the team
• Assists with the elaboration of epics, themes and features into user stories that are small enough, or granular enough, to be achieved in a single sprint
• Responsible for conveying the vision and goals at the beginning of every sprint
• Work closely with key stakeholders throughout the organization
• Responsible for making decisions on release dates and content
• Represent the customer, interfacing and engaging with the customer
• Participate in Daily Scrum as needed
• Participate in Sprint Planning meetings, Reveals and Retrospectives
• Inspect the product progress at the end of every Sprint and accept or reject the work that has been done by the Development Team
• Act as the voice of the team, communicating status externally
• Be a good role model of Scrum values; understand the framework and the roles of each team member
• Be a champion for the agile community and help to further the community within the organization
• Employee is also responsible for performing other job duties as assigned by Client management from time to time.

BACKGROUND/EXPERIENCE:

Required Qualifications

• Four year Bachelor’s degree preferably in computer science, information systems, marketing, communications, engineering or related field
• 5+ years’ experience as a product manager
• 5+ years of experience leading a technical team while simultaneously managing multiple projects
• 3+ years of experience with the Agile methodology
• Product Owner certification (CSPO from Scrum Alliance)
• Demonstrated ability to communicate appropriately to ensure a team’s success
• Domain expert in business applications
• Strong accountability planning/organization, and teamwork
• Highly developed interpersonal skills to deal with sensitive, emotional or potentially controversial situations.
• Excellent oral and written communication skills
  
  

Top candidates will also possess these Qualifications

• Experience managing projects using Agile software tools such as Mingle, VSTS, JIRA, Team Services, Rally
• Experience working with onshore/offshore team model
• Demonstrated ability to empower teams
• Strong accountability, teamwork, and interpersonal skills, and communication skills
• Knowledge of SDLC and demonstrated experience employing SDLC in aspects of the project management process
• Background in Information Technology
• Good knowledge of Client policies, standards, procedures, and a broad understanding of Clients organization

Job description:

TECHNICAL PRODUCT OWNER
Experience: 4–6 Years | Role Type: Technical Product Ownership

Job Summary

• We are looking for a highly motivated Technical Product Owner with 4–6 years of experience in Agile product development and enterprise software delivery.
• The ideal candidate will collaborate with business stakeholders, architects, engineering teams, and customers to translate business needs into well-defined technical solutions.
• This role requires a strong understanding of Java-based backend services, cloud-native architectures on AWS, APIs, microservices, and system integrations.
• The Technical Product Owner will serve as the bridge between business requirements and technical implementation, ensuring that business features are decomposed into actionable technical features and user stories with sufficient service-level and component-level detail for efficient development and delivery.
  

Key Responsibilities

• Define and communicate the product vision, goals, roadmap, and desired business outcomes.
• Own and manage the product backlog, ensuring prioritization aligns with business objectives, architectural direction, delivery capacity, and technical dependencies.
• Gather, analyze, and document business, functional, technical, and non-functional requirements.
• Partner with business stakeholders, architects, and engineering teams to translate business capabilities into technical features and implementation-ready user stories.
• Decompose business features into technical features, enablers, backend services, integrations and platform capabilities.
• Create user stories that include business context, high-level service and component details, affected systems, component interactions, integration points, dependencies, API or event requirements, data considerations, and acceptance criteria.
• Understand and document backend service interactions, data flows, interface contracts, upstream and downstream dependencies, and integration requirements.
• Work closely with engineering teams to understand solution approaches for Java and Spring Boot microservices deployed on AWS.
• Collaborate with architects and developers to understand service contracts, REST API requirements, event-driven workflows, and integration patterns.
• Ensure user stories capture relevant non-functional expectations, including security, performance, scalability, availability, observability, error handling, resiliency, and supportability.
• Facilitate discussions between business stakeholders and technical teams to resolve functional and technical ambiguities.
• Evaluate technical trade-offs, implementation risks, dependencies, and sequencing considerations during backlog prioritization and release planning.
• Lead or actively participate in sprint planning, backlog refinement, sprint reviews, retrospectives, architecture discussions, and release planning.
• Ensure stories meet the Definition of Ready and provide timely clarifications throughout the sprint.
• Validate completed work against functional and technical acceptance criteria and approve user stories.
• Coordinate User Acceptance Testing, product demonstrations, release readiness, and product launches.
• Monitor product performance, operational feedback, adoption, and business impact to drive continuous improvement.
• Identify risks, blockers, and cross-team dependencies and work proactively with stakeholders to resolve them.
• Promote Agile best practices, engineering collaboration, and customer-centric product development.
  

Technical User Story Expectations

• User stories created or refined by the Technical Product Owner should include, where applicable:
• Business objective, user or system outcome, and measurable value.
• Affected Java services, AWS components, APIs, databases, queues, events, or integration endpoints at a high level.
• High-level service and component interactions, including upstream and downstream systems.
• API contract expectations, request and response behavior, validation rules, and error scenarios.
• Data requirements, data ownership, persistence needs, and key data-flow considerations.
• Security, access control, audit, privacy, performance, scalability, availability, resiliency, logging, monitoring, and alerting expectations.
• Technical dependencies, assumptions, constraints, risks, and sequencing requirements.
• Clear functional and technical acceptance criteria that enable development, testing, and validation.
  

Required Qualifications

• Bachelor's degree in Computer Science, Information Technology, Engineering, Business, or a related field.
• 4–6 years of experience as a Product Owner, Technical Product Owner, Business Analyst, or related product role in software delivery.
• Strong understanding of Agile, Scrum, and SAFe methodologies.
• Experience managing product backlogs using Azure DevOps, Jira, Rally, or similar tools.
• Proven ability to translate business features into technical features, user stories, and clear acceptance criteria.
• Strong understanding of backend application architecture, microservices, REST APIs, service-oriented architecture, and distributed systems.
• Experience working with engineering teams developing Java and Spring Boot backend services on AWS.
• Ability to understand high-level solution architecture and convert business requirements into implementable technical deliverables.
• Ability to analyze system interactions, data models, service dependencies, and integration requirements.
• Familiarity with cloud-native development, CI/CD, DevOps, automated testing, observability, and cloud deployment models.
• Strong stakeholder management, communication, facilitation, analytical, and problem-solving skills.
• Ability to balance business priorities, customer needs, technical constraints, risks, and delivery timelines.
  

Preferred Qualifications

• Certified Scrum Product Owner (CSPO), Professional Scrum Product Owner (PSPO), or SAFe Product Owner/Product Manager certification.
• Working knowledge of AWS services such as API Gateway, Lambda, ECS or EKS, SQS, SNS, DynamoDB, RDS, Step Functions, CloudWatch, and IAM.
• Experience working in Java and Spring Boot microservices environments.
• Ability to read and understand technical design documents, API specifications, data-flow diagrams, UML diagrams, and architecture diagrams.
• Experience with event-driven architecture, API-led integrations, and enterprise integration patterns.
• Experience supporting platform modernization, cloud migration, digital transformation, or enterprise application initiatives.
• Experience with data-driven decision-making and product analytics.
  

Key Skills

• Technical Product Ownership and Product Backlog Management
• Business-to-Technical Feature Decomposition
• Java and Spring Boot Fundamentals
• AWS Cloud Architecture and Cloud-Native Development
• Microservices, REST APIs, and System Integrations
• Service and Component Modeling
• Event-Driven Architecture
• Technical User Story and Acceptance Criteria Creation
• Non-Functional Requirements Definition
• Agile, Scrum, and SAFe Delivery
• Azure DevOps, Jira, and Confluence
• Stakeholder Management, Communication, and Negotiation
• Risk, Dependency, and Release Management
• Customer-Centric Product Thinking
• Success Metrics
• Timely delivery of prioritized features and achievement of sprint and release goals.
• Quality, completeness, and readiness of technical features and user stories.
• Percentage of stories meeting the Definition of Ready before sprint planning.
• Reduction in engineering clarifications, requirement ambiguity, rework, and requirement-related defects.
• Effective decomposition of business capabilities into implementable technical work.
• Improved delivery predictability through clear dependencies, technical context, and acceptance criteria.
• Stakeholder satisfaction, product adoption, operational performance, and measurable business impact.

Job Related Statistics

• Responsible for acting as Product Owner for larger, more complex projects with high value to the organization
• Job Duties/Responsibilities may include but not limited to:
• Responsible for maximizing the value of the product and the work of the Development Team
• Responsible for acting as Product Owner for larger, more complex projects with high value to the organization
• Responsible for creating, maintaining and prioritizing the Product Backlog according to business value for the life of the project
• Communicate Product Backlog priorities to the team.
• Act as the key decision-maker regarding what features the product will have
• Responsible for the vision of what is to be built, and conveying that vision to the team
• Assists with the elaboration of epics, themes and features into user stories that are small enough, or granular enough, to be achieved in a single sprint
• Responsible for conveying the vision and goals at the beginning of every sprint
• Work closely with key stakeholders throughout the organization
• Responsible for making decisions on release dates and content
• Represent the customer, interfacing and engaging with the customer
• Participate in Daily Scrum as needed
• Participate in Sprint Planning meetings, Reveals and Retrospectives
• Inspect the product progress at the end of every Sprint and accept or reject the work that has been done by the Development Team
• Act as the voice of the team, communicating status externally
• Be a good role model of Scrum values; understand the framework and the roles of each team member
• Be a champion for the agile community and help to further the community within the organization
• Employee is also responsible for performing other job duties as assigned by Client management from time to time.

BACKGROUND/EXPERIENCE:

Required Qualifications

• Four year Bachelor’s degree preferably in computer science, information systems, marketing, communications, engineering or related field
• 5+ years’ experience as a product manager
• 5+ years of experience leading a technical team while simultaneously managing multiple projects
• 3+ years of experience with the Agile methodology
• Product Owner certification (CSPO from Scrum Alliance)
• Demonstrated ability to communicate appropriately to ensure a team’s success
• Domain expert in business applications
• Strong accountability planning/organization, and teamwork
• Highly developed interpersonal skills to deal with sensitive, emotional or potentially controversial situations.
• Excellent oral and written communication skills
  
  

Top candidates will also possess these Qualifications

• Experience managing projects using Agile software tools such as Mingle, VSTS, JIRA, Team Services, Rally
• Experience working with onshore/offshore team model
• Demonstrated ability to empower teams
• Strong accountability, teamwork, and interpersonal skills, and communication skills
• Knowledge of SDLC and demonstrated experience employing SDLC in aspects of the project management process
• Background in Information Technology
• Good knowledge of Client policies, standards, procedures, and a broad understanding of Clients organization