If you want to screen remote developers fast, run four filters before you spend time on interviews: a video intro, a check of how they talk, verified work history, and a technical test taken on camera. Each one removes a different kind of weak candidate. Together they stop you from burning weeks on people who just started learning or who will not get on a call.
This guide shows how to run each filter yourself, in order, with questions and checks you can use today. Near the end, we explain how Talent Navigator does the same work before a profile reaches you.
Why do remote searches fill up with the wrong people?
Open listings attract everyone. A CV costs a candidate nothing to send, so you get a mix of experienced engineers, beginners and people who copy what others wrote.
A CV also tells you very little. It says what someone claims, not what they can do or how they talk to a teammate.
The fix is to ask for evidence early, in cheap steps, before you invest live time. Order the filters from cheapest for you to most expensive.
Filter 1: Ask for a video introduction
A short video takes the candidate a few minutes and takes you two. It filters out people who are not serious about the role.
Ask for one to two minutes, covering:
- What they have built recently, in plain words
- Which part of it was theirs, not the team's
- What kind of role they want next
Watch for clear speech, a real example and a direct answer. Be wary of a script that reads like a CV, or a video that names no actual project.
Filter 2: Check how they talk on a call
Remote work runs on writing and talking. A strong coder who cannot explain a problem will slow your team down every day.
Keep the call to 15 minutes. Ask them to explain one past decision, such as why they picked a tool, and what they would change now.
Score it simply from 1 to 5 on three points:
- Do they answer the question that was asked?
- Can you follow the explanation without technical background?
- Do they say when they do not know something?
If someone will not get on a call at all, that is your answer for a remote role. Our view is that a communication score belongs next to a technical score, not after it.
Filter 3: Verify work history
Do not take dates and titles on trust. A few checks catch most problems:
- Confirm each employer exists and the dates match what the candidate told you
- Ask the candidate to walk through the most recent role and compare it with the video
- Check that education claims can be confirmed with the institution
Inconsistencies are the signal. A candidate who tells three different stories about the same job has told you what you need to know.
Filter 4: Give a technical test taken on camera
An interview rewards people who talk well about code. A test shows whether they can write it. Make it specific to the role: a data engineer should work on data pipelines, not puzzle questions.
Supervision matters. When a test is taken unwatched, you cannot be sure who did the work. Camera supervision answers that. For more on choosing tools, see our guide to technical hiring assessment software.
Keep it short and tied to real work. Long take-home tasks lose your best candidates, who have other offers.
What to do this week
You can start tomorrow with an open role.
- Write the role down in one page: the work, the stack and the working hours. Our guide to writing a role brief helps.
- Ask every applicant for a two-minute video before any call.
- Hold a 15-minute call with those who pass and score them on the three points above.
- Check history for your top three only, to save time.
- Give a role-specific test, watched on camera, to the remaining two.
If you skip a filter when you are in a hurry, skip the last one you would regret. In our experience, that is usually the history check or the supervised test.
How Talent Navigator does this for you
Vetting is the product here. Every visible profile has already cleared a role-specific technical test taken under camera supervision, a separate communication score, a video introduction, and verified education and work history.
There is no recruiter in the middle. You search, shortlist and interview yourself. You can read the scores before you book anyone, and our piece on reading a developer's score shows how.
The network has 50,000+ developers, and you can expect 48 hrs to your first shortlist. You pay with credits per profile unlock, not a share of salary. If you would rather skip agencies altogether, read about hiring developers without a recruiter.
Frequently asked questions
How long should screening take per candidate?
The video takes you about two minutes to watch, and the call about 15 minutes. Checks and the test add a little more, but only for those who pass the earlier steps.
Can I skip the technical test if the candidate has a strong CV?
We would not. A CV shows claims, while a supervised test shows what the person can actually do. It is the filter that most often changes your mind.
What if I need to hire across borders?
You do not have to open a legal entity. On request, Talent Navigator acts as employer of record: you pick the person, and we employ them legally in their own country for a flat monthly fee.
If you want to see candidates who have already cleared all four filters, you can browse vetted talent and read their scores yourself.