DEV Community: Anas Mallouh

Blind Hiring: Why Companies That Hide Résumés Win

Anas Mallouh — Sat, 25 Jul 2026 01:57:48 +0000

📌 This article was first published on the Talents-OS blog: Blind Hiring: Why Companies That Hide Résumés Win. It is republished here by a member of the Talents-OS team.

TL;DR

Screening bias costs companies their best candidates. Learn what blind hiring is, why it raises hiring quality, and how Talents-OS implements it.

Imagine your best candidate getting rejected in the first thirty seconds of screening — not for weak skills, but because of their name, their university, or their photo. That is not a hypothetical; it is what happens every day in most hiring processes, usually without the screener even noticing.

What the data says about bias

Field experiments around the world have repeated the same finding for decades: résumés with identical content receive radically different callback rates when only the name is changed — with gaps reaching 50% in some studies. The most famous experiment remains the American orchestras: when auditions moved behind a screen that hid the musician's identity, the share of women advancing to final rounds rose dramatically. The talent had not changed — only what the evaluator could see. And bias is not limited to gender or ethnicity: university prestige, age, even a home address all sway screening decisions without the screener's awareness.

What is blind hiring?

Blind hiring flips the equation: instead of evaluation starting with identity and ending with skill, it starts with skill and reveals identity later. Personal data — name, photo, gender, age, university — is hidden during the early screening stages, so the evaluator sees only what actually matters: proven competence.

The payoff is not just fairness — it is quality

Companies that adopt blind screening do not merely earn an ethical reputation; they widen the talent pool they select from. Every excellent candidate who would have been filtered out for a reason unrelated to competence becomes visible. The practical result: stronger hires, more diverse teams, and better performance.

How Talents-OS implements it

We built blind hiring into the core of the platform, not as a cosmetic option. In the first matching stage, the company sees an anonymized profile: auto-graded technical test results, GitHub activity analysis, and an explained match score describing exactly why this candidate fits your role. No name, no photo, no university. Only when the company decides to proceed — based on evidence alone — is the identity revealed for interviews.

The outcome: a decision built on competence first, with bias denied its chance to creep in. That is why companies that hide résumés win — they simply see what their competitors cannot: the full picture of real talent.

Originally published at www.talents-os.com.

MENA Tech Hiring Statistics 2026

Anas Mallouh — Sat, 25 Jul 2026 01:56:02 +0000

📌 This article was first published on the Talents-OS blog: MENA Tech Hiring Statistics 2026. It is republished here by a member of the Talents-OS team.

TL;DR

The verified numbers on MENA tech hiring: WEF projects a net +78M jobs by 2030 (170M created, 86% of businesses transformed by AI), 90% of GCC organisations report skills gaps, and AI literacy is LinkedIn's #1 rising skill — each figure checked against its primary source.

The Middle East tech-hiring market is in its widest transformation yet: surging demand for AI and data skills, a skills gap most organisations acknowledge, and a hiring landscape reshaped by AI. This page gathers verified figures from published global and regional reports — every number checked against its primary source — as a single reference for decision-makers and job seekers.

How many jobs will AI and technology reshape by 2030?

The WEF Future of Jobs Report 2025 projects 170 million new roles created and 92 million displaced by 2030 — a net gain of about 78 million jobs — as AI and information-processing technologies transform 86% of businesses. Nearly 40% of core skills are expected to change by 2030. (Source: WEF Future of Jobs Report 2025)

Which skills and roles are growing fastest?

Technology skills in AI, big data and cybersecurity are among the fastest-growing, and the fastest-growing roles include AI and machine-learning specialists, big-data specialists, fintech engineers, software developers and security specialists. On LinkedIn, AI literacy is the number-one skill on its 2025 Skills on the Rise list, with AI-skill adoption up roughly 20-fold globally since 2016. (Sources: WEF Future of Jobs Report 2025; LinkedIn Skills on the Rise 2025)

How big is the Gulf skills gap?

90% of GCC organisations cited skills shortages in 2025 — attributed to uncompetitive salaries, fierce competition for talent, and limited career progression. A shortage of skilled professionals ranks among the top factors organisations say could limit their strategic goals. (Source: Hays GCC Salary Guide 2025)

Are Gulf companies still hiring?

Yes: 78% of GCC employers plan permanent recruitment and only 14% report no hiring plans, with contract hiring used mainly to access specific project skills. (Source: Hays GCC Salary Guide 2025)

What is the region investing in AI talent?

Saudi Arabia National Strategy for Data and AI targets a pool of 20,000 data and AI specialists and training 40% of the workforce in basic AI skills, backed by about SAR 75 billion in targeted investment; SDAIA reports more than 11,000 specialists already trained as of early 2026. (Source: SDAIA, National Strategy for Data and AI)

