How we vet developers

Every engineer we present has passed a 30 to 45 minute technical interview with one of our trained technical recruiters. Every answer is graded from 1 to 4, and in 2026 we presented 42.5% of the engineers we interviewed. The numbers on this page come from our own recruitment data.

What "interviewed by us" means

Every engineer we present has passed a technical interview with one of our recruiters. The interview takes 30 to 45 minutes and every answer is graded from 1 to 4. In 2026 we presented 42.5% of the engineers we interviewed (530 of 1,247). We have interviewed more than 10,000 engineers since 2019.

The process, step by step

  1. Step 1: Understand the role

    We fill in the Hiring Kickoff Document together: the problem, the ideal candidate and your process.

    1 call

    with your hiring manager

  2. Step 2: Find engineers who fit

    We contact engineers who fit the brief and re-engage our network.

    Salary

    in the first message

  3. Step 3: Interview every candidate

    A trained technical recruiter grades every answer from 1 to 4.

    30–45 min

    technical interview

  4. Step 4: Share only the strongest

    Each one comes with their CV and our written notes on every answer.

    42.5%

    of those we interviewed in 2026

  5. Step 5: You interview them

    You run the interviews. We handle scheduling and candidate feedback.

    Your process

    we handle the logistics

The numbers behind it

These charts come from our own recruitment data: the stage history of every candidate on every engineering role in our applicant tracking system. Client and candidate details are removed. Each chart states its sample size and dates. Hover over a bar for the exact figure.

The senior engineering funnel

For senior roles in 2026 so far, we reached 7,610 people, interviewed 885, presented 451 to clients, and 18 were hired.

Approached by us, or applied and reviewed: 7,61059%Reached7,610Outreach sent: 4,463 (59% of the step before)20%Contacted4,463Our technical interview: 885 (20% of the step before)51%Interviewed by us885Presented to the client: 451 (51% of the step before)35%Presented451Interviewed by the client: 156 (35% of the step before)15%Client interview156Offer made: 23 (15% of the step before)78%Offer23Hired: 18 (78% of the step before)Hired18

Senior, lead, staff and principal engineering roles. Reached means approached by our recruiters or applied and reviewed. Contacted means outreach was sent; replies are not tracked in our system. Each step counts the people who reached it at any point, and the percentage is the conversion from the step before. Block height uses a square-root scale so the small late stages stay visible.

n = 7,610 candidates who entered a senior engineering role between 1 Jan and 13 Nov 2026. Some recent candidates are still in process, so the later steps will grow.

Source: Remote Crew, Recruit CRM stage history, pulled 13 Nov 2026.

Where the engineers we present come from

79% of the engineers we presented to clients since 2024 were actively sourced or re-engaged by our recruiters. The rest applied to the job ads we wrote for the role, or were referred.

Interviewed by us, brought in by our recruiters' outreach: 1,884 of 3,949 (47.7%)Interviewed by us, re-engaged from our network: 901 of 3,949 (22.8%)Interviewed by us, applied to the job ad: 1,153 of 3,949 (29.2%)Interviewed by us, referral: 11 of 3,949 (0.3%)71%actively sourcedor re-engagedInterviewed by usn = 3,949Presented to the client, brought in by our recruiters' outreach: 1,009 of 2,110 (47.8%)Presented to the client, re-engaged from our network: 662 of 2,110 (31.4%)Presented to the client, applied to the job ad: 428 of 2,110 (20.3%)Presented to the client, referral: 11 of 2,110 (0.5%)79%actively sourcedor re-engagedPresented to the clientn = 2,110Hired, brought in by our recruiters' outreach: 53 of 105 (50.5%)Hired, re-engaged from our network: 28 of 105 (26.7%)Hired, applied to the job ad: 22 of 105 (21%)Hired, referral: 2 of 105 (1.9%)77%actively sourcedor re-engagedHiredn = 105
  • Brought in by our recruiters' outreach
  • Re-engaged from our network
  • Applied to the job ad
  • Referral

How each candidate entered the role. Outreach means our recruiters approached them for the role. Re-engaged means they were already in our network more than 30 days before we approached them for this role. Referrals are rarely recorded, so their share is a minimum.

n = 3,949 interviewed by us, 2,110 presented to the client, 105 hired; engineering roles, January 2024 to 13 November 2026.

Source: Remote Crew, Recruit CRM stage history, pulled 13 Nov 2026.

Who says no

Most candidates who don't go further are screened out by us before any interview, mostly on location or missing must-have skills. In 2026, clients made 5% of the rejections.

