Product Manager — Identity, Access Management & Customer Configuration · 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 identity and access management — evolving coverage from human users to AI agents, and incorporating auditing and security governance requirements as they emerge.”
What share of active accounts are fully configured — valid meter assignment, settlement class and tariff?
kpi“Define and drive product requirements for AI agent identity and permissions, working closely with the AI framework team to ensure agentic systems are appropriately secured, auditable, and governed.”
How does the active book split by settlement class — HH vs NHH by customer segment, with mean revenue?
bar chart“Lead the customer configuration product area — understanding how configuration needs vary across customer segments and building scalable, self-service capabilities that reduce operational burden.”
Which active accounts are mis-configured — Traditional meter technology but classified as HH settlement?
deviation“Make evidence-based prioritisation decisions across identity, access, and configuration workstreams, estimating effort and value of roadmap items and communicating trade-offs transparently with stakeholders.”
How many active accounts have a PSR flag set — vulnerable account coverage by region?
bar chart“Define and track key product outcomes — implementing dashboards for real-time performance visibility and using data to drive continuous improvement in security posture and customer experience.”
How are active accounts distributed across tariff types — is every account on a valid, identifiable tariff?
bar chartThe 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.