BMS Controls Mechanical Superintendent
Okland Construction · Salt Lake City, UT · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with sections using for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the description.
The posting includes:
- About Us (company description) – not a heading we need? The instruction: use
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the description.
The posting includes:
- About Us (company description) – not a heading we need? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. "About Us" could be considered "About the role"? Actually "About the role" is a heading for description of the role. The posting has "About This Opportunity" which describes role. So we can put that under About the role
.
- Responsibilities: The "YOUR DAY-TO-DAY" section lists duties. So we can put that under Responsibilities
with - .
- Requirements: The "YOU'RE READY FOR THIS ROLE IF YOU HAVE" lists qualifications: degree, experience, etc. That's requirements/qualifications. We can split into Requirements and Qualifications maybe. But we need to avoid thin sections. Could combine Requirements and Qualifications? The instruction says use those headings if content exists. We have both requirements (experience, degree) and qualifications (certifications). Could put under
Requirements
and Qualifications
if both have content. Let's see.
Requirements: Associate's or Bachelor's degree in Construction Management, Mechanical Engineering, Electrical Engineering, Building Automation, or a related field preferred. Equivalent industry experience will be considered. 8+ years of experience working with BAS, EMS, or DDC. Experience supporting commercial, healthcare, industrial, laboratory, mission-critical, institutional, or higher education construction projects. Strong understanding of commissioning processes, functional performance testing, controls integration, and MEP systems. Experience with BAS platforms such as Delta Controls, Johnson Controls, Siemens, Honeywell, Schneider Electric, Trane, Automated Logic, Tridium Niagara, or similar systems. OSHA 30 certification required.
Qualifications: Commissioning certification, LEED AP, or similar credentials preferred.
Thus we have both.
Skills: Not explicitly listed but could be implied from responsibilities: communication, problem solving, etc. But we should not invent. If no explicit skills section, we should not create Skills heading.
Benefits: The posting has "What We Offer" with subsections: Culture & Recognition, Pay, Ownership & Retirement, Benefits & Wellbeing, Perks & Projects. So we have Benefits content: Free healthcare plan option plus medical, dental, vision, life, and disability coverage, paid parental leave, financial wellness tools, Employee Assistance Program, and mental health support. Also culture & recognition etc. But we need to map to Benefits heading. The instruction: include a section ONLY when posting has real, specific content for it. So we can create Benefits
with list of benefits.
Pay: The posting mentions "Weekly pay, competitive salary and bonus incentives, ESOP employee ownership, and an industry-leading 401(k) with a 6% employer match." That's pay info. So we can create Pay
with that content.
Schedule: Not mentioned. No schedule info. So we should not create Schedule heading.
We also need to include maybe "About the role" heading with content from About This Opportunity.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: EEO statement, Visa and Sponsorship, Physical Environment? The physical environment is not part of required headings; we could drop it as it's not in the list. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop EEO statement, Visa and Sponsorship, Physical Environment (maybe considered not needed). Also "About Us" maybe not needed as heading but could be part of About the role? Actually About Us is company overview; we could include it under About the role? But the instruction says use headings for sections like About the role, Responsibilities, etc. So we can put company overview under About the role as well, or we could omit it. The posting includes "About Us" and "What Makes Okland Different?" That's company info. Might be considered part of About the role? The instruction: "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we can put the description of the role and maybe company overview under About the role. But we should preserve all substantive information; we cannot drop company overview if it's substantive. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." It doesn't say to drop company overview. So we should include it somewhere. Perhaps we can include it under About the role as a paragraph.
Thus structure:
About the role
Okland is a commercial general contractor... (About Us + What Makes Okland Different? + About This Opportunity)
But we need to ensure we don't include boilerplate like EEO etc.
Let's extract substantive paragraphs:
About Us: "Okland is a commercial general contractor and construction management company with more than 1,500 team members, delivering complex projects across healthcare, semiconductor, higher education, sports, hospitality, and other specialized markets. Founded in 1918 in Salt Lake City, we have grown for more than a century and operate throughout Utah, Arizona, and Idaho."
What Makes Okland Different? includes bullet-like paragraphs: "We Create Remarkable Experiences ...", "We Share Success ...", "We Build Better Together ...". We'll keep those as sentences.
About This Opportunity: "If you're a Building Automation Systems expert who enjoys solving complex technical challenges and partnering with project teams to deliver high-performing buildings, we'd love to connect with you. In this role, you'll serve as Okland's subject matter expert for BAS and controls systems, supporting projects from preconstruction through commissioning and closeout. You'll thrive if you have a strong background in controls integration, commissioning, and MEP coordination, and enjoy collaborating with owners, engineers, trade partners, and project teams to ensure successful project outcomes. This role is ideal for someone who can see potential issues before they become problems, communicate effectively with diverse stakeholders, and take pride in delivering exceptional building performance."
We can combine these into a few paragraphs.
Now Responsibilities: list from "YOUR DAY-TO-DAY". We'll extract each bullet.
Preconstruction & Planning Support pursuit, interview, and preconstruction efforts by providing Building Automation Systems expertise. Review controls specifications, sequences of operation, and design documents to identify scope gaps, risks, and coordination challenges. Assist estimating and operations teams with controls scope validation and trade partner evaluations.
Project Execution & Coordination Serve as the primary BAS and controls resource for project teams throughout construction. Coordinate with controls contractors, MEP trade partners, owners, engineers, commissioning agents, and IT teams to support successful system implementation. Track controls installation progress and proactively address schedule, quality, and integration issues.
Systems Integration & Commissioning Oversee integration of BAS with HVAC equipment, lighting controls, metering systems, power monitoring systems, and other building systems. Support programming reviews, graphics development, functional testing, commissioning activities, and project turnover. Troubleshoot controls and integration issues while helping project teams achieve quality, performance, and schedule objectives.
We'll make each bullet a - .
Now Requirements: list from "YOU'RE READY FOR THIS ROLE IF YOU HAVE" up to OSHA 30 certification required.
We'll break into items.
- Associate's or Bachelor's degree in Construction Management, Mechanical Engineering, Electrical Engineering, Building Automation, or a related field preferred. Equivalent industry experience will be considered.
- 8+ years of experience working with Building Automation Systems (BAS), Energy Management Systems (EMS), or Direct Digital Controls (DDC).
- Experience supporting commercial, healthcare, industrial, laboratory, mission-critical, institutional, or higher education construction projects.
- Strong understanding of commissioning processes, functional performance testing, controls integration, and MEP systems.
- Experience with BAS platforms such as Delta Controls, Johnson Controls, Siemens, Honeywell, Schneider Electric, Trane, Automated Logic, Tridium Niagara, or similar systems.
- OSHA 30 certification required.
Now Qualifications: Commissioning certification, LEED AP, or similar credentials preferred.
Now Benefits: from "What We Offer" subsections.
We have:
Culture & Recognition: Consistently recognized as a Best Place to Work in Utah, Arizona, and Idaho.
Pay, Ownership & Retirement: Weekly pay, competitive salary and bonus incentives, ESOP employee ownership, and an industry-leading 401(k) with a 6% employer match.
Benefits & Wellbeing: Free healthcare plan option plus medical, dental, vision, life, and disability coverage, paid parental leave, financial wellness tools, Employee Assistance Program, and mental health support.
Perks & Projects: Rewards including pro sports tickets, fitness memberships, travel vouchers, paid work anniversary sabbaticals, and award-winning projects recognized by AIA, ENR, and AGC.
We need to map to Benefits heading. Could list all these as bullet list under Benefits.
Pay heading: we already have Pay info; but we also have Pay, Ownership & Retirement subsection. Since we have a separate Pay heading, we could put the pay details there. However the Benefits heading could include everything else (culture, benefits, perks). But we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Pay, Ownership & Retirement, Benefits & Wellbeing, Perks & Projects, Culture & Recognition into a single Benefits section? But we also have a Pay heading separate. The instruction says include a section ONLY when posting has real, specific content for it. So we have content for Pay (weekly pay, competitive salary, bonus incentives, ESOP, 401k match). Also we have content for Benefits (healthcare, etc). So we should have both Pay and Benefits sections. The Culture & Recognition and Perks & Projects could go under Benefits as well, or we could make a separate Culture section but not in allowed headings. Since only allowed headings are those listed, we should fold Culture & Recognition and Perks & Projects into Benefits (or maybe Pay?). Probably Benefits is appropriate to include all non-pay benefits: culture, perks, health, etc.
Thus:
Pay
Weekly pay, competitive salary and bonus incentives, ESOP employee ownership, and an industry-leading 401(k) with a 6% employer match.
Benefits
- Consistently recognized as a Best Place to Work in Utah, Arizona, and Idaho.
- Free healthcare plan option plus medical, dental, vision, life, and disability coverage, paid parental leave, financial wellness tools, Employee Assistance Program, and mental health support.
- Rewards including pro sports tickets, fitness memberships, travel vouchers, paid work anniversary sabbaticals, and award-winning projects recognized by AIA, ENR, and AGC.
We could also include ESOP under Pay already.
Now we need to output only HTML fragment, no /, no markdown.
Thus final HTML:
About the role
...
Responsibilities
...
Requirements
...
Qualifications
...
Pay
...
Benefits
...
We should not include Schedule.
About the role
. - Responsibilities: The "YOUR DAY-TO-DAY" section lists duties. So we can put that underResponsibilities
with- .
- Requirements: The "YOU'RE READY FOR THIS ROLE IF YOU HAVE" lists qualifications: degree, experience, etc. That's requirements/qualifications. We can split into Requirements and Qualifications maybe. But we need to avoid thin sections. Could combine Requirements and Qualifications? The instruction says use those headings if content exists. We have both requirements (experience, degree) and qualifications (certifications). Could put under
Requirements
andQualifications
if both have content. Let's see. Requirements: Associate's or Bachelor's degree in Construction Management, Mechanical Engineering, Electrical Engineering, Building Automation, or a related field preferred. Equivalent industry experience will be considered. 8+ years of experience working with BAS, EMS, or DDC. Experience supporting commercial, healthcare, industrial, laboratory, mission-critical, institutional, or higher education construction projects. Strong understanding of commissioning processes, functional performance testing, controls integration, and MEP systems. Experience with BAS platforms such as Delta Controls, Johnson Controls, Siemens, Honeywell, Schneider Electric, Trane, Automated Logic, Tridium Niagara, or similar systems. OSHA 30 certification required. Qualifications: Commissioning certification, LEED AP, or similar credentials preferred. Thus we have both. Skills: Not explicitly listed but could be implied from responsibilities: communication, problem solving, etc. But we should not invent. If no explicit skills section, we should not create Skills heading. Benefits: The posting has "What We Offer" with subsections: Culture & Recognition, Pay, Ownership & Retirement, Benefits & Wellbeing, Perks & Projects. So we have Benefits content: Free healthcare plan option plus medical, dental, vision, life, and disability coverage, paid parental leave, financial wellness tools, Employee Assistance Program, and mental health support. Also culture & recognition etc. But we need to map to Benefits heading. The instruction: include a section ONLY when posting has real, specific content for it. So we can createBenefits
with list of benefits. Pay: The posting mentions "Weekly pay, competitive salary and bonus incentives, ESOP employee ownership, and an industry-leading 401(k) with a 6% employer match." That's pay info. So we can createPay
with that content. Schedule: Not mentioned. No schedule info. So we should not create Schedule heading. We also need to include maybe "About the role" heading with content from About This Opportunity. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: EEO statement, Visa and Sponsorship, Physical Environment? The physical environment is not part of required headings; we could drop it as it's not in the list. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop EEO statement, Visa and Sponsorship, Physical Environment (maybe considered not needed). Also "About Us" maybe not needed as heading but could be part of About the role? Actually About Us is company overview; we could include it under About the role? But the instruction says use headings for sections like About the role, Responsibilities, etc. So we can put company overview under About the role as well, or we could omit it. The posting includes "About Us" and "What Makes Okland Different?" That's company info. Might be considered part of About the role? The instruction: "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we can put the description of the role and maybe company overview under About the role. But we should preserve all substantive information; we cannot drop company overview if it's substantive. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." It doesn't say to drop company overview. So we should include it somewhere. Perhaps we can include it under About the role as a paragraph. Thus structure:
About the role
Okland is a commercial general contractor... (About Us + What Makes Okland Different? + About This Opportunity)
But we need to ensure we don't include boilerplate like EEO etc. Let's extract substantive paragraphs: About Us: "Okland is a commercial general contractor and construction management company with more than 1,500 team members, delivering complex projects across healthcare, semiconductor, higher education, sports, hospitality, and other specialized markets. Founded in 1918 in Salt Lake City, we have grown for more than a century and operate throughout Utah, Arizona, and Idaho." What Makes Okland Different? includes bullet-like paragraphs: "We Create Remarkable Experiences ...", "We Share Success ...", "We Build Better Together ...". We'll keep those as sentences. About This Opportunity: "If you're a Building Automation Systems expert who enjoys solving complex technical challenges and partnering with project teams to deliver high-performing buildings, we'd love to connect with you. In this role, you'll serve as Okland's subject matter expert for BAS and controls systems, supporting projects from preconstruction through commissioning and closeout. You'll thrive if you have a strong background in controls integration, commissioning, and MEP coordination, and enjoy collaborating with owners, engineers, trade partners, and project teams to ensure successful project outcomes. This role is ideal for someone who can see potential issues before they become problems, communicate effectively with diverse stakeholders, and take pride in delivering exceptional building performance." We can combine these into a few paragraphs. Now Responsibilities: list from "YOUR DAY-TO-DAY". We'll extract each bullet. Preconstruction & Planning Support pursuit, interview, and preconstruction efforts by providing Building Automation Systems expertise. Review controls specifications, sequences of operation, and design documents to identify scope gaps, risks, and coordination challenges. Assist estimating and operations teams with controls scope validation and trade partner evaluations. Project Execution & Coordination Serve as the primary BAS and controls resource for project teams throughout construction. Coordinate with controls contractors, MEP trade partners, owners, engineers, commissioning agents, and IT teams to support successful system implementation. Track controls installation progress and proactively address schedule, quality, and integration issues. Systems Integration & Commissioning Oversee integration of BAS with HVAC equipment, lighting controls, metering systems, power monitoring systems, and other building systems. Support programming reviews, graphics development, functional testing, commissioning activities, and project turnover. Troubleshoot controls and integration issues while helping project teams achieve quality, performance, and schedule objectives. We'll make each bullet a - .
Now Requirements: list from "YOU'RE READY FOR THIS ROLE IF YOU HAVE" up to OSHA 30 certification required.
We'll break into items.
- Associate's or Bachelor's degree in Construction Management, Mechanical Engineering, Electrical Engineering, Building Automation, or a related field preferred. Equivalent industry experience will be considered.
- 8+ years of experience working with Building Automation Systems (BAS), Energy Management Systems (EMS), or Direct Digital Controls (DDC).
- Experience supporting commercial, healthcare, industrial, laboratory, mission-critical, institutional, or higher education construction projects.
- Strong understanding of commissioning processes, functional performance testing, controls integration, and MEP systems.
- Experience with BAS platforms such as Delta Controls, Johnson Controls, Siemens, Honeywell, Schneider Electric, Trane, Automated Logic, Tridium Niagara, or similar systems.
- OSHA 30 certification required.
Now Qualifications: Commissioning certification, LEED AP, or similar credentials preferred.
Now Benefits: from "What We Offer" subsections.
We have:
Culture & Recognition: Consistently recognized as a Best Place to Work in Utah, Arizona, and Idaho.
Pay, Ownership & Retirement: Weekly pay, competitive salary and bonus incentives, ESOP employee ownership, and an industry-leading 401(k) with a 6% employer match.
Benefits & Wellbeing: Free healthcare plan option plus medical, dental, vision, life, and disability coverage, paid parental leave, financial wellness tools, Employee Assistance Program, and mental health support.
Perks & Projects: Rewards including pro sports tickets, fitness memberships, travel vouchers, paid work anniversary sabbaticals, and award-winning projects recognized by AIA, ENR, and AGC.
We need to map to Benefits heading. Could list all these as bullet list under Benefits.
Pay heading: we already have Pay info; but we also have Pay, Ownership & Retirement subsection. Since we have a separate Pay heading, we could put the pay details there. However the Benefits heading could include everything else (culture, benefits, perks). But we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Pay, Ownership & Retirement, Benefits & Wellbeing, Perks & Projects, Culture & Recognition into a single Benefits section? But we also have a Pay heading separate. The instruction says include a section ONLY when posting has real, specific content for it. So we have content for Pay (weekly pay, competitive salary, bonus incentives, ESOP, 401k match). Also we have content for Benefits (healthcare, etc). So we should have both Pay and Benefits sections. The Culture & Recognition and Perks & Projects could go under Benefits as well, or we could make a separate Culture section but not in allowed headings. Since only allowed headings are those listed, we should fold Culture & Recognition and Perks & Projects into Benefits (or maybe Pay?). Probably Benefits is appropriate to include all non-pay benefits: culture, perks, health, etc.
Thus:
Pay
Weekly pay, competitive salary and bonus incentives, ESOP employee ownership, and an industry-leading 401(k) with a 6% employer match.
Benefits
- Consistently recognized as a Best Place to Work in Utah, Arizona, and Idaho.
- Free healthcare plan option plus medical, dental, vision, life, and disability coverage, paid parental leave, financial wellness tools, Employee Assistance Program, and mental health support.
- Rewards including pro sports tickets, fitness memberships, travel vouchers, paid work anniversary sabbaticals, and award-winning projects recognized by AIA, ENR, and AGC.
About the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Pay
...
Benefits
- ...