# 20 phone interview questions and answers (sized for a call) | HiredFolio > The 20 questions recruiters ask in a phone screen, with sample answers that fit 30 to 90 seconds, the word budget behind them, and what the law says about the salary and notice questions. Canonical: https://hiredfolio.com/blog/phone-interview-questions Published 2026-11-04 · 14 min Keywords: phone interview questions, phone interview questions and answers, phone screen questions, phone screen interview, how to prepare for a phone interview A phone screen is not a shorter version of the interview. It is a different exercise: a recruiter, usually not the person you would work for, has 15 to 30 minutes to check that nothing about you disqualifies you before the hiring manager spends an hour. The questions are mostly the same ones every guide lists. What changes is the time you have to answer them, and the fact that the person asking is reading a checklist. This post gives you the 20 questions that come up in those calls, with sample answers written to be said out loud in 30 to 90 seconds. Before the list, two things no other guide on this topic does: it converts "keep it under two minutes" into a number of words, and it shows how to read the recruiter's checklist straight out of the job posting. ## How long a phone answer should be, in words Every guide we read says to keep answers short. One says "under two minutes", another "90 seconds to 2 minutes", a third "about 30 seconds per answer". None of them says how many words that is, so people write a 350-word answer, read it fast, and believe it fits. Here is the conversion. We plan at about 160 words a minute, a deliberately unhurried pace that leaves room for pauses, and we did not find a published speaking rate for phone screens, so treat the budgets below as a rule of thumb rather than a measurement. At that pace, 30 seconds is about 80 words, 60 seconds about 160, and "two minutes" about 320. That gives you three budgets, and every sample answer below fits one of them: - **30 seconds, about 80 words.** Logistics: your notice period, your location, whether you are interviewing elsewhere. - **60 seconds, about 160 words.** One proof: a strength, an achievement, your experience with a tool. - **90 seconds, about 250 words.** "Tell me about yourself", and nothing else. Write your answers down and count them before you rehearse. If "tell me about yourself" is past 250 words, it is past 90 seconds however fast it feels in your head. Our guide to [tell me about yourself](/blog/tell-me-about-yourself) does the full conversion for that one question. ## The recruiter's checklist is in the posting A recruiter running a screen is not evaluating you the way a hiring manager will. They are ticking boxes: the must-haves from the posting, plus the four knock-outs (salary, start date, location, work authorization). You can see most of those boxes before the call, because the posting repeats what it cares about. We ran our free [job description keyword extractor](/tools/job-description-keyword-extractor) on the tool's own sample posting, a marketing data analyst role. It found 23 terms. The ones the posting repeats are the ones a screener will ask about: dashboards (3 mentions), SQL, Python, Power BI, Looker and Google Analytics (2 each), then a bachelor's degree and "2+ years" as qualifications. The extractor runs in your browser, groups what it finds into hard skills, tools, qualifications and soft skills, counts how often the posting repeats each one, and leaves the employer's own name out of the list. Turn that output into a one-page sheet: one line per repeated keyword, one proof per line (where you used it, for how long, with what result). When the recruiter asks "can you describe your experience with Power BI?", you are reading, not remembering. That sheet is the phone screen's single real advantage over an in-person interview, so use it. ## The 20 questions, with answers that fit the budget Every answer below is under 140 words, so under a minute out loud at phone pace; most are 45 to 70 words, which is 15 to 25 seconds, and that is deliberate. A screen is a list of checks, and the recruiter has to get through all of them. Each question gets one line on what they are checking, then an answer to adapt. ## The knock-out questions (ask these of yourself first) Recruiters tend to open or close with logistics, because a "no" on any of them ends the process whatever else you say. Have your numbers ready. ### 1. "Are you still looking? What is your situation right now?" They are checking that you are available and that your story matches your resume. > Yes, actively. I am still at Meridian as a support team lead, so I am looking while employed, and I am being selective: I want a role with more ownership of process, which is why your posting stood out. I can make time for interviews during the day with a little notice. ### 2. "When could you start?" They need a date to compare against the team's plan. Give a real one, and know where it comes from. > I have a four-week notice period in my contract. If we got to an offer in the next two weeks, I could start the first week of December. I would rather give a date I can keep than promise sooner and have to move it. Where that date comes from matters, and the guides get it wrong. Three of the pages ranking for this query tell you to offer "the standard two weeks' notice". That is a US custom, not a rule everywhere. In the UK, the statutory minimum is written down: "You must give at least a week's notice if you've been in your job for more than a month", and your contract can require more ([gov.uk, Handing in your notice](https://www.gov.uk/handing-in-your-notice/giving-notice)). Check your contract before the call, because "two weeks" said to a recruiter becomes a start date in a spreadsheet. ### 3. "What are your salary expectations?" The question that filters most people out of a screen, in both directions. Give a range you have researched, and anchor it to the role, not to your current pay. > From what I have seen for this level in this market, I am looking at 68 to 75 thousand base. I am open on the rest of the package, and I would want to understand the bonus structure and the equity before settling on a number. If the recruiter asks what you earn now rather than what you want, know where you stand. In California, the Labor Code says it plainly: "An employer shall not, orally or in writing, personally or through an agent, seek salary history information, including compensation and benefits, about an applicant for employment" ([Labor Code section 432.3(b)](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=LAB§ionNum=432.3)). Other states and cities have their own rules; check yours. Elsewhere, you can still decline politely and redirect to your expectations. Our guide to [answering the salary expectations question](/blog/salary-expectations) has the full set of scripts. ### 4. "Where are you based? Would you relocate, or how often could you be in the office?" A pure logistics check against the posting's hybrid or on-site terms. > I am in Leeds, about forty minutes from your office by train. Three days a week on site is fine for me; I do that now. I would not be looking to relocate, so if the role moved to a different office that would be a conversation. ### 5. "Are you authorized to work here? Will you need sponsorship?" Employers do ask this at the screening stage, because it affects whether they can hire you at all. Answer the question asked. What they should not ask is a different one: the US Equal Employment Opportunity Commission says that "Most employers should not ask whether or not a job applicant is a United States citizen before making an offer of employment" ([EEOC, Pre-Employment Inquiries and Citizenship](https://www.eeoc.gov/pre-employment-inquiries-and-citizenship)). Authorization and citizenship are not the same question. > Yes, I am authorized to work in the US without sponsorship, now and going forward. ### 6. "Are you interviewing with other companies?" They want to know how fast they need to move, and whether you are in demand. Be truthful without naming names. > I am in process with two other companies, one at the final stage. That said, this role is the closest match to what I am looking for, so if your timeline is a few weeks I am happy to work with it. It would help to know roughly when you expect to decide. ## Questions about you ### 7. "Tell me about yourself." The one answer that gets 90 seconds. Present, one relevant piece of the past, and why this role. Count it: 250 words is the ceiling. The example below is 139 words, about 50 seconds, which leaves room for a second proof if you have one. > I am a product designer with six years in B2B software, the last three at Fieldwire where I own the mobile app's onboarding and settings. Before that I was at an agency, which is where I learned to ship fast and to present work to people who do not read design documents. The thing I am proudest of from the last year is cutting our onboarding drop-off from 38 to 21 percent, mostly by removing steps rather than redesigning them. I am looking now because I want to work on a product where design has a seat in the roadmap conversation, not just in the delivery one, and your posting describes exactly that: a designer embedded in a squad with a PM and a tech lead, owning outcomes. I would be glad to go into any part of that. ### 8. "Walk me through your current role. What do you actually do day to day?" They are checking that your title matches your work. Give the week, not the job description. > Most of my week is three things. I run the pipeline for two product lines, so I am in the CRM every morning and with sales twice a week. I write the monthly forecast and present it to the regional director. And I own the onboarding of new reps, which is about a quarter of my time in a hiring quarter. Beyond that, it is the usual firefighting when a big account wobbles. ### 9. "Why are you leaving your current job?" They are listening for anything negative about your employer, and for a reason that this job fixes. > The company was acquired in March, and the role I was hired for, building the analytics practice, is now done out of the parent company's office. I have no complaints about the team. I just want to keep building, and this role is a build. ### 10. "What is your greatest strength?" One strength, one proof, one link to the posting. > Getting a team to ship on a date. At my current company I inherited a release that had slipped twice; we shipped the next three on the day we said, mostly by cutting scope earlier and saying so out loud. Your posting mentions a migration due in Q2, so I expect that is useful. ### 11. "What is your greatest weakness?" A real one, with what you do about it. We have a full guide to [answering the weakness question](/blog/what-are-your-weaknesses); the short version: > I take on too much when a team is short-handed, and then my own deliverables slip. I now keep a written list of what I have agreed to and review it with my manager every two weeks, which has made me say no earlier. It is better than it was; it is not fixed. ### 12. "What achievement are you proudest of?" One story with a number at the end. The [STAR shape](/blog/star-method) works on the phone precisely because it is short; one row each, under 100 words in total.
Situation

