Professional Services Integration Director

Gigawatt is building the AI-native software that runs America s utilities - a modern, agentic suite spanning customer, revenue, service, and procurement operations. We are live with our first major utility customer and scaling fast. Learn more at . Gigawatt s platform is only as valuable as the data moving in and out of it. Integrations run in both directions: they bring a customer s source-system data - CIS and billing, meter and interval usage, outage, clearinghouse, and more - into Gigawatt, and they create and send Gigawatt s data, bills, events, and results back out to customer systems and other platforms. Increasingly they are also a product in their own right: a reusable connector and API capability that lets Gigawatt plug into any customer s landscape. Today integrations are also our biggest constraint - work has slowed delivery, some of it needs to be revised or rewritten, and integration dependencies stall other teams. This role owns that problem in both directions and turns it into a durable capability. As Integrations Lead, you are a hands-on architect and builder - a player-coach who sets the integration patterns and still writes the hard connectors yourself. You own the delivery and connector layer end to end: the connector framework, the inbound source-system integrations, the outbound flows that publish Gigawatt data and results to other systems, the data mappings in both directions, and the pipelines and APIs that carry them - while our Engineering team owns the core platform and its underlying APIs. The role is cross-module from day one, serving Customer, Revenue, and Service, with our anchor customer as the proving ground where patterns get hardened first and then made reusable for the customers we sign next. You ll report into the Customer Organization and partner tightly with Engineering (platform), Product, and each customer s enterprise-integration team - and you ll grow a small integration team behind you as we scale. On the inbound side, our approach is a four-pattern, single-replica design - API read, API write, Kafka initial load, and Kafka change-data-capture - moving data from customer source systems through Oracle GoldenGate and Confluent Kafka, via Boomi, into a Gigawatt local replica that feeds the modules. On the outbound side, Gigawatt exposes a rich integration surface - GraphQL, batch, webhook/hook, and event APIs, plus connectors and event streams - so external systems and platforms can consume Gigawatt s governed data and react to its events. You ll own and evolve both sides on the delivery layer. Key Responsibilities • Own integrations in both directions - Own how data moves into Gigawatt from customer source systems and how Gigawatt creates and sends data, bills, events, and results back out to customer systems and other platforms - inbound and outbound are one accountable surface. • Build the outbound integration capability - Design and build the connectors and APIs (GraphQL, batch, webhooks/hooks, Kafka and event streams) that let client systems and other platforms consume Gigawatt data and events - for example pushing bill results back into the CIS / MACSS, EDI transactions, Choice and market flows (enrollment, load settlement), payment and ticket write-backs, and curated data, analytics, and regulatory outputs. • Build a reusable connector framework - Define and evolve a connector framework and integration patterns (API read/write, batch, event/CDC) that are portable across customers and platforms, so each new client and module is faster to connect than the last. • Build hands-on - Personally design, build, and harden connectors and pipelines (Boomi processes, Kafka / GoldenGate CDC, REST and GraphQL, batch and event APIs), and retire the integration debt that s slowing delivery today. • Own data mapping & quality, both ways - Own source-to-target and target-to-source mapping and establish a data-validation framework, so data lands complete and correct in either direction and mapping gaps are caught before they reach testing rather than during it. • Own the two-way operational handshake - Stand up the trigger/handshake between Gigawatt and customer systems and put monitoring, alerting, reconciliation, and exception handling in place, so inbound feeds and outbound flows are reliable, observable, and automated rather than run by hand. • Onboard new connectors - Stand up integrations to utility systems - CIS / billing, meter data and MDM, outage, clearinghouse, and similar - reusing shared patterns across modules and customers. • Unblock cross-module dependencies - Be the person other module teams rely on to remove integration blockers, and sequence connector work against the roadmap so integration stops being the constraint on delivery dates. • Partner across the boundary - Work closely with Engineering, who own the core platform and its APIs, feeding real integration needs into platform priorities; and work directly with each customer s enterprise-inte...