Job Opportunities API

ABOUT APHEX We're the construction planning platform replacing outdated spreadsheets with multiplayer tools that delivery teams love. Major contractors like Acciona, CPB Contractors, John Holland, and McConnell Dowell use Aphex to deliver projects from £50 million to multi-billion pound mega projects. We're market-leading in Australia and the UK, supporting teams building the roads, rail, tunnels, and hospitals that millions use every day. Our founding thesis: owning the planning layer is a gateway to solving high-friction adjacent processes in what we call the orchestration layer of major project delivery. THE ROLE We're looking for a Senior Product Manager to own our Insight & Data area — the measurement layer of the Aphex platform. You'll report directly to the Head of Product and lead a squad of ~6 engineers that flexes with scope. The opportunity: Aphex captures something unique — granular, structured data about how major projects actually execute. Not just what was planned, but the daily record of what happened: coordination, progress, constraints, the gap between plan and reality. This dataset doesn't exist anywhere else at this fidelity. Our thesis is that the behaviours teams run — publishing cadence, daily coordination routines, statusing discipline — are the leading indicators of project performance. Measuring those routines, scoring them, and connecting them to outcomes is the core intellectual problem of this role. Nobody in construction has done it. Your two customers: 1. The user. Signals surfaced inside their existing workflow that change behaviour on site — not another dashboard. A routine-health score a project team actually acts on. Org-level insight an executive trusts. 2. Aphex itself. Your measurement system is the evidence layer for our own product decisions — activation curves, feature landed-vs-rejected, routine adoption. Success looks like every PM in the company citing your measures in their briefs without having to ask you for a report. Your charter — what you own: - The core measures: the canonical, tool-agnostic definitions of project and user behaviour (publishing scores, daily-cycle activity, routine health) and the taxonomy underneath them - The data platform: the pipelines and aggregated data models everything reads from - MCP and the API surface: how customers and AI tools access their data - Eval frameworks for the AI agents that consume this data - The org/admin surfaces: admin console, org-level insights, report sharing, request-access — end-to-end, your team ships these - Activation as an outcome: instrumenting and driving the behaviours that make projects stick Explicitly not yours: - The daily-cycle workflow itself (briefings, capture, diary) — owned by the Planner and Diary teams - In-workflow rendering of your signals — you own the signal contract (what's measured, what triggers, what good looks like); the surface teams build the moments, prioritised like any other roadmap work That split is deliberate. This is a leverage role: your definitions and data flow through every team's roadmap. WHAT YOU'LL DO Own the measurement system - Define, defend, and version the core measures of project behaviour and performance - Connect behavioural routines to outcomes — build the evidence for what actually predicts delivery - Make the measures self-serve for users, customer teams, and internal product/GTM teams Own delivery - Run discovery through QA to launch with your engineering team - Write specs and briefs your team can execute against — and hold them to their briefs - Independently sanity-check sequencing and estimates; challenge what doesn't smell right - Make daily trade-off calls on scope, timeline, and quality Own the platform - Data pipelines, aggregated models, and the API/MCP access layer - Platform reliability — major projects depend on accurate, accessible data Partner across the company - P