Jobs · Information Technology · North Carolina

Senior Project Manager - Data Center Construction

Jobot · Charlotte, NC · 1 mo ago
On-siteInformation Technology$150k–$200k/yrFull-time
We need to output HTML fragment with sections only when content exists. Remove boilerplate, navigation, EEO, etc. Keep substantive info: about us, why join us, benefits, job details (role description), responsibilities, education & experience required, preferred, salary, maybe relocation offered, etc. We must use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real content. The posting includes: "A bit about us:" (About the company). Could map to "About the role"? Actually "About the role" is for role description; we have "Job Details" describing role. Could use "About the role" heading for that. Also "Why join us?" could be maybe part of Benefits or separate? Could be "Benefits" already separate. Could include "Why join us?" as maybe "About the company" but not in list. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. We have: - Salary: $150,000 - $200,000 per year => Pay section. - Benefits list => Benefits section. - Responsibilities: list under "Essential Job Responsibilities:" => Responsibilities section. - Requirements: Education & Experience REQUIRED => Requirements section (maybe also Qualifications). Could split: Requirements (required) and Qualifications (preferred). The instruction includes both Requirements and Qualifications headings. - Skills: maybe from required: strong computer skills, ability to work calmly, etc. Could put under Skills. - About the role: maybe from "Job Details Are you ready for your next challenge as a Senior Project Manager..." and description of role. - Schedule: not mentioned, so omit. - Pay: we have salary. - Benefits: we have. We also have relocation offered, but not a standard heading; could include in About the role or maybe as a note in Benefits? Probably include in About the role paragraph. We must preserve all substantive information, not invent. Remove boilerplate like EEO, legal, application instructions, etc. We must not repeat job title as heading. The job title is Senior Project Manager (Data Center Construction). Not to put as heading. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

Senior Project Manager within the Data Center Construction industry. Lead a team to manage construction of large-scale Data Centers. Reporting to a Director or Vice President. Oversee project management, estimating, billing, collections, team development. Relocation offered.

Responsibilities

  • Compliance with company, client, and project policies
  • Job site safety and adherence to company national policies
  • Generate estimates, review project proposals
  • Establish project timelines, budgets, and resource allocation
  • Supervise project execution to meet design, budget, and schedule requirements
  • Collaborate with the customer to clarify and meet expectations before, during, and after project completion
  • Coordinate activities of staff and subcontractors
  • Work directly with vendors to ensure timely procurement and delivery
  • Lead efforts for billing early and collecting often
  • Conduct regular site visits to monitor progress and address issues
  • Develop and maintain strong client and employee relationships
  • Assist leadership in the planning of future labor/material needs of the project
  • Provide consistent reports and updates to senior management
  • Forecast financial direction to course correct as needed
  • Develop project scopes and budgets
  • Manage RFPs and Change Management Forms
  • Mentor subordinates to support their development
  • Internal drive for continuous growth both personally and professionally

Requirements

  • 10+ years of Construction Project Management experience
  • 5+ years of Electrical Project Management for large scale, complex IT/Telecommunications Infrastructure projects, including Data Centers installations
  • Experience with Data Center electrical distribution systems, cabling, and white space fit-out
  • Experience with retrofits in operational facilities and cross-discipline critical facility systems
  • Strong computer skills and quick to learn new systems
  • Ability to work calmly under deadlines and external pressure
  • Commitment to continuous improvement of communication, organization and leadership skills
  • Effective scheduling and delegation to accomplish tasks on time
  • Tactful conflict resolution and problem solving abilities

Qualifications

  • Mission Critical Project experience (preferred)
  • Bachelor’s degree in a related field (Project Management, Construction Management, Business, Engineering, etc.), paired with industry experience OR an overall appropriate combination of certification(s), experience, and education (journeyman or master electrician’s license)
  • Project Management Professional (PMP) or PMI-Scheduling Professional (SP)
  • Experience with Google Suite, Salesforce, and ConEst

Skills

  • Strong computer skills
  • Ability to work calmly under deadlines and external pressure
  • Effective scheduling and delegation
  • Tactful conflict resolution and problem solving
  • Continuous improvement of communication, organization and leadership

