Technical Program Manager - Trainee T3

We need to output HTML fragment with headings

for sections: 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. Must preserve all substantive info, remove boilerplate (EEO, legal, etc). Must not create sections with filler like "commensurate with experience". Must not invent or summarize away detail. We need to parse the posting. Key sections: - About The Role: description of Service Global, program, trainee levels description. Should be included. - Responsibilities: "Core Responsibilities Depending On Trainee Level, Responsibilities May Include ..." list of bullet items. Should be included. - Training & Development: maybe could be part of About the role or separate? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Training & Development could be considered part of About the role or maybe Qualifications? But we should include only those headings if content exists. There's a "Training & Development Trainees Receive" section. Could be considered part of About the role or maybe "Qualifications"? Not exactly. The instruction says prefer a few substantive sections over many thin ones. So we could merge Training & Development into About the role or maybe into Responsibilities? Probably better to keep About the role includes description of program and training. So we can incorporate that. - Minimum Qualifications: list of qualifications. That's "Minimum Qualifications". Should be a section "Requirements" or "Qualifications"? The headings list includes Requirements, Qualifications, Skills. We need to decide mapping. Usually "Minimum Qualifications" goes under Requirements or Qualifications. We'll put under

Requirements

maybe. But also there is "Preferred Qualifications". That could go under

Qualifications

or Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have separate headings for Requirements and Qualifications. Likely Requirements = minimum qualifications, Qualifications = preferred qualifications. Skills could be extracted from qualifications (like strong organizational, communication, problem-solving skills, ability to work with spreadsheets, etc). But we could also put skills under Skills heading. However we must not create thin sections. If we split too much, might be thin. Better to combine: Requirements (minimum qualifications) and Qualifications (preferred qualifications). Skills maybe not needed separately if covered. But we could still include Skills if there is explicit skill list. The posting includes: "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." Those are more like requirements/qualifications. Could go under Requirements. Preferred Qualifications list: experience, certifications. Physical & Site Requirements: could be part of Requirements as well. We also have Schedule: "Normally 40 hours per week". That's specific, so we should include a Schedule section. Pay: The posting mentions compensation will be determined based on assigned trainee level, qualifications, etc. No specific numbers. It says "Compensation will be determined based on assigned trainee level, qualifications, relevant experience, job location, and applicable pay practices." That's not a specific number or range. According to instruction: 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. The posting does state schedule (40 hours per week) so Schedule section is okay. For Pay, it's vague but does state that compensation will be determined based on factors; that's still not a specific number but it's a statement about compensation. Is that considered filler? It's not "commensurate with experience" but it's still generic. The instruction says never create Pay section unless posting actually states them. It does state something about compensation, albeit generic. I'd argue we can include Pay section with that statement. However we must avoid filler like "commensurate with experience". The statement is not exactly that but still generic. Might be okay. But to be safe, maybe we omit Pay section because it's not a concrete figure. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about compensation, so we could include. But we need to avoid filler like "commensurate with experience". The statement is not that phrase but still generic. I'd lean to include Pay with the given sentence. Benefits: Not mentioned. So omit Benefits. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must preserve all substantive information. Let's extract content. About the role: Paragraph(s): "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." Then description of trainee levels T1, T2, T3. Could be included as part of About the role. Also "Trainee Levels T1 – Foundation ..." etc. Also "Position Structure & Compensation" paragraph: "This is a paid, full-time W-2 employee position providing structured technical and project management training through supervision, mentorship, and practical project experience. Candidates will be assessed during the interview process and placed at the T1, T2, or T3 trainee level based on demonstrated qualifications, relevant data center infrastructure experience, project/program management capabilities, technical knowledge, and other job-related criteria. Compensation will be determined based on assigned trainee level, qualifications, relevant experience, job location, and applicable pay practices." We could incorporate that into About the role or maybe separate but we don't have a heading for Position Structure. We'll incorporate into About the role. Now Responsibilities: list: - 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. We need to output as

  • each. Now Requirements (minimum qualifications): - 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. Also Physical & Site 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." We could include that under Requirements as well. Now Qualifications (preferred qualifications): - 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. Now Schedule: "Normally 40 hours per week". Also maybe "Nationwide deployment may be required." That's location/travel, not schedule. So schedule is 40 hours per week. Pay: "Compensation will be determined based on assigned trainee level, qualifications, relevant experience, job location, and applicable pay practices." We'll include Pay section with that sentence. Now we need to ensure we don't include boilerplate: EEO, Work Authorization, Equal Employment Opportunity, etc. Remove those. Also remove "Position Structure & Compensation" heading as we incorporate. Now produce HTML. Structure:

    About the role

    ... paragraphs ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Qualifications

    • ...
    ...

    Schedule

    Normally 40 hours per week.

    Pay

    Compensation will be determined based on assigned trainee level, qualifications, relevant experience, job location, and applicable pay practices.

    We need to ensure we didn't miss any substantive info: The description of trainee levels T1/T2/T3 details should be included somewhere. We can include them in About the role as a list maybe. Could be a
    under About the role. But the instruction says use
    • for any list of duties/requirements/benefits. The trainee levels are not duties/requirements/benefits but description. Could be prose. We'll include as paragraphs. Let's craft About the role paragraph(s): Paragraph 1: 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. Paragraph 2: This is a paid, full-time W-2 employee position providing structured technical and project management training through supervision, mentorship, and practical project experience. Candidates will be assessed during the interview process and placed at the T1, T2, or T3 trainee level based on demonstrated qualifications, relevant data center infrastructure experience, project/program management capabilities, technical knowledge, and other job-related criteria. Compensation will be determined based on assigned trainee level, qualifications, relevant experience, job location, and applicable pay practices. Paragraph 3: 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 consistent, job-related interview and qualification criteria. We could make that a
      under About the role? It's a list of trainee levels. The instruction says use
      • for any list of duties/requirements/benefits. This is not exactly those categories but it's