Electrical Engineer - Mission Critical Facilities
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience". Not present.
We need to decide which sections to include:
- About the role: could be the "Your Opportunity" paragraph describing role. That's substantive.
- Responsibilities: "Your Key Responsibilities" list.
- Requirements: maybe "Capabilities and Credentials" includes capabilities and credentials; also "Education and Experience". Could combine into Requirements or Qualifications. The instruction lists both Requirements and Qualifications as possible headings. We need to decide which to use. Probably we can have Requirements (capabilities and credentials) and Qualifications (education and experience). Or we could combine into one Requirements section. But we should follow instruction: prefer a few substantive sections over many thin ones. So maybe combine capabilities and education into one "Requirements" section. However we also have Skills maybe separate? The posting includes capabilities like software proficiency etc. Could be Skills. But we can treat them as Requirements.
We also have Pay section: pay ranges.
Benefits section: benefits summary.
Schedule: schedule full time.
We should not include About Stantec as a heading unless we map to About the role? Actually About the role is about the role, not company. The posting includes "About Stantec" which is company overview. Could be considered "About the role"? Not exactly. But we could include a section "About Stantec" but not in allowed headings list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. Probably we should stick to those. The "About Stantec" could be considered "About the role"? Not really. Might be better to omit it as it's not required; but we must preserve ALL substantive information. If we omit About Stantec, we lose substantive info about company. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include that info somewhere. Could we include it as a
under a generic heading? Perhaps we can include a section "About Stantec" as a heading, but 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. So we can use other headings if needed. But better to follow the spirit: use those headings for those types of content. For company description, we could use "About Stantec" as a heading. That seems reasonable.
Thus sections: About Stantec, About the role (Your Opportunity), Responsibilities, Requirements (Capabilities and Credentials + Education and Experience), Benefits, Pay, Schedule.
We need to ensure we don't create thin sections. Each has substantive content.
Now we need to extract content.
Let's parse the posting.
Stantec’s Buildings team is on a mission... (intro). Then "Join us and design your place with Stantec." Then "Your Opportunity The MCF (Mission Critical Facilities) Engineer performs technical duties under the supervision of a Senior Project Engineer or Project Engineer. Understands and identifies project requirements and performs independent technical work within one’s own discipline. Provides guidance to Designers on completion of duties. The data center industry is continually evolving, and this is an ideal opportunity for candidates who enjoy working on technically challenging projects that require cutting edge designs. Aside from the preferred locations listed, this position is open to any location with a Stantec office presence, for the right candidate."
That's the role description.
Then "Your Key Responsibilities" list bullet points (starting with "Develops basic system designs...").
Then "Capabilities and Credentials" list (starting with "Possess basic knowledge of engineering practices...").
Then "Education and Experience" list (starting with "Accredited engineering degree or equivalent experience required.").
Then "This description is not a comprehensive listing..." (boilerplate, we should remove).
Then "About Stantec" paragraph.
Then "Pay Range Locations in CO, HI, IL, MD & Various CA, NJ, VA Areas-$100,000.00 - $145,000.00 Annually Locations in WA, DC & Various CA, MA, VA Areas-$107,300.00 - $155,500.00 Annually Pay Transparency: In compliance with pay transparency laws, pay ranges are provided for positions in locations where required. Please note, the final agreed upon compensation is based on individual education, qualifications, experience, and work location. At Stantec certain roles are bonus eligible. Actual compensation for part-time roles will be pro-rated based on the agreed number of working hours per week."
Then "Benefits Summary: Regular full-time and part-time employees (working at least 20 hours per week) have access to medical, dental, and vision plans, a wellness program, health saving accounts, flexible spending accounts, 401(k) plan, employee stock purchase program, life and accidental death & dismemberment (AD&D) insurance, short-term/long-term disability plans, emergency travel benefits, tuition reimbursement, professional membership fee coverage and paid family leave. Regular full-time and part-time employees will receive ten paid holidays in each calendar year. In addition, employees will be eligible to accrue vacation between 10 and 20 days per year and eligible for paid sick leave (and if more generous, in accordance with state and local law). Temporary/casual employees have access to 401(k) plans, employee stock purchase program, and paid leave, in accordance with state and local law. The benefits information listed above may not apply to union positions because benefits for such positions are governed by applicable collective bargaining agreements"
Then "Primary Location: United States | IL | Chicago Other Locations: United States | OR | Portland Organization: BC-2357 Buildings-US North Central MCF Employee Status: Regular Business Justification: New Position Travel: No Schedule: Full time Job Posting: 01/09/2026 07:09:08 Req ID: 1007522 #additional"
Then EEO boilerplate etc to remove.
We need to keep schedule: "Schedule: Full time". So we can have a Schedule section with that.
We also have location info maybe not needed as heading; could be included in a paragraph under About the role or maybe not needed. The instruction says do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So location could be minor metadata; we could include in a short p under About the role or maybe drop. But we need to preserve ALL substantive information. Location is substantive? Possibly yes. But we could include it in a paragraph under About the role or maybe under a separate "Location" heading not in list. However we can incorporate location into About the role paragraph: "Aside from the preferred locations listed, this position is open to any location with a Stantec office presence, for the right candidate." Already includes location info. The specific primary location Chicago and other location Portland could be considered metadata; we could keep them in a short p.
But we need to avoid duplication. The posting already mentions "Aside from the preferred locations listed, this position is open to any location with a Stantec office presence, for the right candidate." That's generic. Then later they give Primary Location and Other Locations. That's more specific. We should keep that.
Thus we could add a short paragraph after About the role: "
Primary Location: Chicago, IL. Other Locations: Portland, OR.
" Or similar.
Now we need to format lists.
Responsibilities list: each bullet starts with a verb. We'll put each as - .
Capabilities and Credentials list: each bullet.
Education and Experience list: each bullet.
Benefits: it's a prose paragraph with many items separated by commas. Could be a list but it's a summary; we could keep as
. However instruction: use
- for any list of duties/requirements/benefits. Benefits is a list of benefits; we could turn into
- . But the benefits summary includes many items; we could split into list items. However the instruction says "any list of duties/requirements/benefits". So we should treat benefits as a list. Let's extract each benefit item.
Benefits Summary text: "Regular full-time and part-time employees (working at least 20 hours per week) have access to medical, dental, and vision plans, a wellness program, health saving accounts, flexible spending accounts, 401(k) plan, employee stock purchase program, life and accidental death & dismemberment (AD&D) insurance, short-term/long-term disability plans, emergency travel benefits, tuition reimbursement, professional membership fee coverage and paid family leave. Regular full-time and part-time employees will receive ten paid holidays in each calendar year. In addition, employees will be eligible to accrue vacation between 10 and 20 days per year and eligible for paid sick leave (and if more generous, in accordance with state and local law). Temporary/casual employees have access to 401(k) plans, employee stock purchase program, and paid leave, in accordance with state and local law. The benefits information listed above may not apply to union positions because benefits for such positions are governed by applicable collective bargaining agreements"
We could break into items: medical, dental, vision plans; wellness program; health saving accounts; flexible spending accounts; 401(k) plan; employee stock purchase program; life and AD&D insurance; short-term/long-term disability plans; emergency travel benefits; tuition reimbursement; professional membership fee coverage; paid family leave; ten paid holidays; vacation accrual 10-20 days per year; paid sick leave; temporary/casual employees access to 401(k) plans, employee stock purchase program, paid leave (per state/local law). Also note about union positions.
We could keep as a paragraph to avoid over-splitting. But instruction says use
- for any list of benefits. So we should make a list.
We'll create
with - items summarizing each.
Now Pay section: we have two pay ranges based on location. We'll present as
maybe with two lines.
Schedule:
Full time
.
Now About Stantec: we have paragraph.
Now About the role: we have paragraph from "Your Opportunity".
for prose. We must include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience". Not present. We need to decide which sections to include: - About the role: could be the "Your Opportunity" paragraph describing role. That's substantive. - Responsibilities: "Your Key Responsibilities" list. - Requirements: maybe "Capabilities and Credentials" includes capabilities and credentials; also "Education and Experience". Could combine into Requirements or Qualifications. The instruction lists both Requirements and Qualifications as possible headings. We need to decide which to use. Probably we can have Requirements (capabilities and credentials) and Qualifications (education and experience). Or we could combine into one Requirements section. But we should follow instruction: prefer a few substantive sections over many thin ones. So maybe combine capabilities and education into one "Requirements" section. However we also have Skills maybe separate? The posting includes capabilities like software proficiency etc. Could be Skills. But we can treat them as Requirements. We also have Pay section: pay ranges. Benefits section: benefits summary. Schedule: schedule full time. We should not include About Stantec as a heading unless we map to About the role? Actually About the role is about the role, not company. The posting includes "About Stantec" which is company overview. Could be considered "About the role"? Not exactly. But we could include a section "About Stantec" but not in allowed headings list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. Probably we should stick to those. The "About Stantec" could be considered "About the role"? Not really. Might be better to omit it as it's not required; but we must preserve ALL substantive information. If we omit About Stantec, we lose substantive info about company. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include that info somewhere. Could we include it as a
under a generic heading? Perhaps we can include a section "About Stantec" as a heading, but 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. So we can use other headings if needed. But better to follow the spirit: use those headings for those types of content. For company description, we could use "About Stantec" as a heading. That seems reasonable. Thus sections: About Stantec, About the role (Your Opportunity), Responsibilities, Requirements (Capabilities and Credentials + Education and Experience), Benefits, Pay, Schedule. We need to ensure we don't create thin sections. Each has substantive content. Now we need to extract content. Let's parse the posting. Stantec’s Buildings team is on a mission... (intro). Then "Join us and design your place with Stantec." Then "Your Opportunity The MCF (Mission Critical Facilities) Engineer performs technical duties under the supervision of a Senior Project Engineer or Project Engineer. Understands and identifies project requirements and performs independent technical work within one’s own discipline. Provides guidance to Designers on completion of duties. The data center industry is continually evolving, and this is an ideal opportunity for candidates who enjoy working on technically challenging projects that require cutting edge designs. Aside from the preferred locations listed, this position is open to any location with a Stantec office presence, for the right candidate." That's the role description. Then "Your Key Responsibilities" list bullet points (starting with "Develops basic system designs..."). Then "Capabilities and Credentials" list (starting with "Possess basic knowledge of engineering practices..."). Then "Education and Experience" list (starting with "Accredited engineering degree or equivalent experience required."). Then "This description is not a comprehensive listing..." (boilerplate, we should remove). Then "About Stantec" paragraph. Then "Pay Range Locations in CO, HI, IL, MD & Various CA, NJ, VA Areas-$100,000.00 - $145,000.00 Annually Locations in WA, DC & Various CA, MA, VA Areas-$107,300.00 - $155,500.00 Annually Pay Transparency: In compliance with pay transparency laws, pay ranges are provided for positions in locations where required. Please note, the final agreed upon compensation is based on individual education, qualifications, experience, and work location. At Stantec certain roles are bonus eligible. Actual compensation for part-time roles will be pro-rated based on the agreed number of working hours per week." Then "Benefits Summary: Regular full-time and part-time employees (working at least 20 hours per week) have access to medical, dental, and vision plans, a wellness program, health saving accounts, flexible spending accounts, 401(k) plan, employee stock purchase program, life and accidental death & dismemberment (AD&D) insurance, short-term/long-term disability plans, emergency travel benefits, tuition reimbursement, professional membership fee coverage and paid family leave. Regular full-time and part-time employees will receive ten paid holidays in each calendar year. In addition, employees will be eligible to accrue vacation between 10 and 20 days per year and eligible for paid sick leave (and if more generous, in accordance with state and local law). Temporary/casual employees have access to 401(k) plans, employee stock purchase program, and paid leave, in accordance with state and local law. The benefits information listed above may not apply to union positions because benefits for such positions are governed by applicable collective bargaining agreements" Then "Primary Location: United States | IL | Chicago Other Locations: United States | OR | Portland Organization: BC-2357 Buildings-US North Central MCF Employee Status: Regular Business Justification: New Position Travel: No Schedule: Full time Job Posting: 01/09/2026 07:09:08 Req ID: 1007522 #additional" Then EEO boilerplate etc to remove. We need to keep schedule: "Schedule: Full time". So we can have a Schedule section with that. We also have location info maybe not needed as heading; could be included in a paragraph under About the role or maybe not needed. The instruction says do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So location could be minor metadata; we could include in a short p under About the role or maybe drop. But we need to preserve ALL substantive information. Location is substantive? Possibly yes. But we could include it in a paragraph under About the role or maybe under a separate "Location" heading not in list. However we can incorporate location into About the role paragraph: "Aside from the preferred locations listed, this position is open to any location with a Stantec office presence, for the right candidate." Already includes location info. The specific primary location Chicago and other location Portland could be considered metadata; we could keep them in a short p. But we need to avoid duplication. The posting already mentions "Aside from the preferred locations listed, this position is open to any location with a Stantec office presence, for the right candidate." That's generic. Then later they give Primary Location and Other Locations. That's more specific. We should keep that. Thus we could add a short paragraph after About the role: "
Primary Location: Chicago, IL. Other Locations: Portland, OR.
" Or similar. Now we need to format lists. Responsibilities list: each bullet starts with a verb. We'll put each as. However instruction: use
- for any list of duties/requirements/benefits. Benefits is a list of benefits; we could turn into
- . But the benefits summary includes many items; we could split into list items. However the instruction says "any list of duties/requirements/benefits". So we should treat benefits as a list. Let's extract each benefit item.
Benefits Summary text: "Regular full-time and part-time employees (working at least 20 hours per week) have access to medical, dental, and vision plans, a wellness program, health saving accounts, flexible spending accounts, 401(k) plan, employee stock purchase program, life and accidental death & dismemberment (AD&D) insurance, short-term/long-term disability plans, emergency travel benefits, tuition reimbursement, professional membership fee coverage and paid family leave. Regular full-time and part-time employees will receive ten paid holidays in each calendar year. In addition, employees will be eligible to accrue vacation between 10 and 20 days per year and eligible for paid sick leave (and if more generous, in accordance with state and local law). Temporary/casual employees have access to 401(k) plans, employee stock purchase program, and paid leave, in accordance with state and local law. The benefits information listed above may not apply to union positions because benefits for such positions are governed by applicable collective bargaining agreements"
We could break into items: medical, dental, vision plans; wellness program; health saving accounts; flexible spending accounts; 401(k) plan; employee stock purchase program; life and AD&D insurance; short-term/long-term disability plans; emergency travel benefits; tuition reimbursement; professional membership fee coverage; paid family leave; ten paid holidays; vacation accrual 10-20 days per year; paid sick leave; temporary/casual employees access to 401(k) plans, employee stock purchase program, paid leave (per state/local law). Also note about union positions.
We could keep as a paragraph to avoid over-splitting. But instruction says use
- for any list of benefits. So we should make a list.
We'll create
- with
- items summarizing each.
Now Pay section: we have two pay ranges based on location. We'll present as
maybe with two lines. Schedule:
Full time
. Now About Stantec: we have paragraph. Now About the role: we have paragraph from "Your Opportunity".
- items summarizing each.
Now Pay section: we have two pay ranges based on location. We'll present as
- for any list of benefits. So we should make a list.
We'll create
- . But the benefits summary includes many items; we could split into list items. However the instruction says "any list of duties/requirements/benefits". So we should treat benefits as a list. Let's extract each benefit item.
Benefits Summary text: "Regular full-time and part-time employees (working at least 20 hours per week) have access to medical, dental, and vision plans, a wellness program, health saving accounts, flexible spending accounts, 401(k) plan, employee stock purchase program, life and accidental death & dismemberment (AD&D) insurance, short-term/long-term disability plans, emergency travel benefits, tuition reimbursement, professional membership fee coverage and paid family leave. Regular full-time and part-time employees will receive ten paid holidays in each calendar year. In addition, employees will be eligible to accrue vacation between 10 and 20 days per year and eligible for paid sick leave (and if more generous, in accordance with state and local law). Temporary/casual employees have access to 401(k) plans, employee stock purchase program, and paid leave, in accordance with state and local law. The benefits information listed above may not apply to union positions because benefits for such positions are governed by applicable collective bargaining agreements"
We could break into items: medical, dental, vision plans; wellness program; health saving accounts; flexible spending accounts; 401(k) plan; employee stock purchase program; life and AD&D insurance; short-term/long-term disability plans; emergency travel benefits; tuition reimbursement; professional membership fee coverage; paid family leave; ten paid holidays; vacation accrual 10-20 days per year; paid sick leave; temporary/casual employees access to 401(k) plans, employee stock purchase program, paid leave (per state/local law). Also note about union positions.
We could keep as a paragraph to avoid over-splitting. But instruction says use