Benefits

  • Medical, Dental, and Prescription Drug Insurance (100% of the premium covered US)
  • Life Insurance
  • Accidental Death & Dismemberment Insurance
  • Short & Long-Term Disability Insurance
  • Flexible Spending Accounts
  • 401k retirement and matching
  • Paid Vacation & Holidays
  • Tuition Reimbursement Program
  • Wellness Program

Pay

$150,000 - $200,000 per year

We might also include "About the company" but not required. The instruction says use those headings; we have covered. We must not include any boilerplate like EEO, legal, application instructions, etc. We removed those. Check for any duplicated lines: we have not repeated. Check for any placeholder text like "commensurate with experience" - none. Check for any missing info: we captured relocation offered in About the role paragraph. We captured "Why join us?" content? Not included. The "Why join us?" section includes growth, family, safety priorities, competitive compensation and benefits, world-class learning organization, core values, inclusive environment. That is substantive. Should we include it? Could be part of About the role or maybe a separate section like "Why join us?" but not in prescribed headings. Could incorporate into About the role paragraph or Benefits? Probably better to add a short paragraph under About the role describing why join us. Since we have About the role already, we can extend it. Let's update About the role paragraph to include why join us details. Also we have "A bit about us:" describing company mission, locations, etc. That is also substantive. Could be included in About the role or maybe a separate "About the company" but not in headings. Could incorporate into About the role as well. We must preserve all substantive information. So we need to include that info somewhere. We could add another section like "About the company" but not in allowed headings. However instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It 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? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are the headings we should use. It doesn't explicitly forbid other headings, but to be safe, we should stick to those. So we need to fit all substantive info under those headings. We have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We can put company info under About the role as well. And "Why join us?" also under About the role. Thus About the role paragraph will be longer, containing: role description, company overview, why join us, relocation offered. Let's craft:

About the role

Senior Project Manager within the Data Center Construction industry. Lead a team to manage construction of large-scale Data Centers, reporting to a Director or Vice President. Oversee project management, estimating, billing, collections, and team development. Relocation offered. The company is one of the nation's top Electrical Contractors with 19 strategic locations across the US, providing innovative solutions and quality service while building trusting relationships with clients and employees. Their mission emphasizes trust, collaboration, quality, safety, stewardship, and community, fostering an inclusive environment where growth, family, and safety are top priorities. Employees receive competitive compensation, 100% benefits coverage, unlimited growth opportunities, and a world‑class learning organization that empowers them to live out core values.

That covers company description and why join us. Now ensure we didn't miss any substantive info: The "Benefits" list we captured. The "Salary" captured. The "Responsibilities" captured. The "Requirements" captured. The "Qualifications" captured (preferred). The "Skills" we captured some but maybe we missed some like "Strong computer skills and quick to learn new systems" (we have strong computer skills, ability to work calmly, effective scheduling, tactful conflict resolution, continuous improvement). Could also add "quick to learn new systems". We'll add that. Also we might include "Experience with Data Center electrical distribution systems, cabling, and white space fit-out" under Requirements (we have). "Experience with retrofits in operational facilities and cross-discipline critical facility systems" under Requirements (we have). "Strong computer skills and quick to learn new systems" we have strong computer skills but missing quick to learn new systems; we can add. Also "Ability to work calmly under deadlines and external pressure" we have. "Commitment to continuous improvement of communication, organization and leadership skills" we have. "Effective scheduling and delegation to accomplish tasks on time" we have. "Tactful conflict resolution and problem solving abilities" we have. Now for Qualifications we have mission critical project experience, bachelor's degree or equivalent, PMP or PMI-SP, experience with Google Suite, Salesforce, ConEst. Good. Now we should also include "Experience with Google Suite, Salesforce, and ConEst Interested" maybe under Qualifications. Now check for any other substantive info: "Jobot Job is hosted by: Mark C. Johnson" - that's minor metadata; we can drop per instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. This is minor metadata (hosted by). We can drop it. "Easy Apply now by clicking the "Easy Apply" button and sending us your resume." - application instructions, drop. "Interested in hearing more? Easy Apply now by clicking the "Easy Apply" button." - drop. "Want to learn more about this role and Jobot? Click our Jobot logo and follow our

Similar jobs