AWS Networking operates one of the largest and most complex networks on the planet. The team you'd join is responsible for the availability of that network — measuring how it performs for customers, predicting where it is most likely to degrade, and reshaping how we operate it as the workload grows. We are in the middle of a significant change in how network operations are run. Lessons from our recent work on automation, AI, and ML — including agentic systems that triage and mitigate incidents alongside engineers — are feeding into a broader rethink of where humans focus, where automation takes over, and how we measure whether either is working. We are looking for a Data Scientist to join the team in Sydney to drive the data science strategy behind that change. You will define the metrics that matter, own the evidence the team uses to make decisions, and measure whether each decision delivered the outcomes we expected. You'll be the data science voice on a team of senior network and software engineers — the person who decides what we measure, how we measure it, and what the numbers actually mean. Concretely, that means setting the analytical bar for the program, designing risk and reliability models against telemetry from millions of network devices, surfacing the patterns that drive customer-impact incidents, and turning that analysis into the dashboards and metrics our leaders use to set priorities. It also means owning the evaluations that tell us when a new piece of automation — including the agents we are rolling out to support engineers on the front line — is actually moving the needle on availability, and not just adding noise. If you are a scientist who wants to shape how a tier-one production network is run — using data to drive program strategy, not just to support it — at a scale no academic lab or startup can match, and you're at your best as the data science voice embedded in a team of engineers, this is the team for you. Key job responsibilities - Define and drive the data science strategy for the program — the metrics, the experiments, and what counts as evidence that a change worked - Lead the design and deployment of predictive risk and reliability models for network availability, using device failures, alarm telemetry, ticket data, and traffic signals - Own the evidence behind program decisions: where availability is at risk, where automation is ready to expand, where engineering effort has the highest leverage. Defend recommendations to senior technical and business audiences - Design and own the operational analytics and dashboards (Amazon QuickSight, Amazon CloudWatch, Python) used by senior leadership to track network health and the impact of operational change - Design and run experiments to evaluate the automation we are rolling out — including agentic systems supporting engineers on incidents — measuring whether each rollout improved availability - Drive data quality and classification improvements — event categorisation, root-cause attribution — so the program's metrics rest on solid ground - Build and own event-driven scoring pipelines (Python, SQL, AWS Lambda, Amazon S3, Amazon Athena) that keep the decide / measure / improve loop running - Bring statistical rigour to the engineers you partner with — review experiment designs, push back on unsupported assumptions, and raise the bar on how the team uses evidence A day in the life You might start the morning defining how the team will measure a new initiative — the success metrics, the counterfactual, the bar for calling it a win. By mid-morning you're with the engineering team turning a proposal into a decision: walking through trade-offs, pushing back where the data doesn't support an assumption. The afternoon is outcome measurement — refining the evaluation pipeline that tracks last week's rollout, updating the CloudWatch dashboard senior leadership uses to gate the next expansion, and prepping the data for an upcoming Director review. About the team We sit inside AWS Networking with a strong Sydney presence and a remit that spans network availability, the data and analytics that support it, and the automation we are building to change how operations are done. You'd be the data science voice in a small, senior team of network and software engineers in Sydney, partnering with the broader network engineering organisation across Seattle and Dublin. Small team, high autonomy, direct line to senior leadership, and a roadmap with real production impact rather than research demos.
