They sell the fix for the thing that broke Ashburn twelve days ago.
On July 22, a transmission fault in Data Center Alley knocked roughly 3 GW of load off PJM in seconds. ON.energy sells a medium-voltage system whose entire purpose is to make that not happen. You live twenty minutes from the epicenter and you are interviewing for the job that prices the contracts.
The brief
Logistics first, then the one picture that summarizes the whole dossier.
The invite reads 4:00–4:30 PM (GMT−05:00) Bogotá. Northern Virginia on August 3 runs on EDT, GMT−04:00. Your local start is 5:00 PM ET, not 4:00 PM.
Verified independent press or a regulator — safe to state as fact. Company claim ON.energy's own materials — say "they say." Live moving right now; recheck before you dial in.
The industry
Four forces define this market in 2026. Narrate these four fluently and you sound like someone who already works in the sector.
The megaprojects — who is building what
These five build-outs define the customer landscape ON.energy sells into; each made a different bet on power, and that bet is the commercial story.
Stargate (flagship: Abilene, TX)
Location: Abilene TX flagship (Lancium Clean Campus), plus Shackelford County TX, Doña Ana County NM, Lordstown OH, Milam County TX, Port Washington WI ("Lighthouse," $15B, Oracle+Vantage).
Parties: OpenAI, Oracle, SoftBank; Abilene developed/operated by CRUSOE; Nvidia $100B investment; announced Jan 2025 at the White House.
Scale: ~1.2 GW at Abilene; ~7 GW planned across sites; 10 GW / $500B program target by 2029; >$100B already deployed as of early 2026.
End user: OpenAI training + inference (Oracle Cloud Infrastructure).
Power strategy: West Texas cheap energy + behind-the-meter self-supply incl. up to ~300 MW on-site gas turbines to sidestep interconnection queues.
Why ON cares: Crusoe built Abilene — the same Crusoe that signed ON's 5 GW AI UPS deal in July 2026. This project is one degree from your desk.
Meta Hyperion (Richland Parish, LA)
Parties: Meta + Blue Owl Capital JV (~80% sold to Blue Owl, off balance sheet) + Entergy Louisiana.
Scale: 5 GW compute + 2.5 GW support/cooling; ~3,200 acres; up to 9 buildings; first 2 GW by 2030, full ~2032.
Cost: >$50B (was $10B at Dec 2024 groundbreaking, then $27B — quintupled in under two years).
Energy: Entergy building 10 gas plants (>7 GW, +30% to Louisiana's entire grid); Meta funds 2.5 GW renewables, ~240 miles of transmission, grid-scale BESS at three sites; "Ratepayer Protection Pledge"; Earthjustice challenging the financing at the PSC.
End user: Meta Superintelligence Labs.
Why ON cares: the single biggest example of "the customer pays for the grid now" — generation, transmission, storage all inside the deal. Every one of those line items is a negotiated contract.
xAI Colossus 1/2/3 (Memphis, TN)
Parties: xAI, MLGW/TVA (Colossus 1 grid power), own 1.2 GW gas plant across the Mississippi line for 2 and 3.
Scale: Colossus 1 ~300 MW, ~200k GPUs, built in 122 days in a former Electrolux factory; Colossus 2 ~946 MW IT power — largest known AI data center by IT power (Epoch AI).
Cost: est. $30–40B including recent funding.
End users: xAI's Grok — plus merchant compute: Anthropic leasing ~325k GPUs (~$1.25B/month reported), Google ~110k, the Pentagon.
Power strategy: mostly OFF-GRID behind-the-meter gas; 168 Tesla Megapacks smoothing GPU load swings. Environmental fight over unpermitted turbines.
Why ON cares: proof at scale that GPU swings need a battery buffer — Colossus solved with parallel Megapacks exactly the problem ON argues needs an inline system. That contrast is a sophisticated interview point.
AWS Project Rainier (New Carlisle / St. Joseph County, IN)
Parties: Amazon Web Services, built exclusively for Anthropic.
Scale: 1,200 acres, ~30 buildings, ~910 MW IT power operational, building toward 2.2 GW; 500k+ Amazon Trainium2 chips — the first hyperscale non-Nvidia cluster.
Cost: $11B phase 1 (operational late 2025) + $15B phase 2 announced.
Power strategy: bet on the utility grid (AEP Indiana), natural-gas backed.
Why ON cares: single-tenant, single-chip, grid-dependent — the maximum-exposure profile for exactly the ride-through risk ON prices.
Microsoft Fairwater (Mount Pleasant WI + Atlanta GA)
Parties: Microsoft; serves OpenAI + Azure AI.
Scale: WI campus >350 MW scaling toward ~2 GW, ~half a million chips; Atlanta ~636 MW IT power, second building to >700 MW by 2027; the two linked by dedicated fiber into one "AI superfactory" training a single model across states.
Cost: $7B+ initial WI; total program reported to potentially exceed $100B at completion.
Power strategy: the shocker — the Atlanta site runs straight off Georgia Power with NO UPS and NO diesel generators; Microsoft did the math on what redundancy buys during a training run and cut it.
Why ON cares: the bear case for ON's product, stated by the most sophisticated buyer alive. Know it exists; have a view (ride-through mandates like NOGRR 282 are precisely the counterweight — a regulator can't accept "we did the math").
How to use these in the room
Don't recite; deploy. One sentence pattern: "Every megaproject made a different power bet — Rainier bet on the grid, Colossus went off-grid with Megapacks, Microsoft cut the UPS entirely, Meta is buying the utility's build-out — and each bet creates a different contract surface. ON's thesis is that regulation is about to punish the naked-grid bets."
Figures are press-reported as of July 2026 and move monthly — Grok prompt section 6 covers the refresh.
Ashburn, July 22 — your opening move
The single strongest thing you can bring to the call. It happened twelve days before your interview, thirty minutes from your house, and it is a live demonstration of ON.energy's entire thesis.
"The data centres didn't get knocked off the grid. They jumped. Every campus made a rational decision to protect its own compute — and the sum of those rational decisions is a three-gigawatt hole in PJM."
Suggested phrasing — say it in your own words"Two weeks ago three gigawatts of load dropped off PJM after a fault in Ashburn — twenty minutes from my house. I read the coverage, then read ON.energy's material on the inline architecture, and it was the first time I'd seen a product that addresses both directions of that problem instead of one. I've spent nine years selling energy systems, and I've never seen a market where the regulatory deadline and the customer's own self-interest point at the same purchase order. I want to be on the commercial side of that."
July 10, 2024 — the first warning shot
Two years before Ashburn 2026, the same failure happened at half the scale, in the same place — and everything ON.energy now sells into traces to that night. NERC's own incident review is public; these details are verified.
It converts the Ashburn story from anecdote into pattern. Pattern recognition is what separates "I read the news" from "I understand the market." One suggested sentence: "What struck me is that 2024 and 2026 were the same event at different magnitudes — same county, same failure mode, same protection logic. That's not bad luck, that's a design flaw with a growth rate. And it's why ride-through went from white-paper topic to mandate."
Who ON.energy is
The arc: LATAM integrator → US independent power producer → AI infrastructure technology company. Each phase left something in the DNA that shows up in how they do deals.
The scale numbers they publish
All Company claim — cite as "their materials say."
Hiring signal
The Greenhouse board carries 56 open roles across Reston/Tysons, Houston, Miami, Atlanta, Amarillo, Mexico City and Argentina. Two adjacent hires tell you the most: a Contracts Counsel (being built in parallel with you — hence "you don't wait for Legal") and a Director of Sales, Data Center & Critical Power (the "counterweight" relationship in your JD). Your role is filed under Finance: your deliverables go to the CFO, and your incentives are margin and risk, not bookings.
"We move fast, debate hard, and learn from each other. If you want predictable, this isn't it. If you want impact, welcome."
on.energy — working at ON.energyPair that with the JD's "we cannot teach commercial courage." They are screening for someone who will argue cleanly and stay warm doing it — a muscle you built over nine years in living rooms.
AI UPS, explained properly
You don't need to be an engineer. You need the architecture in one picture and its price in another. Here are both — plus the test data that backs the claims.
Competitive map
Know who else is in the room when a hyperscaler runs this procurement — and where ON's leverage actually comes from.
The honest risks — have a view on these
Concentration
Crusoe is transformative and also one counterparty carrying commissioning risk over years. That's exactly why payment security and change-order mechanics matter — why you exist.
Incumbent response
ABB, Eaton and Schneider have balance sheets, service fleets and existing hyperscaler master agreements. Patents help; a fast follower with an installed base is a durable threat.
Regulatory reversal
TIEC's intervention on ERCOT's authority could reroute NOGRR 282. ON expects the technical requirements to survive — but the tailwind isn't guaranteed.
Supply chain & capital intensity
5 GW of new commitments needs cells, transformers, PCS and working capital. They're hiring a transformer sourcing manager. Back-to-back supply terms are part of your scope.
How they make money
This is what separates you from a candidate who only read the homepage. ON.energy earns four different ways — and each way changes what a contract must do.
The role, decoded
They wrote the JD emotionally — "grey zone," "commercial courage," "when to walk away." Read it as a description of a person, not a task list.
| They wrote | They mean |
|---|---|
| "You do not wait for Legal to tell you a clause is a problem." | Legal is thin and being built now. Self-start on risk identification. |
| "The commercial counterweight" to Sales | Real friction exists between bookings and risk discipline. Hold a line without becoming the department of no. |
| "Deal summaries and negotiation strategies for CFO and executive review" | Direct visibility to Andrea Petersen. Written communication is a core deliverable. |
| "We can teach modeling; we cannot teach commercial courage" | A deliberate opening for a candidate without project-finance modelling. This is your door. |
| "Not a contracts administration role" | They fear paralegal-adjacent applicants. They want an operator. |
| "7+ years negotiating complex commercial agreements" | The hard bar. Address it head-on — Section 10. |
Clause playbook
The JD names eight contract concepts. Two of them deserve pictures, because pictures are how the stakes actually land. The rest are in the expandable cards below.
Performance guarantees
What it is. A promise the system hits specified numbers — availability, efficiency, capacity retention, ride-through — measured a defined way over a defined period.
What it costs. Definitions are everything. "99.9% availability" with no exclusions means you pay for the customer's own switchgear failure.
Your position. Guarantee what you control; exclude force majeure, customer-caused outages, grid unavailability, scheduled maintenance; measure over an annual window; cure period before remedies trigger.
Liquidated damages (LDs)
What it is. Pre-agreed money for missing a date or a number, instead of litigating actual losses.
What it costs. A delayed campus is delayed revenue on billions of GPU capex — uncapped delay LDs can exceed the whole contract.
Your position. Cap delay LDs (commonly low-to-mid single-digit % of contract value with an aggregate cap), cap performance LDs separately, make LDs the sole and exclusive remedy for that failure. Grace period; relief for delays caused by the customer, the EPC, or permitting. And with a 3.2 MW modular product: LDs per module actually late, not per facility.
Indemnification
What it is. Covering the other side's losses from third-party claims — injury, property damage, IP, environmental.
What it costs. Often sits outside the liability cap; battery systems add fire/thermal exposure that insurers price carefully.
Your position. Mutual, proportional to fault, tied to the insurance programme. IP indemnity cuts both ways given the patent position.
Payment structures & security
What it is. Milestones, advances, retainage; LCs, parent guarantees, bonds, escrow.
What it costs. ON buys cells and transformers months before customer milestones pay — the working-capital gap is real (it's what the Lombard Odier facility was structured for). A customer-demanded LC ties up ON's credit capacity.
Your position. Front-load milestones toward procurement/manufacturing; match payment triggers to cash-out events; negotiate the size, form and step-down of security instruments.
Change orders
What it is. The mechanism for adjusting price and schedule when scope, site conditions or specs change.
What it costs. On multi-year multi-site programmes this is where margin is won or lost. Chip generations, cooling architecture and 800 VDC are all moving — a customer redesign changes your sizing, and someone pays.
Your position. Define the baseline precisely; specify who authorizes; set response clocks; agree pricing bases (unit rates) up front. Include a regulatory-change mechanism: if ERCOT or NERC tightens a requirement mid-build, that's a change order, not your absorption.
Dispute resolution
What it is. Escalation ladder, mediation/arbitration/litigation, seat, governing law.
What it costs. With LATAM operations and international counterparties, enforceability isn't boilerplate. A slow dispute on a live project is itself a cost.
Your position. Tiered escalation with named executives and short clocks; continue-to-perform and pay-undisputed-amounts language; a forum you can actually enforce in.
Learning these makes you conversant, not experienced. If asked "have you negotiated an LoL with a hyperscaler," the answer is no, and you say so. What you can honestly claim: you understand what these terms do to economics, and you've negotiated contracts, financing and partner terms in your own business. Overreaching is the fastest way to lose the room — and they'll find out in round two.
The risk lens — how a senior negotiator actually thinks
The realization that upgrades this whole prep: the job isn't negotiating contracts. It's running a repeatable framework for risk-adjusted commercial decisions — so executives get consistent answers to "what is this risk worth and who should own it?" Every clause in Section 08 is just that question wearing different clothes. This section is the lens; your archive in 10B is the proof you already use it.
The three-verb answer if anyone asks how you think about contract risk: "First I ask if we can engineer it out — restructure the deal so the risk can't happen. If not, cap it — bound the exposure in time and dollars. If someone else holds it cheaper, transfer it — insurance, warranty, indemnity. Whatever's left, price it into the commercial terms. And if it can't be priced, that's what walking away is for." Then give one real example per verb — you have them all in Section 10B.
How executives hear a deal — four questions above the clause level
| What the exec is really asking | What it means for how you present |
|---|---|
| "What's the expected return?" | Lead with the economics, not the terms. The clauses exist to protect a number — name the number first. |
| "What's the residual risk after mitigation?" | Never present a risk without its rung on the ladder. "Uncapped indemnity" is a problem; "indemnity capped at 12 months trailing, six-year sunset" is a decision. |
| "Does this fit our risk appetite?" | Some risks are cheap for ON to hold (they own the hardware and the O&M team) and expensive for a customer to hold. Allocation should follow who holds it cheapest — that's the whole art. |
| "Does it fit the strategy?" | A below-market deal with Crusoe-scale strategic value may be right; a rich deal that locks in a bad precedent may be wrong. Terms are portfolio decisions, not single-deal decisions. |
This is the JD line "advise executives on how commercial terms affect project economics and risk" made operational: recommendation first, residual risk stated, ladder rung named.
Formal frameworks exist for all of this (enterprise risk management standards, risk allocation matrices). Know the concepts — probability, impact, mitigation hierarchy, residual risk, risk appetite — but do not name-drop standards you haven't operated under. If an interviewer raises ISO 31000 or COSO, map your ladder to it live: identify → analyze → evaluate → treat is the same spine. Fluency is mapping on demand; costume is citing on spec. Same honesty rule as everywhere else in this dossier: claim only what survives one follow-up question.
The people
Monday is a recruiter screen, not a technical panel. Calibrate for that — but know the map behind her.
Public info on her is thin. The invite itself tells you more: it was issued in GMT−05:00 Bogotá, and ON runs real LATAM operations — she's most likely on Colombia time. Inference
Her job is signal and fit, not clause-drafting quizzes: can you explain your story clearly, do you get what ON does, are comp and location workable, will the hiring manager thank her for you. Her prep email told you the test: STAR-structured answers, and possible probing on BESS. Have three STAR stories ready and the Fig. 9 explanation fluent. Be warm and brief — recruiters remember candidates who make their job easy.
Your fit & your gaps
Straight assessment. You will interview better having already decided how you talk about the gap, rather than discovering it live.
If Andrea signals the years-of-B2B bar is firm, ask directly whether there's a level below — a Manager or Commercial Analyst seat on the same team with the same trajectory. That converts a rejection into a redirect, and demonstrates the exact self-awareness the role demands. With 56 roles open, including several in Reston, odds are decent something fits.
Your STAR bank
Andrea's prep email asked for STAR-structured answers explicitly. These five are built from your actual history — pulled from our past sessions — and each is mapped to the JD line it proves. Two need you to fill in the numbers; the scaffolding is done.
| JD clause | What you actually did | Where |
|---|---|---|
| Payment structures | 30/40/30 milestone splits; 45-day post-PTO backstop; 14-day payment deadlines; redline locked at submission; proportional tranches within 7 business days for cash & commercial | Team Sunshine, Yellowlite, Empower |
| Liquidated damages | Identified and removed two $75,000 LD clauses | Empower / Bold Energy |
| Limitation of liability | Added trailing 12-month liability cap + 6-year survival sunset to their indemnification; separate aggregate cap negotiated | Team Sunshine, Empower |
| Indemnification | Caught asymmetric indemnity (you: negligence; them: gross negligence only) with their investors inside your obligation; pushed mutual + investors removed | Convert Solar, Empower |
| Warranties & performance guarantees | Production guarantee designed as one of nine mandatory lessor obligations in your own lease product | Covenant Solar Lease℠ |
| Security requirements | $7,000 forgivable signing advance with partial-recovery floor; marketing advance converted to capped $500 deductions | Aegis, Team Sunshine |
| Change order mechanisms | Tiered-notice ladder on pricing changes: 7 days documented pass-throughs / 14 days <10% reductions / 30 days material changes; one-increase-per-quarter cap; pipeline rate lock | Empower, Yellowlite |
| Dispute resolution | Arbitration seat negotiated to responding party's home state; continuous portal access + payments continue during disputes; injunctive-relief carve-out | Convert term sheet, Aegis, Yellowlite |
| Order of precedence / unilateral amendment | §1 order-of-precedence placing your agreement above a 46-page platform rulebook; switched off their unilateral-change and 30-day-acceptance provisions | Powur |
Every row is from your own documents, May–June 2026. If asked for detail on any of them, you have it.
№1 — Team Sunshine — the anchor, now with its real numbers
S: "I was building Raynora's installer channel and needed a Massachusetts installer relationship. Team Sunshine's president, Ahmad Hodroj, skipped my term sheet entirely and sent back a pre-executed 17-page channel agreement on their paper — classic anchor move."
T: "Sign their paper as-is, or negotiate a live counterparty who'd already shown he negotiates hard — without losing the relationship."
A three-part: (1) built a one-page locked Addendum through ten versions plus a four-column discussion guide through eleven, sent the PDF the day before with a warm note and held the guide for the live call; (2) traded, didn't demand — deleted chargebacks entirely, framed as a balanced trade against their cancellation rights and non-exclusivity; split payment timing: install-completion for TPO and lease deals, proportional payment within seven business days for cash and commercial; countered commercial pricing at $2.05/W as the explicit trade for accepting their $2.40 TPO; added a 12-month trailing liability cap and a six-year sunset to their indemnity instead of fighting the clause head-on; (3) conceded live — when Ahmad pushed back on the "culpable act or omission" trigger and the personal-guaranty exemption, he was right that both were overreach, and I dropped them on the spot.
R: "Signed agreement, working relationship, and a repeatable two-document playbook I then reused with four other counterparties. And a lesson your JD describes exactly: knowing when to push and when to concede is the same skill."
"An installer's president answered my term sheet by sending back a pre-signed contract on his paper. Over ten drafts and a live text negotiation I traded rather than demanded — gave up chargebacks to win payment timing and a liability cap, took $2.40 on TPO to get $2.05 on commercial — and dropped two of my own asks the moment he correctly called them overreach. We signed. The playbook from that deal became my template for every negotiation since."
№2 — The Covenant Solar Lease℠ — structuring, with the numbers attached
Designed a Sharia-compliant lease product (Ijara Muntahia Bittamleek) satisfying the IRS true-lease test (Rev. Rul. 55-540 eight factors) and Islamic finance constraints simultaneously; locked terms include 20-year term, 8% nominal target IRR on the lease payment stream, ~11–12% all-in SPV yield including ITC and MACRS bonus depreciation, Year-6 purchase-option gate deliberately set one year past the §48E five-year recapture window, FMV methodology at 13% of cost declining 1%/yr to a 5% floor, net buyout = gross FMV minus offsetting obligations floored at zero; benchmarked the design against four national contracts (Sunrun PPA, Participate Energy, Skylight, EnFin) clause by clause, including hell-or-high-water payment provisions; separately produced a §48E Beginning-of-Construction reference covering the 5% Safe Harbor vs the four-year continuity safe harbor and §6418 transferability at 88–94 cents on the dollar.
Caution: keep counterparty-confidential specifics out of it (you've restricted Covenant details in other applications for competitive reasons — same discipline applies here; the structure and the model are yours to discuss, the deal specifics may not be).
When your JD says modeling is teachable — I taught myself the version that matters: what a term does to the economics.
№3 — Convert Solar — the walk-away
S: signed originator agreement in hand, then ran a clause-by-clause plain-English breakdown before scaling the relationship.
T: decide whether the paper was fixable.
A: flagged eight watch-outs and isolated three dealbreakers — zero-day at-will termination for them while I owed 60 days' notice; undefined territorial exclusivity with commission forfeiture as the penalty; and compensation forfeiture if a closed sale never reached completed-install status even with no fault on either side. Drafted the replacement addendum, made the asks.
R: "The economics of their position didn't work at any price I could charge, so I walked and kept my Virginia and Maryland optionality. Your JD says know when to walk away — this is what mine looked like: named dealbreakers, a written record, and no burned bridge."
№4 — Aegis / One World Energy — the diligence pivot
S: mid-negotiation on a channel agreement, terms substantially settled including a disclosed 10% margin cap and a four-step commission formula.
T: before sending for signature, verify the upstream installer network actually existed where they claimed.
A: real-time diligence found no East Coast operating presence — registered-agent addresses instead of warehouses, no Google Business footprint, no response by phone, email, or text. Pulled the agreement and sent a due-diligence email instead, asking specifically who installs in the DMV, Maryland, New Jersey, and Massachusetts.
R: "The deal never closed, and that was the win. Your JD's first behavioral bullet is 'identify commercial risks early' — the cheapest place to catch counterparty risk is before your signature, and I've built that reflex the expensive way, by watching an installer I depended on [Boundless/Freedom Forever] fail."
№5 — The playbook — proof you can build the function
The repeating pattern developed across Boundless, Team Sunshine, Empower, Convert, and Yellowlite: one clean locked executable addendum as a PDF, paired with an editable four-column discussion guide (Section / Proposed language / Rationale / Their notes) for the live call; doctrine of aggressive-but-reasonable v1 baselines, never self-negotiate, let the other side redline; document hygiene rules enforced (column says "Rationale" not "Why," counterparty column says "agreed" not "counter"). Plus the other side of the table: authored Raynora's own 24-section Sales Partner Agreement.
Your JD's last bullet — develop playbooks, templates, negotiation frameworks — isn't aspirational for me. I have one. It's just priced in kilowatts instead of gigawatts.
№6 — Reserve stories — deploy only if the question fits
The five-offer week: May 2026 comp negotiation with layered asks and a pre-decided walk-away — use only if asked about negotiating under personal stakes.
Founding the school: $6M budget, 1,000+ students, operations from zero — use for building-from-scratch questions if the playbook story is already spent.
The 2020 Circle of Excellence year: being the COVID year (adaptability).
These are dealer and channel agreements with five-figure per-deal economics — not EPC or nine-figure supply contracts. Volunteer that distinction: "Same clause surface as your JD, smaller number of zeros — and the zeros are the teachable part." The Green Brilliance / PJM advisory work is usable only at the level of detail you can personally defend when a CFO asks "which substation, which tariff, what did you conclude?" If you can't answer the follow-up, don't make the claim.
Hard questions, with answers
Rehearse out loud. The shape and the honesty matter; the exact words don't.
"Walk me through your background."
"I've spent nine years in US solar, mostly on the front end — Sunrun, where I was a Circle of Excellence honoree in 2020, then running my own advisory business, Raynora, in the Mid-Atlantic. What kept pulling me deeper was the part of the deal after the handshake: how it's financed, what the terms actually obligate you to, what happens when something underperforms. I have a corporate finance degree and I've been running my own P&L, so I've lived on that side by necessity. This role is that work at the scale where it really matters, in the market on my doorstep."
"You haven't negotiated EPC or supply agreements at this scale. Why you?"
The one you must not fumble. Concede fast → redirect to their own stated criteria → offer proof → name reality.
"Fair — I haven't negotiated a nine-figure supply agreement with a hyperscaler's counsel, and I won't pretend otherwise. What I can tell you is that in the last ninety days alone I've negotiated ten entity-to-entity commercial agreements — and the clause surface was your job description: milestone payment structures, liquidated damages I got removed, liability caps I added, asymmetric indemnification I caught and reversed, tiered change-notice mechanisms, payment security, arbitration terms. Two I signed, two I walked away from on named dealbreakers, one I pulled mid-negotiation when due diligence failed. The gap between my record and this seat is the number of zeros on the contracts — and your posting says the zeros are the part you can teach. What you say you can't teach — the judgment about when to push, trade, and walk — is documented in my own archive. I'd also genuinely want your read: is that a bar you can flex on? If not, I'd rather discuss whether there's a level below this seat with the same trajectory."
That last move is the trait they're screening for — knowing when to push and when to name reality — while keeping the door open.
"What do you know about ON.energy?"
"You started around 2015 as a storage developer and integrator in Latin America, became an IPP in ERCOT, and in February launched AI UPS — which is the interesting move, because it isn't a BESS. It's inline at medium voltage: no transfer time, and the whole plant sits behind it, not just the racks. Then in July, 5 GW with Crusoe. What strikes me commercially is you're three businesses at once — manufacturer, integrator, asset owner — so contract terms don't just allocate risk, they decide whether a project gets financed. That's a more interesting problem than vendor contracting."
"Tell me about a time you pushed back and held your position."
STAR, as she requested — and you have two ready in Section 10B: Team Sunshine (№1) if the question is about a commercial deal, or the five-offer week (№3) if it's about holding a position and walking away. Be specific about the number at stake and the outcome. Losing a deal on principle is a better answer than winning one, given the JD's "know when to walk away."
"Why are you leaving your current role?"
"Nothing's wrong where I am — I'm producing. But I've spent nine years paid per transaction, and the work I find most interesting has moved upstream into structure and terms. I want a seat where the output is the quality of the deal, not the volume of them, and where I'm building something durable — playbooks, frameworks — rather than starting from zero every month."
Honest, forward-facing, and it maps directly onto a JD that asks you to build playbooks and templates.
"What are your compensation expectations?"
You already did this work: last session, against your fixed monthly obligations, you landed on $140–160K base as the target, with any equity conversation deferred to later rounds. Walk in with that number owned.
"I'm targeting a base in the $140–160K range with bonus on top, based on senior commercial roles in this market — but I'd rather calibrate to your band. What range is the role approved at?"
"What's a BESS?" — the spot-check she warned you about
"A battery energy storage system — batteries plus power conversion plus controls, sitting beside the power path, storing and dispatching energy over minutes and hours: charge cheap, discharge expensive, sell ancillary services. ON has built and owned those for years. But your CTO's point is that a BESS is parallel — it has to detect a fault and transfer, and even a fast static switch is a few milliseconds, so the GPUs already saw the hit. AI UPS is inline; there's nothing to transfer. I gather you'd rather people didn't conflate the two."
What you ask
Pick three or four. Ask the ones only someone who understood the business would ask.
For Andrea, on Monday
- "Who does this role report to, and who would I meet in the next round?" — confirms the Fig. 20 inference.
- "Is this a new seat or a replacement — and what triggered opening it now?" — the honest answer is almost certainly Crusoe.
- "What does the process and timeline look like from here?"
- "With 56 roles open, how is Reston specifically growing?"
- "What separates candidates who make it through from those who don't?"
Held for the hiring manager
- "With Crusoe phased over 2026–27, how are you handling change-order mechanics as chip and cooling architectures move? An 800 VDC transition changes the load profile you sized to."
- "Because you own assets as well as selling equipment, your lenders effectively read every contract. Which terms do your credit partners treat as non-negotiable?"
- "In an EaaS structure, who captures the grid-services stack — and how do you resolve a conflict between a market dispatch opportunity and the customer's compute demand?"
- "NOGRR 282 is a real tailwind, but TIEC has challenged ERCOT's authority. How do you price regulatory-change risk into a multi-year agreement?"
- "How back-to-back is the 20-year warranty with your Tier-1 suppliers today — and where does the uncovered tail sit?"
- "Is there an existing playbook and template set, or is building that the first six months?"
- "What should this person have delivered by day ninety?"
The 30-minute plan
Thirty minutes with talent acquisition is roughly 12 minutes of you talking. Budget it.
- −60Test the Teams link. Confirm the calendar reads 5:00 PM ET. Quiet background, solid connection, water, resume + this page on a second screen.
- −15Search "ON.energy" and "PJM data center" for weekend news. Thirty seconds of fresh news is disproportionately valuable.
- 0:00Warmth first. Thank her for the confirmation and mention you followed her prep note. Recruiters notice.
- 0:02Your background — 90 seconds, arc not chronology, land on why this role. Then stop talking.
- 0:05Her overview. Listen properly. Ask one clarifying question about something she actually said.
- 0:12Her questions. STAR. If BESS comes up, run the Fig. 9 answer. Keep each answer under two minutes.
- 0:20Bring Ashburn in yourself if she hasn't opened the door. You cannot leave without using it.
- 0:23Your questions — three, not seven. Reporting line, trigger for the role, process.
- 0:27Address the experience gap yourself if it hasn't come up — better from you than discovered later. Ask about adjacent levels if the signal is negative.
- 0:29Close explicitly: "I want this role. What's the best next step from your side?" Confirm timeline.
- +2hThank-you email, four sentences: thanks, one specific from the conversation, one line tying your interest to Ashburn, restated availability.
In-home closing rewards filling silence and steering. A screen is a listening exercise: answer, stop, let her lead. If you're talking more than half the time, you're losing.
Glossary
Skim the night before. Recognize all of these instantly; be able to define about half.
| Term | Meaning |
|---|---|
| AI UPS™ | ON's patented inline medium-voltage UPS with integrated storage. |
| BESS | Battery Energy Storage System. Parallel to the power path; minutes-and-hours energy management. |
| Double conversion | AC→DC→AC continuously, so the load never sees raw grid power. |
| ZVRT / LVRT | Zero / Low Voltage Ride-Through — staying connected through a voltage collapse. |
| NOGRR 282 | ERCOT ride-through mandate for computational loads ≥75 MW. Effective 1 Aug 2026. |
| LCL | Large Computational Load — ERCOT's term for such a facility. |
| Ramp rate | How fast load may rise/fall from the grid's view; regulated because instant swings destabilize. |
| Residual risk | What remains after mitigation — the thing executives actually decide on. Every negotiated clause is a residual-risk statement. |
| Risk allocation matrix | A table mapping each project risk to its owner (developer, EPC, supplier, insurer, customer). The formal version of what a term sheet does implicitly. |
| Risk appetite | How much residual risk an organization will knowingly hold. Allocation should send each risk to whoever holds it cheapest. |
| p.u. | Per unit — voltage as a fraction of nominal. 1.0 is normal; 0 is total collapse. |
| Medium voltage | ~13–35 kV; where most large facilities interconnect. |
| PCS | Power Conversion System — the inverter/rectifier stack. |
| STS | Static Transfer Switch — fast, but still ~4 ms. ON's argument against parallel designs. |
| N+1 / 2N+1 | Redundancy: one spare unit / full duplication plus a spare. |
| Grid-forming | Inverter establishes voltage & frequency itself — enables islanded operation. |
| PJM / ERCOT | Mid-Atlantic RTO (largest US operator, largest DC concentration) / Texas operator (first to regulate large loads). |
| FERC / NERC | Federal economic regulator / reliability-standards body. |
| Co-location | Siting large load at a generator — the subject of FERC's PJM docket EL25-49. |
| Ancillary services | Paid grid support: frequency regulation, reserves, voltage support. |
| ITC / safe harbour / tax equity | Investment Tax Credit (now transferable) / locking a credit vintage by early spend / investor capital exchanged for tax benefits. |
| FEOC | Foreign Entity of Concern — sourcing restrictions affecting tax-credit eligibility. |
| EaaS / offtake | Provider owns the asset, customer pays a service fee / long-term purchase contract that makes a project financeable. |
| EPC | Engineering, Procurement & Construction contractor. Rosendin is a named ON partner. |
| LD / LoL | Liquidated Damages / Limitation of Liability (cap + consequential-damages exclusion). |
| Back-to-back | Passing an obligation upstream on identical terms — never warrant more than you're covered for. |
| Bankability | Whether a lender will finance against the contract. Failing terms kill deals regardless of price. |
| IPP | Independent Power Producer — non-utility owner-operator. ON is one. |
| ISO 31000 / COSO ERM | The two big enterprise risk-management frameworks. Know the spine (identify → analyze → evaluate → treat); don't cite them unprompted. |
| ISO standards | In a manufacturing context (as in the recruiter's email): the ISO 9001 family of quality-management standards. Watch the double meaning — in grid conversation, "ISO" means an Independent System Operator (CAISO, NYISO, ERCOT). Let context tell you which. |
| QMS | Quality Management System — the documented processes a manufacturer runs so quality is repeatable and auditable. Relevant because ON builds hardware in US factories; certification often gates customer payment. |
| ARIES / NLR | DOE research platform and national lab where AI UPS was tested at 13.2 kV. |
Sources
Everything traces to one of these. Company materials are marketing, not audit — treat accordingly.
- Companyon.energy — homepage, technology, financing, team, AI UPS solution pages
- CompanyNOGRR 282 resource guide — their regulatory explainer, unusually substantive
- Company"Don't Call Me BESS" by Ricardo de Azevedo — read in full before Monday
- CompanyCrusoe 5 GW partnership release, 21 Jul 2026
- CompanyFull job description on Greenhouse
- PressRTO Insider — 3 GW load drop, Northern Virginia
- PressData Center Knowledge — Data Center Alley fault
- PressLatitude Media — ride-through rules gain steam
- PressEnergy-Storage.news — company profile and history
- PressPathward — $77.6M construction credit, named deal team
- PressBusiness Wire — $20M Series B
- PressDCD — AI UPS launch, Feb 2026
- RegulatoryBlank Rome — FERC order on PJM large-load interconnection
- RegulatoryNational Law Review — FERC co-located load guidance, Apr 2026
- MarketMorgan Stanley — powering AI, 2026 outlook
- MarketUS DOE — data centre electricity demand
- MarketMarketsandMarkets — data centre UPS market and competitive moves