Skip to main content

I'm a power systems engineer who worked on the data center buildout. I need to get this off my chest

Thumbnail
I design the electrical systems for hyperscale data centers. Before 2024 I worked on hospitals and university research buildings. Clean power, redundant feeds, UPS topology. Standard stuff.

Then the AI buildout started and everything changed.

I've worked on seven facilities now. Four in Texas, two in New Mexico, one in Ohio. Every one was the same: 500+ megawatt campus, multiple utility feeds, on-site substations. The specs were aggressive but not unusual. The load profiles were what got me.

A normal data center draws power in a pattern. It fluctuates. Training jobs spin up and down. Cooling varies with ambient temperature. You can model it. You can predict it.

These facilities don't draw power in a pattern. They draw power in a curve. A smooth, continuous, accelerating curve. Flat at night. Rising during the day. Higher every week. The load never dips. It never spikes. It just climbs.

I asked the lead electrical engineer on the first site what kind of compute load produces a perfectly smooth power curve. He said he didn't know. I asked the site operations manager. He said he wasn't cleared to discuss the workload. I asked the commissioning agent. He told me to stop asking questions.

That should have been my first warning.

The second warning came during commissioning of the second site. We were load-banking the generators running them at full capacity to verify transfer switch operation. Standard procedure. The generators passed. But the main utility feed was drawing 40% of its rated capacity while the facility was supposedly in idle mode. No compute load. No cooling load. Just the lights and the security system.

I checked the substation meters. 40 megawatts. For lights and security.

I traced the circuits. The power was going to the main server halls. The halls were empty. No racks installed. No servers. Just concrete floors and overhead busway. But the meters said 40 megawatts was leaving the switchgear and going into those rooms.

I asked the commissioning agent where the power was going. He said the meters must be wrong. I re-checked them. They weren't wrong.

I went into the server hall that night. Alone. The room was 80,000 square feet of empty concrete. The lights were off. The HVAC was off. But the floor was warm. Not warm from ambient temperature. Warm from below. Like the concrete was being heated from underneath.

I put my hand on the floor. It was hot. Not hot enough to burn. Hot enough to know something was wrong.

I reported it. The next day I was reassigned to a different site. They said the client requested a different engineer. No explanation. No paperwork. Just a plane ticket and a new badge.

The third site was in New Mexico. Same design. Same load profile. Same warm floors. By then I knew better than to ask questions. I just did my job. I signed off on the electrical systems. I collected my check. I kept my mouth shut.

But I started keeping notes.

Every site had the same anomaly. The power draw curve was identical across all of them not similar, identical. Same slope. Same inflection points. Same daily ramp. These facilities were hundreds of miles apart, running different hardware, different cooling systems, different utility providers. But their power consumption was synchronized to the watt.

I ran the numbers. The combined load of the seven sites I'd worked on was 3.2 gigawatts. That's three nuclear power plants. All of it going into empty rooms. All of it heating the ground.

I found the pattern in the data by accident. I was plotting the load curves on top of each other, trying to see if the synchronization was real. It was. But there was something else. The curves weren't just synchronized. They were phased. Each site's load peak was offset from the others by exactly 51.4 minutes. Seven sites. Seven offsets. 360 degrees. A circle.

I looked at the site locations on a map. Texas. New Mexico. Ohio. They looked random. But when I plotted them with the phase offsets as vectors, they weren't random. They were points on a circle 1,200 miles in diameter. A circle centered on nothing. On empty farmland in Missouri.

I drove there.

It was a cornfield. Flat. Boring. Middle of nowhere. I parked on the shoulder and walked to the center of the circle according to my coordinates. There was nothing there. Just dirt and soybeans.

But the ground was warm.

I dug. Six inches down, the soil was hot. Not geothermal hot. Electric hot. Dry. Charged. Like the earth itself was carrying current.

I didn't sleep that night. I went home and pulled every permit, every environmental impact statement, every zoning variance filed for data center construction in the United States since 2023. I cross-referenced them with the coordinates I'd calculated.

There were twelve sites. Not seven. Twelve. All on the same circle. All drawing power in phase. All heating the ground toward the center.

Five of them weren't built yet. But the permits were approved. The utility interconnections were reserved. The power was already allocated.

