Staff Automation and Controls Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Valar Atomics" intro, then "The Team", "The Role", "Key Responsibilities", "Basic Qualifications", "Preferred Skills and Experience", "What We Offer", then salary line. We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. We need to decide which sections to include based on content. We have content: About Valar Atomics (company description). Could map to "About the role"? Actually "About Valar Atomics" is company overview, not role. Could be "About the role"? But we have "The Role" heading. So we can have sections: About the company? Not in list but we can use "About the role"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use those headings if appropriate. We need to include a section only when posting has real, specific content for it. We have: - About Valar Atomics (company description) -> could be "About the role"? Not exactly. Maybe we can treat as "About the role" but it's about company. Could also omit if not matching. But we need to preserve all substantive information; we cannot drop company description. So we need a heading for it. The allowed headings list includes "About the role". We could use that, even though it's about company, but it's okay. Or we could create a custom heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those exact headings when applicable. It doesn't forbid other headings, but likely they want those. We'll use "About the role" for company overview. Then "The Team" could be part of "About the role" or maybe we can merge. But we have separate "The Team" description. Could be part of "About the role". We'll include it under same section. Then "The Role" heading: we can use "Responsibilities"? Actually "The Role" includes description of role. Could be "About the role" already used. Maybe we should use "Responsibilities" for key responsibilities. But we have "Key Responsibilities" separate. So we can have: - About the role (company + team + role overview) - Responsibilities (Key Responsibilities) - Requirements (Basic Qualifications) - Skills (Preferred Skills and Experience) - Benefits (What We Offer) - Pay (Salary line) Schedule not present, so omit. We must not include headings with filler text. Ensure each heading has substantive content. We need to use