2026n = 8,6821 Jan to 13 Nov 2026, screened out by us before any interview: 6,225 (71.7%)72%1 Jan to 13 Nov 2026, rejected by us at the interview or our checks: 1,042 (12%)12%1 Jan to 13 Nov 2026, rejected by the client: 408 (4.7%)1 Jan to 13 Nov 2026, declined or withdrew (the candidate): 1,007 (11.6%)12%Since 2024n = 19,251May 2024 to 13 Nov 2026, screened out by us before any interview: 11,796 (61.3%)61%May 2024 to 13 Nov 2026, rejected by us at the interview or our checks: 4,419 (23%)23%May 2024 to 13 Nov 2026, rejected by the client: 946 (4.9%)May 2024 to 13 Nov 2026, declined or withdrew (the candidate): 2,090 (10.9%)11%
  • Screened out by us before any interview
  • Rejected by us at the interview or our checks
  • Rejected by the client
  • Declined or withdrew (the candidate)

Every final rejection on an engineering role, by who made the call. Rejections recorded only because a role closed are not counted.

n = 8,682 rejections from 1 Jan to 13 Nov 2026, and 19,251 from May 2024 to 13 Nov 2026.

Source: Remote Crew, Recruit CRM stage history, pulled 13 Nov 2026.

What it takes to make one hire

In 2026 we interviewed about 56 engineers and presented about 27 to clients for every hire.

56interviewed by us56 interviewed by us per hire (1,680 in total, 30 hires), 1 Jan to 13 Nov 202627presented to the client26.9 presented to the client per hire (806 in total, 30 hires), 1 Jan to 13 Nov 20261hired1 hired per hire (30 in total, 30 hires), 1 Jan to 13 Nov 2026

Engineering roles. The number of candidates who reached each step in 2026, divided by the number of hires. Each block is one person. Hires are the hired stage in our system; some hires are recorded elsewhere, so the real ratio is a little lower. 2026 is still open, and recent candidates have not had time to be hired yet.

n = 1,680 interviewed, 806 presented and 30 hires, 1 Jan to 13 Nov 2026. Counts everyone presented in the period, including some interviewed earlier, so it isn't our presentation rate (42.5% in 2026).

Source: Remote Crew, Recruit CRM stage history, pulled 13 Nov 2026.

From opening a role to the first offer

How long this takes depends a lot on the client's own process: how many interview rounds there are, and how quickly feedback comes back.

Under 4 weeks: 9 of 56 roles9Under 4 weeks4 to 6 weeks: 18 of 56 roles184 to 6 weeks6 to 8 weeks: 10 of 56 roles106 to 8 weeks8 to 12 weeks: 12 of 56 roles128 to 12 weeks12+ weeks: 7 of 56 roles712+ weeks

Weeks from the day the role was opened in our system to its first offer. Only roles that reached an offer are counted.

n = 56 engineering roles opened between 1 Jan 2025 and 13 Nov 2026 that reached an offer.

Source: Remote Crew, Recruit CRM stage history, pulled 13 Nov 2026.

Why people get rejected

Every rejection in our system carries a reason. These are the figures for engineering roles in 2026, up to 13 November.

  • Before any interview: we screened out 6,225 people who applied or whom we considered. 55% were outside the locations the role allows, and 45% were missing a must-have skill.
  • At our interview or our checks: we rejected 1,042 candidates. Technical skills was the most common reason, at 38%. Then came not enough relevant experience (11%), not turning up (10%), fake profiles (9%), English (4%) and soft skills (4%). 22% have no reason recorded.
  • After we presented them: clients rejected 408 candidates. 63% were on technical skills, and 15% were people already in the client's own pipeline.

Behind most technical rejections is the same gap. The person has used a framework for years but can't explain what happens underneath it: how the database locks, how concurrency works, what git does. That's why we ask how things work, not whether someone has used a tool.

A fake candidate we caught

Fake candidates are a real problem. In 2026 we rejected 90 candidates for engineering roles as fake profiles. We had recorded none before 2026.

One candidate presented himself as Brazilian, with a degree from a university in São Paulo. The interview was in English. He had a strong accent that didn't fit his background, and he didn't look like his profile photo. Miguel, our founder, is Portuguese, so he asked whether he had studied in Portuguese. The candidate said yes. Miguel asked his next question in Portuguese, and the candidate left the call.

We check every profile before the interview and again during it. People do these checks, not software. We are testing tools that could help, but we don't rely on any of them.

What our interview doesn't check

Our interview is a screen, not a full technical assessment. To be clear about its limits:

  • We don't run live coding, deep system design rounds or long take-home challenges. Those belong in your process, and we help you design them.
  • We don't judge team fit the way your engineers will.
  • We don't screen on years of experience. Hard cut-offs filter out ambitious people who are ready to step up.
  • We don't run formal background or ID checks.

Frequently asked questions

  • Who interviews the candidates?

  • How long is your technical interview, and how is it graded?

  • How many of the engineers you interview do you present?

  • Why do candidates fail your interview?

  • How do you catch fake candidates?

  • Where do your candidates come from?

  • Should we give candidates a take-home challenge?

  • Do you check references?

  • What does your interview not check?

Want to see the process on a real role?

Tell us about the role. We'll walk you through how we'd run the search, from the kickoff call to the written notes on every candidate we present.