You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Xero

Senior Engineer - Product & Tech: Operations

  • Hybrid
  • 6+ years

Salary

Not stated

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The team builds the internal operating system that keeps the company's Product and Technology function running. Instead of leaders working through spreadsheets and manual steps, you'll build tools and AI-driven workflows that give about 2,000 people more time for building products.

The work is hands-on, and you'll have real say in direction. You'll take a problem from spotting friction through to production-grade tools that operations managers, TPMs and product leaders use every day. The users are internal, but the impact reaches across a global organisation.

The Operating Tools and Workflows team sits in Global P&T Operations. It works directly with the Director of Operating Tools and Models and with embedded operations managers across product and engineering, automating quarterly planning, delivery tracking, resource management and roadmapping. You'll be the technical partner to operations leaders, TPMs and senior P&T stakeholders, who know the business problems and rely on you to turn them into working solutions.

At 6 months, you'll have shipped at least one operational tool into daily use, prototyped solutions for 2-3 operational problems with a clear next-phase plan, and be the person operations managers and TPMs bring problems to directly. At 12 months, the suite of delivery status synthesis, headcount forecasting and roadmapping with dependency mapping will be in use and trusted, and the broader operations team will be building with AI using patterns you set.

Responsibilities

  • Build an intelligent system that pulls delivery data from Jira and removes the weekly manual status gathering that takes significant leadership time.
  • Design AI-assisted forecasting and resource planning tools that show operations leaders their capacity, flag upcoming bottlenecks and help them allocate about 2,000 people.
  • Create tools that map cross-team dependencies, raise conflicts early and produce roadmaps that match how work actually moves through the organisation.
  • Continuously look for toil, inefficiency and manual workarounds in the operating model, then pitch and prototype fixes before anyone asks.
  • Own the full lifecycle of each tool, from problem definition and prototype through to reliable, documented production systems that scale.
  • Lift the wider operations team's AI capability by sharing patterns and tools they can use in their own work, including Claude Code and AI automation.

Requirements

  • Hands-on software engineering experience, with a record of shipping production systems in Python, TypeScript or a similar language.
  • Judgment on when to write code from scratch and when to extend existing platforms and APIs.
  • Production experience with LLMs, agents, automations or workflows that solved real problems at scale, not personal projects or experiments.
  • Experience with coding agents such as Claude Code or GitHub Copilot.
  • Experience working within product engineering teams at scale, ideally in a large global technology company.
  • Full-stack ability to design simple data models, integrate through APIs and work with enterprise systems such as Jira, Confluence, Workday, Google Workspace and data warehouses.
  • Operational problem solving: you can judge whether a custom build, low-code workflow, vendor customisation or a mix gives the best return with the lowest maintenance load.
  • A bias to shipping: you move from idea to working prototype quickly and improve it based on real feedback.
  • A product mindset for internal tools: you treat operations managers as customers, build workflows non-technical people can use, and focus on adoption and reliability.
  • Curiosity about how large organisations operate, including operating models, workflows and bottlenecks in a fast-moving Product and Technology function.
  • Sound engineering fundamentals in resilient design, security, data integrity and documentation, so tools stay maintainable.
  • Clear communication across audiences: you can explain what is and isn't technically feasible, and translate between engineering and operations language.

Conditions

You can be based anywhere in Australia or New Zealand.

The team works hybrid, collaborates across time zones and meets in person regularly to align, plan and work intensively together.

Where you’d work

Part of the week in the office

You can work from

  • Australia

About the company

Xero

Office in Auckland, New Zealand

Also hiring in Vancouver, Canada, Toronto, Canada, Sydney, Australia and 4 more places

2 of their 32 open roles are remote

Your chances

We've checked whether it's still hiring and how crowded it is.

  • 19 checks run
  • 0 red flags

Still hiring?

13 checks

No red flags

How crowded?

6 checks

No red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details12 facts · Role, Location, Compensation, Employment
Tech stack
  • TypeScript
  • Python
  • LLMs
Seniority
Senior
Type
Full-time
Specialty
Backend
Region
Australia
Pay period
Annual
Show 6 more factsShow less

Role

Category
Development
Specialty
Backend
Seniority
Senior
Experience
6+ years
Tech stack
  • TypeScript
  • Python
  • LLMs

Location

Work model
Hybrid
Region
Australia
Office
  • Auckland, New Zealand
Remote from
  • Australia

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Full-time

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason