Commissioning Technician

HDR · Wichita, KS · 3 wk ago

On-siteEngineeringFull-time

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". So we need to parse the posting. Let's extract content: Intro paragraph about HDR culture etc. That's about the role? Could be "About the role". The posting includes description of role: "As part of HDR’s Building Engineering Services Group, you’ll help design the critical infrastructure..." etc. Also "In the role of Commissioning Technician, we'll count on you to:" then list of duties. Then "Preferred Qualifications" list: Engineering degree, EIT, CxA Certification, or Equivalent, A strong controls background is highly desirable. Then "Required Qualifications": list of many items. Then "What We Believe" etc. That's more about company culture; could be part of About the role or maybe separate but not required heading. We can include as part of About the role. Then "Our Commitment" etc. Also culture. Then "Primary Location: United States-Kansas-Wichita", "Industry: Construction, Project Controls & Design/Build", "Schedule: Full-time", "Employee Status: Regular", "BusinessClass: Building Commissioning", "Job Posting: Sep 22, 2026". These are metadata; we can fold minor metadata into a short
or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include location, schedule, etc in a paragraph maybe under About the role or separate? Probably we can include them in a short
after the role description. We must not create Pay/Benefits/Schedule sections unless posting actually states them. Schedule is stated: "Schedule: Full-time". So we can include a Schedule section with that content. However the instruction says: "Prefer a few substantive sections over many thin ones." So maybe we can incorporate schedule into About the role paragraph rather than a separate thin section. But they said include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Schedule is specific: Full-time. So we could have a Schedule section with

Schedule

Full-time

. That's not filler. Similarly Benefits and Pay are not mentioned, so we should not create those sections. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we only include those with real content. Likely we have About the role (intro + role description), Responsibilities (list of duties), Requirements (maybe required qualifications), Qualifications (preferred qualifications), Skills (maybe list of skills like communication, troubleshooting, etc). Could combine some. Let's extract: About the role: The introductory paragraphs about HDR culture and role description: "At HDR, our employee-owners are fully engaged...". Also "As part of HDR’s Building Engineering Services Group, you’ll help design the critical infrastructure...". Also "This isn’t just a job, it’s a chance to lead innovation...". That's about the role. Responsibilities: The list after "In the role of Commissioning Technician, we'll count on you to:" includes items: - Verify systems are designed, installed, functionally tested and capable of being operated and maintained according to the owner’s operational needs - Adhere to project activity budgets, budgeted man-hours and execute commissioning services - Follow and exemplify site safety procedures - Coordinate with the client and assist the contractors in scheduling the commissioning activities: plans, pre-functional checklists, functional performance tests, training plans, O&M, record document and shop drawing reviews and opposed season testing - Assist commissioning leaders with various commissioning activities - Be the main contact between the client and HDR and direct and manage all Commissioning activities on the project - Perform other duties as needed We need to put each as

inside

. Qualifications: Preferred Qualifications list: Engineering degree, EIT, CxA Certification, or Equivalent, A strong controls background is highly desirable. Skills: Could be extracted from required qualifications that are skill-based: communication, time management, interpersonal, troubleshooting, report writing, etc. But we might combine skills into Requirements or Qualifications. However we have a separate Skills section possible. We could list skills like: Strong written, verbal communication; time management; exceptional interpersonal; ability to interact with people at all levels; troubleshooting HVAC, TAB, Controls; report writing; proficiency with Microsoft Office Suite; multitasking; valid driver's license; etc. But many of those are already in Required Qualifications. To avoid duplication, we could treat Required Qualifications as Requirements, and Preferred Qualifications as Qualifications, and Skills maybe not needed. But we need to decide. Given instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one section? But they ask to use headings for those categories if content exists. We have content for both Required and Preferred. So we can have Requirements (required qualifications) and Qualifications (preferred qualifications). Skills maybe not needed if we already covered. But we could still include Skills if we have distinct skill content not captured elsewhere. However the required qualifications already include many skills; we could still have Skills section but risk duplication. Better to omit Skills section if not distinct. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. We must not include Benefits, Pay unless present. Not present. Now we need to output HTML fragment only, no /, no markdown. We'll produce:
About the role

