Job description

A leading organization is seeking a Project Manager to coordinate and deliver automation initiatives supporting HEDIS workflows. The Project Manager will oversee an automation backlog, coordinate work across multiple teams, maintain scope discipline, and provide clear visibility into project progress and budget tracking.

Responsibilities

• Manage execution of the automation backlog supporting HEDIS workflows.
• Coordinate automation efforts across multiple business and technical workstreams.
• Maintain project scope and help ensure work remains aligned with established priorities.
• Manage stakeholder communication and coordination throughout project delivery.
• Track project progress, deliverables, dependencies, and budgets.
• Use Jira and Confluence to organize project information and support execution.
• Partner with engineering and data science teams on automation initiatives.
• Help advance reusable automation capabilities that reduce manual effort and support future HEDIS needs.
• Coordinate priorities across teams to support efficient delivery without adding unnecessary workload to existing resources.

Required experience and skills

• Project management experience supporting automation initiatives
• Experience managing cross-functional or cross-stream projects
• Strong scope management and stakeholder management skills
• Project tracking and budget tracking experience
• Experience with Jira and Confluence
• Experience collaborating with technical teams, including engineering and data science
• Experience executing or coordinating automation backlogs
• Experience supporting HEDIS-related initiatives

FAQs

1. What does a Project Manager do?

A Project Manager plans, coordinates, and oversees projects from initiation through completion. The role involves managing scope, timelines, resources, risks, dependencies, budgets, and stakeholder communication to keep delivery aligned with project objectives.

2. How does a Project Manager create and manage a project plan?

The Project Manager breaks project objectives into deliverables, milestones, tasks, dependencies, and ownership. The plan is then tracked and updated as requirements, timelines, resources, or risks change throughout the project lifecycle.

3. How does a Project Manager manage project scope?

Scope is established by documenting objectives, deliverables, requirements, assumptions, and constraints at the beginning of the project. When new requests arise, the Project Manager evaluates their impact on schedule, budget, resources, and priorities before incorporating approved changes.

4. How does a Project Manager track project progress?

Project Managers use schedules, milestone tracking, status reports, dashboards, action logs, and project management tools to monitor progress. They compare actual delivery against planned timelines and address delays or dependencies before they significantly affect project outcomes.

5. How does a Project Manager manage project risks and issues?

The Project Manager identifies potential risks, assesses their likelihood and impact, and develops mitigation or contingency plans. Active issues are tracked with clear owners, deadlines, and escalation paths until they are resolved.

6. Which tools are commonly used by Project Managers?

Project Managers may use tools such as Jira, Asana, Monday.com, Smartsheet, Microsoft Project, Trello, Excel, or similar platforms. Communication and documentation may also involve tools such as Microsoft Teams, Slack, SharePoint, or Confluence.

7. How does a Project Manager coordinate cross-functional teams?

The Project Manager establishes responsibilities, communication routines, milestones, and dependencies across teams. They facilitate meetings, remove delivery blockers, coordinate handoffs, and ensure that teams have the information needed to complete their work.

8. How does a Project Manager communicate with stakeholders?

Project Managers provide clear updates on progress, milestones, risks, decisions, budget, and upcoming activities. Communication is adapted to the audience, with executives typically receiving concise outcome-focused summaries while delivery teams receive more detailed operational information.