English
  • English
  • Dutch
  • German

Contract and permanent hiring are not simply two ways to buy the same IT capability. The right choice depends on the work, when it is needed and whether the organisation must retain that knowledge after delivery.

November 2026 market evidence shows a cautious hiring picture, with IT still attracting selective permanent demand.

For technology leaders setting 2027 budgets, the distinction matters. The wrong mix can leave a project unfinished, a platform dependent on knowledge that leaves with a contractor, or a permanent hire without work that fits their level.

Cost is only one part of the decision

Comparing a contractor’s daily rate with a permanent employee’s salary can make the decision look straightforward. It is not like-for-like. A permanent salary sits within wider employment costs, while a contract rate reflects a time-limited engagement and may include the contractor’s business costs, gaps between assignments and other risks. A fair comparison includes sourcing, onboarding, management, delivery and continuity.

The Office for National Statistics reported 690,000 UK vacancies between August and October 2026, down 22,000 or 3.0% compared with May to July 2026. This all-sector measure is not a technology vacancy count, but it provides context for cautious headcount decisions.

The financial question is what the organisation needs to secure. A contractor can bring specialist capacity at a defined point in a programme. A permanent employee can build context, maintain systems and develop capability over time. A lower initial cost can become expensive if it creates repeated handovers or leaves no one accountable after launch.

Match the engagement to the work

Contract hiring tends to fit work with a defined outcome, time horizon or temporary capacity gap. Examples include a platform migration, cloud landing-zone build, systems integration, data-centre exit, major software release or delivery backlog. It can also suit a business that needs a specialist skill for one critical phase but cannot justify a permanent role afterwards.

Permanent hiring is often more appropriate where work is continuous and connected to the operating model. Maintaining core infrastructure, owning architecture decisions, supporting users, managing service reliability and improving engineering standards continue beyond a project milestone. They require knowledge of the organisation, its systems, stakeholders and risk appetite.

The distinction is about the work, not the title. A DevOps engineer might establish deployment pipelines for a defined transformation on contract, or own the engineering platform permanently. A software developer might join a fixed-term product build or a team maintaining a product for years. Seniority alone does not determine the model.

Some work needs both. A permanent team can own the service and its long-term direction, while contractors add capacity during a delivery peak. This works when responsibilities are explicit, documentation is part of delivery and knowledge transfer is planned from the start.

Market signals call for selective hiring

The KPMG and REC UK Report on Jobs, published in November 2026 and based on October survey data, found that permanent placements fell for the first time in four months. Temporary billings declined after rising for six consecutive months. Overall vacancies continued to fall at the softest pace since August 2024. Six of the ten monitored job categories recorded increased demand for permanent workers, led by IT and Computing and Engineering. Of the four categories recording higher demand for temporary staff, the steepest increase was in Blue Collar roles. The report is a UK recruitment survey across sectors, with specific breakdowns by job category.

The CIPD’s Labour Market Outlook: autumn 2026, published in November 2026, found that 58% of private sector employers planned to recruit over the next three months. This covers employers across all private sector industries, not IT specifically. It indicates general hiring appetite, not a forecast of technology recruitment.

IT Jobs Watch provides a role-specific view. For the UK, it reported a median permanent DevOps Engineer salary of £70,000 from 1,615 adverts and 1,113 salary quotations over the six months to 18 November 2026. For contract DevOps Engineer roles over the same period, it reported a median daily rate of £525 from 1,107 adverts and 851 daily-rate quotations. These are indicative advertised measures, not guaranteed pay or take-home comparisons. Annual salary and daily rate are not equivalent totals.

The evidence points to selective permanent demand in IT alongside a wider market where temporary hiring has softened. Employers need to understand which capabilities are difficult to source, how long they are needed and what must remain in-house.

A balanced team protects delivery

Consider a retailer replacing its ageing order-management platform across several regions. The programme has a fixed implementation window, complex integrations with warehouse and supplier systems, and a support requirement that will continue after rollout. An entirely permanent team may leave excess capacity when implementation ends. Contractors for every part of the programme may leave the organisation short of people who understand the platform after specialists move on.

A better model starts with the future operating requirement. The retailer retains a permanent product owner, platform lead and service team, accountable for priorities, architecture, supplier relationships and ongoing support. Contractors join for defined integration, migration, testing and release work where extra delivery capacity is needed. The permanent team works alongside them, reviews design decisions and owns documentation and operational handover.

The plan identifies knowledge to transfer before each contract ends. Acceptance criteria include tested runbooks, support procedures, system documentation and time for the incoming team to work through live scenarios. The organisation is clear about which expertise is temporary and which knowledge it must retain.

The reverse applies too. A business facing a long-term skills shortage should not use successive short contracts to cover a permanent operational need. Where demand is continuous, a permanent role may provide better continuity and a stronger basis for developing internal capability.

Candidates weigh more than the rate

Experienced IT professionals assess the two routes differently, and neither is automatically more attractive. Contracting can offer variety, exposure to different environments, control over assignments and, in some circumstances, a higher headline rate. It can also mean gaps between engagements, uncertainty about future work, time spent finding the next contract and responsibility for business costs and administration.

Permanent roles can offer a predictable salary, paid leave, benefits, development and the chance to build influence within one organisation. For professionals who want to shape a platform, mentor colleagues or progress into leadership, continuity can be valuable. The trade-off may be less variety.

The assignment itself matters. Contractors will want clarity on scope, deliverables, duration, authority, working arrangements and the likelihood of extension. Permanent candidates will assess the team, technology roadmap, management quality, progression and whether the role has a meaningful remit. Both will consider whether expectations are realistic and decisions are made promptly.

Employment status and off-payroll arrangements are separate from the commercial preference for a contract. HM Revenue & Customs guidance on off-payroll working, last updated in February 2026, explains that the rules can apply where a worker provides services through an intermediary and would have been an employee if engaged directly. Treatment depends on the circumstances and relevant rules. Businesses and individuals should seek specialist employment and tax advice rather than assume a contract label determines status.

Set the workforce plan before budgets close

Before finalising 2027 budgets, technology leaders should map planned work against the capability needed to deliver and operate it. Separate project demand from ongoing service demand. Then identify skills already in the team, gaps that can be developed internally and expertise that must be brought in.

The plan should identify the cost and consequence of each option. For a contract engagement, define the outcome, duration, handover and exit criteria before recruitment begins. For a permanent role, confirm the continuing workload, reporting line, decision rights and development opportunity. For a blended team, agree who owns delivery decisions and how knowledge will be retained.

Finance, HR and technology leaders should make these decisions together. Finance can test affordability across the full engagement, HR can support a sustainable workforce structure, and technology leaders can define the capabilities and accountabilities required. Legal and tax specialists should advise where employment status or off-payroll rules are relevant. A clear brief gives candidates a more accurate picture and gives the business a better basis for evaluating the market.

Specialist IT recruitment with MBA

Michael Bailey Associates supports organisations with contract, interim and permanent IT recruitment across specialist technology environments. By understanding the work to be delivered, the capability that must remain and the experience available in the market, MBA helps clients shape hiring requirements around business priorities. If you are reviewing the balance of your IT team for 2027, a discussion about the work ahead and the skills required can be a useful place to start.

 

19 November 2026

Why Cybersecurity Is No Longer One Talent Pool

05 October 2026

Contract or Permanent: Building the Right IT Team for 2027

10 September 2026

Why the IT Talent Market Is Moving Faster Than Most Hiring Strategies Can Keep Up With