Service Transformation Officer at QUT: What the Role Actually Involves and Who Should Apply

Work that starts where the front line ends

The Service Transformation Officer at Queensland University of Technology (QUT) is not a frontline customer-facing role. The successful candidate won't be answering enrolment questions at the HiQ desk or sorting out a student's fee dispute over the phone. They'll sit behind the teams that do that work, finding ways to stop the same questions and the same manual rework from piling up each semester.

Student Administration is the administrative core of the university. It covers admission, enrolment, fees and invoicing, timetabling and class registration, examinations, results, records, progression and graduation. Every one of those functions runs on documents, guides, dashboards and automated workflows. When the documents are stale, the guides are outdated and the dashboards don't reflect reality, the busiest stretch of the academic year becomes a scramble.

The day-to-day, in plain terms

The position description breaks the work into a few related habits. The officer maintains information and knowledge repositories in SharePoint, Confluence and the intranet, applying information governance, records management and content quality standards so the right document doesn't disappear into an old team drive. Writing user-focused communication and capability resources is the second habit—the one-page guide that replaces a sixteen-step procedure. Third is the data work: pulling records out of the system, checking them against the source, validating what's inconsistent and interpreting what the pattern says before it lands in a dashboard.

Automation sits underneath all of it. The role names Power Automate and Microsoft Copilot alongside Teams and Power BI. It asks for sound judgement when a flow breaks or an issue needs escalation, which is a pointed ask: the university wants enough technical grasp to configure a simple workflow, and enough organisational sense to know when a problem is a governance decision rather than a configuration error.

The reporting line also matters. The officer reports to the Manager of Service Transformation, which means the work feeds directly into the wider service reform program rather than a general administrative pool.

Why the role exists right now

QUT has spent heavily on digital transformation in recent years. Its 2024 annual report notes that the pace of change accelerated and drove additional information technology costs in a tight labour market. The university has built a connected-campus program with Accenture on Salesforce's platform. Accenture's case study reports an 84 per cent lift in proactive student engagement and a 69 per cent reduction in response times after more enquiry work moved onto a shared CRM and AI layer. A single Salesforce org now supports 24 business groups and around 750 frontline agents.

Those are large platform numbers. They only hold if the content inside the platform is clean, the guides are current and the dashboards leaders look at are fed with reliable data. KPMG's 2024 study of student service improvement across roughly half of Australia's universities found that institutions lag in using customer-experience tools—not because senior staff don't care, but because student service delivery sits inside a deeply complex operating environment. The unglamorous repair work behind the CRM numbers is exactly what this role exists to carry.

Two examples show what that repair work can produce. When the University of Melbourne redesigned its Stop 1 service, average phone wait times for current students fell from two minutes and thirty seconds to thirty-three seconds. At the University of Technology Sydney, moving the core student management platform to the cloud through Boomi cut the grade ratification process from sixteen days to twenty-four hours for roughly 40,000 students. Different institutions, different starting points, same lesson: after the big platform goes live, someone still has to own the process detail.

What a convincing application shows

QUT lists the formal expectations plainly. A degree or equivalent experience in business, communications, information management or a related discipline, combined with subsequent professional experience. Demonstrated experience running information and knowledge repositories, writing user-focused resources, supporting service improvement or business change initiatives, and analysing data through reports and dashboards. SharePoint, Teams, Power BI, Power Automate and Microsoft Copilot are named as hands-on tools, not as nice-to-haves.

The selection criteria also reveal a stronger test: QUT wants someone who can do process analysis and requirements gathering and then convert that into an implemented improvement. A process map is not the end product. The role asks for evidence that you consulted the staff who do the work, understood their constraints and delivered a change they actually adopted.

The final criterion—demonstrated commitment to equity, diversity and Indigenous Australian engagement—sits inside QUT's strategic priority of Indigenous Australian success. Treat it as a real criterion and bring a specific example, not a sentence of good intentions.

Pay, location and the fine print

The role is classified at HEW6, the Higher Education Worker level that covers much of the professional staff work in Australian universities. QUT quotes total remuneration of $111,341 to $120,557 a year, which includes a base salary of $94,084 to $101,872, superannuation of 17 per cent and recreation leave loading of 17.5 per cent. If you're comparing this to a private-sector salary, the total package is the fairer number to use.

The position is fixed-term and full-time until 31 July 2027, based at the Kelvin Grove campus with a hybrid option available. It's open to current QUT staff with unrestricted work rights for the length of the fixed-term appointment. In support of the university's strategic priority of Indigenous Australian success, Aboriginal Australians and Torres Strait Islander people who are not QUT staff are also eligible and encouraged to apply. Current staff seeking a secondment need their supervisor's approval before submitting.

Applications close at 11.30pm on 3 November 2026. The fixed-term end date of 31 July 2027 signals a defined piece of work with a clear horizon, not an open-ended posting. A full plain-English walk-through of the position description is also available on AcademicJobs.

What this means for your team

Most service transformation work at Australian universities arrives as fixed-term money attached to a platform rollout, and most of it is advertised internally first. That internal-only base rate is worth stating plainly: if you're outside the university and the ad doesn't say otherwise, you can't apply. QUT's exception is specific and deliberate—Aboriginal Australians and Torres Strait Islander people who aren't QUT staff are explicitly encouraged. Read the eligibility clause before you spend an evening on the application.

A colleague—call her Dr. R—spent her first fortnight in a similar improvement role rebuilding a timetabling dashboard that pulled from a spreadsheet kept by someone who had left six months earlier. Multiply her by every enrolment peak. The technology was fine. The information governance was not. That's the habit this role is meant to enforce: one shared repository with a current README and a named owner, applied from day one, not retrofitted after the audit.

The one concrete next step

If you're a current QUT staff member, open the position description and check the eligibility clause against your own status before you do anything else. Ask your supervisor about secondment approval now, because the close date of 3 November 2026 allows less than two weeks from listing to lodgement. Candidate enquiries go to Ruth Stegeman, Manager of Service Transformation, on (07) 3138 6660. Ring with a specific question about the work, not a general one about the role.

If you're outside QUT and don't meet the Indigenous Australian eligibility pathway, the honest move is to watch for the next externally advertised round and build the evidence in the meantime: a documented process improvement, a dashboard you rebuilt, a set of user guides that actually got used—and ideally one Power Automate flow that survived its first exception.