Steal These 100 Phone Screening Questions (And Stop Wasting Your Week on Bad Hires)

You have 50 resumes and 20 minutes each. That is 1,000 minutes of phone screening for one role. Most of those calls will end in a "no." The hard part is finding the few "yes" candidates without wasting a full week of your life.

The right questions do that work for you. They surface dealbreakers in the first five minutes. They tell you who can actually do the job, not just who wrote a good resume. And when you ask every candidate the same questions, you can finally compare people fairly.

This post gives you 100 phone screening questions. They are sorted by category, so you can copy the ones you need. You also get a scoring rubric, the signs of a strong (and weak) answer, and a faster way to run screens when your pipeline gets big.

Let's start with why this matters.

Why the Right Phone Screening Questions Matter

A phone screen has one job: decide who moves forward. It is a filter, not a deep interview. Get the questions wrong and you waste hours on bad fits. Get them right and you protect your hiring managers' time.

Here is what good questions buy you.

Consistency. When you ask every candidate the same set, you compare answers, not vibes. One recruiter said a candidate was "sharp." Another said the next one was "a bit slow." Those words mean nothing. A shared question list turns gut feelings into evidence.

Less bias. Unstructured calls drift. You chat about a shared hometown, you like the person, and suddenly they pass. Structured questions pull you back to the job. Research on hiring is clear on this: structured interviews predict job performance far better than casual ones. The same logic applies to screens.

Saved time. A sharp dealbreaker question early ("This role pays X — does that work for you?") can end a call in 90 seconds. That is a gift. You just saved 18 minutes and a follow-up email.

A better candidate experience. Good questions feel fair. The candidate knows you are taking them seriously. Even the people you reject leave with a decent impression of your company.

Now the questions.

General / Universal Screening Questions (15)

Use these for almost any role. They check motivation, logistics, and basic fit before you go deeper.

1. Tell me about yourself in two minutes.
2. What made you apply for this role?
3. What do you know about our company?
4. Why are you leaving your current job? (Or: why did you leave your last one?)
5. What are you looking for in your next role?
6. What is your current notice period or availability to start?
7. What are your salary expectations?
8. Are you interviewing anywhere else right now?
9. Is this role remote, hybrid, or onsite for you — and does our setup work?
10. Walk me through your last role and your main responsibilities.
11. What part of your current job do you enjoy most?
12. What part do you enjoy least?
13. What is one accomplishment you are proud of from the last year?
14. What questions do you have about the role or the company?
15. Why should we move you to the next round?

These 15 will weed out most of your mismatches. Salary, notice period, and location alone end a surprising number of calls — for good reason.

Role-Specific Questions by Category

Now go deeper. These questions test whether the person can actually do the work.

Sales Roles (15)

You are screening for drive, process, and the ability to handle a "no." Listen for specifics: numbers, named deals, real objections.

1. Walk me through your sales numbers from last quarter. Did you hit quota?
2. What was your average deal size and sales cycle length?
3. How do you research a prospect before reaching out?
4. Tell me about the hardest deal you ever closed.
5. How do you handle a prospect who says, "Send me an email and I'll get back to you"?
6. Describe your sales process from first contact to close.
7. What tools and CRM have you used?
8. How many calls or emails do you make on a typical day?
9. Tell me about a deal you lost. What happened?
10. How do you handle rejection day after day?
11. How do you prioritize your pipeline when everything feels urgent?
12. What is your strategy for hitting quota in a slow month?
13. How do you handle a price objection?
14. Sell me this pen — or anything on your desk right now.
15. What motivates you beyond commission?

A weak sales candidate talks in generalities ("I'm a people person"). A strong one gives you numbers, names, and a clear process.

Tech / Engineering Roles (15)

You are not running a coding interview here. You are checking the basics: experience, communication, and whether the resume holds up.

1. Walk me through your tech stack and what you used most.
2. Describe a project you are proud of. What was your exact role?
3. How do you approach debugging a problem you have never seen before?
4. Tell me about a technical decision you made that you later regretted.
5. How do you keep your skills current?
6. How comfortable are you with [specific language/framework] on a scale of 1 to 10, and why?
7. Describe how you work with non-technical teammates.
8. How do you handle code review feedback you disagree with?
9. Tell me about a time you had to learn a new technology fast.
10. What does a good development process look like to you?
11. How do you balance speed and code quality under a deadline?
12. Have you worked in an Agile or Scrum team? What was your role?
13. What is the largest scale (users, data, traffic) you have worked with?
14. How do you test your own code before it ships?
15. What kind of technical work do you want to avoid in your next role?

Listen for someone who can explain a technical idea simply. If they cannot describe their own project clearly, that is a flag.

Customer Support / BPO Roles (15)

You are screening for patience, clarity, and grace under pressure. Communication is the job, so the call itself is part of the test.

