Joulent's $1.75B Round Needs 599 Engineers. Apple Already Hired 4.

On July 8, 2026, Joulent closed a $1.75B strategic minority investment from National Grid Ventures to build Project Kilby, a 2.67 GW generation campus feeding a Microsoft data center under a 20-year PPA. The press release promises to "expand the engineering workforce." The problem: the workforce Joulent needs does not live at OpenAI or Anthropic. It lives at Calpine, Bechtel, GE Vernova, and inside Chevron's Energy Forge, and there are far fewer of them than any recruiter working an AI req would guess.

Why Project Kilby is a hiring story, not an AI story

Project Kilby is a 2.67 GW co-located gas facility in West Texas that sends electrons straight from GE Vernova turbines to Microsoft server racks without touching the wider grid, and its binding constraint is licensed power engineers, not GPUs. Joulent CEO Chris James framed the round around infrastructure speed. National Grid Ventures took a 35% stake at an implied ~$5B post-money. Energy Forge, a Chevron Power Solutions subsidiary, is co-developer. First power targets 2028.

That timeline is the tell. To hit 2028 first power on a 2.67 GW "Across-the-Meter" campus, Joulent must staff up substation, protection and controls, and 138kV/345kV interconnect engineering inside the next four quarters. Those disciplines carry a licensed-PE requirement and a stamp on the drawings. You cannot backfill them with a bootcamp cohort.

The IBEW estimates electrical work is 45% to 70% of total data center construction cost. The US now imports over 80% of its large power transformers, with 2 to 4 year lead times. When the transformer shows up in 2027, someone has to have already engineered the yard it sits in. That someone is the hire.

The exact pool is 599 people. Here's where they sit.

In Refolk's index of professional profiles, only 599 US-based people carry the exact titles "High Voltage Engineer," "Substation Engineer," or "Power Systems Engineer," and that pool shrinks to 402 once you restrict to the industries that actually train them. That is fewer engineers than one mid-size AI lab employs, and it is the entire literal-title market Joulent, Lancium, GridSite, and every hyperscaler power team is fighting over.

599

The employer distribution is the interesting part. When you sort the 599 by top employer, the number one concentration is not a utility. It is Apple, with 4. Meta, Google, and Oracle are already inside this pool. Anyone still telling founders "AI labs don't hire these people" is working from 2023 data.

The last row is the one to memorize.

Title search is showing you 5% of the market

Recruiters searching LinkedIn by title are seeing roughly 5% of the actual pool, because utility, EPC, and IPP job architectures do not use the titles the tech industry expects. The same skills at Senior+ seniority return 11,638 US profiles, a 19.4x expansion over the literal-title search.

The mechanism is job-family design. A protection and controls engineer stamping 345kV drawings at Sargent & Lundy is not called a "High Voltage Engineer." They are called:

• Staff Electrical Engineer
• Project Engineer II
• Protection & Controls Engineer
• Interconnection Engineer
• T&D Engineer
• Senior Electrical Designer, Substations

None of those strings light up a typical AI-infrastructure boolean. This is the exact gap Refolk closes for power and data center power engineers hiring: you describe the person in plain English ("US-based licensed PE with 138kV+ substation experience who has stamped interconnect drawings for a gas peaker or data center") and get a ranked shortlist instead of a keyword-shaped hole.

Filter by title and you see 599 people. Filter by skill and stamp authority and you see 11,638. Same market, 19x the visibility.

The five titles doing most of the hiding

If you must run a boolean, run these instead of the obvious three:

1. "Protection and Controls" OR "P&C Engineer"
2. "Interconnection" AND ("138kV" OR "345kV" OR "500kV")
3. "Substation Design" AND ("PE" OR "Professional Engineer")
4. "Relay Engineer" OR "SCADA Engineer"
5. "T&D" OR "Transmission and Distribution"

Where to source: eight companies tech recruiters ignore

The eight companies that concentrate the Project Kilby profile are utility, EPC, and IPP shops, plus one hyperscaler power org, and none of them appear on standard tech-recruiter target lists. Start here:

• Calpine. Largest US independent gas power producer. Direct match for Project Kilby's tech stack.
• Bechtel. EPC that has built more than half of the megawatts in Texas. The construction leads are here.
• GE Vernova. Turbine OEM on Kilby. Their grid solutions arm carries the substation and protection engineers most tech recruiters cannot name.
• Chevron Energy Forge. Named in the Joulent release as co-developer. This is a data-center-power engineering org that Chevron quietly stood up, and it is the sleeper source.
• Electric Power Engineers (Austin, TX). Top single employer of the energy-filtered pool with 6 profiles. In Joulent's backyard.
• Sargent & Lundy. Power consulting, heavy on substation and interconnect PE work.
• Kiewit Energy and Burns & McDonnell. EPCs with deep 345kV benches.
• LCRA and PSEG Long Island. Utility sources for transmission engineers.

Add Asplundh Engineering Services, NGEN Mission Critical, and GridSite to the second-tier list. Lancium, whose CEO Michael McNamara has publicly said hyperscalers want the industry to move from 1 GW per year to 1 GW per quarter to 1 GW per month, is a direct competitor for the same reqs.

The comp math is different from software

