Project Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: WHY JOIN ENTREGA (company overview), POSITION DETAILS (work arrangement), POSITION SUMMARY, Responsibilities, Qualifications, PERFORMANCE PROFILE, CAREER GROWTH. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to these headings. The instructions: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings? Probably we should use those headings where appropriate. The posting includes sections like "WHY JOIN ENTREGA" (company overview) maybe map to "About the role"? Actually "About the role" could be the position summary. "Responsibilities" is present. "Requirements" maybe map to Qualifications? "Qualifications" is present. "Skills" maybe part of Qualifications. "Benefits", "Pay", "Schedule" not present (except schedule maybe in POSITION DETAILS: Work Location, Employment Type, Travel). Not specific benefits or pay. So we should not include Benefits, Pay, Schedule sections because no specific content. Also we should not repeat job title as heading. No Job ID. We need to preserve all substantive information, remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes "View All Jobs WHY JOIN ENTREGA" maybe that's navigation; we should remove "View All Jobs". Also remove duplicated lines. We need to output only HTML fragment, no /, no markdown. Thus produce something like:

About the role

Entrega is a growing technology professional services firm headquartered in Michigan, delivering enterprise technology, digital, and business solutions to global clients. ... (the WHY JOIN ENTREGA paragraph).

But we need to ensure we don't repeat content unnecessarily. The "WHY JOIN ENTREGA" is basically company overview and reasons to join. Could be considered "About the role"? Might be better as "About the role" includes position summary? Actually position summary is separate. The instructions say "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose which headings to include based on content. We have content for About the role (company overview and why join), Responsibilities, Qualifications (maybe split into Requirements and Qualifications?), Performance Profile maybe could be "Requirements"? But we already have Qualifications. Performance Profile is more about expected behaviors; could be considered "Requirements"? Might be redundant. Better to include sections: About the role, Responsibilities, Qualifications, Performance Profile (maybe as "Requirements"?). But we should not create thin sections; we can combine similar content. We have: - WHY JOIN ENTREGA (company overview) - POSITION DETAILS (work location, employment type, travel) - could be part of About the role? Or maybe we could include a short paragraph under About the role covering work arrangement. - POSITION SUMMARY (description of role) - Responsibilities (detailed) - Qualifications (experience, knowledge & skills, education & certifications) - PERFORMANCE PROFILE (high-impact execution role, successful candidates will demonstrate...) - CAREER GROWTH (commitment to investing in employees) We could map: - About the role: combine WHY JOIN ENTREGA + POSITION DETAILS + POSITION SUMMARY? Might be too much but okay. - Responsibilities: as is. - Requirements: maybe we can use "Requirements" for the Qualifications section (experience, knowledge & skills, education). But we already have Qualifications heading; we could use "Qualifications" as heading. - Skills: maybe part of Qualifications; we could skip separate Skills. - Benefits, Pay, Schedule: omit. Thus we will output sections: About the role, Responsibilities, Qualifications, Performance Profile, Career Growth. But the instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as examples. It's safer to stick to those headings. However we have content for Performance Profile and Career Growth which are not in the list. Could we map Performance Profile to "Requirements"? Or maybe we can treat Performance Profile as part of Qualifications? But it's distinct. The instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't say we cannot use other headings; it just gives examples. So we can use other headings if needed. But to be safe, we could use the provided headings and put content accordingly, maybe merging Performance Profile into Qualifications or Requirements. However the Qualifications section already includes experience, knowledge & skills, education. Performance Profile is about expected behaviors and traits; could be considered "Requirements". So we could have a "Requirements" section that includes both the qualifications and performance profile. But we already have a Qualifications section with detailed bullet-like paragraphs. Might be okay to split: Requirements (performance profile) and Qualifications (experience, education). But the instruction says prefer a few substantive sections over many thin ones. So maybe better to have just About the role, Responsibilities, Qualifications (which includes experience, knowledge & skills, education & certifications, performance profile). Career Growth could be omitted? It's substantive but maybe could be included as a separate section; but we could also fold into About the role? It's about career growth, distinct. We need to preserve ALL substantive information. So we must include career growth content somewhere. If we omit a separate heading, we need to include it under some heading. Could add a

under About the role or Qualifications. But that might mix unrelated content. Better to have a separate section for Career Growth, even if not in the example list. The instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." indicates examples, not exclusive. So we can use other headings. Thus final HTML:

About the role