1. Why do you want to work in customer support?
2. Walk me through how you would handle an angry customer.
3. Tell me about a time you turned an unhappy customer around.
4. How do you stay calm when someone is rude to you?
5. What does good customer service mean to you?
6. How do you handle a question you do not know the answer to?
7. Describe your typing speed and the tools you have used (CRM, ticketing).
8. Are you comfortable working night shifts or rotating shifts?
9. How do you handle repetitive work without losing focus?
10. Tell me about a time you broke a rule to help a customer. Was it the right call?
11. How do you handle several chats or tickets at once?
12. What do you do when a customer is right but policy says no?
13. How do you handle feedback from a QA review or team lead?
14. Describe a time you de-escalated a tense situation.
15. How do you measure your own success in a support role?

The call is the test. Are they clear? Warm? Easy to understand? If the screen itself is hard work, the customer calls will be too.

Operations / Logistics Roles (15)

You are screening for organization, problem-solving, and staying steady when plans break. Listen for process and prioritization.

1. Walk me through a typical day in your last operations role.
2. How do you prioritize when everything is urgent?
3. Tell me about a time a process broke and how you fixed it.
4. How do you track and improve key metrics in your work?
5. Describe a time you cut costs or saved time with a process change.
6. What tools have you used to manage workflows or inventory?
7. How do you handle a vendor or partner who misses a deadline?
8. Tell me about a time you managed several moving parts at once.
9. How do you spot a bottleneck before it becomes a crisis?
10. Describe a mistake that cost time or money. What did you learn?
11. How do you handle last-minute changes to a plan?
12. What does a well-run operation look like to you?
13. How do you keep a team aligned on a shared process?
14. Tell me about a report or dashboard you built or relied on.
15. How do you balance speed against accuracy in your work?

Strong ops candidates think in systems. They talk about process, metrics, and how they keep things from breaking. Weak ones just react.

Culture Fit Questions (10)

Skill gets the work done. Fit decides whether the person stays. These 10 questions check how someone works with others and what they need to do their best.

1. Describe the work environment where you do your best work.
2. How do you like to receive feedback?
3. Tell me about a manager you loved working for. What made them great?
4. Tell me about a manager you struggled with. What happened?
5. How do you handle disagreement with a teammate?
6. What does a good team look like to you?
7. Do you prefer clear direction or freedom to figure things out?
8. What kind of company values matter most to you?
9. How do you handle a heavy workload or a stressful week?
10. What would your last team say about working with you?

There are no universally right answers here. A person who needs structure is not "worse" — they are just wrong for a chaotic startup. You are matching the person to your reality.

Red Flag Questions — What to Watch For in Answers

Some questions are designed to surface trouble. The question matters less than how the person answers. Here is what to listen for.

Vague answers with no specifics. Ask "Tell me about a project you led." A strong candidate names the project, their role, and the result. A weak one says "I led a lot of projects and they went well." When someone cannot get specific, they often were not as involved as they claim.

Blaming everyone else. Ask "Why did you leave?" Listen for the story. "My manager was terrible, the team was a mess, the company was a joke." Everyone has had a bad job. But if every past job was someone else's fault, the common factor is the person on the phone.

No questions for you. When you ask "What questions do you have?" and they have none, that often means low interest. The best candidates are interviewing you too.

Inconsistent timeline. "I worked there three years" but the resume says one. Small gaps happen. But probe dates that do not add up.

Bad-mouthing past employers in detail. A little honesty is fine. A long, bitter rant is a preview of how they will talk about you.

Trouble with the basics of the call. Late with no notice. Can barely hear them and they do nothing about it. Distracted. The phone screen is the easiest test they will face. If they fumble it, that tells you something.

Useful red-flag questions to add:

1. What would your last manager say is your biggest area to improve?
2. Why are there gaps between these roles on your resume?
3. What is one piece of feedback you have received more than once?
4. Tell me about a time you failed at something at work.
5. If I called your last manager, what would they say about you?

Question 90 is powerful. A confident candidate answers easily. A worried one starts hedging.

How to Score Answers Consistently (The Rubric Approach)

Good questions are only half the job. If you score answers by feel, you lose all the consistency you just built. The fix is a simple rubric.

Pick 4–6 things that matter for the role. For most screens, that is something like: relevant experience, communication, motivation, role fit, and any red flags. Score each one on a 1–5 scale.

Define what each score means before you start. For "communication":

• 1 — Hard to follow. Rambling or unclear.
• 2 — Gets there, but you work for it.
• 3 — Clear and organized. No problems.
• 4 — Clear and concise. Easy to follow.
• 5 — Sharp. Explains complex things simply.

Do this for every category. Now "she was sharp" becomes "communication: 5, experience: 4, red flags: none." That is something a hiring manager can act on. That is something you can defend.

