There is a signal worth paying attention to coming out of the recruitment market. Businesses are becoming markedly more selective about permanent hires, longer decision cycles, more approval layers, tighter budgets, while contract and embedded roles keep moving quickly, particularly across design, technology, transformation, and delivery functions. Candidates, too, are reportedly more open to contract work than they were a year to eighteen months ago. We work next to this market rather than in it, and the pattern matches what we see on the delivery side. It is worth saying clearly what the shift actually means, because the way it is usually framed, perm versus contract, is not the decision that matters.
This piece is a perspective on what the permanent-versus-contract shift signals for how UAE businesses resource delivery. The argument is opinionated. We are not arguing that permanent hiring is in decline as a thing worth doing, or that contracting is universally better. We are arguing that perm-versus-contract is a second-order question; that the first-order question is whether a given need is a permanent capability or a time-boxed outcome; that most real needs are a mix of both and get mispriced because they are forced onto a single instrument; and that the market is moving toward selectivity on headcount and speed on outcomes because businesses are, often without naming it, starting to separate the two. The shift is not employment-type fashion. It is the market learning to ask a better question.
The audience for this analysis is founders, transformation leads, delivery owners, and hiring decision-makers in UAE businesses who are feeling the slower perm cycle and the pull toward faster contract or embedded resourcing, and want a way to decide that is not just "perm or contract". The useful diagnostic question is not "should we hire permanently or contract this" but "is this need a permanent capability, a time-boxed outcome, or, as is usually true, both, and are we resourcing each part with the right instrument".
Capability or Outcome: The Question Underneath the Shift
Below is a short read on a single need. Answer each factor for something you are currently deciding how to resource. The point is not the verdict; it is that "perm or contract" never appears in the questions, because it is downstream of them. What decides the right instrument is whether the need is an enduring capability, a time-boxed outcome, or a mix, and the exercise is built to surface which.
Is this a permanent capability or a time-boxed outcome?
Answer each factor for a real need you are resourcing, then read the verdict
Why the Real Question Is Capability Versus Outcome
The reason perm-versus-contract is the wrong first question is that employment type is an instrument, not a need. A permanent hire is the right instrument for a permanent capability: a function that will exist indefinitely, where value comes from continuity and presence, and where the seniority is needed every day for the foreseeable future. An embedded or contract engagement is the right instrument for a time-boxed outcome: a defined piece of work with an end state, where value is the result delivered, and where the seniority is needed for the work and not at the same level afterward. When a business asks "perm or contract" first, it is choosing the instrument before it has characterised the need, which is how the wrong instrument gets attached to the work.
The mispricing is the part that gets missed. Forcing a time-boxed outcome onto a permanent hire means carrying a level of cost and seniority past the point it is needed, and accepting the perm decision cycle when the window for impact was now. Forcing a permanent capability onto a rolling contract means paying a premium for flexibility on something that was never going to flex, and risking the continuity the function actually depended on. Both are the same error in opposite directions: a mismatch between the duration and nature of the need and the instrument used to meet it. The recruitment-market shift, selective on perm, fast on contract, is what it looks like when businesses start, often implicitly, to stop making that error.
The honest complication is that most real needs are not purely one or the other. A transformation programme usually has an enduring core that should be permanent and a concentrated delivery push that should not. A new capability often needs senior outcome delivery now and a smaller permanent footprint later. The businesses that resource well are not the ones that picked perm or contract; they are the ones that separated the permanent capability from the time-boxed outcome inside the same initiative and used the right instrument for each, instead of buying one instrument for a need that had two shapes.
The shift in one observation
"Are you hiring perm or contract right now" is the question the market is asking out loud. The question underneath it is "which parts of this need are permanent capability and which are time-boxed outcome", and most needs are both. The businesses resourcing well are not choosing an employment type; they are separating the two shapes of the need and matching an instrument to each.
Where the Perm-Versus-Contract Framing Breaks
Treating the decision as an employment-type choice breaks in four predictable places.
A permanent hire for a finite outcome
Headcount is added for what was really a defined piece of work. Once it is delivered, the business carries a level of cost and seniority it no longer needs, and it waited through a perm cycle while the window for impact was open.
A rolling contract for a permanent function
A genuinely enduring capability is met with a rolling contract, paying a flexibility premium on something that was never going to flex and exposing the function to the discontinuity it most needed to avoid.
One instrument for a mixed need
A programme with both an enduring core and a time-boxed push is forced onto a single instrument. Half of it is mispriced by definition, and which half is silent because the need was never separated into its two shapes.
The decision cycle outlasts the window
When outcome-shaped work goes through the permanent approval cycle, the speed the work needed is lost to the process the headcount needed. The business gets the right seniority too late to deliver the impact it was for.
How the Shift Reads
Two Ways to Read the Same Shift
The difference between businesses that resource delivery well and those that overpay is whether they treat the shift as an employment-type trend or as a signal about separating capability from outcome.
| Dimension | Perm-versus-contract framing | Capability-versus-outcome framing |
|---|---|---|
| First question | Which employment type do we use? | What shape is this need, and for how long? |
| Enduring core | May be contracted for flexibility it will not use. | Resourced permanently, for continuity. |
| Time-boxed delivery | May become permanent headcount. | Resourced as embedded senior delivery, then done. |
| Mixed need | Forced onto one instrument, half mispriced. | Separated, each part matched to its instrument. |
| Speed | Outcome work waits on the headcount cycle. | Outcome work moves at outcome speed. |
The market is asking whether it is easier to hire perm or contract right now. The more useful question is whether the need in front of you is a permanent capability or a time-boxed outcome, because the honest answer is usually both, and the cost lives in pretending it is only one.
What Resourcing the Shift Well Looks Like
The pattern in businesses that resource delivery well in this market is recognisable. They characterise the need before the instrument: is this an enduring function, a defined outcome, or a mix. They resource the enduring core permanently, where continuity and presence are the value, and accept the perm cycle there because the need outlasts it. They meet the time-boxed delivery with embedded senior capability that plugs in at the level the work needs, for the duration the work needs, and steps back when the outcome is delivered, without carrying that cost and seniority indefinitely. And where a need is genuinely mixed, which is the common case, they separate it and use both instruments deliberately rather than forcing one onto the whole and mispaying for half. The employment-type question still gets answered; it just gets answered last, by the shape of the need, not first, by habit or market mood.
This is a decision-quality point, not a product. The right answer is specific to the need and the business, and the most valuable early work is separating the permanent capability from the time-boxed outcome inside whatever initiative is being resourced, before committing to an instrument. Where the two cannot yet be cleanly separated, knowing that is itself the result, because it prevents committing the whole need to one instrument prematurely.
How This Sits With BY BANKS, Honestly
We have a clear interest here, and it is fair to state it plainly rather than dress the argument as neutral. BY BANKS provides embedded senior software and delivery capability, for short or long term, that plugs into a business at the level the work needs. That is precisely the instrument the time-boxed-outcome side of this argument points to, and we also build the enduring software a permanent capability runs on. So we benefit when a business separates capability from outcome, because the outcome side is what we do.
That stated, the position is still the honest one. We are an independent software engineering company based in the UAE. We are not a recruitment agency, we do not place candidates, we do not provide staffing, payroll, or employment services, and the recruitment-market pattern referenced here is a signal we hear from that market, not our own field data and not a recruiter speaking through us. We build and deliver software with embedded senior people; the business owns its hiring, employment, and workforce decisions and their legal and regulatory implications entirely. The accountable party leads and owns those obligations; we provide delivery capability to their direction.
Where This Analysis Is Useful
The conversations where this perspective is most useful tend to be at three moments: a business feeling the slower perm cycle and unsure whether to wait it out or resource differently; a transformation or delivery lead with an initiative that has both an enduring core and an urgent delivery push and is about to force both onto one instrument; or a founder weighing headcount against speed and sensing the framing itself is wrong. The honest answer is usually the same: the question is not perm or contract, it is capability or outcome, it is usually both, and resourcing well means separating them rather than picking a side.
For broader related work, see our perspective on what the core banking system will expose and our perspective on why citizen-portal projects succeed or fail before any code. The applied work sits across our operational platforms and technical consultancy capabilities. Get in touch if a 45-minute conversation about a specific resourcing decision would be useful.
Frequently Asked Questions
No. We are an independent software engineering company based in the UAE. We provide embedded senior software and delivery capability, for short or long term, and we build software. We are not a recruitment agency, we do not place candidates, and we do not provide staffing, payroll, or employment services. On any engagement, the business owns its hiring, employment, and workforce decisions and their legal and regulatory implications. We provide delivery capability to the business's direction; the business owns the employment relationship and its obligations.
It is a signal we hear from the recruitment side of the market, slower, more selective permanent hiring and faster contract and embedded hiring across design, technology, transformation, and delivery, and it matches what we see on the delivery side. It is presented as a market signal and our reading of it, not as BY BANKS proprietary data, not as statistics, and not as a recruiter's words attributed to us. We have not put numbers to it because we do not have sourced UAE figures for it, and we will not invent them.
No. Permanent hiring is exactly the right instrument for a permanent capability, an enduring function where continuity and presence are the value, and the perm cycle is the right cost to pay there. The argument is not against permanent hiring; it is against choosing the instrument before characterising the need. For an enduring core, hire permanently. The point is only that not every need is that, and many are a mix.
No. It is an observational reasoning aid to make one point concrete: that "perm or contract" is downstream of "capability or outcome". It is not a methodology, a model, or hiring, employment, or legal advice, and it describes no specific business. Real resourcing decisions depend on the specific need, the business, and its own legal and regulatory context, which the business owns and should take qualified advice on.
Most real needs are mixed, an enduring core plus a time-boxed delivery push. Applying this means separating the two inside the same initiative before choosing instruments: resource the enduring core permanently for continuity, and meet the time-boxed delivery with embedded senior capability that steps back when the outcome is delivered. The value is in not forcing one instrument onto a need that has two shapes; how the split falls is specific to the initiative.
The perm-versus-contract shift coming out of the recruitment market, selective and slow on headcount, fast on contract and embedded delivery, is real and matches what we see on the delivery side, but the framing it usually gets is the wrong one. Employment type is an instrument; the decision that matters is whether a need is a permanent capability, a time-boxed outcome, or, as is usually true, both. Businesses overpay when they force a mixed need onto one instrument and mispay for half of it; they resource well when they separate the enduring core from the time-boxed delivery and match an instrument to each. We have a stake in saying so, the outcome side is what BY BANKS does, and the position holds anyway: we build and deliver software with embedded senior people, the business owns its hiring and employment decisions and their implications entirely, and the better question is capability or outcome, not perm or contract.
This article reflects our perspective and a qualitative signal we hear from the recruitment market; it cites no figures and presents no statistics, and the market observation is not BY BANKS proprietary data, not attributable to any named individual, and not a recruiter speaking on our behalf. Patterns described are observational and illustrative rather than measured. BY BANKS is an independent software engineering company; we provide embedded senior software and delivery capability and build software. We are not a recruitment agency, we do not place candidates, and we do not provide staffing, payroll, or employment services, and we are not affiliated with or endorsed by any authority. On any engagement, the business owns its hiring, employment, and workforce decisions and responsibility for their legal and regulatory implications. This article is not hiring, employment, HR, or legal advice; businesses should obtain qualified advice for their specific circumstances. Any general reference sources are listed on our Sources and Data page.
Ready to Build Something?
If this resonated, let's talk about how we can apply these ideas to your business.
Start a Conversation