QUT has put two software engineer roles on the board at once, and if you've been circling a move to Brisbane or out of a pure product company, that's worth a second look.

The listing is live through Queensland University of Technology's e-recruitment portal and mirrored on AcademicJobs under the title Engineer, Software (2 positions available). Two seats, one application track. You don't need to know anyone inside the university to be considered; you need to read the position description, address the selection criteria, and submit through the portal.

This is not a teaching role, and you won't be marking assignments. The university runs a large technology and information services operation alongside its faculties. The work tends to sit in teams responsible for enterprise systems, integration, identity, student platforms, research data, or digital products. Which team these two roles land in is set out in the position description on QUT's job card.

Two software engineer roles at QUT: what to weigh before you hit apply

Queensland University of Technology has two main campuses: Gardens Point, right on the edge of the Brisbane CBD, and Kelvin Grove, just over two kilometres north. Professional and technical staff are spread across both. If you're comparing this with a product company or a bank, the trade-offs are different from what many engineers expect. Base salaries at universities can sit below private-sector packages at fintechs and mining technology firms. The package is where the gap narrows: superannuation at Australian universities is generally above the legislated minimum, leave arrangements are usually strong, and the work touches systems with tens of thousands of students and staff.

You need to check four things before you spend an evening on the application.

• Read the position description first. QUT's selection criteria drive shortlisting. If the ad asks for cloud experience, integration platforms, or identity systems, open with a specific example that shows you've done it and what changed as a result.
• Do not paste your CV into the criteria boxes. Tailor each response to the criterion. A university selection panel reads dozens of these. A concrete result beats an adjective every time.
• Use a clean structure. Situation, task, action, result is still the most reliable way to answer selection criteria. It forces you to include a measurable outcome.
• Check the closing date and apply early. QUT roles can close at a specific time on the listed day. Last-minute portal traffic is not your friend.

The fact that QUT is hiring two people at once changes the arithmetic. The panel isn't hunting for one perfect candidate; it can appoint two strong engineers with overlapping skills. If you meet eight of ten criteria, apply. Software engineers routinely under-apply compared with candidates in other fields, and the biggest filter in this process is simply not being in the pool.

You'll find the full position description through QUT's e-recruitment job card at QUT's recruitment portal. If the long link gives you trouble, search the university's jobs page for Engineer, Software and you'll see the two positions listed together.

Before you write anything, spend fifteen minutes on the university's own pages. QUT's careers page links to organisational structure, digital strategy, major technology projects, and its published technology roadmap. That context helps you name the systems and problems that matter in your application, which is the difference between a generic response and one that reads like someone who already knows the institution.

Also keep the AcademicJobs listing open as a reference. It mirrors the key details and keeps the application link easy to find when you're ready to submit.

How QUT's application process works

Once you're in the portal, you'll need an account. QUT's e-recruitment system lets you save a draft, but a saved draft is not an application. After you hit submit, you should get an acknowledgement email. If you don't, log back in and check the status.

Shortlisting at universities works differently from private-sector hiring. The panel scores your written responses against the selection criteria before they decide who to interview. A CV alone rarely gets you through that gate. The person who reads your application isn't scanning for buzzwords; they're checking whether the evidence under each heading matches the criterion above it.

That means you should write plainly. Lead with the outcome: what you built, what it ran on, how many users it served, and what improved after you shipped it. Don't waste the opening line on a summary of your career; the panel already has your CV.

The ad won't always name the technology stack. University job ads sometimes stay broad deliberately, because the team may work across several systems and the hiring manager wants evidence you can adapt. If the position description names a stack, use that language in your examples. If it doesn't, show breadth across cloud architecture, integration, software delivery, and observability rather than listing every tool you've ever touched.

Keep your CV to four pages. That's enough to show recent, relevant work. A reviewer who is scoring criteria responses won't read a ten-page CV, and a longer document doesn't make you look more experienced.

The cover letter should be one page. Use it to say why QUT and this role, not just why software engineering. Connect one recent project to the university's digital work. If the ad references a student platform, a research data service, or identity systems, name the one you'd strengthen and why.

What a university software role is actually like

Universities are not slow because they lack technical talent. They're slow because the technology estate is broad, regulated in places, and tied to the academic calendar. You'll likely work with a mix of bespoke and off-the-shelf systems, legacy enterprise platforms, cloud services, and identity infrastructure. The problems are meaningful: enrolment systems that spike around offer rounds, research data moving between institutions, student-facing portals that need to stay available during exams, and enterprise identity services that handle thousands of concurrent logins.

That said, university procurement and security processes are real constraints. If you're used to shipping fast in a small product team, expect more governance, more stakeholders, and more documentation. Some engineers find that frustrating. Others find it a fair trade for working on campus systems that outlast any startup runway.

Brisbane's technology market has changed considerably over the past decade. The city now has a substantial presence of banks, consultancies, government agencies, and product companies all chasing the same mid-level engineers who can work across cloud and enterprise systems. A university position is rarely the highest offer on the table, but it is often the most stable, and the two-role ad signals that QUT is building depth rather than replacing one person.

For national demand data, Jobs and Skills Australia publishes occupation-level projections for software and applications programmers. It's worth a quick look if you're weighing a Brisbane move against another city.

If you reach interview

If the panel invites you in, expect technical questions plus scenario questions about working with non-technical stakeholders, vendors, and incident response. University technology work usually involves a mix of build, integrate, maintain, and sometimes decommission systems. You'll be asked how you handle a production incident during exam week or how you'd explain a technical trade-off to a business owner who isn't an engineer.

Prepare a short answer for why you want to work at a university. It doesn't need to be sentimental. A direct answer about stability, scale, or the type of problems on campus is more persuasive than pretending you always dreamed of working in higher education.

What to do this week

Do not wait for the closing date to get started. University recruiting can be slower than private industry, but the panel will not chase you. Submit a complete application, confirm the receipt, and then follow up only if the advert says to.

This week, open the QUT position description and draft one criterion response before you close your laptop.