Senior Project Manager I - MEP
for section headings, - for any list of duties/requirements/benefits, and
for prose.
We need to decide which sections to include:
- About the role: combine introductory paragraphs about role and company culture.
- Responsibilities: list of duties (the bullet-like sentences after "Lead MEP projects...").
- Requirements: maybe include education, experience, authorization, physical demands? Could also include Qualifications? Actually we have both Requirements and Qualifications as allowed headings. We need to decide what goes where. Typically Requirements are mandatory items; Qualifications are preferred. But we can split: Requirements: Bachelor's degree, 10+ years experience, authorized to work in US, PE license preferred? Actually PE license preferred is maybe Qualification. But we can put both under Requirements and Qualifications as needed.
Better: Use Requirements for mandatory: Bachelor's degree, 10+ years experience, authorized to work in US, knowledge of codes, leadership skills, communication skills, proficiency in tools, ability to manage competing priorities. Use Qualifications for preferred: PE license preferred, PMP or equivalent certification accepted in lieu.
Skills: maybe list of skills like leadership, communication, etc. But we already have those in Requirements. Could create Skills section for soft skills and technical skills.
But we must avoid thin sections. Perhaps combine Requirements and Qualifications into one Requirements section? But we have both headings allowed; we can use both if we have distinct content.
Let's extract:
Mandatory (Requirements):
- Bachelor of Science degree in Mechanical Engineering, Electrical Engineering, or a closely related field.
- 10+ years of experience in MEP project management.
- Strong knowledge of relevant mechanical, electrical, and plumbing codes and standards.
- Proven leadership and team management skills with the ability to coordinate across multiple disciplines.
- Excellent written and verbal communication skills; comfortable presenting to clients and senior stakeholders.
- Proficiency in project management tools such as Procore, Autodesk Construction Cloud, or MS Project.
- Ability to manage competing priorities across multiple active projects.
- Applicants must be currently authorized to work in the U.S. on a full-time basis. (No sponsorship)
Preferred (Qualifications):
- Professional Engineer (PE) license preferred.
- PMP or equivalent project management certification accepted in lieu.
Skills: maybe we can list technical skills: knowledge of MEP codes, proficiency in PM tools, leadership, communication, etc. But that overlaps.
Maybe we can have Skills section for technical and soft skills: "Strong knowledge of MEP codes and standards", "Leadership and team management", "Excellent written and verbal communication", "Proficiency in Procore, Autodesk Construction Cloud, MS Project", "Ability to manage competing priorities". But that's similar to Requirements.
Better to keep Requirements as the list of mandatory qualifications, and Qualifications as preferred certifications. Skills maybe not needed.
Benefits: we have list.
Pay: we have "competitive salary". We'll include a paragraph.
Schedule: none, so omit.
About the role: combine intro and company culture.
Now we need to remove duplicated lines: The posting includes some repeated sentences like "Lead MEP projects from inception through closeout, ensuring delivery on time, within budget, and to quality standards." and then "Oversee the design, installation, and commissioning of mechanical, electrical, and plumbing systems across large-scale projects." etc. Those are responsibilities.
We need to format responsibilities as
- each.
Similarly benefits as
- .
Requirements as
- .
Qualifications as
- .
About the role as
prose (maybe multiple paragraphs). We'll wrap each paragraph in
.
Now ensure we don't include boilerplate: Remove EEO, unsolicited resumes, vendor agreement, etc. Also remove "Physical Demands" heading? We'll incorporate physical demands description into Requirements maybe as a paragraph, but we need to decide if we want to include it. The physical demands description includes: "Work is performed in an office setting. Hand-eye coordination is necessary to operate a computer, keyboard and mouse. Use of a telephone headset will allow for virtual communication with team members through Zoom and/or Microsoft Teams. While performing the duties of this job, the employee is often required to sit for prolonged periods, use hands/fingers to handle, feel or operate objects, tools or controls and reach with hands and arms, speak and hear. Specific vision abilities required by this job include close vision, distance vision, color vision, peripheral vision, depth perception, and the ability to adjust focus."
This is substantive but not a requirement per se; it's about work environment. Could be included under Requirements as a paragraph. However we might decide to omit because it's not strictly a requirement but it's still info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it. Where to put? Could be under Requirements as a paragraph (not list). Or we could create a separate section like "Work Environment" but not allowed heading. So we must fit into allowed headings. The closest is Requirements (maybe includes physical demands). We'll add a
after the list maybe.
But we must not create a heading for Physical Demands. So we can add a
under Requirements after the list.
Similarly, the statement about "If you have what it takes..." is basically a call to action; we should remove application instructions. That line is an application instruction ("please apply today.") So we should remove that. Also "In return, WGI provides a competitive salary and an outstanding work environment." The competitive salary part we keep for Pay; the outstanding work environment maybe part of Benefits? But we already have benefits list; we could add a sentence about outstanding work environment as a
under Benefits? But it's vague. Might be considered filler? It's not a specific benefit. Might be okay to include as a prose under Benefits. But we already have benefits list; we could add a
after list: "WGI provides an outstanding work environment." That's substantive.
Now Pay: we have "competitive salary". We'll output a
under Pay heading.
Now ensure we don't include any duplicated lines: The responsibilities list includes some sentences that may be similar; we need to keep each distinct.
Let's extract responsibilities sentences from the posting:
"Lead MEP projects from inception through closeout, ensuring delivery on time, within budget, and to quality standards."
"Oversee the design, installation, and commissioning of mechanical, electrical, and plumbing systems across large-scale projects."
"Manage and mentor a team of M
for prose. We need to decide which sections to include: - About the role: combine introductory paragraphs about role and company culture. - Responsibilities: list of duties (the bullet-like sentences after "Lead MEP projects..."). - Requirements: maybe include education, experience, authorization, physical demands? Could also include Qualifications? Actually we have both Requirements and Qualifications as allowed headings. We need to decide what goes where. Typically Requirements are mandatory items; Qualifications are preferred. But we can split: Requirements: Bachelor's degree, 10+ years experience, authorized to work in US, PE license preferred? Actually PE license preferred is maybe Qualification. But we can put both under Requirements and Qualifications as needed. Better: Use Requirements for mandatory: Bachelor's degree, 10+ years experience, authorized to work in US, knowledge of codes, leadership skills, communication skills, proficiency in tools, ability to manage competing priorities. Use Qualifications for preferred: PE license preferred, PMP or equivalent certification accepted in lieu. Skills: maybe list of skills like leadership, communication, etc. But we already have those in Requirements. Could create Skills section for soft skills and technical skills. But we must avoid thin sections. Perhaps combine Requirements and Qualifications into one Requirements section? But we have both headings allowed; we can use both if we have distinct content. Let's extract: Mandatory (Requirements): - Bachelor of Science degree in Mechanical Engineering, Electrical Engineering, or a closely related field. - 10+ years of experience in MEP project management. - Strong knowledge of relevant mechanical, electrical, and plumbing codes and standards. - Proven leadership and team management skills with the ability to coordinate across multiple disciplines. - Excellent written and verbal communication skills; comfortable presenting to clients and senior stakeholders. - Proficiency in project management tools such as Procore, Autodesk Construction Cloud, or MS Project. - Ability to manage competing priorities across multiple active projects. - Applicants must be currently authorized to work in the U.S. on a full-time basis. (No sponsorship) Preferred (Qualifications): - Professional Engineer (PE) license preferred. - PMP or equivalent project management certification accepted in lieu. Skills: maybe we can list technical skills: knowledge of MEP codes, proficiency in PM tools, leadership, communication, etc. But that overlaps. Maybe we can have Skills section for technical and soft skills: "Strong knowledge of MEP codes and standards", "Leadership and team management", "Excellent written and verbal communication", "Proficiency in Procore, Autodesk Construction Cloud, MS Project", "Ability to manage competing priorities". But that's similar to Requirements. Better to keep Requirements as the list of mandatory qualifications, and Qualifications as preferred certifications. Skills maybe not needed. Benefits: we have list. Pay: we have "competitive salary". We'll include a paragraph. Schedule: none, so omit. About the role: combine intro and company culture. Now we need to remove duplicated lines: The posting includes some repeated sentences like "Lead MEP projects from inception through closeout, ensuring delivery on time, within budget, and to quality standards." and then "Oversee the design, installation, and commissioning of mechanical, electrical, and plumbing systems across large-scale projects." etc. Those are responsibilities. We need to format responsibilities as
- each.
Similarly benefits as
- .
Requirements as
- .
Qualifications as
- .
About the role as
prose (maybe multiple paragraphs). We'll wrap each paragraph in
. Now ensure we don't include boilerplate: Remove EEO, unsolicited resumes, vendor agreement, etc. Also remove "Physical Demands" heading? We'll incorporate physical demands description into Requirements maybe as a paragraph, but we need to decide if we want to include it. The physical demands description includes: "Work is performed in an office setting. Hand-eye coordination is necessary to operate a computer, keyboard and mouse. Use of a telephone headset will allow for virtual communication with team members through Zoom and/or Microsoft Teams. While performing the duties of this job, the employee is often required to sit for prolonged periods, use hands/fingers to handle, feel or operate objects, tools or controls and reach with hands and arms, speak and hear. Specific vision abilities required by this job include close vision, distance vision, color vision, peripheral vision, depth perception, and the ability to adjust focus." This is substantive but not a requirement per se; it's about work environment. Could be included under Requirements as a paragraph. However we might decide to omit because it's not strictly a requirement but it's still info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it. Where to put? Could be under Requirements as a paragraph (not list). Or we could create a separate section like "Work Environment" but not allowed heading. So we must fit into allowed headings. The closest is Requirements (maybe includes physical demands). We'll add a
after the list maybe. But we must not create a heading for Physical Demands. So we can add a
under Requirements after the list. Similarly, the statement about "If you have what it takes..." is basically a call to action; we should remove application instructions. That line is an application instruction ("please apply today.") So we should remove that. Also "In return, WGI provides a competitive salary and an outstanding work environment." The competitive salary part we keep for Pay; the outstanding work environment maybe part of Benefits? But we already have benefits list; we could add a sentence about outstanding work environment as a
under Benefits? But it's vague. Might be considered filler? It's not a specific benefit. Might be okay to include as a prose under Benefits. But we already have benefits list; we could add a
after list: "WGI provides an outstanding work environment." That's substantive. Now Pay: we have "competitive salary". We'll output a
under Pay heading. Now ensure we don't include any duplicated lines: The responsibilities list includes some sentences that may be similar; we need to keep each distinct. Let's extract responsibilities sentences from the posting: "Lead MEP projects from inception through closeout, ensuring delivery on time, within budget, and to quality standards." "Oversee the design, installation, and commissioning of mechanical, electrical, and plumbing systems across large-scale projects." "Manage and mentor a team of M
- .
About the role as
- .
Qualifications as
- .
Requirements as