Project Manager - Data Center Construction-Travel

We need to output HTML fragment with sections: About the role? The posting includes description. We need headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Key info: - Role: Data Center Construction Project Manager (full-time travel role, travel 75-100%, home about once a month while project active). Per diem, vehicle allowance, cell phone allowance cover travel cost. - Salary: $90,000 to $130,000 per year, plus a team bonus pool. - Career path: Technician I ... Project Manager is where LINX hands you full budget and workforce ownership on a project. Also direct path to Senior Project Manager and Program Manager. - Responsibilities: list bullet points under "What You'll Be Doing": Project Planning and Site Coordination, Budget Ownership, Materials and Procurement Management, Workforce and Team Management, Change Management and Documentation, Closeout and Training. - Requirements: Minimum Requirements: 3+ years experience managing large-scale hyperscale data center construction projects OR 3+ years general commercial construction project management experience with direct ownership of at least one project budget in $1M-$3M range. 5+ years experience in a construction leadership role, or equivalent labor management experience organizing, prioritizing, scheduling work assignments across multiple crews. Ability and willingness to travel 75-100% of the time to long-term project sites across US, with typical trips home about once a month while a project is active. Proficiency with Microsoft Office (Excel, Word, PowerPoint). Valid driver's license. - Preferred: Low voltage construction experience, Four-year college degree, RCDD, BICSIDCDC, BICSIPMP. - Not right for: bullet points. - Benefits: list: 401(k) with 50% employer match on first 5% contributed; Medical, dental, vision insurance with FSA and HSA options; Short and long-term disability coverage; 3 weeks PTO (vacation and sick combined); 8 paid holidays; Cell phone allowance; Vehicle allowance; Per diem for all travel expenses; Manufacturer and industry training and certification support; Direct advancement path to Senior Project Manager and Operations Manager. - About LINX: description. We need sections: About the role (maybe overview), Responsibilities, Requirements, Qualifications (maybe Preferred?), Skills (maybe proficiency with MS Office, driver's license?), Benefits, Pay, Schedule. But we must only include sections with real specific content. Let's decide. - About the role: we have description of role, travel, etc. That's substantive. - Responsibilities: we have bullet list. - Requirements: we have minimum requirements. - Qualifications: we have preferred qualifications (low voltage experience, degree, certifications). Could be separate. - Skills: maybe proficiency with MS Office, driver's license could be considered skills but they are also in requirements. Might be redundant. Could combine into Requirements. But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include those that have content. - Pay: salary range and bonus pool. - Schedule: travel percentage and home once a month. We also have Benefits section. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: Equal Opportunity Statement, etc. We must not include application instructions. We must preserve all substantive info. Let's craft HTML:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Skills

Proficiency with Microsoft Office (Excel, Word, PowerPoint); Valid driver's license.

Benefits

• ...
...

Pay

Salary: $90,000 to $130,000 per year, plus a team bonus pool.

Schedule

Full-time travel role with travel making up roughly 75% to 100% of your schedule; projects are long‑term assignments and you’ll typically be home about once a month while a project is active.

We need to ensure we don't include filler like "commensurate with experience". Not present. Check that we didn't duplicate content. Now write the content. About the role paragraph: combine description: LINX is hiring a Data Center Construction Project Manager to lead hyperscale builds at project sites across the country. This is a full-time travel role, with travel making up roughly 75% to 100% of your schedule. Projects are long-term assignments, not short trips, and you'll typically be home about once a month while a project is active. Per diem, vehicle allowance, and cell phone allowance cover the cost of that travel. If you've spent the last three years managing schedules, budgets, and crews on large-scale hyperscale data center projects, and you want a role built around long-term hyperscale assignments instead of general commercial construction, this is that role. Also mention career path: Technician I ... Project Manager is where LINX hands you full budget and workforce ownership on a project. It's also the direct path to Senior Project Manager and Program Manager as LINX's hyperscale footprint expands into new markets. We can include that. Responsibilities bullets: list each bullet from "What You'll Be Doing". Need to capture each bullet. Let's extract: - Project Planning and Site Coordination: Lead project kickoff meetings, define project schedules, and conduct site walkthroughs with clients and stakeholders at each new hyperscale location; Adapt project plans to the specific site conditions, local labor market, and client requirements of each new long-term assignment - Budget Ownership: Own the full multi-million dollar project budget, including labor hours, shift costs, materials, and equipment; Track spend against budget in real time and flag variances before they become overruns - Materials and Procurement Management: Coordinate with the LINX procurement team to ensure all equipment and materials are ordered, received, and staged before each project's start date; Manage vendor and supplier relationships specific to each project site - Workforce and Team Management: Oversee scheduling, hiring, and performance management of installation technicians on each project; Build and lead project teams from the ground up at new sites, since crews and site conditions change with every assignment - Change Management and Documentation: Track project milestones and manage change orders throughout the project lifecycle; Maintain complete, accurate project documentation from kickoff through closeout - Closeout and Training: Deliver final project closeout and conduct client training at project completion; Facilitate post-project reviews to carry lessons learned into the next site We'll make each as