Power engineers cost less than staff software engineers on paper but carry a scarcity premium that inverts the usual tradeoffs. Data center engineers earn $84K to $196K base, with senior roles hitting $240K+, and power electronics specialists land at $150K to $250K. Those numbers look cheap next to Anthropic's $460K PM band, but the supply curve is nearly vertical: a licensed PE with 345kV interconnect experience cannot be minted in under seven years.

19.4x

The negotiation tell: cash total comp usually clears the incumbent by 15% to 25%, but the closer is stamp authority, project ownership on a named gigawatt build, and equity in a company like Joulent that just took a $1.75B check. A protection engineer at PSEG making $170K will move for $210K plus a lead role on the Kilby interconnect. They will not move for $210K and vague "AI infrastructure" branding.

What to promise in the first message

• The named project (Kilby, 2.67 GW, Microsoft PPA, 2028 first power)
• The voltage class they will own (138kV yard, 345kV interconnect)
• The stamp (are they the PE of record, or supporting one)
• The equity refresh, not just base

Geography is inverted from the AI map

The high-voltage pool is distributed across Cedar Park TX, Bozeman MT, Eugene OR, Knoxville TN, and Wilmington DE, not San Francisco, which structurally advantages any Houston-based employer over any Bay Area recruiter chasing the same requisition. Joulent's HQ is a sourcing moat. So is Chevron's, GE Vernova's Cambridge grid office, and Sargent & Lundy's Chicago bench.

For AI infrastructure recruiting more broadly, this means the SF-first playbook fails. You need to run reqs out of Austin, Houston, Charlotte, and Knoxville, and you need to stop pretending relocation to the Bay Area is a benefit. It is a friction cost.

Three practical implications:

1. Put the req owner in the same time zone as the pool. A Texas-based recruiter closing Texas-based PEs is a 40% higher reply-rate motion than an SF sourcer cold-messaging them.
2. Attend IEEE Power & Energy Society (PES) sections in Austin, Houston, and Charlotte. That is where the community lives. It is not on X.
3. NERC-certified system operators and IBEW Local 611 (NM) and Local 353 (Toronto) are the organized-labor overlap on hyperscale builds. Map them.

Refolk pulls from GitHub, LinkedIn, and the open web, which matters here because a lot of these engineers have IEEE PES paper authorship, PE license lookups, and NERC certifications that never make it to a LinkedIn profile. When you ask in plain English for "licensed PEs in Texas who authored an IEEE PES paper on substation protection in the last three years," you get a set that a keyword search structurally cannot produce.

The three mistakes that kill these reqs

The three mistakes are (1) searching by title, (2) restricting to major metros, and (3) writing outreach that leads with AI branding instead of the physical project. Fix those and the req becomes closable.

• Mistake 1: title search. Covered above. 599 vs. 11,638.
• Mistake 2: metro restriction. The pool is in secondary cities. Any "must be in SF/NYC" clause cuts your addressable market by ~70%.
• Mistake 3: AI-branded outreach. These engineers have watched three AI cycles from the utility side. They care about the turbine, the PPA counterparty, the voltage class, and the interconnect queue position. Lead with those.

Joulent's advantage on Kilby is that it can name all four in the first sentence: GE Vernova turbines, Microsoft PPA, 345kV interconnect, ERCOT West. Any recruiter working an AI infrastructure recruiting req without those four facts is losing to Joulent before the first outreach goes out.

FAQ

How many US engineers actually match the Project Kilby profile?

In Refolk's index, 599 US profiles carry the exact titles "High Voltage Engineer," "Substation Engineer," or "Power Systems Engineer," and 402 of those sit inside utilities, oil and energy, renewables, or electrical manufacturing. Expand to a skills-based search at Senior+ seniority and the pool grows to 11,638, which is the number you should actually be recruiting against. The 19x gap between title and skill search is the single most important fact for anyone running a gigawatt project engineers req.

Are AI labs really competing for this pool?

Yes, and the data is already showing it. The number one employer of the exact-title pool in Refolk's index is Apple with 4 profiles, and Meta, Google, and Oracle appear in the top segments. Any recruiter still assuming hyperscalers do not touch high-voltage hiring is working from a 2023 mental model. For Joulent hiring specifically, the direct competition is Apple's data center power team and Chevron's Energy Forge, not other IPPs.

Where should I start sourcing for a Project Kilby style req?

Start at Calpine, Bechtel, GE Vernova's grid solutions arm, Chevron Energy Forge, Electric Power Engineers in Austin, Sargent & Lundy, Kiewit Energy, and Burns & McDonnell. These eight companies concentrate the licensed PEs with 138kV and 345kV substation experience that a gigawatt buildout needs. Add IEEE PES chapter attendance and PE license lookups in Texas, Louisiana, and Oklahoma to catch engineers whose LinkedIn profiles undersell their stamp authority.

Why does title search miss so many people?

Utility and EPC job architectures use generic labels like "Staff Electrical Engineer," "Project Engineer II," "Protection & Controls Engineer," and "Interconnection Engineer" for work that a tech recruiter would call substation or high-voltage engineering. The literal titles surface 599 profiles; the actual skill population is 11,638. Skill-based and plain-English search closes that gap, which is why high voltage engineer sourcing that relies on title booleans consistently underestimates the market by roughly 95%.