The role & impact
You'll join a team that builds the operating system keeping Product & Technology's nervous system running. Rather than watching operational leaders wrestle with spreadsheets and manual processes, you'll design and ship internal tools and AI powered workflows that free up 2,000 people to focus on what they do best, building great products.
This is hands on builder work with real influence. You'll own the full lifecycle from identifying operational friction through to shipping reliable, production grade tools that operations managers, TPMs and product leaders depend on every day. You're not building features for external customers, you're building solutions that directly unlock scale across a global organisation.
The team & how they connect
The Operating Tools & Workflows team sits within Global P&T Operations, working directly with the Director of Operating Tools and Models and embedded operations managers across the product and engineering organisation. You'll be the technical partner in a small team focused on building automation and intelligent systems that power Xero's operating rhythms, quarterly planning, delivery tracking, resource management, and roadmapping. You'll work closely with operations leaders, TPMs and senior P&T stakeholders who understand the business problems but rely on you to translate them into working solutions.
Initially, you will focus on
•Delivery Status Reporting: Build an intelligent system that synthesizes delivery data across Jira, reducing the weekly manual status gathering that currently consumes significant leadership time
•Headcount Management: Design AI-assisted forecasting and resource planning tools that help operations leaders understand capacity, predict bottlenecks, and allocate people effectively across a ~2,000 person organization
•Automated Roadmapping: Create tools that map cross team dependencies, surface conflicts early, and generate roadmaps that actually reflect how work flows through the organisation
•Finding the next opportunity: Scan P&T's operating model constantly for toil, inefficiency and manual workarounds, then pitch and prototype solutions before you're asked
Where and how you can work
You can be based anywhere in Australia or New Zealand. The team works hybrid and is used to collaborating across time zones with regular in person time to align, plan and work together intensively.
Here are some of the things we're looking for
•You bring hands on software engineering experience with a track record of shipping production systems, comfort with Python, TypeScript or similar languages paired with sound judgment on when to code from scratch versus when to extend existing platforms and APIs
•You've built or shipped actual solutions using AI and LLMs: not just experimented with ChatGPT, but designed and deployed real, production-ready AI systems (agents, automations, workflows) that solved meaningful problems at scale
•You understand operational systems thinking: you can listen to how an org actually works, spot where manual effort could be automated, and propose solutions that balance engineering elegance with practical impact
•You have a product mindset for internal tools, you treat operations managers as customers, design intuitive workflows that work for non-technical users, and obsess over adoption and reliability rather than architectural purity
•You bias toward rapid prototyping and shipping: comfortable moving from problem definition to working prototype in days, then iterating quickly based on how people actually use your tools
•You can translate between worlds: comfortable moving between engineering conversations and operations conversations, explaining technical constraints and possibilities in language that lands with both audiences
•You bring genuine curiosity about how large organizations operate: real interest in operating models, workflows, and what actually creates bottlenecks in a fast-moving Product & Tech function
•You understand sound engineering fundamentals: you know enough about resilient system design, security, data integrity and documentation to avoid building fragile, one-off solutions that become unmaintainable nightmares
SUCCESS LOOKS LIKE
At 6 months:
•You've shipped at least one operational tool (Delivery Status Reporting, Headcount Forecasting, or Roadmapping) into production that operations leaders are using daily
•You've prototyped solutions for 2-3 operational problems, narrowed down which ones to build vs. buy vs. automate, and have a clear roadmap for the next phase
•Operations managers and TPMs are coming to you directly with problems, recognising you as the person who can rapidly prototype and ship
•You've demonstrated deep understanding of P&T's operating rhythms, how quarterly planning works, where manual effort is highest, what creates bottlenecks
At 12 months:
•You've delivered a suite of tools that materially reduce operational toil, delivery status synthesis, headcount forecasting, roadmapping with dependency mapping are all in use and trusted
•Your tools are reliable, well-documented and maintainable: they scale with the organisation, not fragile hacks that break when assumptions change
•You've lifted the broader operations team's capability with AI: they're using Claude Code and AI automation in their own work, following patterns you've established
•Operations and P&T leadership see you as a trusted technical partner who understands both what's possible technically and what actually matters operationally
WHAT YOU'LL BRING
•Experience working with or within product engineering teams at scale, ideally in a large global technology company
•Production agentic AI experience: Hands-on track record building with LLMs, coding agents (eg Claude Code, GitHub Copilot) and AI automation — real solutions shipped and used, not personal projects or prototypes
•Sound software engineering fundamentals: Proficient in a coding language, with the judgment to know when to write custom code versus when to leverage, configure or extend existing platforms
•Full-stack thinking: Comfortable owning problems from data layer to interface: you can design simple data models, integrate via APIs, work with common enterprise systems (Jira, Confluence, Workday, Google Workspace, data warehouses)
•Operational problem solving: Ability to assess friction points in how organisations actually work, and determine whether a custom build, low code workflow, vendor customization or combination of approaches yields the highest return with the lowest maintenance burden
•Bias to shipping: You move from idea to working prototype quickly, then iterate based on real feedback rather than perfectionism
•Communication across audiences: You can explain what's technically feasible and what isn't, translate between engineering and operations language, and help non-technical stakeholders understand tradeoffs and constraints
Our Hiring Process
1. TX phone screen (45 minutes): a conversation with your Talent Specialist about your background, motivations and the role.
2. Round 1 (60 minutes each): Consists of two seperate interviews:
1. Coding hackerrank interview
2. Case Study
3. Round 2 (60 minutes each): Consists of two interviews:
1. Values: a conversation focused on how you work with senior stakeholders and show up against Xero's values, including ownership, customer thinking and AI fluency.
2. Technical Deepdive
If this role sounds like it aligns with what you're looking for and have experience with, hit the apply button!