The company is a young startup working to make clean, high-temperature nuclear power scalable for industry, hydrogen, and next-generation manufacturing.
Its first pilot plant in Orangeville, Utah is meant to prove out advanced nuclear systems and fuel fabrication.
The Instrumentation and Controls team sits within Engineering and designs the systems that monitor, automate, and protect the company's facilities and reactor technologies.
The team builds dependable control architectures for safe and efficient operation.
Responsibilities
Before its third anniversary, the company designed, built, commissioned, and operated a DOE-authorized research reactor outside the national laboratory system.
Turn operating needs into sound technical decisions, practical designs, and standards that execution teams can apply.
Set out how systems should be built and verified, and explain the engineering reasoning behind them.
Settle open or conflicting questions through implementation, either within one specialty or across several connected disciplines.
OT Engineering covers power and rack infrastructure, compute, networks, identity, physical and cyber security, operational data, and industrial software platforms such as FactoryTalk.
For FactoryTalk, the work covers backend deployment, configuration, integration, and recovery.
PLC programming and controls-code development are not part of this role.
Convert operational needs into requirements, interface definitions, design choices, and acceptance criteria you can measure.
Write standards, drawings, engineering manuals, and procedures detailed enough to build and test from.
Compare options on reliability, security, compatibility, recovery, maintainability, and lifecycle needs within your technical scope.
Clear up ambiguous or conflicting requirements and record the technical basis for major decisions.
Help execution teams with design questions, check implementation evidence, and fix gaps in guidance.
Use commissioning, operational, and failure data to improve designs and standards.
Requirements
You have written technical designs, standards, or procedures that implementation or operations teams have used successfully.
You can turn operational needs into requirements, interface definitions, engineering decisions, and acceptance criteria.
You can weigh options, dependencies, failure modes, security, recovery, and lifecycle effects using evidence.
You can review work, resolve ambiguity, guide execution, and check documentation against implementation and test results.
You meet all of the above and show at least one of the specialties below. They are alternatives, so you do not need all of them.
Power distribution and backup: define distribution and backup requirements, load and capacity analysis, redundancy, interfaces, and acceptance tests.
Racks and cabling: create rack layouts, cable specifications, separation rules, installation details, and workmanship and test criteria.
Compute, storage, and virtualization: design for capacity, compatibility, availability, and recovery.
Industrial software backends: define backend architectures, integration and compatibility standards, configuration baselines, and recovery checks.
Networking: produce architectures, addressing and segmentation plans, firewall and interface requirements, and tests for connectivity, isolation, and failover.
Technical documentation: write technically sound requirements, manuals, and procedures, and validate them through implementation, testing, and review.
Windows domain administration: design domain services, Group Policy baselines, trust and dependency requirements, and administration and recovery standards.
Access control: define role and privilege models, service account controls, access reviews, and authorization acceptance criteria.
Central logging and authentication: design logging and authentication services and integration standards covering coverage, retention, failure behavior, and testing.
Log and packet analysis: build diagnostic methods, logging coverage, evidence requirements, and repeatable fault-isolation procedures.
Operational data systems: design data systems and interfaces with fidelity, retention, access, capacity, and recovery acceptance requirements.
Preferred: experience creating technical standards used across several projects, programs, or sites.
Preferred: hands-on installation, commissioning, troubleshooting, or operations support that shapes practical engineering guidance.
Preferred: experience reviewing interfaces and shared dependencies across several infrastructure disciplines.
Conditions
Salary range: $175,000 - $230,000 USD.
Benefits
Base salary that is competitive
Equity ownership in a fast-growing advanced energy company
Comprehensive medical coverage
Unlimited paid time off
Free lunch and dinner every day on site
Generous stipend for personal protective equipment
Startup setting with major ownership and independence
Fast career growth and chances to move up internally
Work directly with experienced operators, engineers, and industry leaders