I knew someone who stayed in a Queensland Government contract for ten years. Same role, same desk, same fluorescent lights. No long service leave, just a slightly worn-out lanyard and a vague sense of existential drift.
There’s comfort in long-term gigs. You know who to talk to, who to avoid, and which meeting room still has working HDMI. If you’re lucky, the work keeps rolling: new phases, new projects, same ID badge photo from 2014.
But eventually, it ends
By then, the market has usually moved on. Tools change. Job titles mutate. Suddenly you’re explaining to a recruiter what Lotus Notes was and why you still have nightmares about records management systems.
I’m not here to hand out advice, just sharing some battle scars. Personally, I’ve always made a point of stepping away once the heavy lifting is done, usually post go-live, when the chaos gives way to BAU and the meetings start having minutes. Not because I’m done, but because the role is. I’d rather move on before the platform clears out and I’m left watching the next train disappear into the distance, CV in hand.
It isn’t always a trap
Long-term contracts can work in your favour. Sometimes you get to move sideways, learn something new and embed yourself across programs. The old consultancy playbook, land and expand, still works if you’re not afraid of a few extra hats.
The uncomfortable bit is that perceptions shift, especially in government. Contractors are often first to go when budgets tighten. I learned that the hard way after a change of government made contractors a target. Next thing I knew, I was working in Sydney. I didn’t plan it, but I packed a bag, went, and learned about bushfire risk mitigation along the way, which I found strangely interesting.
The lesson: keep your skills current, keep your network warm, and know why you’re staying.
Thinking about your next move? See how Talexa supports IT contractors.
