The Five-Year Gig: What a Long Fractional Engagement Actually Looks Like

From 2018 to 2023, I worked part-time as an Azure architect and DevOps lead for a century-old heavy equipment manufacturer. Five years. Not full-time — fractional, a few days a week, sometimes more when things were busy, sometimes less when they weren’t. But consistently there, consistently involved, consistently part of the team.

In the contracting world, that’s unusual. The typical engagement is three to six months: parachute in, assess the situation, fix things, hand over, leave. There’s a rhythm to it. You learn to ramp up fast, deliver quickly, document thoroughly, and extract yourself cleanly. It’s what most people picture when they think of a contractor.

Five years is something else entirely.

How it started

I joined to help with an Azure migration. Classic scenario — a large, complex on-premises estate that needed moving to the cloud, a team that was skilled in their existing stack but had limited cloud experience, and a timeline that was ambitious without being insane. The kind of engagement where you bring in someone who’s done it before so the team doesn’t have to learn everything the hard way.

The initial scope was straightforward: architecture, guidance, some hands-on work to establish patterns and practices. Help the team get going, build their confidence, set up the foundations. Three to six months, maybe nine. Then hand over and move on.

That was the plan, anyway.

What actually happened was that the work kept evolving. The migration surfaced architectural decisions that needed revisiting. The team grew and needed mentoring. New projects came along that benefited from someone who understood both the existing landscape and the Azure platform. DevOps practices needed embedding — not just the tooling, but the culture. CI/CD pipelines, infrastructure as code, monitoring, incident response — all the things that make cloud infrastructure sustainable rather than just “on-premises but someone else’s data centre.”

So I stayed. Not because they couldn’t manage without me — they absolutely could, and increasingly did. But because there was genuine value in continuity, and both sides recognised it.

What long-term fractional actually looks like

There’s a world of difference between a five-year part-time engagement and a five-year permanent role. Understanding that difference is important, because it’s easy to slide from one into the other without noticing.

You’re still external. This never changes, no matter how long you’re there. You don’t get the benefits. You don’t get the pension. You don’t get the stock options or the annual bonus. You don’t get invited to the company retreat — or if you do, it’s as a courtesy, not an entitlement. You’re not in the promotion pipeline. You don’t have a career path within the organisation. You are, fundamentally, a supplier.

This sounds like a disadvantage, and in some ways it is. But it’s also a superpower. Being external means you can say things that internal people can’t. You can point out that the emperor has no clothes without worrying about your next performance review. You can push back on bad ideas without political consequences. You can be honest in a way that permanent staff often can’t afford to be.

I used that licence regularly. Not to be difficult — to be useful. “This architecture won’t scale.” “This process is slowing the team down.” “You’re over-engineering this.” “The vendor is selling you something you don’t need.” When you’re not playing the internal politics game, you can focus entirely on what’s right for the work.

You build deep domain knowledge. This is the biggest advantage of a long engagement, and it’s the one that short-term contractors never get. After a year, I understood the business domain — not just the technology, but why things were built the way they were, what the constraints were, what had been tried before and failed. After two years, I knew the organisational dynamics — who the decision-makers were, who the blockers were, how to get things done. After three years, I had institutional memory that most of the permanent team didn’t have, because turnover had cycled through several rounds of new hires.

That depth matters enormously. Technology decisions don’t exist in a vacuum. Every architecture choice is shaped by the business context, the team’s capabilities, the organisation’s appetite for risk, and the history of what came before. A contractor who’s been there six months can give you technically correct advice. One who’s been there five years can give you advice that actually works in your specific context.

You maintain a different perspective. The flip side of deep domain knowledge is the risk of going native — losing the outside perspective that made you valuable in the first place. This is a real risk, and I’ll come back to it. But if you manage it, the combination is powerful: deep enough to understand the context, external enough to see it clearly.

The risks are real

Five years is a long time, and not all of it is upside.

Becoming furniture. The biggest risk. You’ve been around so long that people stop noticing you’re there. You become part of the background — comfortable, familiar, unchallenging. The urgency that existed when you first arrived dissipates. You settle into a routine. The engagement stops being about delivering transformative value and starts being about maintaining the status quo.

I caught myself drifting towards this a couple of times. The antidote is deliberate discomfort — actively looking for things to challenge, new problems to tackle, areas where you’re adding value rather than just occupying a chair. If you can’t articulate what specific value you delivered this month that justifies your rate, you’ve become furniture.

Being treated as permanent without the benefits. This is a contractual and psychological trap. The longer you’re there, the more the organisation treats you like an employee. You get added to the org chart. You’re expected at all-hands meetings. People forget you’re a contractor and start making assumptions about your availability, your loyalty, and your obligations.

But you’re not an employee. You don’t have the protections, the benefits, or the security. If the budget gets cut, you’re the first to go — no redundancy, no notice period beyond what’s in your contract, no emotional farewell. I’ve seen contractors at other organisations get blindsided by this after years of being treated as part of the team. The relationship felt permanent. The contract wasn’t.

Maintaining clear boundaries is essential. I always made sure the engagement had explicit scope, regular reviews, and mutual understanding that either side could end it. Not because I wanted out — because clarity protects everyone.

