Technical Project Manager

Key Responsibilities

• Drive a shared, well-defined understanding of requirements and use cases across Product, Engineering, and Services, and maintain traceability from requirement to design to build to test to customer sign-off.
• Own the delivery operating rhythm: services-led status and escalation, a living risk register, dependency tracking, and go/no-go checkpoints, and align Gigawatt’s cadence with the customer’s sprint / PI-planning cadence so both sides plan against the same dates and dependencies.
• Orchestrate the end-to-end test effort across teams—system integration testing, parallel bill validation, and user acceptance testing—while Product and Engineering own quality within their own work; establish a shared definition of done and a clear defect-resolution and communication process, and prepare and support the customer’s testing team so their cycles aren’t blocked.
• Partner with Engineering to hold the environment strategy across dev/test/UAT/prod, and steward the promotion and release workflow (dev-first testing and smoke tests before controlled promotion to staging and production with the right approvals) so environments stay stable for both testing and live customer demos.
• Institutionalize “quality is everyone’s job” as an operating practice: reduce drift from designs, enforce requirement traceability, and drive release-readiness reviews—making the pieces line up rather than substituting for the teams that own the code and the tests.
• Bridge customer & UAT communication—be the reliable communication conduit between Gigawatt and the customer’s business and UAT teams and their test center of excellence; coordinate per-account validation and sign-off tracking (including documented, conditional sign-offs where a variance is accepted), keep the customer informed on the tight cadence they expect, and help hold the customer accountable to their side of scope, process, and data commitments.
• Partner cross-functionally—hold a clear RACI so each team owns its own deliverables rather than the program absorbing everyone’s tasks, and translate what you learn in delivery into a structured feedback loop for Product and Engineering.

What You’ll Bring

• Utility experience: Meaningful experience in the utility or energy industry— you understand how utilities operate and can hold your own with customer SMEs.
• Consulting / SI background: A track record delivering complex software or integration programs for enterprise clients as a consultant or systems integrator.
• Project & program management: Proven technical project/program management on multi-team software delivery, with real fluency in requirements definition, use-case traceability, and structured delivery governance.
• Testing & UAT coordination: Hands-on experience coordinating testing and UAT across a vendor and a customer, with a shared definition of done and a disciplined defect process.
• Environments & release: Comfort with environment and release management concepts—multiple environments, promotion workflows, and release readiness as a first-class dependency.
• Customer presence: Clear, calm, and credible communication under a demanding customer’s expectations, with the ability to translate between technical and business audiences.
• High agency: A strong bias for ownership—does the homework, brings options, and drives to decisions rather than escalating raw problems; low-ego, high-cooperation, and comfortable with ambiguity.

Nice to Have

• Exposure to utility CIS / billing systems and data—customer/billing platforms, meter/interval usage, and tariff and rate structures.
• Familiarity with integration tooling and patterns (e.g., Boomi, Kafka / CDC, REST APIs).
• Experience in Agile / SAFe / PI-planning environments and with delivery tooling such as Jira.
• Experience standing up PMO / delivery discipline in a fast-moving, high-growth setting.