Project Manager
Endava · United States · 3 wk ago
RemoteRemoteInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role? The posting includes "Technology is our how..." intro, then "Job Description Role Overview". We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only if posting has real specific content. Let's parse.
Content:
- Intro paragraph: "Technology is our how...". That's about the company, could be "About the role"? Actually "About the role" is more about the role description. The intro is about company mission. Could be considered "About the role"? Might be okay. But we need to decide sections.
We have:
- Role Overview: description of Project Manager responsibilities (defining objectives, etc.) This could be "About the role" or "Responsibilities". The posting then has "Key Responsibilities" with bullet points (though not bullet list but sentences). We need to extract list items for
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only if posting has real specific content. Let's parse.
Content:
- Intro paragraph: "Technology is our how...". That's about the company, could be "About the role"? Actually "About the role" is more about the role description. The intro is about company mission. Could be considered "About the role"? Might be okay. But we need to decide sections.
We have:
- Role Overview: description of Project Manager responsibilities (defining objectives, etc.) This could be "About the role" or "Responsibilities". The posting then has "Key Responsibilities" with bullet points (though not bullet list but sentences). We need to extract list items for - . The responsibilities are described in paragraphs with colon headings: "Project Leadership & Planning:", "Execution & Management:", "Communication & Stakeholder Management:", "Risk & Issue Management:". Each contains multiple sentences. We can break each sentence into list items? The instruction: Use
- for any list of duties/requirements/benefits. So we should treat each duty as a list item. We can split by sentences or by semicolons. Better to capture each bullet-like duty.
Let's extract duties:
From "Project Leadership & Planning:":
- Lead, plan, schedule, track, and manage project deliverables, goals, and milestones for PATH workstreams.
- Create detailed work plans identifying all necessary activities, resources (time, money, equipment), and objectives.
- Develop and communicate project scope, timeline, resource requirements, and assumptions.
- Map complex dependencies across workstreams (e.g., clinical workflows, billing, offline capabilities) to ensure alignment.
From "Execution & Management:":
- Provide day-to-day direction and oversight for project teams.
- Monitor progress against goals and adjust plans or resources to meet customer and clinical needs.
- Manage project budgets, track expenses, and monitor resource utilization.
- Implement review and quality assurance procedures to ensure successful execution.
- Identify and track tasks to completion, ensuring blockers are resolved.
- Create and execute project plans, monitoring timelines and resource allocation.
From "Communication & Stakeholder Management:":
- Coordinate clear communication with all stakeholders impacted by the project's scope, budget, risk, and resources.
- Proactively report on project status (metrics, scope, schedule) to leadership and team members.
From "Risk & Issue Management:":
- Develop strategies for risk mitigation and create contingency plans.
- Identify, resolve, and escalate functional, quality, and timeline issues as they arise.
Now Qualifications section: "Qualifications Minimum of 3-5 years of project management experience, with a preference for software or clinical application projects. Proficiency in project management tools, including MS Project. Intermediate to advanced skills in MS Word, Excel, PowerPoint, and Outlook. Experience with JIRA, Confluence, and Teams. Certifications: A Project Management Professional (PMP) is preferred. Education: High school diploma or GED required; Bachelor’s degree preferred"
We can split into list items for requirements.
Also "Additional Information" includes benefits: "Discover some of the global benefits that empower our people to become the best version of themselves:" then categories: Finance, Career Development, Learning Opportunities, Work-Life Balance, Health, Community. Each with list items separated by semicolons. Also "Additional Employee Requirements" includes various physical requirements. Also "USA Benefits (Full time roles only...)" includes specific US benefits.
We need Benefits section only if posting actually states them. It does. So we should create Benefits section with list items. Should we separate US benefits? Could combine but maybe separate? The instruction: Prefer a few substantive sections over many thin ones. So we can have one Benefits section covering all benefits mentioned (global and USA). But we need to ensure we don't include filler like "commensurate with experience". Not present.
We also have Pay and Schedule sections: Not explicitly stated. There's no mention of salary numbers or schedule specifics. So we should NOT create Pay or Schedule sections.
We also have Skills? Could be derived from qualifications but we have Qualifications section. Could also have Skills section separate? The instruction: Use headings for Skills if present. The posting mentions proficiency in tools etc. That could be skills. But we already have Qualifications covering experience, certifications, education. Skills could be separate: proficiency in MS Project, MS Office, JIRA, Confluence, Teams. However we can incorporate into Qualifications or Requirements. To keep few sections, we can have Qualifications (includes experience, certifications, education) and maybe Skills separate? But we can also treat those as Requirements. The heading "Requirements" is allowed. We could put all requirements (experience, tools, certifications, education) under Requirements. Then we could have Skills maybe not needed. Let's decide: Use Requirements for experience, tools, certifications, education. Use Skills maybe for soft skills? Not present. So we skip Skills.
We also need About the role: Could be the introductory paragraph plus Role Overview. Let's create About the role section with prose (
) summarizing the role overview. But we must not repeat job title. We'll include the description: "The Project Manager will define project objectives aligned with current ways of working, oversee quality control throughout the project lifecycle, manages impacts of dependency systems, and ensure clear communication with all stakeholders to support this mission-critical clinical data repository." That's from Role Overview. Also we could include the introductory company description? Might be considered About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put the role overview there.
Thus sections:
About the role
The Project Manager will define project objectives aligned with current ways of working, oversee quality control throughout the project lifecycle, manages impacts of dependency systems, and ensure clear communication with all stakeholders to support this mission-critical clinical data repository.
Then Responsibilities: Responsibilities
with - items as extracted.
Then Requirements:
Requirements
with - items: 3-5 years project management experience, preference for software/clinical; proficiency in MS Project; intermediate to advanced skills in MS Word, Excel, PowerPoint, Outlook; experience with JIRA, Confluence, Teams; PMP certification preferred; High school diploma/GED required; Bachelor's degree preferred.
We could also include "Ability to go into corporate or client offices..." etc under Additional Employee Requirements. Those are also requirements (physical). Should we include them? They are requirements. Could add to Requirements list. But they are more about physical demands. Might be okay to include.
But we must not create sections with filler. So we can include them as list items under Requirements.
Now Benefits:
Benefits
with - items from global benefits and USA benefits.
Let's extract benefits:
Finance: Competitive salary package, share plan, company performance bonuses, value-based recognition awards, referral bonus;
Career Development: Career coaching, global career opportunities, non-linear career paths, internal development programmes for management and technical leadership;
Learning Opportunities: Complex projects, rotations, internal tech communities, training, certifications, coaching, online learning platforms subscriptions, pass-it-on sessions, workshops, conferences;
Work-Life Balance: Hybrid work and flexible working hours, employee assistance programme;
Health: Global internal wellbeing programme, access to wellbeing apps;
Community: Global internal tech communities, hobby clubs and interest groups, inclusion and diversity programmes, events and celebrations.
USA Benefits: Robust healthcare and benefits including Medical, Dental, vision, Disability coverage, and various other benefit options; Flexible Spending Accounts (Medical, Transit, and Dependent Care); Employer Paid Life Insurance and AD&D Coverages; Health Savings account paired with our low-cost High Deductible Medical Plan; 401(k) Safe Harbor Retirement plan with employer match with immediately vest.
We need to split each item into list items. Could keep each benefit as separate list item.
Now we must not include boilerplate like EEO etc. The posting includes EEO statements at end: "At Endava, we’re committed to creating an open, inclusive, and respectful environment..." etc. That's boilerplate; we should remove.
Also remove "Additional Information" heading etc.
Now produce HTML fragment.
Check for any repeated content: Ensure we preserve all substantive information. Did we miss anything? The "Additional Employee Requirements" includes many physical demands: Participation in both internal meetings and external meetings via video calls, as necessary. Ability to go into corporate or client offices to work onsite, as necessary. Prolonged periods of remaining stationary at a desk and working on a computer, as necessary. Ability to bend, kneel, crouch, and reach overhead, as necessary. Hand-eye coordination necessary to operate computers and various pieces of office equipment, as necessary. Vision abilities including close vision, toleration of fluorescent lighting, and adjusting focus, as necessary. For positions that require business travel and/or event attendance, ability to lift 25 lbs, as necessary. For positions that require business travel and/or event attendance, a valid driver’s license and acceptable driving record are required, as driving is an essential job function. If requested, reasonable accommodations will be made to enable employees requiring accommodations to perform the essential functions of their jobs, absent undue hardship.
We should include these as requirements (maybe under Requirements). They are substantive.
Also "USA Benefits (Full time roles only, does not apply to contractor positions)" we captured.
Now ensure we don't include any fluff like "as necessary" maybe keep it.
Now produce HTML.
We'll structure:
About the role
The Project Manager will define project objectives aligned with current ways of working, oversee quality control throughout the project lifecycle, manages impacts of dependency systems, and ensure clear communication with all stakeholders to support this mission-critical clinical data repository.
Responsibilities
- Lead, plan, schedule, track, and manage project deliverables, goals, and milestones for PATH workstreams.
- Create detailed work plans identifying all necessary activities, resources (time, money, equipment), and objectives.
- Develop and communicate project scope, timeline, resource requirements, and assumptions.
- Map complex dependencies across workstreams (e.g., clinical workflows, billing, offline capabilities) to ensure alignment.
- Provide day-to-day direction and oversight for project teams.
- Monitor progress against goals and adjust plans or resources to meet customer and clinical needs.
- Manage project budgets, track expenses, and monitor resource utilization.
- Implement review and quality assurance procedures to ensure successful execution.
- Identify and track tasks to completion, ensuring blockers are resolved.
- Create and execute project plans, monitoring timelines and resource allocation.
- Coordinate clear communication with all stakeholders impacted by the project's scope, budget, risk, and resources.
- Proactively report on project status (metrics, scope, schedule) to leadership and team members.
- Develop strategies for risk mitigation and create contingency plans.
- Identify, resolve, and escalate functional, quality, and timeline issues as they arise.
Requirements
- Minimum of 3-5 years of project management experience, with a preference for software or clinical application projects.
- Proficiency in project management tools, including MS Project.
- Intermediate to advanced skills in MS Word, Excel, PowerPoint, and Outlook.
- Experience with JIRA, Confluence, and Teams.
- Certifications: A Project Management Professional (PMP) is preferred.
- Education: High school diploma or G
- for any list of duties/requirements/benefits. So we should treat each duty as a list item. We can split by sentences or by semicolons. Better to capture each bullet-like duty.
Let's extract duties:
From "Project Leadership & Planning:":
- Lead, plan, schedule, track, and manage project deliverables, goals, and milestones for PATH workstreams.
- Create detailed work plans identifying all necessary activities, resources (time, money, equipment), and objectives.
- Develop and communicate project scope, timeline, resource requirements, and assumptions.
- Map complex dependencies across workstreams (e.g., clinical workflows, billing, offline capabilities) to ensure alignment.
From "Execution & Management:":
- Provide day-to-day direction and oversight for project teams.
- Monitor progress against goals and adjust plans or resources to meet customer and clinical needs.
- Manage project budgets, track expenses, and monitor resource utilization.
- Implement review and quality assurance procedures to ensure successful execution.
- Identify and track tasks to completion, ensuring blockers are resolved.
- Create and execute project plans, monitoring timelines and resource allocation.
From "Communication & Stakeholder Management:":
- Coordinate clear communication with all stakeholders impacted by the project's scope, budget, risk, and resources.
- Proactively report on project status (metrics, scope, schedule) to leadership and team members.
From "Risk & Issue Management:":
- Develop strategies for risk mitigation and create contingency plans.
- Identify, resolve, and escalate functional, quality, and timeline issues as they arise.
Now Qualifications section: "Qualifications Minimum of 3-5 years of project management experience, with a preference for software or clinical application projects. Proficiency in project management tools, including MS Project. Intermediate to advanced skills in MS Word, Excel, PowerPoint, and Outlook. Experience with JIRA, Confluence, and Teams. Certifications: A Project Management Professional (PMP) is preferred. Education: High school diploma or GED required; Bachelor’s degree preferred"
We can split into list items for requirements.
Also "Additional Information" includes benefits: "Discover some of the global benefits that empower our people to become the best version of themselves:" then categories: Finance, Career Development, Learning Opportunities, Work-Life Balance, Health, Community. Each with list items separated by semicolons. Also "Additional Employee Requirements" includes various physical requirements. Also "USA Benefits (Full time roles only...)" includes specific US benefits.
We need Benefits section only if posting actually states them. It does. So we should create Benefits section with list items. Should we separate US benefits? Could combine but maybe separate? The instruction: Prefer a few substantive sections over many thin ones. So we can have one Benefits section covering all benefits mentioned (global and USA). But we need to ensure we don't include filler like "commensurate with experience". Not present.
We also have Pay and Schedule sections: Not explicitly stated. There's no mention of salary numbers or schedule specifics. So we should NOT create Pay or Schedule sections.
We also have Skills? Could be derived from qualifications but we have Qualifications section. Could also have Skills section separate? The instruction: Use headings for Skills if present. The posting mentions proficiency in tools etc. That could be skills. But we already have Qualifications covering experience, certifications, education. Skills could be separate: proficiency in MS Project, MS Office, JIRA, Confluence, Teams. However we can incorporate into Qualifications or Requirements. To keep few sections, we can have Qualifications (includes experience, certifications, education) and maybe Skills separate? But we can also treat those as Requirements. The heading "Requirements" is allowed. We could put all requirements (experience, tools, certifications, education) under Requirements. Then we could have Skills maybe not needed. Let's decide: Use Requirements for experience, tools, certifications, education. Use Skills maybe for soft skills? Not present. So we skip Skills.
We also need About the role: Could be the introductory paragraph plus Role Overview. Let's create About the role section with prose (
) summarizing the role overview. But we must not repeat job title. We'll include the description: "The Project Manager will define project objectives aligned with current ways of working, oversee quality control throughout the project lifecycle, manages impacts of dependency systems, and ensure clear communication with all stakeholders to support this mission-critical clinical data repository." That's from Role Overview. Also we could include the introductory company description? Might be considered About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put the role overview there. Thus sections:
About the role
The Project Manager will define project objectives aligned with current ways of working, oversee quality control throughout the project lifecycle, manages impacts of dependency systems, and ensure clear communication with all stakeholders to support this mission-critical clinical data repository.
Then Responsibilities:Responsibilities
with- items as extracted.
Then Requirements:
Requirements
with- items: 3-5 years project management experience, preference for software/clinical; proficiency in MS Project; intermediate to advanced skills in MS Word, Excel, PowerPoint, Outlook; experience with JIRA, Confluence, Teams; PMP certification preferred; High school diploma/GED required; Bachelor's degree preferred.
We could also include "Ability to go into corporate or client offices..." etc under Additional Employee Requirements. Those are also requirements (physical). Should we include them? They are requirements. Could add to Requirements list. But they are more about physical demands. Might be okay to include.
But we must not create sections with filler. So we can include them as list items under Requirements.
Now Benefits:
Benefits
with- items from global benefits and USA benefits.
Let's extract benefits:
Finance: Competitive salary package, share plan, company performance bonuses, value-based recognition awards, referral bonus;
Career Development: Career coaching, global career opportunities, non-linear career paths, internal development programmes for management and technical leadership;
Learning Opportunities: Complex projects, rotations, internal tech communities, training, certifications, coaching, online learning platforms subscriptions, pass-it-on sessions, workshops, conferences;
Work-Life Balance: Hybrid work and flexible working hours, employee assistance programme;
Health: Global internal wellbeing programme, access to wellbeing apps;
Community: Global internal tech communities, hobby clubs and interest groups, inclusion and diversity programmes, events and celebrations.
USA Benefits: Robust healthcare and benefits including Medical, Dental, vision, Disability coverage, and various other benefit options; Flexible Spending Accounts (Medical, Transit, and Dependent Care); Employer Paid Life Insurance and AD&D Coverages; Health Savings account paired with our low-cost High Deductible Medical Plan; 401(k) Safe Harbor Retirement plan with employer match with immediately vest.
We need to split each item into list items. Could keep each benefit as separate list item.
Now we must not include boilerplate like EEO etc. The posting includes EEO statements at end: "At Endava, we’re committed to creating an open, inclusive, and respectful environment..." etc. That's boilerplate; we should remove.
Also remove "Additional Information" heading etc.
Now produce HTML fragment.
Check for any repeated content: Ensure we preserve all substantive information. Did we miss anything? The "Additional Employee Requirements" includes many physical demands: Participation in both internal meetings and external meetings via video calls, as necessary. Ability to go into corporate or client offices to work onsite, as necessary. Prolonged periods of remaining stationary at a desk and working on a computer, as necessary. Ability to bend, kneel, crouch, and reach overhead, as necessary. Hand-eye coordination necessary to operate computers and various pieces of office equipment, as necessary. Vision abilities including close vision, toleration of fluorescent lighting, and adjusting focus, as necessary. For positions that require business travel and/or event attendance, ability to lift 25 lbs, as necessary. For positions that require business travel and/or event attendance, a valid driver’s license and acceptable driving record are required, as driving is an essential job function. If requested, reasonable accommodations will be made to enable employees requiring accommodations to perform the essential functions of their jobs, absent undue hardship.
We should include these as requirements (maybe under Requirements). They are substantive.
Also "USA Benefits (Full time roles only, does not apply to contractor positions)" we captured.
Now ensure we don't include any fluff like "as necessary" maybe keep it.
Now produce HTML.
We'll structure:
About the role
The Project Manager will define project objectives aligned with current ways of working, oversee quality control throughout the project lifecycle, manages impacts of dependency systems, and ensure clear communication with all stakeholders to support this mission-critical clinical data repository.
Responsibilities
- Lead, plan, schedule, track, and manage project deliverables, goals, and milestones for PATH workstreams.
- Create detailed work plans identifying all necessary activities, resources (time, money, equipment), and objectives.
- Develop and communicate project scope, timeline, resource requirements, and assumptions.
- Map complex dependencies across workstreams (e.g., clinical workflows, billing, offline capabilities) to ensure alignment.
- Provide day-to-day direction and oversight for project teams.
- Monitor progress against goals and adjust plans or resources to meet customer and clinical needs.
- Manage project budgets, track expenses, and monitor resource utilization.
- Implement review and quality assurance procedures to ensure successful execution.
- Identify and track tasks to completion, ensuring blockers are resolved.
- Create and execute project plans, monitoring timelines and resource allocation.
- Coordinate clear communication with all stakeholders impacted by the project's scope, budget, risk, and resources.
- Proactively report on project status (metrics, scope, schedule) to leadership and team members.
- Develop strategies for risk mitigation and create contingency plans.
- Identify, resolve, and escalate functional, quality, and timeline issues as they arise.
Requirements
- Minimum of 3-5 years of project management experience, with a preference for software or clinical application projects.
- Proficiency in project management tools, including MS Project.
- Intermediate to advanced skills in MS Word, Excel, PowerPoint, and Outlook.
- Experience with JIRA, Confluence, and Teams.
- Certifications: A Project Management Professional (PMP) is preferred.
- Education: High school diploma or G
- items from global benefits and USA benefits.
Let's extract benefits:
Finance: Competitive salary package, share plan, company performance bonuses, value-based recognition awards, referral bonus;
Career Development: Career coaching, global career opportunities, non-linear career paths, internal development programmes for management and technical leadership;
Learning Opportunities: Complex projects, rotations, internal tech communities, training, certifications, coaching, online learning platforms subscriptions, pass-it-on sessions, workshops, conferences;
Work-Life Balance: Hybrid work and flexible working hours, employee assistance programme;
Health: Global internal wellbeing programme, access to wellbeing apps;
Community: Global internal tech communities, hobby clubs and interest groups, inclusion and diversity programmes, events and celebrations.
USA Benefits: Robust healthcare and benefits including Medical, Dental, vision, Disability coverage, and various other benefit options; Flexible Spending Accounts (Medical, Transit, and Dependent Care); Employer Paid Life Insurance and AD&D Coverages; Health Savings account paired with our low-cost High Deductible Medical Plan; 401(k) Safe Harbor Retirement plan with employer match with immediately vest.
We need to split each item into list items. Could keep each benefit as separate list item.
Now we must not include boilerplate like EEO etc. The posting includes EEO statements at end: "At Endava, we’re committed to creating an open, inclusive, and respectful environment..." etc. That's boilerplate; we should remove.
Also remove "Additional Information" heading etc.
Now produce HTML fragment.
Check for any repeated content: Ensure we preserve all substantive information. Did we miss anything? The "Additional Employee Requirements" includes many physical demands: Participation in both internal meetings and external meetings via video calls, as necessary. Ability to go into corporate or client offices to work onsite, as necessary. Prolonged periods of remaining stationary at a desk and working on a computer, as necessary. Ability to bend, kneel, crouch, and reach overhead, as necessary. Hand-eye coordination necessary to operate computers and various pieces of office equipment, as necessary. Vision abilities including close vision, toleration of fluorescent lighting, and adjusting focus, as necessary. For positions that require business travel and/or event attendance, ability to lift 25 lbs, as necessary. For positions that require business travel and/or event attendance, a valid driver’s license and acceptable driving record are required, as driving is an essential job function. If requested, reasonable accommodations will be made to enable employees requiring accommodations to perform the essential functions of their jobs, absent undue hardship.
We should include these as requirements (maybe under Requirements). They are substantive.
Also "USA Benefits (Full time roles only, does not apply to contractor positions)" we captured.
Now ensure we don't include any fluff like "as necessary" maybe keep it.
Now produce HTML.
We'll structure:
- items: 3-5 years project management experience, preference for software/clinical; proficiency in MS Project; intermediate to advanced skills in MS Word, Excel, PowerPoint, Outlook; experience with JIRA, Confluence, Teams; PMP certification preferred; High school diploma/GED required; Bachelor's degree preferred.
We could also include "Ability to go into corporate or client offices..." etc under Additional Employee Requirements. Those are also requirements (physical). Should we include them? They are requirements. Could add to Requirements list. But they are more about physical demands. Might be okay to include.
But we must not create sections with filler. So we can include them as list items under Requirements.
Now Benefits:
- items as extracted.
Then Requirements: