A recruiter screening is a short 20–30 minute conversation that checks not the depth of your knowledge, but a basic fit: whether your experience matches the role, whether your salary and work-format expectations line up, whether you're motivated, and whether you can clearly talk about yourself. You can prepare for it in half an hour — if you know which questions will come up and what's behind them.
What the recruiter is really checking in a screening
A screening is a filter before the technical or final interview. The recruiter isn't assessing how deeply you know your tools — the hiring manager will do that. Their job is to not pass along a candidate who makes the team spend an hour only to discover that something is fundamentally off.
As a recruiter who has run more than 5,000 interviews, I can tell you that screenings don't filter out the "weak" candidates — they filter out the unclear ones: people who can't explain in two minutes what they do, get tangled up in the dates on their own CV, or don't know what they want.
- Experience fit — whether you have what's listed in the "must-have requirements" of the role.
- Consistency with your CV — whether your story matches what's on paper.
- Motivation — why you're looking and why this company specifically, not just any.
- Conditions — salary expectations, work format, location, start date.
- Communication — whether you speak in a structured way, and for international companies, your level of English too.
12 common questions: what they want to hear and how to answer
Below are the questions that come up in almost every screening. For each: what they're really checking and a short sample answer. The examples are generic — swap in your own details.
1. Tell me about yourself
What they want to hear: a short professional story focused on relevant experience, not your life story from childhood.
Sample answer: I'm a QA engineer with 4 years in web application testing, the last two in e-commerce. I set up automated tests for critical payment scenarios, and the number of bugs in production dropped noticeably. Right now I'm looking for a product team where I can work more with automation.
Keep this answer to two minutes: your current role, your main result, what you're looking for next. If the recruiter wants more, they'll ask for details themselves.
2. Why are you looking for a new job?
What they want to hear: a neutral reason that pulls you forward, not complaints about your previous employer.
Sample answer: Over three years I've grown to a point where I want to own the entire frontend of a module, and in my current structure a role like that won't open up anytime soon.
3. What do you know about our company?
What they want to hear: that you spent at least 10 minutes on their site, product, and job posting, rather than applying en masse.
Sample answer: You build a logistics service for small businesses and recently launched a mobile app. I really like that the product solves a real operational problem — I've worked with exactly those kinds of clients.
4. Tell me about your experience in your most recent job
What they want to hear: the scale (team, product, users), your area of responsibility, and 1–2 results.
Sample answer: A team of 8, a B2B platform for accountants. I was responsible for onboarding new clients: I rewrote the process, and the time from signing the contract to a client's first login dropped from two weeks to a few days.
5. Why are you interested in this particular position?
What they want to hear: a connection between the role's requirements and your experience, or the direction you want to grow in.
Sample answer: This role involves a lot of funnel analytics, which is the part of marketing I find most interesting and where I already have results.
6. What are your salary expectations?
What they want to hear: a realistic range that fits the budget, and a willingness to discuss.
Sample answer: I'm looking at a range of X to Y net, depending on the full package and scope of work. Does that fit your budget for the position?
Decide on your range before the conversation rather than making it up on the spot: the recruiter can hear uncertainty and remembers the first figure you name.
7. When can you start?
What they want to hear: specifics: notice period, planned vacation, any other commitments.
Sample answer: After an offer I'd need two weeks to hand over my work. So roughly from the start of next month.
8. Are you considering other offers?
What they want to hear: an honest but calm answer — it helps the recruiter plan the pace of the process.
Sample answer: Yes, I'm interviewing with two other companies, and with one I'm at the final stage. Your role is my priority, so I'd appreciate it if you could let me know the timeline.
9. What work format suits you?
What they want to hear: whether your preference matches what the company offers. Honesty matters here: don't agree to five days in the office if you know you'll leave within a month.
Sample answer: I'm most comfortable with hybrid or remote. If the office is needed twice a week, that's fine.
10. Tell me about a difficult situation at work and how you handled it
What they want to hear: a specific case following the pattern: situation — what you personally did — result.
Sample answer: A week before release, the developer leading an integration left. I broke the task into pieces, arranged help from two colleagues, and pushed back the non-essential features. The release went out on time, missing only one secondary report's integration.
11. What's your level of English?
What they want to hear: an honest assessment and an example of how you use it. Often the recruiter will simply switch to English mid-conversation.
Sample answer: Upper-Intermediate: I email clients daily and run a demo in English once a week.
12. Do you have any questions for us?
What they want to hear: that you care. Answering "no, everything's clear" is a missed opportunity.
Sample answer: What does the next step look like and who will be on the technical interview? What's the biggest challenge someone in this role would face in their first three months?
Red flags for a recruiter
These things don't always mean rejection, but each of them makes a recruiter hesitate. And in a screening, doubt often tips the decision in favor of another candidate.
- "My last job had terrible management, nobody could make a decision."
- "Honestly, I don't care what I do as long as the pay is stable."
- "Well, I did a lot of things there, it's hard to say off the top of my head."
- "I want to join a team where decisions are made faster — it matters to me to see the results of my work."
- "I'm looking for a product company where I can grow toward analytics."
- "My main area is payments: integrations with banks and transaction monitoring."
Preparing for a screening in 30 minutes
You don't need to memorize your answers — a rehearsed script is obvious right away. You need to refresh the facts and have a few stories ready to go.
-
5 minutes: reread the job posting
Write down 3–4 key requirements. For each one, recall where you've had that experience — this is the foundation of your answers.
-
5 minutes: reread your CV
The exact version you sent. Dates, company names, numbers — the recruiter will cross-check your story against the text.
-
5 minutes: look into the company
The website, the product, their LinkedIn company page, recent news. Find one thing that genuinely interests you.
-
10 minutes: say it out loud
Your 2-minute intro, your reason for looking, and one "situation — action — result" story. Out loud, not just in your head.
-
5 minutes: conditions and questions
Note down your salary range, start date, preferred format, and 2–3 questions for the company. Keep the note in front of you.
If the company is active on LinkedIn, check the profiles of the people you'll be talking to as well — it's easier to find common ground that way. And for what a recruiter can see in your profile before the call, read our article on the LinkedIn profile for an IT specialist.
What to do after the recruiter interview
The conversation is over, but you can still influence the outcome.
- At the end of the conversation, ask about the next steps and timeline. "When can I expect to hear back?" is a perfectly normal question that eases a week's worth of anxiety.
- Send a short thank-you message the same day. 2–3 sentences: thank them for their time, confirm your interest in the role, and if you forgot to mention something, add it in one line.
- Write down what you learned. The salary range, team composition, process stages, interviewers' names. It'll come in handy at the next stage.
- Don't wait in silence past the promised date. If the deadline has passed, send one polite follow-up 2–3 business days later. That's normal and doesn't come across as pushy.
If screenings aren't happening at all, the problem is most likely one step earlier, in your CV. Check how a recruiter sees it with COScafe's free CV review: you'll get a score across three categories and see what to fix first.
In short
- A screening checks fit, motivation, conditions, and communication — not the depth of your knowledge.
- Know your CV by heart: dates, companies, numbers.
- Prepare a 2-minute intro, your reason for looking, and one story with a result.
- Have your salary range, start date, and 2–3 questions for the company ready.
- After the conversation — a thank-you, your notes, and one follow-up if the deadline has passed.