...
Then
Responsibilities
Then
Requirements
Then
Qualifications
Then
Schedule
Full-time
We need to ensure we preserve all substantive info. Let's craft About the role paragraph(s). Could be multiple
elements. We'll combine into maybe two paragraphs. About the role content: - At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? Watch Our Story: https://www.hdrinc.com/our-story' Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world. We believe building engineering is more than systems and structures, it’s about powering progress and enabling innovation. As part of HDR’s Building Engineering Services Group, you’ll help design the critical infrastructure that supports the digital age and shapes the spaces where people work, connect, and thrive. From high-performance data centers driving the future of AI to dynamic commercial environments, your work will directly support technological advancement, sustainability, and human experience. We bring together mechanical, electrical, structural, and civil engineering experts to solve complex design challenges with precision, creativity, and collaboration. Whether you're optimizing energy efficiency, integrating resilient systems, or engineering the backbone of next-generation facilities, your contributions will help define the future of the built environment. This isn’t just a job, it’s a chance to lead innovation, engineer impact, and build a legacy of excellence. We should remove the URL maybe? The instruction: remove boilerplate, navigation, legal, EEO, etc. The URL is part of the story link; it's not boilerplate but maybe considered navigation? It's a link to Our Story. Might be considered optional but we can keep as part of description? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The URL is not necessarily boilerplate; it's a link to Our Story. Might be okay to keep. But we could drop it as it's not essential. However we need to preserve ALL substantive information; the link is substantive? It's a reference to Our Story; maybe not essential. I'd keep it as plain text without markdown. Could keep as plain text. We'll include as is. Now Responsibilities list: we need to capture each bullet exactly. Let's list them: 1. Verify systems are designed, installed, functionally tested and capable of being operated and maintained according to the owner’s operational needs 2. Adhere to project activity budgets, budgeted man-hours and execute commissioning services 3. Follow and exemplify site safety procedures 4. Coordinate with the client and assist the contractors in scheduling the commissioning activities: plans, pre-functional checklists, functional performance tests, training plans, O&M, record document and shop drawing reviews and opposed season testing 5. Assist commissioning leaders with various commissioning activities 6. Be the main contact between the client and HDR and direct and manage all Commissioning activities on the project 7. Perform other duties as needed Note: there is a typo "opposed season testing" maybe "opposed season testing"? We'll keep as is. Now Requirements list (Required Qualifications): - A minimum of 4 years of industry experience dealing with mechanical, electrical and controls disciplines - Proven ability to lead commissioning efforts from design through project completion - Should have a passion for sustainability and knowledge of the commissioning process and experience with design, installation and operation of building systems (including but not limited to: HVAC, electrical, mechanical, and controls) - Must be willing to travel to site-based locations as reasonably based on HDR needs - Must have demonstrated ability to troubleshoot HVAC, TAB, and Controls and have excellent report writing skills - Must have a solid understanding of operational requirements, safety requirements, code inspections and maintenance considerations - Strong written, verbal communication and time management skills; exceptional interpersonal skills; ability to interact with people at all levels - Technical knowledge of MEP systems and HVAC expertise - Proficiency with Microsoft Office Suite - Multitasking ability - Valid driver's license - An attitude and commitment to being an active participant of our employee-owned culture is a must We need to preserve all. Now Qualifications list (Preferred Qualifications): - Engineering degree - EIT, CxA Certification, or Equivalent - A strong controls background is highly desirable Now Schedule: Full-time. We might also include Location etc as a short paragraph maybe under About the role or separate? The instruction: fold minor metadata into a short
or drop it. We could add a
after About the role: "Primary Location: United States-Kansas-Wichita; Industry: Construction, Project Controls & Design/Build; Employee Status: Regular; Business Class: Building Commissioning; Job Posting: Sep 22, 20

Commissioning Technician

Schedule

About the role

Responsibilities

Requirements

Qualifications

Schedule

Similar jobs