Controls Field Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need headings like About the role, Responsibilities, Requirements, Benefits, etc. The posting includes "About Giga" and "Why join Giga". Those could be combined into "About the role"? Actually "About the role" is a generic heading; we could use "About Giga" as section heading? 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 other headings if appropriate, but likely they want those standard headings. However we must preserve all substantive information. We can create sections: About the role (combining About Giga and Why join Giga), What You’ll Do (maybe as Responsibilities?), Where you’ll work (maybe as Schedule? but schedule not given). Actually "Where you’ll work" describes remote role with site-based requirements; could be placed under "Schedule"? Not exactly. Better to create a section "Work Location" but not in examples. However instruction: "Prefer a few substantive sections over many thin ones." So we could combine "What You’ll Do" and "Responsibilities" into Responsibilities section. Also "Where you’ll work" could be part of Responsibilities or a separate section like "Work Location". But we have no explicit heading for location in examples; maybe we can omit it if not required? But we must preserve substantive information. Could include it as a paragraph under Responsibilities or under a new heading like "Work Location". The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings. We can place location info under Responsibilities as a paragraph.
We need Benefits section: they have benefits listed.
We need Requirements section: they have Requirements and Bonus points (maybe combine into Requirements). Also "How We Work" could be part of Requirements or a separate section like "Skills"? But "How We Work" is about values; could be placed under Requirements or maybe under a "Skills" section? Not exactly. Could treat as part of Requirements (soft skills). We'll include it in Requirements.
We must not include Pay or Schedule sections because not specified.
We must not include placeholder text.
We must output only HTML fragment, no /, no markdown.
Thus produce something like:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings. We can place location info under Responsibilities as a paragraph.
We need Benefits section: they have benefits listed.
We need Requirements section: they have Requirements and Bonus points (maybe combine into Requirements). Also "How We Work" could be part of Requirements or a separate section like "Skills"? But "How We Work" is about values; could be placed under Requirements or maybe under a "Skills" section? Not exactly. Could treat as part of Requirements (soft skills). We'll include it in Requirements.
We must not include Pay or Schedule sections because not specified.
We must not include placeholder text.
We must output only HTML fragment, no /, no markdown.
Thus produce something like:
About the role
...combined About Giga and Why join Giga...
Responsibilities
- ...list items...
Requirements
- ...list items...
Benefits
- ...list items...
About the role
Giga is building gigawatts of AI data centers to hasten a future of intelligence and abundance. We build data centers fast and at scale by combining the capabilities of an equipment supplier, engineering firm, general contractor, and real estate developer under one roof. Our team moves quickly and thinks practically. If you're ready to make an impact in an industry that matters, we're looking for people like you.
The Pace: We're building at a speed most companies talk about but never actually operate at. If you've been bored somewhere else, you won't be here.The Impact: Every person at Giga touches the work that matters. No layers, no waiting for approval chains. You'll see your fingerprints on what we ship.The Team: A team of operators defining the future of AI infrastructure. We recruit A-players from the most innovative companies in the world, and they choose Giga because the work here means more.The Moment: AI doesn't run without power, and that's us. Giga is the picks and shovels behind the AI revolution. This industry is about to explode, and you'll be in the room where it's already happening.
Responsibilities
As the Controls Field Engineer, you will own the BMS and controls systems that keep a data center alive — the sequences, points, and logic that make sure UPS, switchgear, and CRAH/CRAC systems actually talk to each other and respond the way they're supposed to. You'll write and review control sequences of operation, program and configure controllers, and troubleshoot points and logic in the field as systems come online. You'll work closely with the commissioning team to get systems ready for FPTs and IST, and you'll be the person who can look at a control system acting up and know whether it's a wiring issue, a programming issue, or a sequence issue — and fix it.
This is a remote role with heavy site-based requirements. During heavy controls milestones, you'll be on-site full-time at an active Giga data center construction site, with the specific location depending on current project needs, with potential relocation or extended assignment to other active sites as the portfolio grows.
- Write, review, and refine sequences of operation for BMS and controls systems in coordination with OPR/BOD requirements
- Program, configure, and commission controllers, points, and control logic for mechanical and electrical systems
- Troubleshoot controls issues in the field, distinguishing between wiring, hardware, and programming root causes
- Support the commissioning team in preparing systems for FPTs and IST, and resolve controls-related issues found during testing
- Review controls drawings, points lists,