Project Manager – Federal Contact Center (Remote)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. First paragraph: "Project Manager - Federal Contact Center (Remote) ITCON Services is a forward-thinking consulting firm delivering innovative technology and management solutions that help our federal clients achieve mission success. We pride ourselves on fostering a collaborative, high-performance environment where experienced professionals can make a meaningful impact. ITCON is seeking an experienced Project Manager to support the successful delivery of a large-scale federal contact center program. Working closely with the Program Manager, this role will provide day-to-day operational and project leadership to ensure work performed under the Performance Work Statement (PWS) is completed successfully and in accordance with contractual requirements, Service Level Agreements (SLAs), and established performance standards. This is a high-visibility role requiring strong operational oversight, stakeholder management, workforce coordination, and the ability to identify and resolve issues quickly in a fast-paced, mission-critical environment." That's about the role. So we can have

About the role

with that paragraph(s). Might split into

. Next: "What You'll Do" list of duties. That's responsibilities. So

Responsibilities

with

• each bullet. Then "What You Bring" list of qualifications/skills/experience. Could be split into Requirements and Qualifications and Skills. The posting includes "What You Bring" with bullet-like sentences. Then later "Requirements" with numbered list. Then "Preferred Qualifications". Then "Why Join ITCON?" with benefits etc. We need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have specific content for: - About the role: yes. - Responsibilities: from "What You'll Do". - Requirements: from "Requirements" numbered list (10+ years etc). Also includes U.S. Citizenship required, clearance, availability, location, response time. - Qualifications: maybe "Preferred Qualifications" list. - Skills: could be extracted from "What You Bring" (skills like experience managing complex projects, etc). But we might combine "What You Bring" into Qualifications or Skills. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Qualifications (including preferred), Benefits. Skills maybe not needed if covered. But we must include sections only when posting has real specific content. We have content for Benefits: "Why Join ITCON?" includes bullet points: Opportunity to support a mission-critical federal program..., High-visibility role..., Collaborative and supportive team environment., Competitive compensation and benefits., Professional development opportunities., 100% remote flexibility. That's benefits. Pay: Not mentioned specifically (no salary). So we should NOT include Pay section. Schedule: The posting mentions "Must be available Monday-Friday, 8:00 AM-6:00 PM Eastern Time." That's schedule info. Also "Must be able to respond to technical or operational issues within one hour during required business hours." That's also schedule/availability. So we have schedule content. So we should include Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications (maybe combine preferred qualifications), Benefits, Schedule. We could also have Skills but maybe not needed. We need to ensure we don't repeat job title as heading. Good. We must not include boilerplate like EEO, equal opportunity, etc. Remove that. We must preserve all substantive info; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (or close). Must not omit any duty, requirement, qualification, benefit, schedule detail. We need to format as HTML:

  About the role

  ... maybe multiple paragraphs.

  etc. For lists:
  • ...
  . We must not include markdown fences. Let's extract content precisely. About the role text: The first paragraph(s) up to "What You'll Do". Let's copy: "ITCON Services is a forward-thinking consulting firm delivering innovative technology and management solutions that help our federal clients achieve mission success. We pride ourselves on fostering a collaborative, high-performance environment where experienced professionals can make a meaningful impact. ITCON is seeking an experienced Project Manager to support the successful delivery of a large-scale federal contact center program. Working closely with the Program Manager, this role will provide day-to-day operational and project leadership to ensure work performed under the Performance Work Statement (PWS) is completed successfully and in accordance with contractual requirements, Service Level Agreements (SLAs), and established performance standards. This is a high-visibility role requiring strong operational oversight, stakeholder management, workforce coordination, and the ability to identify and resolve issues quickly in a fast-paced, mission-critical environment." We could also include the opening line "Project Manager - Federal Contact Center (Remote)"? But we must not repeat job title as heading; but we could include it in the paragraph? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid including it in the paragraph. However, the job title appears at start of posting; we could keep it as part of the about role description? Might be redundant but not a heading. Safer to keep it? The instruction says do NOT repeat the job title as a heading. It doesn't say to remove it from content. But typical reformatting might drop it. I'd keep it maybe as part of first sentence? But the first sentence currently starts with "ITCON Services is...". If we include the job title, we would be repeating it. The posting already shows the job title elsewhere; we could omit it from the paragraph to avoid repetition. I'd omit it. Thus About the role paragraph as above. Now Responsibilities: list from "What You'll Do". Let's capture each bullet: - Support the Program Manager in the planning, execution, and successful delivery of program and contractual requirements. - Provide day-to-day oversight of work performed under the PWS, ensuring compliance with contract requirements, SLAs, KPIs, quality standards, and customer service expectations. - Coordinate contact center operations to ensure consistent service delivery, workforce readiness, and operational performance. - Monitor program performance, analyze trends, identify risks and service gaps, and implement corrective actions and continuous improvement initiatives. - Support staffing, resource allocation, workforce planning, and operational readiness to meet changing program demands. - Lead and coordinate cross-functional teams, including operations, quality assurance, training, workforce management, and IT support. - Track project milestones, deliverables, risks, action items, and dependencies to ensure timely completion. - Assist with the development of performance reports, dashboards, briefings, and other contract deliverables. - Participate in meetings and briefings with government stakeholders, including the Contracting Officer (CO), Contracting Officer's Representative (COR), and other client representatives. - Maintain strong communication among government stakeholders, program leadership, subcontractors, and internal teams. - Identify, escalate, and coordinate resolution of technical, operational, and customer service issues. - Respond to technical or operational issues within one hour during required business hours. - Support compliance with federal requirements, security requirements, company policies, procedures, and contract standards. - Promote a culture of accountability, collaboration, continuous improvement, and high performance across the program. We need to ensure we keep all. Now Requirements: numbered list: - 10+ years of project management, program management, operations management, or related leadership experience. - Experience supporting large-scale contact/call center operations or customer service delivery environments. - Experience supporting complex federal government contracts or programs. - Experience monitoring and managing performance against SLAs, KPIs, quality standards, and contractual requirements. - U.S. Citizenship required. - Must be eligible to obtain and maintain the required government clearance. - Must be available Monday-Friday, 8:00 AM-6:00 PM Eastern Time. - Must be able to respond to technical or operational issues within one hour during required business hours. - Must reside within the continental United States, Alaska, Hawaii, or Puerto Rico. Note: The last two about availability and response time also appear in schedule; but we keep them in Requirements as they are requirements. However schedule section will also include them? Might duplicate. But we need to preserve all substantive info; we can include them in both sections? That would be duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid duplication. However schedule section should contain schedule specifics; we could move the availability and response time to Schedule section, and keep other requirements in Requirements. But the Requirements list includes those items; if we move them, we would be omitting from Requirements unless we keep them there too. The instruction says do not summarize away detail; we can keep them in both places? That would be duplication but not loss. However duplication might be considered unnecessary but not prohibited. The instruction: "Prefer a few substantive sections over many thin ones." Duplication could make sections thicker but okay. However we might avoid duplication by placing schedule-specific items in Schedule and not repeating them in Requirements. But then we would be removing them from Requirements list, which is part of the posting. That would be losing detail. So better to keep them in Requirements and also include them in Schedule? That duplicates but preserves detail. However the schedule section would then contain the same info; it's okay. But we could also have Schedule section contain the schedule details (availability, response time) and keep Requirements without those items, but then we would be missing them from Requirements. To preserve all detail, we need to keep them somewhere; we could keep them in Requirements and also mention them in Schedule (duplicate). That's acceptable. Now Qualifications: The "What You Bring" list includes many items. Could treat as Qualifications. Also there is "Preferred Qualifications" list. We could combine both into Qualifications section, maybe separate subheadings? But we only allowed headings from list; we cannot add custom headings. So we need to decide: either put all under Qualifications, or split into Qualifications and Skills. The "What You Bring" includes experience, skills, knowledge, abilities. The "Preferred Qualifications" includes education, certifications, specific experiences. We could put "What You Bring" under Qualifications, and "Preferred Qualifications" under Qualifications as well (maybe as a sublist). But we need to output only HTML fragment; we could have

  Qualifications

  then maybe two
  lists: one for required qualifications (What You Bring) and another for preferred qualifications. However the instruction: Use
  • for any list of duties/requirements/benefits. So we can have multiple lists. Thus Qualifications section will contain two lists: first list for "What You Bring" (required qualifications), second list for "Preferred Qualifications". Ensure we keep all items. Now Benefits: from "Why Join ITCON?" list: - Opportunity to support a mission-critical federal program serving a large customer population. - High-visibility role with exposure to government leadership and key stakeholders. - Collaborative and supportive team environment. - Competitive compensation and benefits. - Professional development opportunities. - 100% remote flexibility. We should not include EEO etc. Now Schedule: we need to include schedule specifics: Must be available Monday-Friday, 8:00 AM-6:00 PM Eastern Time. Must be able to respond to technical or operational issues within one hour during required business hours. Possibly also mention remote? But remote is benefit. Thus schedule section with those two items as list. Now we need to ensure we don't include any boilerplate like "Equal Opportunity Employer" etc. Now construct HTML. We'll start with

    About the role

    ...

    Then

    Responsibilities

    ...
    Then