Project Manager

We need to output HTML fragment with sections: About, Position Summary, Key Responsibilities, Qualifications (maybe split into Skills and Competencies, Experience and Education). The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to include sections only if there is real content. The posting includes: Brief Description (Project Manager Location Davidson, NC Temporary Position). About InSource Solutions. Position Summary. Key Responsibilities (long list). Qualifications (Skills and Competencies, Experience and Education). Why Join InSource Solutions? (maybe a Benefits/Why join section). There's no explicit Pay, Schedule, Benefits. The "Why Join" is more like a benefits/value proposition; could be considered Benefits? But the instruction says only create Benefits section if posting actually states them. The "Why Join" is not explicit benefits like health insurance, etc. It's more marketing. Might be okay to include as a section "Why Join InSource Solutions?" but heading should be from list: Benefits? Not exactly. Could use "About the role"? Already have About InSource Solutions. Could treat "Why Join" as a separate section with heading maybe "Why Join InSource Solutions?" but not in prescribed list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. So we should map content to those headings. We have About InSource Solutions -> could be "About the role"? Actually "About the role" is generic; but we have "About InSource Solutions". Could use "About the role" heading and put the About InSource Solutions content there? Might be okay. But we also have Position Summary. Could be "Responsibilities"? Actually Position Summary is separate. Could map to "Responsibilities"? But we also have Key Responsibilities separate. Might be better to have sections: About the role (About InSource Solutions), Responsibilities (Position Summary?), Requirements (Qualifications?), Skills (maybe split). However we need to avoid thin sections. Let's think: The posting includes: - Brief Description (Project Manager Location Davidson, NC Temporary Position) - could be a short paragraph meta. - About InSource Solutions (company description) - Position Summary (role overview) - Key Responsibilities (detailed list) - Qualifications (Skills and Competencies, Experience and Education) - could be combined into Requirements/Qualifications. - Why Join InSource Solutions? (motivation) We need to decide which headings to use. Given the examples, we could use:

  About the role

  -> include About InSource Solutions + Position Summary? Might be too much. Better: Use separate headings: About the role (About InSource Solutions), Responsibilities (Position Summary + Key Responsibilities?), Requirements (Qualifications), Benefits (Why Join). But we need to avoid filler. Let's see if any content matches "Skills" heading: The Qualifications includes Skills and Competencies list; we could put that under

  Skills

  . Experience and Education could be under

  Requirements

  or

  Qualifications

  . The examples include Qualifications as a heading. So we could have:

  About the role

  -> About InSource Solutions.

  Responsibilities

  -> Position Summary + Key Responsibilities (maybe combine).

  Requirements

  -> Experience and Education.

  Skills

  -> Skills and Competencies.

  Benefits

  -> Why Join InSource Solutions? (though not explicit benefits, but it's a motivation section; could be considered Benefits? Might be okay.) We must not create Pay/Schedule sections. We need to use
  • for any list of duties/requirements/benefits. So for responsibilities list, we need
    • . For skills list, also
      • . For experience/education list? It's more prose but could be list. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from each section. We need to remove boilerplate: cookie/navigation/legal/EEO etc. There's none. We need to not repeat job title as heading. We'll not. We need to not put Job ID/requisition numbers as headings; none. We need to output only HTML fragment. Let's extract content. Brief Description: "Project Manager Location Davidson, NC Temporary Position". Could be a short paragraph: maybe combine as

        Project Manager – Davidson, NC – Temporary Position

        . Keep. About InSource Solutions: paragraph(s). Let's copy: "InSource Solutions is a leading industrial software solutions provider and a trusted partner of AVEVA, a global leader in engineering and industrial software. Leveraging AVEVA's portfolio and the portfolios of our other partners, we specialize in delivering cutting-edge services and solutions that empower businesses across various industries to optimize their operations, improve efficiency, and achieve their digital transformation goals." Position Summary: The paragraph(s) after "Position Summary". Let's copy: "The Project Manager independently manages multiple professional services projects of moderate complexity from delivery handoff through client acceptance and project closeout. This role coordinates client and delivery teams to achieve agreed-upon scope, schedule, budget, quality, and intended project outcomes. The Project Manager is responsible for establishing and maintaining project plans, schedules, budgets, resource forecasts, milestones, risks, changes, and acceptance criteria while ensuring clear communication among clients, technical resources, internal stakeholders, partners, and subcontractors. This role serves as the primary point of contact for project coordination and is expected to manage routine project decisions independently using established InSource delivery practices. The Project Manager engages the Solutions Delivery Manager when decisions exceed delegated authority or when risks, issues, or changes may materially affect project commitments. Success in this role requires strong project management discipline, sound judgment, financial awareness, client communication, organization, and the ability to lead technical and business teams without direct authority." Key Responsibilities: a long list with headings like "Project Handoff and Kickoff:", etc. We need to turn each bullet into
      • . The headings are like "Project Handoff and Kickoff:" then description. We'll treat each as a list item with the heading bold? But we just need to output
      • containing the text. We'll keep the heading as part of the li text. List items: - Project Handoff and Kickoff: Review statements of work, estimates, assumptions, deliverables, and client commitments with Sales and technical leads. Confirm delivery readiness and lead project kickoff activities. - Project Planning and Management: Develop and maintain project plans, schedules, budgets, resource forecasts, milestones, deliverables, and acceptance criteria throughout the project lifecycle. - Resource Coordination: Coordinate staffing requirements with resource managers and communicate changes in project schedules, workload, skill requirements, and resource needs. - Client and Team Coordination: Lead project meetings and coordinate client personnel, technical resources, partners, vendors, and subcontractors. Track decisions, dependencies, action items, responsibilities, and client commitments. - Requirements and Documentation Coordination: Coordinate requirements and specification reviews with clients and technical leads. Ensure required documentation, reviews, and approvals are completed while maintaining technical content ownership with appropriately qualified technical resources. - Project Financial Management: Monitor scope, project progress, labor and expense consumption, forecast to complete, and project margin. Maintain accurate and timely project records and identify and explain variances and required corrective actions. - Invoicing and Revenue Support: Provide accurate project completion and timing forecasts to support invoicing and revenue recognition. Verify milestone evidence and coordinate billing-related questions with Finance. - Risk, Issue, and Change Management: Maintain project risk, issue, and change logs. Assess potential impacts, coordinate change requests, and obtain required approvals before committing to changes in scope, fees, or delivery dates. - Client Communication and Status Reporting: Serve as the primary point of contact for project coordination. Provide clear and timely status reports, manage client expectations, resolve routine issues, and escalate material risks with recommended actions. - Testing, Deployment, and Transition Coordination: Coordinate testing, deployment, training, and transition activities with technical and client leads. Confirm readiness, document client acceptance, and ensure outstanding project commitments are addressed. - Project Closeout: Manage project activities through client acceptance and closeout, ensuring required documentation, approvals, financial information, and transition activities are completed. - Continuous Improvement: Capture lessons learned and project outcomes and contribute recommendations that improve established project delivery practices. - Proposal and Estimating Support: Support proposal planning, project scoping, and estimating activities as requested. - Project Leadership: Provide project leadership and coordinate assigned resources, vendors, and subcontractors. Resource managers retain staffing and personnel-management authority, while technical leads retain responsibility for solution design and technical quality. Qualifications: split into Skills and Competencies, Experience and Education. Skills and Competencies list: many bullet points. We'll turn each into
      • . Let's extract them: - Strong project planning, organization, and coordination skills. - Ability to independently manage multiple concurrent projects and competing priorities while consistently following through on commitments. - Strong understanding of project scope, schedules, budgets, forecasts, risks, issues, changes, and acceptance criteria. - Ability to interpret statements of work, deliverables, assumptions, and acceptance criteria and recognize when additional clarification or approval is required. - Strong financial awareness with the ability to monitor project budgets, labor and expense consumption, forecast to complete, and project margins. - Strong risk, issue, and change-management capabilities. - Excellent facilitation, written communication, presentation, and interpersonal skills. - Ability to lead and influence technical and business teams without direct authority. - Strong client-facing communication skills with the ability to manage expectations and communicate project performance effectively. - Sound judgment, initiative, and a proactive approach to identifying and resolving issues. - Ability to recognize when risks or decisions require escalation to the Solutions Delivery Manager. - Proficiency with project scheduling and tracking tools. - Proficiency with Microsoft 365 applications, including Excel, Teams, PowerPoint, and Outlook. - Working understanding of software implementation lifecycles, including requirements, testing, deployment, acceptance, and transition to support. - Ability to work effectively with technical specialists and understand technical project dependencies without requiring hands-on programming, database design, or solution architecture expertise. - Commitment to InSource Solutions ethical standards, confidentiality, accurate reporting, and timely submission of time and expenses. Experience and Education: paragraph(s). Let's copy: "Degree in Engineering, Information Technology, Manufacturing, Business, Project Management, or a related field, or equivalent relevant work experience. 3–5 years of relevant project management experience. Experience independently managing scope, schedule, budget, and coordination for client-facing technical or professional services projects. Demonstrated experience managing multiple concurrent projects. Experience maintaining project budgets and forecasts and communicating project performance to clients and internal leaders. Experience managing project risks, issues, and changes. Experience coordinating technical and