A simple scorecard looks like this:

CategoryScore (1–5)NotesRelevant experienceCommunicationMotivation / interestRole fitRed flagsTotal/25

Set a bar. Maybe anyone above 18 moves forward, and anyone below 12 is a clear no. The middle gets a second look. The point is to decide the rule before the calls, not after — that is how you keep your own bias out of it.

Why Manual Scoring Breaks Down at Scale

The rubric works great for 10 candidates. At 50, it starts to crack. At 100, it falls apart.

Here is why.

You get tired. Your standard at 9 a.m. is not your standard at 5 p.m. after eight calls. Candidate number 9 gets a harsher read than candidate number 2 — not because they were worse, but because you were drained. This is real and it is unfair.

You drift. Even with a rubric, your sense of "a 4" shifts over a week of calls. The bar you set Monday is not the bar you apply Friday. Multiply that across a team of recruiters and the scores stop meaning the same thing.

You cannot schedule fast enough. Fifty 20-minute calls is over 16 hours of pure talk time. Add scheduling, no-shows, and write-ups, and one role eats your week. Your best candidates get bored waiting and take another offer.

Notes suffer. When you are listening, scoring, and typing at once, something slips. Usually the notes. Two weeks later you cannot remember why candidate 23 got a 3.

None of this is a skill problem. It is a volume problem. Humans are not built to score 100 conversations identically. The questions can be perfect and the scoring still won't be.

The AI Alternative: Let Skillora Ask and Score for You

This is the part that changes the math. You do not have to run every screen yourself.

Skillora is an AI interviewer. You give it the questions — your sales list, your support list, whatever the role needs. It calls every candidate, asks each one the same questions in a natural conversation, and scores the answers against your rubric. Automatically.

Here is what that gives you.

Every candidate gets the same screen. Candidate 1 and candidate 100 face the exact same questions, asked the same way, scored the same way. No fatigue. No drift. No "it was late and I was tired."

All 50 happen at once. AI does not have a calendar. Your whole pipeline can screen tonight, in parallel. Tomorrow morning you open a ranked list instead of a stack of resumes.

You get a ranked shortlist. Each candidate comes back with scores per category, a transcript, and an overall rank. You read the top 10 in detail and skip the rest. Your time goes to the people who earned it.

The notes are perfect. Full transcript, every time. Nothing slips. You can always see exactly why someone scored what they did.

You stay in control. AI handles the first pass — the consistent, repetitive filtering it does better than a tired human. You handle judgment, relationships, and the real interviews. That is the right split.

The questions in this post are the hard part to get right. Skillora is how you ask and score them across 50 or 500 people without losing your week or your consistency.

Let AI ask and score these questions for you → Try Skillora free

Frequently Asked Questions

How long should a phone screening call be? Most phone screens run 15 to 30 minutes. The goal is to filter, not to run a full interview. If you find yourself going past 30 minutes often, you are probably asking deep-interview questions too early. Save those for the next round.

How many questions should I ask in a phone screen? Pick 8 to 12 questions for a 20-minute call. That leaves room for follow-ups and for the candidate's own questions. Trying to cram in 20 questions makes the call feel like an interrogation and gives you shallow answers.

What questions can I not legally ask in a phone screen? Avoid questions about age, race, religion, marital or family status, pregnancy, disability, or national origin. Laws vary by country and region, so check your local rules. The safe path is to keep every question tied directly to the job and the candidate's ability to do it.

What is the difference between a phone screen and a phone interview? A phone screen is a short filter early in the process — it decides who moves forward. A phone interview is deeper and usually comes later, often with the hiring manager. The screen checks for dealbreakers and basic fit. The interview tests skill and depth.

Should I tell candidates the salary range during the screen? Yes. Confirming the range early is one of the best uses of a screen. It saves everyone hours when expectations do not match. In many places it is now required by law, so leading with it is both smart and safe.

How do I keep phone screens fair across many candidates? Ask every candidate the same core questions and score them with a fixed rubric you set before the calls. The two biggest fairness killers are changing your questions on the fly and scoring by gut feel. A shared question list and a 1–5 scorecard fix most of it. At high volume, an AI interviewer like Skillora keeps every screen identical by design.

Can AI really screen candidates as well as a human? For the first pass, often better — because it never gets tired and never drifts. AI is strongest at consistent, repetitive filtering against a clear rubric. Humans are still better at judgment, nuance, and building a relationship. The best setup uses AI for the first screen and humans for the real interviews.

What are the best phone screening questions to ask first? Start with logistics and dealbreakers: notice period, salary expectations, and work setup (remote, hybrid, onsite). These end mismatched calls in minutes. Once you confirm the basics line up, move into motivation and role-specific questions.

Ready to screen your whole pipeline without burning out? Try Skillora free and let AI ask and score these questions for you.