Automation and Control System Developer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key content: - Intro paragraph about HDR culture, mission, etc. That's "About the role"? Actually "About the role" could be description of role and company. We'll put that in
under About the role heading. - Then description of Automation and Control Systems Applications Developer responsibilities: list of duties. - Preferred Qualifications list. - Required Qualifications list. - What We Believe (maybe part of About the role? Could be separate but not required heading; we could include under About the role as prose.) - Our Commitment (employee network groups, benefits description). Benefits: medical, dental, vision, short/long-term disability, life insurance, EAP, paid time away, parental leave, paid holidays, retirement savings plan with employer match, employee referral bonus, tuition reimbursement. Also mention comprehensive benefits package. - Pay: "The expected compensation range for this position depends upon skills, experience, education and geographical location. (Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits.) Montana: $66000- $94000". So we have pay range for Montana. So we can include Pay section with that range. - Schedule: "Schedule:Full-time". Also "Employee Status:Regular". So schedule: Full-time. - Location: Primary Location: United States-Montana-Missoula; Other Locations: Billings, Butte. Could be included in About the role or maybe separate but not required heading. We could include location in About the role paragraph. - Industry: Building Engineering. BusinessClass: Control Systems and OT Cybersecurity. Job Posting date: Aug 26, 2026. Might be metadata; we could drop or include in short p. We must not create sections with filler text. So we need to decide which sections have substantive content. Sections: - About the role: we have substantive description of role, company mission, location, etc. So include. - Responsibilities: we have list of duties (programming, testing, implementing, commissioning, coordination, etc). So include. - Requirements: could be split into Required Qualifications and Preferred Qualifications. But we have both. Could combine under Requirements or separate Qualifications and Skills. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements and Qualifications separate if needed. But we must not create empty sections. We have both Required and Preferred qualifications; we could put Required under Requirements, Preferred under Qualifications, or combine. Let's follow typical: Requirements = required qualifications; Qualifications = preferred qualifications; Skills maybe separate but we have skills listed in responsibilities and qualifications. Could omit Skills if no distinct list. Better to include Skills if we have specific skill list: e.g., PLC logic, HMI integration, ability to create/read logic and P&ID diagrams, etc. But those are already in responsibilities/qualifications. Might be redundant. Safer to include Skills section only if we have distinct skill bullet list not covered elsewhere. We have "Excellent communication, leadership and planning skills, and ability to thrive in a team environment." Also "Proficient with Microsoft Office". Also "Good verbal and written communication skills". Could be considered skills. But we could put them under Qualifications. Since we have both Required and Preferred qualifications, we can make Requirements = Required Qualifications, Qualifications = Preferred Qualifications. Then we might not need Skills. Benefits: we have substantive list. So include Benefits. Pay: we have compensation range for Montana. So include Pay. Schedule: we have Full-time. So include Schedule. We must not include headings with filler like "commensurate with experience". We have actual numbers. Now we need to output HTML fragment only, no /, no markdown fences. Structure:
About the role
... (combined intro, mission, location, industry, business class, posting date maybe)
Responsibilities
- ... ...
Requirements
- ... (required qualifications)
Qualifications
- ... (preferred qualifications)
Benefits
- ...
Pay
...
Schedule
Full-time
We need to ensure we don't repeat job title. Also we should not include "Job ID / requisition numbers". Not present. Now extract substantive content. About the role paragraph: combine: "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. The Automation and Control Systems Applications Developer will have responsibility for, programming, testing, implementing and commissioning the control system as designed. The Automation and Control Systems Applications Developer will be responsible for coordination of the control system with the Design team, construction team and Client. The individual must have proven experience in PLC logic and HMI integration in any of the following PLCs (Allen Bradley, Modicon, GE, Siemens, etc.) and HMIs (FactoryTalk, Wonderware, iFix, Ignition, VTScada, etc.). Must be able to create and read logic and P&ID diagrams for program design, programming, simulation, testing and startup. The ideal candidate will have a proven track record in programming as well as the ability to develop and implement standard engineering practices, as well as provide detailed documentation upon project completion. This person will be the project applications engineer and may be responsible for leading project task activities." But note that some of that is actually responsibilities and qualifications. Might be better to keep About the role as general company description, not include the specific role duties. However the instruction: "Preserve ALL substantive information". So we need to keep everything somewhere. If we put duties in Responsibilities section, we should not duplicate them in About the role. So we should trim About the role to exclude the detailed duties and qualifications that belong elsewhere. Thus About the role: include the introductory paragraphs about HDR culture, mission, building engineering, etc., up to before the specific role responsibilities start. Let's locate where the role-specific content begins: "The Automation and Control Systems Applications Developer will have responsibility for, programming, testing, implementing and commissioning the control system as designed." That's start of responsibilities. So About the role ends before that sentence. Thus About the role paragraph: combine everything before that. Let's copy: "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." Now we also have location info: "Primary Location:United States-Montana-Missoula Other Locations:United States-Montana-Billings, United States-Montana-Butte". Could add to About the role as a sentence. Also "Industry:Building Engineering" and "BusinessClass:Control Systems and OT Cybersecurity" and "Job Posting:Aug 26, 2026". Could include as metadata but maybe not needed. We could include location and industry in About the role. Now Responsibilities: list from the posting: - Programming the project control system as defined by the project scope – SCADA, PLC, HMI, Historian, Communications hardware, etc. - Manage project tasks within scope budget and schedule - Coordinate with Design, Construction and Start-up team leader for project control system - Download, test and document control system programs and communication systems as defined in scope - Participate in field testing and commissioning of the control system - Must be willing to travel as necessary. Duration of travel and frequency of travel will depend on project/HDR needs. We should keep each as