with the two sentences combined maybe separated by semicolon. Requirements bullets: Minimum Requirements: - 3+ years of experience managing large-scale hyperscale data center construction projects OR 3+ years of general commercial construction project management experience with direct ownership of at least one project budget in the $1 million to $3 million range. - 5+ years of experience in a construction leadership role, or equivalent labor management experience organizing, prioritizing, and scheduling work assignments across multiple crews - Ability and willingness to travel 75% to 100% of the time to long-term project sites across the United States, with typical trips home about once a month while a project is active - Proficiency with Microsoft Office (Excel, Word, PowerPoint) - Valid driver's license Qualifications (Preferred): - Low voltage construction experience - Four-year college degree - RCDD (Registered Communications Distribution Designer), BICSIDCDC (Data Center Design Consultant), BICSIPMP (Project Management Professional) Skills: maybe we already have proficiency and driver's license in Requirements; but we can still have Skills section with those. However to avoid duplication, maybe we put them in Skills and not repeat in Requirements? But Requirements already includes them. The instruction: preserve ALL substantive information; do not invent or summarize away detail. Duplication is okay? It says remove duplicated lines. So we should not duplicate identical content. If we put proficiency and driver's license in both Requirements and Skills, that's duplication. Better to put them only once. Where to place? Could be under Requirements (makes sense). Then Skills could be omitted if no other specific skills. But we need to include Skills heading only if there is real specific content. If we have none besides those already covered, maybe we omit Skills. However the instruction list includes Skills as an example heading but we only include if posting has real specific content. The posting does mention proficiency with MS Office and driver's license; those are skills. But they are also in Requirements. Could we move them to Skills and remove from Requirements? But Requirements also includes other items; we could keep those other items in Requirements and move the skill-specific ones to Skills. That avoids duplication. Let's do that. Thus Requirements bullets: experience, leadership, travel. Skills bullets: proficiency with MS Office, valid driver's license. Now Benefits bullets: list each. Pay: salary range plus bonus. Schedule: travel percentage and home once a month. Now About LINX paragraph: maybe we could put under About the role or separate About LINX? The heading list includes About the role, not About LINX. But we could include About LINX under About the role or maybe we could add a section About LINX? Not in list; but we could include as part of About the role. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those. But we should stick to those given. So we can include About the role covering both role description and company overview. Thus About the role paragraph includes role description and LINX overview. Now ensure we don't include boilerplate: Equal Opportunity Statement, evergreen posting, etc. Now produce HTML. Let's craft. Check for any missing info: The "This Role Is Probably Not Right For*" bullet points: we should include? It's substantive info about fit. Could be under a section like "Not a good fit if". But not in heading list. Could we include under About the role? Might be considered extra. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that info somewhere. Where to put? Could be under About the role as a paragraph, or maybe under a heading like "Not a good fit if". But heading list does not include that. However we can still include a heading not in the list? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. But to be safe, we could incorporate that info into About the role or Responsibilities? Probably better to add a subsection like "Not a good fit if" as a heading? Might be considered extra but not prohibited. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but we could also use other headings if needed? It's ambiguous. Safer to stick to those headings only. Then we need to fit the "Not right for" info somewhere else, maybe under About the role as a note. We'll add a paragraph under About the role: "This role is probably not right for you if..." and list bullet points. Thus we preserve that info. Now ensure we don't include duplicated lines: we have travel mention in About the role and also in Schedule; that's duplication? About the role mentions travel 75-100% and home once