Scope creep — the “Charlie knows” problem. After a few years, you become the person who knows how everything works. Developers come to you with questions about systems you set up three years ago. Managers ask you to review things that aren’t in your remit because “Charlie knows the context.” You become a single point of knowledge for parts of the estate that should be owned by the team.

This is dangerous for both sides. For the client, it creates dependency. For you, it means you’re spending time on maintenance rather than value-adding work. The solution is aggressive knowledge transfer — documenting everything, pairing with team members, and actively pushing back when people come to you instead of learning the system themselves. “I can help you figure this out, but next time you should be able to do it without me.”

That’s not being unhelpful. That’s doing your job properly.

The world changed around us

Five years is a long time in technology, and the period from 2018 to 2023 was particularly eventful.

COVID. I started the engagement in an office. By March 2020, everyone was at home. The shift to remote work was abrupt and total, and for a contractor who was already used to working across multiple clients and locations, it was less of an adjustment than it was for the permanent staff. But it fundamentally changed the engagement model. The informal conversations, the whiteboard sessions, the overheard discussions — all gone. Replaced by Teams calls and Slack messages and the slightly exhausting performance of being present on camera.

Remote work actually suited the fractional model better, in some ways. When you’re not physically in the office, the distinction between “part-time contractor” and “full-time employee” becomes less visible. Everyone’s a tile on a screen. But it also made it harder to build relationships with new team members who joined after the transition. You lose something when you’ve never shared a coffee with someone.

Azure evolved enormously. The Azure platform in 2018 was a very different beast to the one in 2023. When I started, Azure DevOps was still relatively new — it had only just been rebranded from Visual Studio Team Services. AKS was early-stage. Azure Policy was limited. The whole governance and landing zone story was immature.

By 2023, the platform was unrecognisable in many ways. AKS was mature and battle-tested. Azure Landing Zones had become a well-documented framework. Bicep had emerged as a viable alternative to ARM templates. The security and compliance tooling had leapt forward. GitHub Actions was eating Azure Pipelines’ lunch.

Watching a major cloud platform evolve from the inside over half a decade is a rare experience, and it’s one of the things that kept the engagement fresh. There was always something new to evaluate, adopt, or — just as importantly — decide not to adopt. Not every new feature is worth the migration cost, and having the historical context to make that judgement is one of the biggest advantages of a long engagement.

The team changed completely. Over five years, almost every member of the original team moved on. New people joined, brought different skills and perspectives, and needed different things from me. The architect role evolved from “help us migrate to Azure” to “help us build a cloud-native engineering culture.” The work shifted from hands-on implementation to mentoring, reviewing, and strategic guidance.

That evolution is natural, and it’s healthy. If you’re doing exactly the same work five years in as you were on day one, something’s wrong. Either you’re not growing, or the team isn’t.

The antithesis of mercenary

There’s a narrative in the industry that contractors are mercenaries — parachute in, collect the money, disappear. No loyalty. No investment in the outcome. No skin in the game.

A five-year engagement is the opposite of that. You can’t sustain a relationship like that without genuine investment in the team, the work, and the outcome. I cared about whether the architecture held up. I cared about whether the team was developing. I cared about whether the decisions we made in year one were still serving the organisation in year five. That’s not mercenary behaviour.

The Harvard Business Review and others have written about the rise of fractional and portfolio careers. The model is growing because it works — for organisations that need senior expertise without the full-time cost, and for professionals who want variety, autonomy, and the ability to work at the level where they add the most value.

But fractional only works if you commit to it properly. That means being genuinely engaged, not just turning up. It means caring about the outcome, not just the invoice. It means building relationships and transferring knowledge and making yourself redundant on the things that the team should own — even though your continued engagement depends on being needed.

The paradox of good fractional work is that you’re constantly trying to make yourself unnecessary, while simultaneously finding new ways to be valuable. If you can sustain that tension, the model is incredibly rewarding for both sides.

When to walk away

The hardest part of a long engagement is knowing when it’s done.

Not when the contract ends — that’s mechanical. But when the value equation has shifted. When the team is strong enough that your contributions are marginal. When the work has become routine rather than challenging. When you’re maintaining rather than building. When you’ve become furniture.

I left the engagement in 2023 because it was the right time. The team was capable. The platform was mature. The major challenges had been addressed. There were new things to do — there always are — but they were things the team could handle without me. My job was done.

That’s the best way for a long engagement to end: not with a crisis, not with a budget cut, but with a mutual recognition that the work is complete. The team is stronger than when you arrived. The systems are better. The knowledge has been transferred. And you leave with relationships and references that last far longer than the engagement itself.

Not every engagement should last five years. Most shouldn’t. But when it works — when the scope keeps evolving, the value stays high, and both sides remain honest about what the relationship is — it’s a model that serves everyone well.

After nearly thirty years of contracting, the five-year gig remains one of the most rewarding things I’ve done. Not because it was the most technically challenging — other engagements have been harder. But because it proved that you can be a contractor and still be invested, still be trusted, and still leave things better than you found them.

That’s not mercenary. That’s professional.