Technical Program Manager - Trainee T3

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About The Role: description of Service Global, program details, trainee levels description. Should be under

About the role

with

content. - Responsibilities: "Core Responsibilities Depending On Trainee Level, Responsibilities May Include" list of bullet points. Should be

Responsibilities

with

• each. - Training & Development: maybe under "Training & Development" could be a section like "Training & Development" but not in list of allowed headings? Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map "Training & Development" maybe to "Requirements"? Not exactly. Could be part of "Qualifications"? But better to include as a separate section? The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It 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 using those. Likely we should stick to those headings; we can place training info under "Requirements" or "Qualifications". However "Minimum Qualifications" and "Preferred Qualifications" are clearly qualifications. So we can have

  Qualifications

  with subparts Minimum and Preferred maybe as

  or

  . Also "Minimum Qualifications" and "Preferred Qualifications" content. - "Physical & Site Requirements" could go under "Requirements". Could be a subsection. - "Schedule: Normally 40 hours per week" and "Location & Travel: Nationwide deployment may be required." Also "Work Environment: Data center, low-voltage infrastructure, and project coordination environments". This could go under "Schedule" and maybe "Requirements"? But schedule heading is allowed. So we can have

  Schedule

  with

  containing schedule info, location/travel maybe also. - Pay: "Compensation will be determined based on assigned trainee level, qualifications, relevant experience, job location, and applicable pay practices." Also earlier: "This is a paid, full-time W-2 employee position providing structured technical and project management training". So we have pay info but not specific numbers. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation will be determined based on factors, but not a specific number. Is that enough to include a Pay section? It says "Compensation will be determined based on assigned trainee level, qualifications, relevant experience, job location, and applicable pay practices." That's a statement about compensation. So we can include a Pay section with that info. However we must avoid filler like "commensurate with experience" etc. This is somewhat generic but still a statement. It's not "not specified". It says compensation will be determined based on... That's substantive. So we can include Pay. - Benefits: Not mentioned. So no Benefits section. - Skills: Could be derived from "Strong organizational, communication, and problem-solving skills.Ability to work with spreadsheets and learn project-management, ticketing, reporting, and documentation tools.Ability to coordinate effectively with multiple stakeholders." That's skills. So we can have

  Skills

  with
  or

  . - Requirements: Minimum qualifications etc. Could be under Requirements. We need to avoid duplication. Let's structure:

  About the role

  Service Global delivers data center and technology infrastructure services, including low-voltage cabling, fiber, network deployment, quality management, documentation, and project delivery. The Technical Program Manager Trainee program develops employees to support and coordinate increasingly complex infrastructure projects. Prior Technical Program Manager experience is not required. Trainee Levels: T1 – Foundation (supports project documentation, trackers, schedules, action items, infrastructure walkthroughs, quality records, and issue escalation while developing foundational technical and project coordination skills). T2 – Intermediate (coordinates defined workstreams, schedules, risks, vendors, field teams, QA/QC activities, reporting, and project deliverables with increased independence). T3 – Advanced Trainee (supports ownership of larger work packages, stakeholder coordination, project meetings, SLA and risk tracking, customer communication, issue resolution, project closeout, and continuous improvement. T3 remains a trainee classification and does not independently replace the authority of a Project Manager or Technical Program Manager unless formally assigned). Candidates are not required to apply separately for T1, T2, or T3; placement will be based on interview and qualification criteria.

  But we need to preserve all substantive info; we can condense but not lose detail. Must not invent or summarize away detail. We can keep bullet list for trainee levels maybe. Better: Use
  for list of duties/requirements/benefits. For About the role we can use

  . For trainee levels we could embed in

  or

  . Since it's a list, we could use
  . But the instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. So trainee levels could be considered a list (of levels). So we can do

    About the role

    Service Global delivers ...

    • T1 – Foundation: ...
    • T2 – Intermediate: ...
    • T3 – Advanced Trainee: ...
    That seems fine. Next Responsibilities: list bullet points.

    Responsibilities

    • Maintain project trackers, schedules, action items, dashboards, issue logs, and documentation.
    • Support cable schedules, labeling records, redlines, test trackers, and turnover packages.
    • Coordinate with Project Managers, Technical Program Managers, field teams, vendors, material teams, and other stakeholders.
    • Track schedule, SLA, risk, quality, testing, punch-list items, rework, and project blockers.
    • Prepare project status reports and support customer-facing communication.
    • Participate in data center walkthroughs and project-site activities.
    • Support project closeout and recommend improvements to reporting, documentation, workflow, and data quality.
    Next Training & Development: maybe under "Requirements" or "Qualifications"? Could be its own section but not in allowed headings. Could be placed under "Requirements" as part of requirements? But it's more about training provided. Could be under "Qualifications"? Not exactly. Perhaps we can create a section "Training & Development" but the instruction says use those headings e.g. but not strictly limited? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests examples, not exhaustive. But to be safe, we could incorporate training info into "Requirements" or "Qualifications". However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we can combine training & development into "Qualifications" as part of what the role provides? But qualifications are about candidate attributes, not training provided. Better to have a separate section "Training & Development" but it's not in the list; risk of being considered not following instruction. However 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 the examples are those. I'd stick to those headings to be safe. So we need to place training & development info somewhere else. Could be under "Requirements" as part of what the candidate will receive? But requirements are about what candidate must have. Training is what they will get. Could be under "About the role" as part of program description. Actually the About the role already mentions program develops employees... So we can incorporate training & development details into About the role section. That would avoid extra section. Thus we can add training & development bullets into About the role after trainee levels maybe as a

    under same heading? But we already used a
    for trainee levels; we could add another
    for training & development. That's okay. Now Minimum Qualifications and Preferred Qualifications: we can put under

    Qualifications

    with two subheadings? But we cannot use

    maybe? Not prohibited but we can just use

    with bold? But we should keep semantic: maybe

    Qualifications

    Minimum Qualifications: ...

    Preferred Qualifications: ...

    . Or we could use
    for each list. Minimum Qualifications list: - Relevant education, technical training, professional experience, or transferable experience related to technology, infrastructure, engineering, data, or project management. - Strong organizational, communication, and problem-solving skills. - Ability to work with spreadsheets and learn project-management, ticketing, reporting, and documentation tools. - Ability to coordinate effectively with multiple stakeholders. - Ability to travel nationally and work at assigned project locations where required. - Ability to work a full-time schedule. - Must be legally authorized to work in the United States by the employment start date. - Relevant academic disciplines may include Information Systems, Information Technology, Computer Science, Engineering, Telecommunications, Project or Construction Management, Data/Systems disciplines, or related fields. Preferred Qualifications list: - Data center, low-voltage, structured cabling, fiber, copper, or network infrastructure experience. - Project coordination or project-management experience. - Experience with trackers, schedules, dashboards, issue logs, QA/QC, testing, commissioning, or project closeout. - Experience coordinating vendors, technicians, contractors, or cross-functional teams. - Relevant technical or project-management certifications. Physical & Site Requirements: could be under Requirements heading. Let's create

    Requirements

    with maybe a

    that includes Physical & Site Requirements plus maybe other requirements like work authorization etc. But we already have work authorization in Minimum Qualifications. So we can combine. We need to avoid duplication: Minimum Qualifications already includes ability to travel nationally, ability to work full-time schedule, legally authorized to work in US. Physical & Site Requirements includes ability to perform essential site responsibilities, working in active data center or construction environments, extended standing/walking, navigating authorized work areas, following PPE, occasionally lifting up to approx 25 pounds. We'll include that. Thus Requirements section could have two lists: Minimum Qualifications and Physical & Site Requirements (maybe as sublist). But we must not repeat content already in Qualifications section. If we put Minimum Qualifications under Qualifications, we shouldn't repeat under Requirements. So Requirements could contain Physical & Site Requirements only. But the instruction says we can have Requirements section for any list of duties/requirements/benefits. So we can put Physical & Site Requirements there. Thus:

    Requirements

    • With or without reasonable accommodation, ability to perform essential site responsibilities, which may include working in active data center or construction environments, extended standing or walking, navigating authorized work areas, following PPE requirements, and occasionally lifting up to approximately 25 pounds.
    But also maybe include "Ability to travel nationally and work at assigned project locations where required." That's already in Minimum Qualifications; we shouldn't duplicate. So we keep it only there