Entrega is a growing technology professional services firm headquartered in Michigan, delivering enterprise technology, digital, and business solutions to global clients. We help leading organizations solve complex business challenges through the successful execution of business-critical technology initiatives, supported by our ongoing investment in our people, processes, and technology. At Entrega, we believe exceptional client outcomes begin with exceptional employees. We provide an environment where professionals are trusted with meaningful responsibility, supported by experienced leadership, and empowered to make a measurable impact. You'll work alongside a talented team serving Fortune 500 clients, contribute to high-visibility initiatives, and have opportunities to influence how our company continues to grow. As we expand, employees who consistently deliver results have opportunities to broaden their responsibilities, advance their careers, and help shape the future of the organization. If you're looking for an opportunity to make a meaningful impact, learn and grow professionally, and help shape the future of a growing professional services firm, we encourage you to explore a career with Entrega.

Work Location: Onsite – Troy, Michigan
Employment Type: Full-Time
Travel: Occasional local travel, as needed

Responsibilities

• Develop and maintain detailed project plans that translate approved scope and delivery commitments into milestones, activities, dependencies, timelines, and responsibilities.
• Lead day-to-day project execution and ensure work progresses in alignment with agreed scope, schedule, budget, and delivery expectations.
• Coordinate project activities across delivery teams, functional stakeholders, and other participants required to execute the work.
• Establish clear execution priorities and maintain visibility into current and upcoming project activities.
• Monitor progress against project commitments and identify deviations early.
• Support effective transitions between planning, execution, delivery, and project closeout activities.
• Maintain current visibility into project scope, schedule, milestones, and budget status.
• Track approved project commitments and identify potential impacts from changes in scope, timing, staffing, dependencies, or delivery conditions.
• Ensure proposed changes are documented, evaluated, and escalated through the appropriate governance process.
• Partner with the Service Delivery Manager and other stakeholders to understand the impact of delivery changes on project commitments.
• Maintain disciplined project controls that help prevent unplanned scope, schedule, and budget deterioration.
• Identify, document, and actively manage project risks, issues, assumptions, and dependencies.
• Establish clear owners and actions for material risks and issues and monitor them through resolution.
• Escalate emerging delivery concerns early to the Service Delivery Manager and other appropriate stakeholders.
• Facilitate resolution of project execution obstacles and ensure unresolved concerns remain visible.
• Maintain current risk and issue reporting that supports effective decision-making and delivery oversight.
• Maintain the project-management structure, documentation, and operating cadence required for disciplined execution.
• Facilitate project planning sessions, execution meetings, status reviews, and governance checkpoints.
• Ensure material project decisions, changes, actions, and commitments are documented and communicated.
• Maintain appropriate project artifacts, including project plans, status reports, decision logs, risk and issue registers, and related documentation.
• Support adherence to Entrega's delivery processes, standards, governance practices, and project-management expectations.
• Help ensure projects remain prepared for leadership, client, quality, or operational reviews.
• Coordinate communication and execution across project stakeholders to ensure responsibilities, priorities, dependencies, and timelines are understood.
• Provide clear and timely updates regarding project progress, risks, issues, decisions, and upcoming activities.
• Facilitate productive working sessions and ensure meetings result in clear decisions, actions, owners, and follow-through.
• Work closely with the Service Delivery Manager to ensure project execution information supports broader delivery oversight and client communication.
• Coordinate appropriately with Delivery Leads and delivery teams without replacing their responsibility for managing and executing production work.
• Prepare accurate and consistent project status reporting for delivery leadership and other stakeholders.
• Maintain current visibility into project health, milestones, schedule performance, risks, issues, and execution progress.
• Ensure project-management systems and tracking tools accurately reflect current project conditions.
• Identify trends or execution concerns that may affect delivery performance and communicate them proactively.
• Support project performance reviews through reliable data, documentation, and analysis.
• Coordinate project closeout activities and ensure required documentation, approvals, and outstanding actions are completed.
• Capture project lessons learned, execution challenges, and improvement opportunities.
• Contribute to the continuous improvement of project-management processes, tools, reporting, and delivery practices.
• Share practical insights that can improve consistency and execution across future engagements.

Qualifications

Experience

• 5–10+ years of progressive project-management experience within professional services, consulting, technology delivery, or another complex project environment.
• Demonstrated experience leading complex projects involving multiple stakeholders, workstreams, and delivery teams.
• Experience managing project scope, schedules, milestones, budgets, risks, issues, dependencies, and reporting.
• Demonstrated experience developing and maintaining detailed project plans and structured project governance.
• Experience identifying