What does this mean for your company or career?

For companies: competition for verified talent will intensify — those who verify skills with evidence hire faster and more accurately. For job seekers: AI and data skills are rising fastest, and a profile proven by tests and real work beats any polished résumé. That is the philosophy Talents-OS is built on.

Originally published at www.talents-os.com.

How to Pass the Technical Interview: A Practical Guide for Arab Developers

Anas Mallouh — Fri, 24 Jul 2026 22:54:24 +0000

Originally published on the Talents-OS blog. Disclosure: I work on Talents-OS.

TL;DR: A practical preparation plan for technical interviews: interview formats, effective prep, thinking aloud, STAR behavioral answers, and handling rejection — through a MENA lens.

The technical interview is not an intelligence test — it is a trainable skill. Most people who fail it do not fail for lack of competence, but because they never practiced the format of the test itself. This guide distills what we actually see making the difference for developers in our region: methodical preparation weeks ahead, handling the hard moments inside the room, and what you do afterwards.

Know the interview formats before you train

Technical interviews in our market usually come in four shapes: coding problems (algorithms and data structures), system-design discussions for senior roles, take-home assignments or live pairing sessions, and the behavioral interview. Ask the recruiter early which format to expect — preparing for an algorithms round is radically different from preparing for a practical assignment, and your time is too valuable to spend in the wrong direction.

The preparation plan: two to four weeks

Do not start preparing the day before. Set aside two to four weeks: in week one, review fundamentals (data structures, time complexity, the core concepts of your main language); in week two, solve problems of increasing difficulty daily — one consistent hour every day beats a weekend marathon. In the final two weeks, simulate real interview conditions: a timer, explaining aloud, and no help from a smart editor.

Master fundamentals before frameworks

Many developers in our region are strong in frameworks (React, Laravel, Flutter) yet stumble on the fundamentals interviews are built on: why is this solution O(n²)? When do you reach for a HashMap instead of an array? How does async actually work in your language? A good interviewer tests understanding, not memorization — and solid fundamentals are what let you handle any unexpected question. They are also exactly what auto-graded technical tests on serious platforms measure.

Practice thinking out loud

The biggest difference between a candidate who passes and one who fails with the same solution quality: the first makes their thinking audible. Explain your understanding of the problem before writing a line, name the alternatives you are discarding and why, and narrate trade-offs as you code. The interviewer is not grading only the final output but how you got there — and long silence usually reads against you even when your solution is correct.

The interview language: prepare your technical vocabulary

In our market, many interviews run in English even inside Arab companies — especially with Gulf and international employers. Nobody expects literary mastery; they expect technical fluency. Practice explaining your projects and technical decisions in English out loud before the interview, and prepare ready phrases for recurring moments ("let me think out loud", "I'll start with a simple solution and then optimize"). If the interview is in Arabic, do not force literal translations of terminology — use the standard English terms naturally.

Your projects and GitHub are your real résumé

Before the interview, review your public repositories the way the interviewer will: is your latest activity from a year ago? Do your main projects lack a clear README? Pick two or three projects you can discuss in depth: why this architecture? What was the hardest problem? What would you change if you rebuilt it today? Real GitHub activity has become part of verification on modern hiring platforms, and one project you know deeply is more convincing than ten certificates.

Interview day: the question you cannot answer

A question will come that you do not know — and it is not the end of the interview; it is the heart of it. Do not bluff and do not collapse. Say plainly: "I have not worked with this technology, but let me approach the problem with what I know", then decompose it out loud. Handling the unknown calmly and methodically is precisely what companies are screening for, because it is what real work looks like.

The behavioral interview: the STAR method

"Tell me about a time when..." questions need structure, not improvisation. Use STAR: the Situation, the Task, the Action you specifically took, and the describable Result. Before the interview, prepare five true stories from your experience covering: a technical disagreement with a colleague, a mistake you made and learned from, a high-pressure deadline, an initiative nobody asked for, and a hard technical decision. Prepared stories turn the most feared part of the interview into the easiest.

Ask your own questions

The interview runs in both directions, and your questions reveal professional maturity. Ask: how is code reviewed on the team? How is a developer's success measured in the first six months? What is the team's biggest technical challenge right now? Avoid making vacation policy your first question — and leave salary for its natural stage, armed with market bands from published salary guides.

After the interview: rejection is data, not a verdict

Send a short thank-you message within a day, and ask for specific feedback if you are not selected. Then treat every interview as data: which question tripped you? Which category of questions trips you repeatedly? Developers who turn each rejection into a specific training item pass their next interviews at visibly higher rates. In an active tech market, rejection is not a final judgment — it is one round in a long game whose rules you can absolutely learn.