Company Overview

See https://gigawatt.ai

Job Summary

We are seeking a Principal Product Manager to lead Gigawatt’s Integrations & Developer Platform team, the group that makes our platform something other people can build against. Every utility we serve runs on systems we do not own: MV90, Oracle Customer Care & Billing (CC&B), SAP IS-U, meter data management systems, AMI head-ends, asset management, and GIS. Getting data out of those systems, keeping it trustworthy, and getting results back into the utility’s stack is what stands between a signed contract and a working deployment.

Your team does not build every connector. Systems integrators (SI), consultants, and utility IT teams do that, in tools like Boomi, against our GraphQL APIs and exports. Your job is to make that work possible without a Gigawatt engineer in the room. The bar for success is a partner who integrates us, deploys, and never needs to call us.

You own three surfaces: data in, data quality, and data out. You also own a boundary. This team builds reusable product; bespoke, single-customer work belongs to services, and you will be the person who defends that line while our lighthouse customer is going live.

The deployment reality shapes everything you build. Our customers run SaaS, on-premise, and hybrid, and in most cases their data never leaves their network. You will design for version skew, upgrades you do not control, and diagnosing failures without being able to look at the data. The exceptions matter too: market data comes in from PJM, and wholesale settlement postings go out, where a data error moves money.

This is an early-stage, build-it-from-the-ground-up role. Reporting to the SVP of Product and leading one product team, you’ll partner closely with engineering, services, data science, and our first utility customers to:

• Own the integration surface: GraphQL APIs, SDKs, export formats, and logs and diagnostics detailed enough that someone outside Gigawatt can build and debug an integration on their own.
• Make data quality legible: profiling, freshness, completeness, and drift, attributed to a source system and an owner so a utility knows what to fix, with hard gates only where data drives money or an irreversible action.
• Get data out: reverse ETL, events, APIs, and files into a utility’s BI stack or warehouse, including the managed Snowflake option we offer customers who do not have one.
• Cut time-to-integrate: establish the real baseline for onboarding a utility and drive it down, module by module and system by system.

Key Responsibilities

• Own the roadmap: Drive strategy and roadmap for the integration surface, data quality tooling, and outbound data products, and make the build-versus-buy calls along the way.
• Own the integration flow catalog: Define and curate the canonical set of integration flows across source systems and modules: what data moves, in which direction, on what trigger, at what latency, with what error and replay semantics. Module PMs own the business use case and the acceptance criteria; you own the flow that satisfies it in a way the next customer and the next module can reuse. When a module needs a bespoke path where a canonical one exists, you own the call.
• Own the data mastering point of view: Drive a clear position on which system masters each core entity: customer and account, premise, meter and interval data, assets, network topology, outage events, work orders, and the data Gigawatt itself creates. In most cases the utility's systems of record win, and our job is to consume them cleanly. Where Gigawatt does master data, agent decisions, recommendations, settlement calculations, and quality assessments, you define how it is governed, synced, and reconciled. You hold the pen and drive it to a decision with engineering and the data fabric team.
• Build for partners, not just for us: Own API and SDK design, documentation, sandboxes, reference implementations, and error messages good enough to self-diagnose. How fast an SI can integrate us without our help is your headline number.
• Own the API contract: Versioning, backwards compatibility, and deprecation policy. Customers deploy on their own schedules and inside their own networks, so you cannot break them and you cannot assume they upgraded.
• Coordinate with the AI Platform team: Agent tool and action APIs are owned by AI Platform; the underlying integration flows and data contracts are owned here. You define where that seam sits and keep it from drifting.
• Ship data quality as a lens: Surface issues, attribute them to a source system and an owner, and give utilities a path to resolution. Gate hard where correctness is non-negotiable, starting with wholesale settlement. Make quality signals available to our AI platform so agents know when not to trust their inputs.
• Own data out: Define the outbound story across reverse ETL, event streams, APIs, and files, and the warehouse offering for customers without one of their own.
• Defend the product line: Define the criteria for when a services-built integration gets promoted into the product, and the criteria for when it does not. Support the lighthouse deployment without becoming its integration team.
• Execute: Drive with engineering to release production-ready capabilities on compressed timelines. Drive the product lifecycle by defining use cases and technical requirements, collaborating on data model and API design, and conducting product testing to ensure key requirements are met.
• Own outcomes: Set KPIs (time-to-integrate, share of go-lives requiring core product changes, integrations built without Gigawatt engineering involvement, API coverage against the data model, data quality incidents caught before they reach a customer, post-go-live support load) and manage dependencies across the platform.
• Wear many hats: Do whatever it takes to move the platform forward. This role covers more surface than one person will own permanently, and we expect it to split as we scale. You will help decide how.

Qualifications

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

• Experience: 8+ years in product management, with significant time on integration, API, or data platform products that people outside your own company built against.
• Partner and developer enablement: You have shipped APIs, SDKs, or a connector framework that third parties depended on in production. You have lived versioning and deprecation, partner escalations, and the difference between an API that works and an API someone else can succeed with unaided.
• Enterprise deployment reality: You have shipped software that runs in a customer’s environment, on-premise or hybrid. You know what version skew, customer-controlled upgrades, and debugging without access to the data actually cost, and you design for them from the start.
• Messy systems of record: You have integrated with legacy enterprise systems where every customer’s instance is different and the standard is implemented differently everywhere. Healthcare interoperability, financial data aggregation, insurance, or ERP integration all translate well here.
• Data quality judgment: A real point of view on profiling, freshness, lineage, and anomaly detection, and on the harder question of when to flag an issue versus block the pipeline.
• Data movement fluency: Comfort across reverse ETL, event streaming, batch and file transfer, and API delivery, plus enough warehouse fundamentals to own a Snowflake-based offering.
• Holding the line: You have been asked to ship a one-off into the core product and can describe how you handled it. We want someone who has both the judgment to say no and the credibility to make it stick with a services team.
• Collaboration: Able to bridge partners, SMEs, services, and engineering; strong communication and structured problem-solving.
• Startup mindset: You thrive in early-stage ambiguity, move fast, and are comfortable with a role that grows and changes as the company scales.
• Bonus: Exposure to utility source systems (MV90, CC&B, SAP IS-U, MDM, AMI head-ends, EAM, GIS), wholesale market operations, or a background in software or data engineering before moving into 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!