
Which Tech Roles Should Stay In Australia? Bunnings Just Published Its Answer
Blake Manchester4 min read
The roles to keep onshore are the ones holding administrative access, vendor authority and the architecture decisions. Delivery work can sit anywhere. Bunnings said on Tuesday it will make around 230 Australian technology staff redundant and end roughly 120 contractor engagements, moving delivery to Tata teams in India and the Philippines from December 2026.
It is also keeping an Australian technology team of around 500 people.
The second number sits in the same announcement and it is the one worth reading twice.
Outstaffer employs people in both of the countries Bunnings named, so read what follows as a disclosure of interest. If you are working out where a role could sit, the country explorer is the list we use ourselves.
Bunnings kept its Australian technology team and moved the delivery
Reported by the Australian Computer Society’s Information Age, the shape is plain. Bunnings keeps roughly three in five of its technology people in Australia and hands a greater proportion of delivery to a vendor. Wesfarmers’ 2026 annual report puts Bunnings at more than 51,000 team members across 506 stores, with earnings up 5.1 per cent to $2,455 million for the year to 30 June.
So a 500-person technology team is under one per cent of the headcount, and it is the part that did not move.
Information Age lists Qantas, Telstra, Woolworths, Officeworks and the Commonwealth Bank as other recent Australian examples of technology work moving offshore. It says nothing about what any of them kept, which is the number this post is about and the one hardest to find.
The arithmetic a thirty-person business should run instead
Bunnings is moving about 350 technology staff and contractor engagements against a retained team of 500. That is our own sum of the three published figures rather than a ratio the company stated. Your version is one developer of one. At that ratio the split Bunnings just made is not available to you, because there is nobody left onshore to hold the half it kept.
Which means the test is not the role. It is the ratio.
What does the role actually control?
Count the systems where that person is the only one who can grant, revoke or restore access. If the answer is more than zero, moving them does not move delivery. It moves control, and you will not notice until the morning it matters.
Which parts are genuinely downstream?
Build, test, support queues, reporting, integration maintenance and release work are downstream of a decision somebody else made. That is the same division an agency owner would recognise from the list the ad industry published this year: production travels, client judgement does not.
Cheap capacity is not the same purchase as a retained core
The honest counter is that most small businesses have no architecture worth defending and no vendor relationship worth holding, and for them the distinction is theatre. Often true. A two-person SaaS running on managed services has nothing to split.
It stops being true the first time a founder hires a second engineer and keeps paying the first one to be the only person who understands anything. That is not a staffing problem offshore or onshore, and a Vietnamese developer will not fix it either.
The Australian Computer Society put the risk as a question worth stealing: if a critical system goes down, who in Australia has the access, the authority and the expertise to get it running again?
Related reading
- Which country should I hire remote staff from? The clock just moved
- Australian job vacancies are down 31 per cent
What I would do on Monday
Write down every system in the business and the name of the person who can restore it. Then look at how many names you have. If it is one, your next hire decision is about redundancy of knowledge, not about a rate.
Then move the work that sits below those names, and keep the names. That is what the big end did this week, and it is the only part of it that scales down. If you want to test the shape on a live role rather than a spreadsheet, sign up and run one through it.
Which tech roles should stay in Australia is a question with a one-word answer at thirty staff, and most founders have never written the word down. How many of your systems have a second name against them?
Posted in Global Hiring category




