MEP Preconstruction Manager
for each heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate (EEO etc). Preserve all substantive info. Include a section only when posting has real specific content for it. So we need to extract content.
Let's parse the posting:
Intro: Trueline's client... seeking an MEP Preconstruction Manager (Design Phase Manager) to join their team in Minneapolis, MN, on a hybrid schedule. You'll lead the design phase on complex commercial projects, with an emphasis on electrical systems, owning MEP estimating, designer and trade partner selection, scheduling, design development, and commissioning planning, with base salaries reaching $170,300 in Minneapolis and up to $187,300 in select markets, plus an incentive plan. Minneapolis is the focus, but outstanding candidates in other markets are encouraged to apply, and relocation assistance may be available for the right candidate. The right person pairs deep MEP and preconstruction expertise with a humble, team-first approach and wants a long-term home at a company with work booked through 2030.
Then "What You'll Do as the MEP Preconstruction Manager:" bullet list (actually sentences). Then "Must-Haves as the MEP Preconstruction Manager:" list. Then "Nice-to-Haves as the MEP Preconstruction Manager:" list. Then "Our Client Offers:" list.
We need sections: About the role (intro paragraph). Responsibilities (What You'll Do). Requirements (Must-Haves). Qualifications? Could combine Must-Haves and Nice-to-Haves? Usually Qualifications separate. But we have Must-Haves (requirements) and Nice-to-Haves (preferred). Could put Requirements as Must-Haves, Qualifications as Nice-to-Haves? Or Skills as Nice-to-Haves? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include only those sections that have real specific content. So we need to decide which sections we have content for.
We have:
- About the role: intro paragraph (first paragraph). Good.
- Responsibilities: "What You'll Do..." list.
- Requirements: "Must-Haves..." list.
- Qualifications: maybe "Nice-to-Haves..." list? Or could be Skills. But we have both Nice-to-Haves and Benefits etc.
- Benefits: "Our Client Offers:" includes many benefits.
- Pay: salary info.
- Schedule: hybrid schedule info.
Thus we can map:
About the role: intro paragraph.
Responsibilities: bullet list of duties.
Requirements: Must-Haves list.
Qualifications: Nice-to-Haves list (or maybe Skills). But we have also Skills? Not separate. Could treat Nice-to-Haves as Skills. But we have both Nice-to-Haves and Benefits. The instruction says prefer a few substantive sections over many thin ones. But we need to include sections only when posting has real specific content. We have content for all these sections. Could combine Qualifications and Skills? But we have separate headings list; we can include both if we have content. Let's see if we have content for Skills: The Nice-to-Haves list includes specific experiences/skills like Electrical preconstruction, design-build experience, Lean Design Delivery, BIM/VDC, LEED tracking, MEP commissioning planning, data center etc. Those are skills/experience. So we could put Skills heading for Nice-to-Haves. Qualifications could be Must-Haves? But we already used Requirements for Must-Haves. Actually Requirements often refers to mandatory qualifications. Qualifications could be preferred qualifications (nice-to-haves). So we can set:
- Requirements: Must-Haves.
- Qualifications: Nice-to-Haves.
- Skills: maybe not needed if we already have Qualifications. But we could omit Skills to avoid thin sections. The instruction: prefer a few substantive sections over many thin ones. So we could combine Nice-to-Haves into Qualifications and not have Skills. Or we could have Skills as Nice-to-Haves and omit Qualifications. Let's decide: We have both Must-Haves (mandatory) and Nice-to-Haves (preferred). So we can have Requirements (mandatory) and Qualifications (preferred). That seems appropriate. Then we can skip Skills.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. Use
- for any list of duties/requirements/benefits, and
for prose.
We need to avoid boilerplate: EEO etc at end. Remove that.
Also remove duplicated lines, cookie/navigation/legal etc. Not present.
Now let's extract each section content.
About the role: The intro paragraph(s) before "What You'll Do". Let's capture:
"Trueline's client, one of the largest and most respected builders in the country, is seeking an MEP Preconstruction Manager (Design Phase Manager) to join their team in Minneapolis, MN, on a hybrid schedule. You'll lead the design phase on complex commercial projects, with an emphasis on electrical systems, owning MEP estimating, designer and trade partner selection, scheduling, design development, and commissioning planning, with base salaries reaching $170,300 in Minneapolis and up to $187,300 in select markets, plus an incentive plan.Minneapolis is the focus, but outstanding candidates in other markets are encouraged to apply, and relocation assistance may be available for the right candidate. The right person pairs deep MEP and preconstruction expertise with a humble, team-first approach and wants a long-term home at a company with work booked through 2030."
Note there is a missing space after "plan.Minneapolis". We'll keep as is but maybe add a space for readability? We must preserve ALL substantive information; we can fix minor punctuation? Probably keep as is but we can add a space? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Adding a space is not inventing info, just formatting. Safer to keep original text but we can adjust spacing for readability; it's not substantive. I'll keep as is but maybe add a space after period. It's minor.
Now Responsibilities: The bullet list after "What You'll Do as the MEP Preconstruction Manager:" includes multiple sentences each starting with a verb. We'll turn each into
- .
List:
- Manage the design phase for one or more concurrent commercial projects, including estimating, business partner selection, preliminary scheduling, design development, quality control, and MEP commissioning planning
- Work closely with owners to define project expectations and the critical success factors to focus on during design
- Facilitate the solicitation, selection, and contracting of designers on design-build projects
- Develop and lead the preparation and presentation of project proposals
- Build detailed design-phase and baseline construction schedules
- Lead construction planning, including the contract manual, subcontractor selection, MWD/BE participation, trade and site utilization, disruption avoidance, and owner direct purchase planning, using Lean Design Delivery principles and BIM/VDC technology
- Guide design teams to build constructability and logistics solutions into the design, and provide meaningful input on programming and conceptual design
- Lead estimating team members on the technical design side, including drawings, specifications, scheduling, and cost documentation
- Manage design-phase costs through estimate preparation, technical estimating, value engineering, life-cycle analysis, and budget management
- Secure regulatory approvals, meet risk management requirements for insurance, bonding, owner contracts, and subcontractor terms, and implement LEED tracking and analysis
- Supervise, mentor, and develop Design Phase Engineers, including work direction, performance evaluations, and hiring decisions
- Set the tone for exceptional customer relationships, gather feedback throughout design, and help identify future project opportunities
Now Requirements (Must-Haves): list after "Must-Haves as the MEP Preconstruction Manager:":
- Bachelor's degree in Construction, Architectural, Mechanical, or Electrical Engineering, or a related field
- 10+ years of construction experience
- 5+ years of estimating or on-site project management experience, including 1-2 years as a Preconstruction Manager
- Thorough knowledge of mechanical, electrical, plumbing, and low-voltage systems
- Working knowledge of construction equipment, techniques, scheduling, cost control, drawings, specifications, and standards
- Proven leadership experience, with the ability to build relationships and influence at every level of an organization
- A humble, team-first approach and the integrity to do the right thing when nobody's looking
- Working knowledge of EEO, inclusive leadership practices, and Affirmative Action requirements
- Ability to travel up to 70% to project sites and work in the office Tuesday through Thursday when not traveling
- Authorization to work in the U.S. without current or future visa sponsorship
Now Qualifications (Nice-to-Haves): list after "Nice-to-Haves as the MEP Preconstruction Manager:":
- Electrical preconstruction, estimating, or design phase experience
- Background with an electrical or mechanical contractor
- Design-build experience, including designer solicitation and contracting
- Lean Design Delivery and BIM/VDC experience
- LEED tracking and analysis experience
- MEP commissioning planning experience
- Data center, healthcare, sports, federal, or manufacturing project experience
Now Benefits: from "Our Client Offers:" list. Let's extract each bullet:
- Base salary of $113,500-$170,300 in Minneapolis, depending on experience, and up to $187,300 in select markets
- Eligibility for the company's incentive plan
- Hybrid schedule: project site travel comes first, and otherwise you'll be in the office Tuesday through Thursday and remote Monday and Friday
- Relocation assistance may be available for the right candidate
- Medical and prescription drug coverage with vision included at no additional cost, plus dental
- 401(k) with a generous company match
- Paid time off, holidays, and other paid leave
- Employer-paid life, AD&D, and disability insurance
- Tuition reimbursement, adoption assistance, and a gym membership discount program
- No-cost mental health support and work-life concierge resources
- Work booked through 2030 at a company that has grown roughly 40% in most years
- A leadership role building and developing a team of Design Phase Engineers
- Opportunity to move across regional offices and business units as the company expands into new markets and industries
- A humble, respectful culture with genuine leadership, where many team members have built 30+ year careers
Note: Some of these overlap with Pay, Schedule, Benefits. We need to separate Pay, Schedule, Benefits sections as per instruction. So we need to extract Pay info, Schedule info, and Benefits info.
Pay: base salary range and incentive plan. Also maybe mention up to $187,300 in select markets. So Pay section should contain that.
Schedule: hybrid schedule details.
Benefits: the rest (medical, 401k, PTO, etc.) plus other items like work booked through 2030, leadership role, opportunity to move, culture etc. Those could be considered Benefits or maybe other sections like "About the company". But we only have allowed headings: Benefits, Pay, Schedule. So we put all other offerings under Benefits.
Thus we need to parse "Our Client Offers:" and split.
Let's list each item and categorize:
1. Base salary of $113,500-$170,300 in Minneapolis, depending on experience, and up to $187,300 in select markets -> Pay.
2. Eligibility for the company's incentive plan -> Pay (or Benefits? It's compensation; could be Pay). We'll put in Pay.
3. Hybrid schedule
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate (EEO etc). Preserve all substantive info. Include a section only when posting has real specific content for it. So we need to extract content. Let's parse the posting: Intro: Trueline's client... seeking an MEP Preconstruction Manager (Design Phase Manager) to join their team in Minneapolis, MN, on a hybrid schedule. You'll lead the design phase on complex commercial projects, with an emphasis on electrical systems, owning MEP estimating, designer and trade partner selection, scheduling, design development, and commissioning planning, with base salaries reaching $170,300 in Minneapolis and up to $187,300 in select markets, plus an incentive plan. Minneapolis is the focus, but outstanding candidates in other markets are encouraged to apply, and relocation assistance may be available for the right candidate. The right person pairs deep MEP and preconstruction expertise with a humble, team-first approach and wants a long-term home at a company with work booked through 2030. Then "What You'll Do as the MEP Preconstruction Manager:" bullet list (actually sentences). Then "Must-Haves as the MEP Preconstruction Manager:" list. Then "Nice-to-Haves as the MEP Preconstruction Manager:" list. Then "Our Client Offers:" list. We need sections: About the role (intro paragraph). Responsibilities (What You'll Do). Requirements (Must-Haves). Qualifications? Could combine Must-Haves and Nice-to-Haves? Usually Qualifications separate. But we have Must-Haves (requirements) and Nice-to-Haves (preferred). Could put Requirements as Must-Haves, Qualifications as Nice-to-Haves? Or Skills as Nice-to-Haves? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include only those sections that have real specific content. So we need to decide which sections we have content for. We have: - About the role: intro paragraph (first paragraph). Good. - Responsibilities: "What You'll Do..." list. - Requirements: "Must-Haves..." list. - Qualifications: maybe "Nice-to-Haves..." list? Or could be Skills. But we have both Nice-to-Haves and Benefits etc. - Benefits: "Our Client Offers:" includes many benefits. - Pay: salary info. - Schedule: hybrid schedule info. Thus we can map: About the role: intro paragraph. Responsibilities: bullet list of duties. Requirements: Must-Haves list. Qualifications: Nice-to-Haves list (or maybe Skills). But we have also Skills? Not separate. Could treat Nice-to-Haves as Skills. But we have both Nice-to-Haves and Benefits. The instruction says prefer a few substantive sections over many thin ones. But we need to include sections only when posting has real specific content. We have content for all these sections. Could combine Qualifications and Skills? But we have separate headings list; we can include both if we have content. Let's see if we have content for Skills: The Nice-to-Haves list includes specific experiences/skills like Electrical preconstruction, design-build experience, Lean Design Delivery, BIM/VDC, LEED tracking, MEP commissioning planning, data center etc. Those are skills/experience. So we could put Skills heading for Nice-to-Haves. Qualifications could be Must-Haves? But we already used Requirements for Must-Haves. Actually Requirements often refers to mandatory qualifications. Qualifications could be preferred qualifications (nice-to-haves). So we can set: - Requirements: Must-Haves. - Qualifications: Nice-to-Haves. - Skills: maybe not needed if we already have Qualifications. But we could omit Skills to avoid thin sections. The instruction: prefer a few substantive sections over many thin ones. So we could combine Nice-to-Haves into Qualifications and not have Skills. Or we could have Skills as Nice-to-Haves and omit Qualifications. Let's decide: We have both Must-Haves (mandatory) and Nice-to-Haves (preferred). So we can have Requirements (mandatory) and Qualifications (preferred). That seems appropriate. Then we can skip Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. Use
- for any list of duties/requirements/benefits, and
for prose. We need to avoid boilerplate: EEO etc at end. Remove that. Also remove duplicated lines, cookie/navigation/legal etc. Not present. Now let's extract each section content. About the role: The intro paragraph(s) before "What You'll Do". Let's capture: "Trueline's client, one of the largest and most respected builders in the country, is seeking an MEP Preconstruction Manager (Design Phase Manager) to join their team in Minneapolis, MN, on a hybrid schedule. You'll lead the design phase on complex commercial projects, with an emphasis on electrical systems, owning MEP estimating, designer and trade partner selection, scheduling, design development, and commissioning planning, with base salaries reaching $170,300 in Minneapolis and up to $187,300 in select markets, plus an incentive plan.Minneapolis is the focus, but outstanding candidates in other markets are encouraged to apply, and relocation assistance may be available for the right candidate. The right person pairs deep MEP and preconstruction expertise with a humble, team-first approach and wants a long-term home at a company with work booked through 2030." Note there is a missing space after "plan.Minneapolis". We'll keep as is but maybe add a space for readability? We must preserve ALL substantive information; we can fix minor punctuation? Probably keep as is but we can add a space? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Adding a space is not inventing info, just formatting. Safer to keep original text but we can adjust spacing for readability; it's not substantive. I'll keep as is but maybe add a space after period. It's minor. Now Responsibilities: The bullet list after "What You'll Do as the MEP Preconstruction Manager:" includes multiple sentences each starting with a verb. We'll turn each into
- . List: - Manage the design phase for one or more concurrent commercial projects, including estimating, business partner selection, preliminary scheduling, design development, quality control, and MEP commissioning planning - Work closely with owners to define project expectations and the critical success factors to focus on during design - Facilitate the solicitation, selection, and contracting of designers on design-build projects - Develop and lead the preparation and presentation of project proposals - Build detailed design-phase and baseline construction schedules - Lead construction planning, including the contract manual, subcontractor selection, MWD/BE participation, trade and site utilization, disruption avoidance, and owner direct purchase planning, using Lean Design Delivery principles and BIM/VDC technology - Guide design teams to build constructability and logistics solutions into the design, and provide meaningful input on programming and conceptual design - Lead estimating team members on the technical design side, including drawings, specifications, scheduling, and cost documentation - Manage design-phase costs through estimate preparation, technical estimating, value engineering, life-cycle analysis, and budget management - Secure regulatory approvals, meet risk management requirements for insurance, bonding, owner contracts, and subcontractor terms, and implement LEED tracking and analysis - Supervise, mentor, and develop Design Phase Engineers, including work direction, performance evaluations, and hiring decisions - Set the tone for exceptional customer relationships, gather feedback throughout design, and help identify future project opportunities Now Requirements (Must-Haves): list after "Must-Haves as the MEP Preconstruction Manager:": - Bachelor's degree in Construction, Architectural, Mechanical, or Electrical Engineering, or a related field - 10+ years of construction experience - 5+ years of estimating or on-site project management experience, including 1-2 years as a Preconstruction Manager - Thorough knowledge of mechanical, electrical, plumbing, and low-voltage systems - Working knowledge of construction equipment, techniques, scheduling, cost control, drawings, specifications, and standards - Proven leadership experience, with the ability to build relationships and influence at every level of an organization - A humble, team-first approach and the integrity to do the right thing when nobody's looking - Working knowledge of EEO, inclusive leadership practices, and Affirmative Action requirements - Ability to travel up to 70% to project sites and work in the office Tuesday through Thursday when not traveling - Authorization to work in the U.S. without current or future visa sponsorship Now Qualifications (Nice-to-Haves): list after "Nice-to-Haves as the MEP Preconstruction Manager:": - Electrical preconstruction, estimating, or design phase experience - Background with an electrical or mechanical contractor - Design-build experience, including designer solicitation and contracting - Lean Design Delivery and BIM/VDC experience - LEED tracking and analysis experience - MEP commissioning planning experience - Data center, healthcare, sports, federal, or manufacturing project experience Now Benefits: from "Our Client Offers:" list. Let's extract each bullet: - Base salary of $113,500-$170,300 in Minneapolis, depending on experience, and up to $187,300 in select markets - Eligibility for the company's incentive plan - Hybrid schedule: project site travel comes first, and otherwise you'll be in the office Tuesday through Thursday and remote Monday and Friday - Relocation assistance may be available for the right candidate - Medical and prescription drug coverage with vision included at no additional cost, plus dental - 401(k) with a generous company match - Paid time off, holidays, and other paid leave - Employer-paid life, AD&D, and disability insurance - Tuition reimbursement, adoption assistance, and a gym membership discount program - No-cost mental health support and work-life concierge resources - Work booked through 2030 at a company that has grown roughly 40% in most years - A leadership role building and developing a team of Design Phase Engineers - Opportunity to move across regional offices and business units as the company expands into new markets and industries - A humble, respectful culture with genuine leadership, where many team members have built 30+ year careers Note: Some of these overlap with Pay, Schedule, Benefits. We need to separate Pay, Schedule, Benefits sections as per instruction. So we need to extract Pay info, Schedule info, and Benefits info. Pay: base salary range and incentive plan. Also maybe mention up to $187,300 in select markets. So Pay section should contain that. Schedule: hybrid schedule details. Benefits: the rest (medical, 401k, PTO, etc.) plus other items like work booked through 2030, leadership role, opportunity to move, culture etc. Those could be considered Benefits or maybe other sections like "About the company". But we only have allowed headings: Benefits, Pay, Schedule. So we put all other offerings under Benefits. Thus we need to parse "Our Client Offers:" and split. Let's list each item and categorize: 1. Base salary of $113,500-$170,300 in Minneapolis, depending on experience, and up to $187,300 in select markets -> Pay. 2. Eligibility for the company's incentive plan -> Pay (or Benefits? It's compensation; could be Pay). We'll put in Pay. 3. Hybrid schedule