Company Overview

See https://gigawatt.ai

Job Summary

We are seeking a Principal Product Manager to lead Gigawatt's Power team, the group that builds what a utility's customers see when the lights go out. You own two surfaces: powerout.info, a public destination open to anyone, and the utility-branded experiences we deliver through our Customer modules, including embeddable outage maps, mobile and web, and the notification system behind them.

This is Gigawatt's only consumer product. Everything else we build is bought by a utility and used by its employees. This is used by millions of people who never chose us, on a phone at 11pm, on the worst night of their year. Peak value and peak load are the same moment: baseline traffic is close to nothing, and during a hurricane it is a thousand times that within minutes.

Trust is the product, and it is asymmetric. A wrong restoration estimate is worse than no restoration estimate, because people decide whether to move a relative on oxygen or drive to a shelter based on what we tell them. The same asymmetry governs notifications: every message you send is a call you either prevented or caused.

You also own a real tension. Deciding what is public, what is utility-controlled, and what happens when they conflict is the central judgment of this role.

This is an early-stage, build-it-from-the-ground-up role. Reporting to the SVP of Product and leading the Power product team, you will partner closely with engineering, design, the Customer and Platform module teams, our AI platform team, and our first utility customers to:

• Ship the consumer experience: premise-level power status, outage reporting open to anyone, alert signup, and a restoration tracker people already know how to read.
• Own the notification system: what triggers a message, how it is deduplicated and throttled, and how a utility configures its own rules without producing noise.
• Make the platform survive its own success: the load profile we design against, the failure modes we accept, and the degraded experiences still worth serving.
• Turn public reports into operational signal the utility will act on.

Key Responsibilities

• Own the roadmap: Drive strategy and roadmap for powerout.info, the utility-branded outage surfaces, embeddable widgets, and notifications, and make the build-versus-buy calls along the way.
• Own the public and private boundary: Define what is public by default, what a utility can brand or withhold, and what we will not let a utility suppress. Write the principle down and hold it when a customer pushes.
• Own what we tell people: Define the confidence model behind status and restoration estimates, when we publish, when we widen an estimate, and when we say we do not know. Silence and uncertainty are product decisions here, not gaps.
• Own notification quality: Triggers, delay rules, deduplication, quiet hours, channel preference, and the consent and opt-out flows that keep mass messaging lawful and welcome. Complaint and unsubscribe rates are primary quality signals.
• Design for the people with the most at stake: Medical baseline and life-support customers, non-English speakers, low-bandwidth devices, accessibility, and a phone that is losing charge. In a storm these are not edge cases.
• Own scale as a requirement: Set the concurrency, latency, and availability targets we build and test against, and run the game days that prove them before a storm does.
• Own where status comes from: Utility feeds, meter pings, last interval data, call center signals, public and third-party sources, and customer reports. Own the quality, latency, and dependency risk of each, including the plan for when a source disappears.
• Turn reporting into signal: Keep public reporting genuinely open while handling duplicates, noise, and abuse, and define how validated reports reach utility operations.
• Coordinate the seams: Power status intelligence, AI agents, and customer service surfaces belong to other teams. Define where your product ends and keep that boundary from drifting.
• Execute: Drive with engineering and design to release production-ready capabilities on compressed timelines, defining use cases and technical requirements and conducting product testing to ensure key requirements are met.
• Own outcomes: Set KPIs (call deflection during peak events, time from losing power to first accurate notification, alert signup and retention, delivery and complaint rates, restoration estimate accuracy, availability and p95 latency during named events, reports per event and duplicate rate, CSAT) and manage dependencies across the platform.
• Wear many hats: Do whatever it takes to move the product forward, and take on new areas of ownership as priorities evolve.

Qualifications

Utility experience is a plus but not a requirement. We have deep domain expertise in house and will teach it.

Must Have

• Consumer product experience: 8+ years in product management, including significant time on a product used directly by the public at scale, where you owned comprehension and retention rather than a feature set negotiated with a buyer. You have shipped to users with no training and no patience.
• High-stakes products: You have shipped something people relied on in a moment that mattered: emergency or safety, health, travel disruption, payments, or logistics tracking. You know the difference between a product that is usually right and one people can act on.
• Scale and reliability as product problems: You have owned a product with a spiky, event-driven load profile and specified availability, latency, and graceful degradation rather than leaving them to engineering. You can hold your own in an architecture review. You do not need to write production code.
• Notifications at scale: You have run push, SMS, or email for a large user base and lived its consequences: deliverability, throttling, deduplication, consent, and the point where volume starts destroying trust.
• Data you do not control: You have built a user-facing experience on data you could not fully trust, and made calls about what to show, what to caveat, and what to withhold.
• Two masters: Experience with a product serving an enterprise buyer and an end consumer whose interests diverge, and a point of view on adjudicating that rather than escalating it.
• Startup mindset: You thrive in early-stage ambiguity and are comfortable with a role that grows and changes as the company scales.

Nice to Have

• Maps and geospatial: Consumer mapping, tiling, clustering, and representing uncertain geographic state honestly.
• Crowdsourced data products: Products whose value depends on user-contributed data, including cold start, density, and abuse.
• Regulated communications: Consumer messaging compliance, accessibility requirements, or regulated customer communications.
• AI-native product work: Retrieval, intent detection, and guardrails, shipped against a quality bar rather than a demo.
• Embeddable and white-label products: Widgets or embedded experiences deployed inside someone else's brand.
• Domain and background: Utility or energy exposure, outage management systems, or a background in engineering, design, or data before product.
• Tools: Experience with Jira, Figma, and standard product management tools.

Location

• Remote: prioritizing central and eastern timezones (ideally Chicago, Austin, or Nashville).

What We Offer

• Competitive salary and equity.
• The chance to shape a transformative AI product in a vital industry with a rock-star team.
• Comprehensive benefits: health insurance, remote flexibility, and 401k match.
• If you are passionate about modernizing the systems that run America's utilities, apply today!