A hiring funnel can look healthy right up until you inspect who makes it through. In this inclusive hiring case study, a European software company found that women and candidates from underrepresented backgrounds were applying, yet too few were reaching the final interview stage. The issue was not a lack of talent. It was a process built around familiarity, speed, and inconsistent judgment.
What follows is a composite case based on practices increasingly used across European tech. The company and figures are illustrative, but the operating lessons are real for founders, people leaders, and hiring managers trying to build teams that reflect the markets they serve.
The hiring problem was hiding in plain sight
Northline Systems, a fictional 450-person B2B data infrastructure company headquartered in Amsterdam, was growing quickly. It planned to hire 90 people in a year across engineering, product, sales, customer success, and leadership roles.
Its leaders had already made a public commitment to representation. Yet its internal dashboard showed a familiar pattern: women accounted for 38% of applicants for nontechnical roles and 24% for technical roles, but just 17% of technical hires. The drop-off was sharpest between the recruiter screen and the hiring manager interview.
The first assumption was that the company had a sourcing problem. More candidate pipelines, leaders argued, would solve it. But a closer review showed qualified candidates were already entering the process. They were simply being assessed differently once they arrived.
Interviewers described some candidates as "not quite senior enough" despite comparable experience to people who had been hired. Others were ruled out for not having worked at a well-known scale-up, even when they had led complex work in adjacent sectors. The company was over-indexing on polished confidence, personal referrals, and recognizable employer names.
That matters in European tech, where career paths are rarely linear. A candidate may have built expertise at a public institution, a regional startup, a consultancy, or after returning from caregiving leave. Treating one narrow route as proof of potential does not raise the bar. It narrows the room.
What changed in this inclusive hiring case study
Northline did not launch a one-off diversity campaign. It rebuilt several decision points in the hiring flow, beginning with the role itself.
Job descriptions stopped describing a mythical candidate
The talent team audited job descriptions for inflated requirements and coded language. A product manager posting that had asked for "10+ years in high-growth SaaS" became a role focused on demonstrated outcomes: leading product discovery, managing stakeholders, making trade-offs with engineering teams, and using customer insight to shape a roadmap.
This was not about lowering standards. It was about separating essential capability from inherited preference. The company also removed degree requirements unless they were legally or technically necessary, and published salary ranges for every role.
The practical effect was immediate. More candidates applied, but more importantly, recruiters reported stronger conversations because applicants understood what success would look like in the first year.
Every interviewer used the same evidence
Before the change, interviewers arrived with broad prompts and left with vague impressions. One manager valued strategic thinking. Another wanted technical depth. A third was looking for someone they could "grab coffee with." None of those instincts are inherently useless, but they are unreliable when they decide a career.
Northline introduced role-specific scorecards before a job was posted. Each scorecard included four to six competencies, a definition of strong evidence, and interview questions assigned to individual panel members. For a senior engineering role, the panel assessed system design, delivery leadership, collaboration, learning agility, and communication. It did not assess whether someone had used the company’s exact tool stack.
Interviewers had to submit notes and ratings before the debrief. That simple rule prevented the most senior person in the room from setting the narrative before others had recorded their own judgment.
The company also replaced the question, "Would you hire this person?" with a more useful one: "What evidence did we hear against each criterion?" The shift moved debriefs away from chemistry and toward decisions that could be explained.
The interview process became more accessible, not easier
Candidates received a clear outline of stages, expected preparation time, and the names and roles of interviewers. For take-home work, Northline offered a paid alternative: a live, time-boxed case discussion using the same assessment criteria. This recognized that unpaid assignments can disadvantage people with caregiving responsibilities, multiple jobs, disabilities, or limited free time.
Accommodation requests were handled directly and without requiring candidates to explain more personal information than necessary. Interviews could be scheduled across different hours when feasible, and video interview guidance included captions and communication expectations.
There was a trade-off. These changes required more coordination from recruiters and hiring managers. Some leaders initially worried that a more structured process would feel impersonal. Candidate feedback showed the opposite. Clarity made the company feel prepared, respectful, and serious about people’s time.
The data that made accountability real
The company tracked representation across each stage: application, recruiter screen, hiring manager interview, panel, offer, and acceptance. It reviewed outcomes by function, seniority, location, and where legally appropriate, demographic groups reported voluntarily by candidates.
The point was not to set quotas or treat candidates as data points. It was to identify where the process produced uneven outcomes. If women progressed at similar rates until the manager interview and then fell away, the team knew where to investigate. If offer acceptance was lower for a particular group, compensation, flexibility, or employer reputation might be part of the answer.
Within 12 months, Northline saw the proportion of women hired into technical roles rise from 17% to 29%. The share of women reaching final interviews rose more quickly, from 22% to 35%. Hiring managers also reported fewer drawn-out debriefs because scorecards made disagreements more specific.
Those results should be read carefully. One year of progress does not prove that every barrier has disappeared, and representation metrics can move for reasons beyond a hiring process. Market conditions, role mix, and hiring volume all matter. Still, the company had evidence that its changes affected where candidates advanced, which is more actionable than an annual headline figure alone.
Why leadership behavior mattered more than a statement
The most consequential change was not a revised job ad. It was the expectation that leaders would own hiring quality.
At Northline, every hiring manager completed interview training before opening a role. The training used real examples of vague feedback, affinity bias, and inconsistent standards. Leaders were shown how comments such as "not executive enough" can mask a preference for a particular communication style rather than an actual gap in leadership.
Executives reviewed hiring data quarterly alongside business performance. When one department repeatedly produced unbalanced shortlists, its leader worked with talent partners to examine sourcing channels, assessment design, and panel composition. The conversation was not punitive, but neither was it optional.
That is a key distinction. Inclusion efforts lose credibility when they sit only with the people team or employee resource groups. Recruiting is a business system. The people who define roles, conduct interviews, approve offers, and allocate budget shape it every week.
What other tech teams can take from the case
The lesson is not that every company needs Northline’s exact process. A 20-person startup cannot operate like a 450-person scale-up, and a regulated cybersecurity business may need different technical assessments than a consumer app company.
But nearly every team can ask three hard questions: What evidence are we actually using to hire? At which stage do qualified candidates disappear? And can we explain a rejection without relying on instinct or vague fit?
Start with one high-volume or high-impact role family. Build a clear scorecard, standardize interviews, make pay information transparent where possible, and look at conversion rates by stage. Then listen to candidates who withdraw or decline. Their feedback often reveals friction that internal teams have normalized.
For European tech companies that want to compete for talent, inclusive hiring is not a side project for a brand campaign. It is a way to see more of the talent already in front of you. The next strong hire may not match the familiar profile on the team today. That is often precisely the point.
