Note: The job is a remote job and is open to candidates in USA. Gigawatt is seeking a Principal Product Manager to lead its Integrations & Developer Platform team. The role owns integration surfaces, data quality tooling, outbound data products, API and SDK design, partner enablement, and the roadmap for making utility platform integrations self-service and scalable.
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
Skills
- 8+ years in product management, with significant time on integration, API, or data platform products that people outside your own company built against
- 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
- 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
- You have integrated with legacy enterprise systems where every customer's instance is different and the standard is implemented differently everywhere
- 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
- Comfort across reverse ETL, event streaming, batch and file transfer, and API delivery, plus enough warehouse fundamentals to own a Snowflake-based offering
- 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
- Able to bridge partners, SMEs, services, and engineering; strong communication and structured problem-solving
- You thrive in early-stage ambiguity, move fast, and are comfortable with a role that grows and changes as the company scales
- Experience with Jira, Figma, and standard product management tools
- Remote: prioritizing central and eastern timezones (ideally Chicago, Austin, or Nashville)
- Utility experience is a plus but not a requirement
- 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
Benefits
- Equity
- Health insurance
- Remote flexibility
- 401k match
Company Overview
Company H1B Sponsorship