Technical Program Manager - Trainee T1

We need to output HTML fragment with sections only when content present. Must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate: EEO, legal, scam warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we need to extract relevant content: The posting includes: - Technical Program Manager Trainee – Data Center Infrastructure Trainee Levels: T1 Company: Service Global Employment Type: Full-time, paid W-2 position Schedule: Normally 40 hours per week Work Environment: Data center, low-voltage infrastructure, and project coordination environments Location & Travel: Nationwide deployment may be required. Current active projects include Ohio and Virginia. - Position Structure & Compensation: description of 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 interview and placed at 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. - About The Role: description of Service Global delivering data center and technology infrastructure services, etc. 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: description. - T2 – Intermediate: description. - T3 – Advanced Trainee: description. - Candidates are not required to apply separately for T1, T2, or T3. Placement will be based on consistent, job-related interview and qualification criteria. - Core Responsibilities: list of responsibilities (bulleted). We need to put as

• . - Training & Development: description. - Minimum Qualifications: list. - Preferred Qualifications: list. - Physical & Site Requirements: description. - Equal Employment Opportunity: boilerplate, remove. - Work Authorization: description (must be legally authorized to work in US). This is a requirement; we can include under Requirements or Qualifications? It's a requirement. We'll include under Requirements maybe. - Service Global participates in E-Verify etc: maybe part of Work Authorization; but it's boilerplate? It's still relevant but maybe considered legal. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Work Authorization might be considered legal but it's a substantive requirement. However "Work Authorization Applicants must be legally authorized to work in the United States by the employment start date." That's a requirement. The rest about E-Verify maybe legal boilerplate; we can keep the requirement but drop the rest about E-Verify? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The E-Verify part is legal boilerplate; we can drop it. Keep the requirement about being legally authorized. We need to decide which sections to output. We have content for: - About the role (we have About The Role section). Use heading

  About the role

  . - Responsibilities (Core Responsibilities). Use heading

  Responsibilities

  . - Requirements (Minimum Qualifications). Use heading

  Requirements

  (or maybe Qualifications?). The instruction list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping. Usually Requirements = minimum qualifications. Qualifications = preferred qualifications. Skills maybe separate but we can combine. We'll output Requirements for minimum qualifications, Qualifications for preferred qualifications. Skills maybe not needed if not explicit. Benefits, Pay, Schedule: we have Schedule: Normally 40 hours per week. That's a schedule detail. We have no explicit Benefits or Pay beyond compensation determination statement. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." We have schedule stated: "Normally 40 hours per week". So we can create a Schedule section. Pay: we have "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, but it's stating compensation will be determined based on factors. Is that considered stating Pay? It's vague but it's about pay. The instruction says never create Pay section unless posting actually states them. It does state compensation will be determined based on... That is a statement about pay. However it's not a specific number or range. The instruction also says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The phrase "Compensation will be determined based on assigned trainee level, qualifications, relevant experience, job location, and applicable pay practices." is somewhat vague but not exactly placeholder like "commensurate with experience". It does give factors. Might be acceptable. But to be safe, maybe we should not create Pay section because it's not a specific figure. The instruction says avoid filler/placeholder text like "commensurate with experience". This is similar. I'd lean to omit Pay section. Benefits: not stated. So omit. Schedule: we have "Normally 40 hours per week". That's specific enough. So we can create Schedule section. We also have Work Environment, Location & Travel, Position Structure & Compensation (which includes description of training). Could be part of About the role or separate? The instruction says prefer a few substantive sections over many thin ones. We could combine some info into About the role or Responsibilities. But we need to preserve all substantive information. We can include details like Employment Type, Work Environment, Location & Travel within About the role section as prose. We also have Position Structure & Compensation description (training, mentorship, etc). Could be part of About the role or maybe a separate section like "Training & Development". Actually there is a separate "Training & Development" section later. So we can keep that. Thus sections: - About the role (includes company, employment type, work environment, location/travel, position structure & compensation overview maybe). - Responsibilities (Core Responsibilities). - Requirements (Minimum Qualifications). - Qualifications (Preferred Qualifications). - Skills (maybe we can extract from Minimum Qualifications: strong organizational, communication, problem-solving skills; ability to work with spreadsheets; ability to coordinate; ability to travel; ability to work full-time; legally authorized. Those are skills. Could put under Skills. But we already have Requirements and Qualifications; maybe we can put skills under Requirements. To avoid thin sections, we could omit Skills section and include those in Requirements. - Schedule (40 hours per week). - Training & Development (maybe we can incorporate into About the role or separate). There's a distinct "Training & Development" section. Could be its own heading? Not in the allowed list; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add Training & Development as a heading unless we map it to one of those. Could treat as part of About the role or Responsibilities. Probably best to incorporate into About the role. Thus we will output:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Schedule

  Normally 40 hours per week.

  We must ensure we preserve all substantive info. Let's extract details. About the role content: - Company: Service Global. - Employment Type: Full-time, paid W-2 position. - Work Environment: Data center, low-voltage infrastructure, and project coordination environments. - Location & Travel: Nationwide deployment may be required. Current active projects include Ohio and Virginia. - Position Structure & Compensation: 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. - 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 description (T1, T2, T3) maybe part of About the role or Responsibilities? Could be included in About the role as part of role description. We need to preserve trainee levels details. Could include them in About the role as a list. Thus About the role paragraph(s) can include multiple paragraphs. We'll use

  for prose; we can have multiple

  under the heading. We must not repeat job title as heading. Now Responsibilities: list from Core 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. We'll put each as

• . 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. We could also include the academic disciplines as part of the first bullet or separate. We'll keep as separate bullet. 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. Schedule: Normally 40 hours per week. We should also include maybe the note about "Candidates are not required to apply separately for T1, T2, or T3. Placement will be based on consistent, job-related interview and qualification criteria." This could go under About the role or Responsibilities? It's about placement. Could be part of About the role. Also "Trainee Levels T1 – Foundation ..." etc. We'll include those under About the role as a list maybe. We must not create sections with filler text. All content we have is substantive. Now we need to output only HTML fragment, no /, no