Last year our customer support backlog was running at four days, and churn in the first 90 days was climbing.

Task

I was asked to get first-response time under a day without adding headcount.

Action

I pulled the 200 most recent tickets, found that a third were the same two billing questions, wrote the two help articles and had the product team put the answers in the invoice email.

Result

Ticket volume fell 28 percent in six weeks and first response went to nine hours. Early churn stopped climbing the following quarter.

### 13. "Tell me about a time you failed." They want to hear that you can name a failure without blaming anyone, and that something changed afterwards. > I launched a pricing change in 2024 without testing the email to existing customers. Around 300 people got a message that read like a price increase when it was not, and we spent a week on the phone. Since then, anything that touches billing gets a review from support before it goes out, and I have not shipped a change like that since. ## Questions about the job and the company ### 14. "Why do you want to work here?" They are checking that you read beyond the job title. One specific fact about the company, one link to you. Our guide to [why do you want to work here](/blog/why-do-you-want-to-work-here) has twelve more. > Two reasons. You moved the whole product to usage-based pricing last year, and I have run that transition once; I know where it hurts. And your engineering blog is written by the people doing the work, which tells me something about how the company treats expertise. I would like to work somewhere that does that. ### 15. "What do you know about the role?" Repeat the posting back in your own words, then name one thing you would want to understand. > As I read it, it is the first dedicated data analyst on the marketing team, owning the Power BI and Looker dashboards and the weekly reporting, with a lot of SQL against the warehouse and some Python to automate the recurring parts. The piece I would want to understand is how the CRM data gets from Salesforce into the warehouse today, because that is usually where the time goes. ### 16. "Can you describe your experience with [tool or skill from the posting]?" This is where the keyword sheet pays off. Years, context, depth, in that order. > SQL daily for five years, mostly PostgreSQL, against a warehouse of about 40 tables. I write the queries behind our dashboards, and I have done the less glamorous work too: migrating the reporting layer when the schema changed. Python I use for the automation around it, pandas mainly, not for modelling. ### 17. "How would you describe your work style? How do you handle pressure?" Two questions that get the same answer: a habit, and a moment where it held. > I plan the week on Monday and protect two mornings for deep work, and I am direct about trade-offs before a deadline rather than after. In the last quarter-end crunch, that meant telling finance on day two that one of the three reports would be a day late, which they could plan around. The alternative is all three late and no warning. ### 18. "What are you looking for in your next role? What motivates you?" They are checking the fit between what you want and what this job is. Be specific enough that a mismatch would show. > Ownership of a product area end to end, including the metrics, and a manager who gives feedback often. I did my best work in the two years I had both. I am less interested in a role that is mostly coordination, which is why I asked about the squad structure. ### 19. "Tell me more about [a line on your resume]." Usually a gap, a short stint or a title that does not match. Answer in two sentences and stop; a long explanation sounds like a defence. If it is a gap, our guide to [resume gaps](/blog/resume-gaps) covers the wording. > The eight months in 2023 were a planned break: my partner relocated for work and I took the time to finish a data engineering certificate before looking again. I started at my current company the month after. ### 20. "Do you have any questions for me?" Always yes, and the two that matter on a screen are about process. Our list of [questions to ask the interviewer](/blog/questions-to-ask-interviewer) has the rest. > Two, if I may. What does the rest of the process look like, and when do you expect to decide? And is this a new position or a backfill? That tells me a lot about what the first months would be. ## When the call comes without warning Several of the French and English guides we read say the same thing: the first recruiter call often comes unannounced, and it is fine to ask to call back in half an hour. Do that. The harder problem is that by the time they call, you may have applied to thirty jobs and the posting may be gone from the site; we wrote about [why postings get taken down](/blog/job-posting-taken-down) and how to find them again. The fix is to keep the posting at the moment you apply. If you track applications in HiredFolio, the browser extension saves the job with its title, company and the description text as it was on the day, and the tracker shows that description on the job's page. When the recruiter calls, you open the job, read the must-haves back, and your keyword sheet is next to it. Thirty seconds of "sorry, which role was this?" is a bad start to a call whose whole purpose is to check that you are organised.

