Principal Product Engineer, Cloud Platform

GPU racks pull 120–140 kW today. By 2027, that number hits 600 kW to 1 MW per rack. The entire AI buildout — hundreds of billions in capex — is being erected on a grid that was not designed for it. Design margins have compressed from 30% to 10–15%. The monitoring systems built for the last generation of infrastructure poll at one-second intervals.

GPU workloads ramp in eight milliseconds.

AI is accelerating faster than the infrastructure beneath it can be understood.

We are not a monitoring solution. We are the electrical intelligence layer — the validation layer that sits between the physical environment and the autonomous control systems the industry is building toward. Solving this matters beyond the business case. Carbon‑free AI, stranded capacity recovery, and the long‑term reliability of the compute layer the world is betting on all depend on getting electrical intelligence right at the physical layer.

Twenty people. Lean by design. We have raised serious capital, refocused the company around the most consequential problem in AI infrastructure, and come out the other side with real customers, real revenue, and hardware that has been running in colocation and owned data center facilities for more than a decade. The cloud platform processes billions of 8 kHz waveform readings and turns them into validated operating limits that operators use daily.

This unique position—built on our high‑fidelity 8 kHz metering—converts the strain on electrical infrastructure into a definitive roadmap for solving the AI industry's most critical power bottleneck and driving the sector's next wave of technological improvement.

Today that means reliability and early warning. Tomorrow it means capacity optimization and machine‑facing orchestration APIs that GPU schedulers consume directly.

We are hiring an Engineering Manager to own the cloud platform — the system that makes all three product pillars work:
Observability, Intelligence, and Orchestration.

You would manage a team of elite engineers, report to the cofounder/CTO, and hold a mandate to raise the bar on how this team builds and ships. This is a player‑coach role. You will set direction, run the engineering operating cadence, and manage people. You will also read code, debug production issues, and make architectural calls. If you have not been in a codebase recently, this is not the right fit.

We are building the management layer to accelerate towards best‑in‑class industry standards: clear ownership, a culture of high craft, and leadership that empowers and accelerates rather than administrates. The candidate we want believes in this velocity.

One more thing: a big part of how we operate is through deliberate, opinionated use of agentic coding tools. The team is actively migrating towards an AI‑native culture, learning how to adopt practices that scale. You will be instrumental in defining and coaching the next standard for AI‑native development here, and you will recruit and coach to that standard.

The platform works. Customers depend on it. The 8 kHz ingestion pipeline is real and running in production.

The platform is at a strategic inflection point: we must mature the architecture and organizational structure to support the scale and velocity of our next‑generation product roadmap. We need someone who can take ownership of the platform, organize the team around clear ownership, and raise the quality bar — while also building toward future application layers that do not exist yet.

• Audit the platform: reliability, scalability, observability, tech debt. Form your own view, not just ours.
• Organize ownership across the three‑pillar stack. Ingestion and the 8 kHz pipeline. ML signal processing and validated operating limits. The APIs, MCPs, and workflows that deliver them.
• Stand up an engineering operating cadence: roadmap reviews, incident reviews, delivery planning, architecture reviews.
• Get your hands dirty on the hardest reliability and performance problems. Ship fixes, not just plans.
• Establish AI‑native development practices on the team. Not a policy — real tooling norms, a shared view on where agentic coding…