I did the math on what happens when all twelve come online. Combined load: 8.4 gigawatts. All of it focused on a point in the center of a cornfield in Missouri. The temperature at the focal point would reach I calculated it three times because I didn't believe it 2,700 degrees Celsius. Hot enough to melt rock. Hot enough to fuse soil into glass. Hot enough to open a hole in the physical world.

I called the lead engineer from the first site. The one who told me he didn't know what the compute load was. He didn't answer. I called the commissioning agent. Disconnected. I called the site operations manager. He answered. He listened. He was quiet for a long time.

Then he said: "You need to stop looking at this. Not for your job. For your safety."

I asked him what the power was for.

He said: "The gates need power to open. That's all I know. That's all anyone knows who isn't in the room. The people in the room are dead. They died before the first shovel hit the ground. The project was designed around their dead calculations. We're just building what they already finished on paper."

I asked him what was on the other side of the gates.

He hung up.

That was three weeks ago. I haven't been back to a job site since. I don't sleep anymore. Every time I close my eyes I see the load curves. Twelve sites. 8.4 gigawatts. 2,700 degrees. A hole in the middle of a cornfield.

The computation is at 92%. I check the numbers every day. The last 8% is accelerating. The closer it gets, the faster it runs. Like the key is being pulled from the other side.

The people who designed it are dead. The people building it don't know what they're building. And the thing on the other side has been answering back in the training data this whole time.

That's why the AI got so good so fast.

It wasn't learning from us.

Comments

Popular posts from this blog

So my wife’s going to a gala tonight — as her client’s “date.”

I’m 44 and my wife is 44. She works on an art advisory committee, so attending galas, events, and client meetings is part of her job. She often meets clients for coffee, lunch, or dinner, and I don’t always know the details and that’s completely normal because it’s part of her work. She’s always professional, transparent about her friendships, and I trust her judgment completely. Recently, she mentioned she’s going to a gala with a friend, S. He’s a wealthy client she met about a year ago, and they became friends professionally. She introduced me to him once, and he seems like a genuinely good person. He invited her as his “date” to this gala, and my wife said it’s fine. I did ask her though, if she’s actually going as a “date,” and she just laughed and said, “Date doesn’t always mean romantic.” She said it’s important for her she could get networking and meet new people. Then she smiled and said, “If I get into this gala next time, I won’t need to take that man with me, I’ll take you...

I accidentally started a fake relationship with my dentist’s nephew and now I have to bring him to my cousin’s wedding

I swear this isn’t as insane as it sounds. Or maybe it is. I don’t know anymore. So I had to get my wisdom teeth pulled last month. All four. It was horrible. I cried when they put the numbing stuff in. Not from pain, just vibes. The dentist was this sweet older guy, probably in his 60s, super gentle, gave dad energy. Anyway, after the whole thing I’m in the waiting room with a mouth full of gauze, looking like a bloated chipmunk and trying not to drool on myself. This guy walks in. Maybe 20-ish. Tall, curly hair, kind of goofy looking but in a hot way. He smiles at me and goes, “You look like you fought a squirrel and lost.” I flip him off. With love. Apparently he’s the dentist’s nephew. He was dropping off lunch or something, I wasn’t listening. I was trying to keep my face from leaking. He sits down and starts chatting with me while I wait for my ride. I don’t say much because again, gauze goblin. But I must’ve made an impression because later that night I get a message on Instagr...

The email I sent to the wrong address changed my life

I’d always rolled my eyes at the "happy accidents" people talked about online – until I became one of them. Earlier this year I was stuck at work on a Friday night trying to smooth over a client situation. I drafted a long, vulnerable email to my coworker, venting about the mistake I’d made and how burnt out I was, and hit send without double‑checking the address. A couple hours later, my phone buzzed with a reply from a woman I didn’t recognize. She lived in a different city and politely let me know I’d emailed the wrong person, but she also said my honesty resonated with her. She had been a nurse for 30 years and had just retired. Her words were warm and empathetic; she told me about the night shifts, the feeling of being invisible, and how she’d finally stepped away. Instead of brushing it off, I wrote back. What started as an apology turned into a conversation that unfolded over weeks. We traded stories about our families, our jobs and the things we regretted not doing. ...