Senior Modelling Software Engineer, Squad Lead

The Origin Model sits at the centre of Aurora's forecasting capability, allowing Aurora to help governments, investors, and utilities make billion-dollar decisions on the journey to net zero. The models span power markets across the globe — translating complex energy system dynamics into robust, scalable software that underpins our market outlooks, client insights, and software platforms.This is a founding role. Aurora's São Paulo office is an established modelling hub for the Americas, but the Origin Model Development team there is still to be built — and you'll be the one building it. You will lead a new cross-office squad within the Origin Model Development team — with existing Oxford-based engineers and São Paulo-based engineers that you will help recruit. If you're drawn to the early-stage work of standing up a team — hiring the first engineers, setting the working norms, earning technical authority by doing the work yourself — this is that job. Bridging the two sites and keeping the squad working as one is the heart of it.This is a hands-on technical leadership role — the technical work is the primary job, not delivery management alone. You will write and review production code alongside your squad, co-design the squad's module boundaries with a senior technical authority who holds final say on architecture contracts, and deliver new features and progressive migration from a mature Python codebase into a well-bounded, modern architecture. The codebase uses GAMS with MOSEK as the optimisation solver. Deep expertise in energy system and numerical optimisation is strongly preferred for this work.Aurora is investing actively in AI-assisted engineering — not as a policy, but as a practice. Engineers here are expected to use AI tools fluently across the full development workflow: writing, reviewing, testing, and analysing code. Beyond personal productivity, this role contributes to building the agent workflows and tooling that raise the velocity of the whole team. If you have strong opinions about what good AI-assisted engineering actually looks like in production, this is an environment where those opinions matter.Running a cross-office team well is genuinely hard. Neither office is secondary to the other — the squad lead's job is to ensure São Paulo never becomes a remote execution arm for Oxford decisions. You will own the cohesion of the squad across two offices and two time zones — protecting the daily overlap window as synchronous time, and defaulting to async-first written decisions outside it.The São Paulo role requires 3 days a week in the office. Building a new team requires consistent in-person presence, and you will work closely with the existing teams already based there.