About this role
Aurora is expanding how clients access and use our analytical capabilities. Alongside our applications, we increasingly make our data, models and insights available programmatically, so they can be embedded directly into our users' own systems, workflows and decision-making. Chronos is Aurora's storage valuation platform, used by asset developers, investors and utilities to navigate complex decisions about how battery storage assets are valued and deployed across global energy markets. Your mission in this role is to productise our sophisticated analytical capability, Aurora's storage and hybrid asset dispatch modelling, into a coherent programmatic surface. The Asset Dispatch API is a consumption and distribution surface for Chronos: success means deeper and more valuable use of Chronos (valuable workflows enabled, depth of use, adoption and retention, and reusable leverage across Aurora products). The hard problem is not exposing existing functionality through endpoints, but deciding which problems should be served programmatically, for whom, through which capabilities and in what sequence, and which should be served another way or not at all. This is a senior individual contributor role with no line management. You will work in close partnership with our engineering organisation, shaping the API contract together: its abstractions are both technical architecture and product design. This is a fixed-term maternity cover with a small number of concrete outcomes to reach within the cover period. The final outcome set will be agreed at offer stage. You will need to get to the important questions quickly, establish evidence early, and turn that learning into incremental delivery. Productise Aurora’s asset dispatch capability into a coherent programmatic surface. Own which Chronos problems are served programmatically, for whom, through which capabilities, and in what sequence. The depth and value of client use measures success. Decide what belongs on the API and what does not. The Chronos application, files, scheduled outputs, agent tooling, or another Aurora-built experience may best serve a given need. The API should focus on core programmatic needs rather than duplicating every application feature. Run API-specific discovery. Investigate requests for endpoints, feeds, and integrations to understand the underlying workflow, decision constraints, and reusable programmatic needs. Triangulate user requests with observed usage data where available. Shape the API contract jointly with engineering. Investigate requests for endpoints, feeds, and integrations to understand the underlying workflow, decision constraints, and reusable programmatic needs. Triangulate user requests with observed usage data where available. Own the developer experience as product. Investigate requests for endpoints, feeds, and integrations to understand the underlying workflow, decision constraints, and reusable programmatic needs. Triangulate user requests with observed usage data where available. Manage the lifecycle consequences. Define what each version guarantees, assess the impact of changes on consumers, and plan deprecation timelines clearly. Own the migration of existing users, tooling, and workflows onto the new surface, treating it as a product problem of segmentation, sequencing, and enablement rather than just a communication task. Make Asset Dispatch compose within Aurora's wider programmatic offering. Aurora's domain APIs should compose into coherent workflows rather than become a collection of disconnected endpoints. Preserve genuine domain differences within Asset Dispatch while helping establish shared concepts and conventions where they create leverage. Bring constraints in early and represent the product clearly. Work with commercial, legal, entitlement and enablement stakeholders early enough that their constraints inform decisions rather than emerge at launch. Communicate product direction and trade-offs clearly to senior stakeholders, and support go-to-market teams with product narratives and demos.