• for any list of duties/requirements/benefits. So for responsibilities, requirements, skills, benefits we need to convert to lists where appropriate. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details, but we can format as lists. We need to avoid boilerplate: EEO statement, etc. Remove that. Also remove application instructions, cookie/navigation/legal etc. Not present. We need to output only HTML fragment. Let's extract content. Company description: "About Valar AtomicsAt Valar Atomics, we're redefining what's possible in energy. Our mission is to make clean, high-temperature nuclear power scalable—unlocking abundant energy for industry, hydrogen, and next-generation manufacturing. We are a team of builders, engineers, and operators who believe nuclear energy should be fast to deploy, factory-made, and built for the real world. Our first pilot plant in Orangeville, Utah will demonstrate how advanced nuclear systems and fuel fabrication can power the future. Joining Valar Atomics means becoming part of a company where autonomy, ownership, and impact exist at every level." Team description: "The Team You will be joining Valar Atomics' Automation and Controls team within the Instrumentation, Control & Electrical (IC&E) organization. Automation and Controls own the logic and data layer PLC and DCS application code, ISA-88 batch sequences, SCADA and HMI applications, historian infrastructure, and enterprise integration across the reactor program and fuel manufacturing operations. You will work alongside I&C Hardware, electrical, process, and nuclear safety engineers in an environment that blends traditional control systems with modern software and data integration practice. As a staff engineer, you will be one of the technical anchors of this team: the engineer others come to when the problem is novel, ambiguous, or high-consequence. The team values operator-focused design, data integrity, disciplined documentation, and a safety-first culture." Role description (The Role): "The RoleValar Atomics is seeking Staff Automation and Controls Engineers to serve as discipline technical authorities for control system software across our reactor and nuclear fuel manufacturing facilities. The role spans the full controls software domain: PLC and DCS programming, SCADA and HMI applications, ISA-88 batch control, alarm management, safety logic, historians, enterprise integration, and OT infrastructure, from capital project execution through ongoing plant operations. This is a staff position: in addition to owning the most complex controls software scope end-to-end, you will set the coding standards, template libraries, and configuration management practices the discipline runs on, lead resolution of first-of-a-kind plant control problems where no established solution exists, review and approve the work of other engineers, and provide technical direction and mentorship across the software team. You are accountable not only for your own code, but for the technical quality and consistency of controls software across projects and sites." Key Responsibilities (list): "Technical Leadership and Discipline Ownership Serve as the responsible engineer and discipline technical authority for controls software on assigned systems; review and approve PLC/DCS application code, SCADA applications, safety logic, and test documentation produced by other engineers, contractors, and integrators. Establish, maintain, and enforce discipline software standards including application coding standards, template and UDT libraries, the ISA-101/HPHMI display style guide, alarm philosophy implementation standards, testing standards, and the software configuration management and change control practice used across projects and sites. Lead control strategy and software architecture development for first-of-a-kind plant control problems where no established solution exists, including control approach trade studies, platform capability evaluation, prototyping, and validation planning. Lead controls software participation in interdisciplinary design reviews, HAZOP studies, control narrative reviews, and licensing-support activities; represent the discipline's position and own the resolution of cross-discipline technical conflicts. Define the controls platform and integrator strategy, including SCADA and PLC platform standardization, system integrator qualification and oversight approach, make-or-buy evaluations, and framework specifications that constrain downstream project work. Mentor senior and junior software engineers; run the structured code review practice; develop discipline training and qualification approaches; contribute to hiring and technical interviewing for the software team. Design and Engineering Execution Own the PLC and DCS application architecture for assigned facilities — program structure, task and scan organization, template and library design, and inter-controller coordination on platforms such as Rockwell ControlLogix, Siemens S7/TIA Portal, Emerson, or equivalent, per IEC 61131-3. Own SCADA application architecture on platforms such as Ignition, FactoryTalk, AVEVA, or WinCC, including tag database and UDT design, scripting architecture, template systems, and server, client, and redundancy architecture. Own the HMI design system to ISA-101 and HPHMI principles — display hierarchy, navigation model, faceplate standards, and situational awareness approach — and approve display packages against it. Own the ISA-88 batch architecture including the equipment model, phase and equipment module design patterns, recipe management strategy, arbitration, and material tracking; approve batch application designs and lead complex sequence development. Own the alarm system to ISA-18.2, including leadership of alarm rationalization, philosophy implementation, shelving and suppression design, and alarm performance KPI programs. Develop, configure, and functionally test safety logic on SIS platforms (Rockwell GuardLogix, Siemens F-CPU, Triconex, or equivalent) in accordance with IEC 61511; own the safety application software validation regime and approve safety logic changes within delegated authority. Own historian architecture (OSIsoft PI / AVEVA PI, Ignition Historian, or equivalent) including asset framework modelling strategy, data quality and compression standards, and the operational reporting and dashboard framework. Own ISA-95 enterprise-control integration architecture including interface design between control systems and MES, ERP, and LIMS, and the API and database interface standards used to implement them. Own OT network architecture and cybersecurity controls in accordance with IEC 62443 or NIST SP 800-82, including zone and conduit design, role-based access control, secure protocol configuration, and the patching and allow-listing program, coordinating with the OT/Infrastructure function. Testing, Commissioning, and Operations Develop and approve software FAT, SAT, and commissioning test plans; lead test execution and witness contractor and integrator testing; own the quality of turnover and as-built software documentation including functional specifications, control narratives, cause-and-effect matrices, and alarm databases. Lead diagnosis and root cause analysis of the most complex control system software faults, communication failures, logic defects, sequence stalls, historian data gaps, and performance issues, and feed lessons learned back into standards, templates, and test practice. Coordinate with I&C Hardware Engineers on I/O assignment, tag naming, signal scaling, and loop commissioning to ensure control logic and field hardware are consistent; own the software side of the change control interface between logic and field configuration. Provide technical direction to contractors, integrators, and consultants on controls software scope; review, redline, and approve their deliverables to ensure compliance with project standards and nuclear quality requirements. Maintain disciplined engineering records consistent with nuclear quality requirements, ensuring traceability of design decisions, software changes, and test results." Basic Qualifications (list): "Bachelor's degree in Electrical, Electronic, Computer, Systems Engineering, Computer Science, or a related discipline. 8+ years of controls software, PLC programming, or SCADA development experience in process industries. Demonstrated end-to-end ownership of the controls software scope on at least one major capital project, from functional specification through commissioning and startup. Track record of technical leadership: running structured code review, checking and approving the work of other engineers or integrators, and setting or improving software standards, template libraries, or configuration management practice. Expert-level PLC programming on at least one major platform (Rockwell, Siemens, Emerson, or equivalent) across the IEC 61131-3 languages, including application architecture and library design, not just code authorship. Expert-level SCADA application development on at least one major platform (Ignition, FactoryTalk, AVEVA, WinCC, or equivalent), including architecture-level design of tag structures, templates, and redundancy. Experience developing safety logic under IEC 61511 within a formal software validation and functional test regime. Experience leading alarm rationalization or owning an alarm system to ISA-18.2, and designing HMI systems to ISA-101 or HPHMI principles. Experience developing ISA-88 batch software at the architecture level (equipment models, recipe strategy), not just phase implementation. Working knowledge of OT network architecture and cybersecurity practice under IEC 62443 or NIST SP 800-82. Experience configuring plant historians and designing asset framework or equivalent data models. Experience mentoring, directing, or supervising the technical work of other engineers or integrators." Preferred Skills and Experience (list): "Ignition Certified Designer, Rockwell Automation Certified Programmer, Siemens TIA Portal certification, or equivalent platform certification. ISA Certified Automation Professional (CAP) or equivalent credentials. Professional Engineer (PE) license. Experience developing control strategies or software architecture for first-of-a-kind processes or plants without established precedent. Experience with OSIsoft PI / AVEVA PI including PI AF asset framework design and PI Web API. Experience with SQL, Python, and REST APIs applied