Technical Product Manager

About the role

Support the delivery of an EMS/PMS (Energy & Power Management System) product line built for AI-era data centers — software that monitors and manages power systems (BESS, switchgear, UPS, distribution, SCADA/edge) and optimizes energy across battery, grid, and HVAC load, with AI agents handling alarm response. You will work alongside the senior technical product manager, inside the engineering organization. This is a hands-on execution role: you keep the backlog honest, the requirements written, and the status real — so that when someone asks where a feature stands, the answer is a fact rather than an opinion. Full-time hours (up to 160/month). Note: you do NOT need EMS, SCADA, or industrial-controls experience — we have senior people to teach the domain. What we cannot teach is holding a complex program together, writing clearly under pressure, and telling someone a date is going to move before it moves.

What you'll do

• Requirements — write crisp product requirements and acceptance criteria for well-defined features, directly with engineers and QA

• Sprint execution — maintain the backlog and run sprint ceremonies; keep tickets accurate enough that the burndown actually means something

• SDLC tracking — track development across engineering areas (optimization, data platform, SCADA/edge) at sprint granularity; surface slips and dependencies early, with data, not status theater

• Documentation — own specifications, decision records, and release notes, and keep them current as scope moves

• Product metrics — instrument and report the KPIs that matter: alarm response performance, system availability, deployment velocity

• Deployment support — support UAT, commissioning readiness, and field-feedback capture at deployment sites; help fold what the first production site teaches us back into the backlog

• Reporting — assemble the weekly delivery update for the senior product manager and engineering leadership

What we're looking for

• 3–5 years in product management, product ownership, technical program management, or business analysis on software delivery

• You can write a requirement an engineer can build from without a follow-up meeting — this matters more than anything else on this list

• Working fluency in SDLC mechanics — sprints, branching, QA cycles, environment promotion, release trains; you can read a burndown and a ticket queue and tell what is actually true

• Comfortable in technical conversation about APIs, databases, data pipelines, and time-series telemetry — you do not need to write code, but you need to ask the right question in a design review

• Exceptional written communication — specs and updates people actually read

• Comfortable in a formation-stage organization: ambiguity, speed, and senior visibility

• The judgment to escalate a slipping dependency early rather than hope it recovers

Nice to have

• Exposure to energy systems, industrial controls/SCADA, IoT/edge, or other physical-world software (energy, utilities, manufacturing, data center infrastructure)

• Battery storage (BESS), grid services and demand response, or building-systems (HVAC) optimization

• Exposure to AI or agentic product features, and what it takes to productionize them

• Any hands-on engineering background