On the phone what the recruiter hears, and what they do not

Costs you the screen

Answering from a car or a café because declining felt rude

A 350-word "tell me about yourself" read at speed

"Two weeks" as a start date you have not checked

A single salary number, or your current salary

Gets you the next round

"Can I call you back in thirty minutes?" and a quiet room

Under 250 words, written down and counted

Your contract's notice period, turned into a date

A researched range, anchored to the role

The recruiter cannot see you, so the only thing being scored is what you say and how long it takes.

## After the call Ask for the next step and the date before you hang up, then write both down. Send a short thank-you the same day; our [thank-you email templates](/blog/thank-you-email-after-interview) include one for a recruiter screen. If the date passes with no news, a one-line follow-up is normal, not pushy. ## Prepare the screen in HiredFolio Paste the posting into the free [keyword extractor](/tools/job-description-keyword-extractor) to get the list of skills, tools and qualifications it repeats, and write one proof per line. Save the job to your tracker so the posting is still there when the call comes; after the screen, move the job to Interviewing and set its follow-up date, and the daily digest reminds you when it is due. [Try HiredFolio for free](/home)

Key takeaways before the recruiter calls

01

Write your answers and count them: 80 words for logistics, 160 for one proof, 250 for "tell me about yourself", at a planning pace of about 160 words per minute.

02

Pull the repeated keywords out of the posting and prepare one proof per keyword; that list is the recruiter's checklist.

03

Check your contract's notice period and your market range before the call, so the two knock-out questions get real numbers.

Next step: time your "tell me about yourself" to 90 seconds, the one answer every screen opens with.

## Read next - [Where do you see yourself in 5 years? How to answer, with the numbers the interviewer already knows](https://hiredfolio.com/blog/where-do-you-see-yourself-in-5-years) - [Why do you want to work here? How to answer with what the job posting doesn't say](https://hiredfolio.com/blog/why-do-you-want-to-work-here) - [Why should we hire you? How to answer, with 5 example answers](https://hiredfolio.com/blog/why-should-we-hire-you)