Product Manager — API · vacancy
Here's what AI can do for this role — and what still needs a human. Built straight from ENSEK's own job advert, running live on my_db.ensek_demo.accounts — 27,640,145 real rows via MotherDuck (DuckDB). Not a slide about AI. The job, getting done.
Every line on the left is lifted from ENSEK's actual job ad. If a card lacks a harvested JD line, it is omitted. On the right is the AI doing it — with eligible cards running live against the warehouse and offline inspection clearly labelled in the workspace.
“Own the strategy, vision and roadmap for both the API-as-a-product programme — engaging stakeholders across engineering, commercial, and customer teams to define, validate and iterate it continuously.”
What is the API resource volume by region — account and meter count per region (the payload scale the API must serve)?
bar chart“Define and drive a consistent framework for API definition and management across three tiers: internal domain APIs, cross-NSEC internal APIs, and external APIs for customers, brokers, and third parties.”
What is the monthly consumption data volume — kwh and bill totals per month (the data transfer volume the API handles for monthly reporting integrations)?
bar chart“Make evidence-based prioritisation decisions, estimating effort and value of roadmap items using AI-powered estimation tools, and communicating trade-offs transparently with stakeholders.”
Which customer segments have the most accounts and highest consumption — the priority API consumer profiles?
bar chart“Define and track key product outcomes — implementing dashboards for real-time performance visibility and using data to drive continuous improvement.”
What is the smart vs traditional meter API payload complexity — meter_tech distribution (smart = high-frequency reads, traditional = manual-read orchestration)?
bar chart“Build long-term stakeholder relationships, implementing communications strategies and influencing effectively to drive alignment and outcomes.”
What is the dual fuel account share — main_fuel mix among active accounts (dual fuel customers need two meter API calls — the doubled-payload case)?
kpiThe honest other half. AI does the analysis; a person owns the decision — especially where regulation, fairness and accountability bite.
A plain-English question — the same one the job ad describes — is translated to SQL by the agentic backend.
Curated cards run server-side against MotherDuck when eligible. The workspace separately labels any local inspection path.
Runs against my_db.ensek_demo.accounts (27,640,145 rows declared by the manifest). No synthetic numbers.
Each figure carries a falsifier — recomputed from the result set, not a stored number, so it can't quietly drift.
It's the role getting done: curated questions run live server-side against the warehouse; local inspection is labelled inside the workspace.
Open the live workspace →Provenance. Representative ENSEK-style operational dataset (480 accounts · 728 meters · 5,676 monthly consumption records). Schema mirrors my_db.ensek_demo.accounts/meters/consumption_monthly. Seed 20260609 — reproducible. No real ENSEK or customer data. Live server-side path: my_db.ensek_demo.accounts (27.6M rows). Dormant until operator provisions MOTHERDUCK_TOKEN.
It's Sorted — I took ENSEK's job ads and didn't write a report on what AI could do. I built it. Get the rest sorted →
I'm trained on this proof and the real ENSEK: the Ignition meter-to-cash platform (seven modules), the move under Centrica in 2024, 7M+ energy accounts migrated for suppliers like British Gas and Utility Warehouse, and the Ofgem framing. Ask me how the Data Analyst function changes shape, or which open roles map to which Ignition module.