Skip to content
All posts

You Applied Online, Then the Phone Rang: A Sample Recruiter Call

After you submit your resume on a job platform, the first real step is usually a short call from a recruiter. Here's a full sample conversation, line by line, with notes on why each answer works.

Harshil Moradia

8 min read

You Applied Online, Then the Phone Rang: A Sample Recruiter Call

You've uploaded your resume on a job platform, filled in the same details the resume already had, and clicked submit. A few days later an unknown number calls. It's a recruiter, and they'd like "a quick chat."

This first call, often called a phone screen, usually lasts 15 to 30 minutes. The recruiter isn't testing your coding. They're checking a few basics: are you real, does your background match the role, are you actually interested, and do your salary and availability fit. If those check out, you move on to the technical rounds.

Below is a full sample call for a developer role, with notes on what makes each answer work.

Before the phone rings

Once you start applying, assume a call can come at any time:

  • Keep a list of where you applied: company, role, date, and the job post link. "Which position was this again?" is not a great start.
  • Save each job description. Postings often disappear once a role closes.
  • Have a short intro ready, about 60 seconds, covering who you are, what you work on, and what you're looking for.
  • Know your numbers: your salary expectation, your notice period, and when you could start.

If the call comes at a bad time, it's fine to say so: "Thanks for calling! I'm just stepping out of something. Could we talk at 3pm today?" A short delay is much better than a distracted conversation.

The sample call

The candidate, Alex, applied for a Full-Stack Developer (React / Node.js) role through a job platform. The recruiter, Jordan, calls three days later.


Jordan: Hi, is this Alex? This is Jordan from BrightPath Software. You applied for our Full-Stack Developer position on the job board last week. Is now a good time to talk for about 20 minutes?

Alex: Hi Jordan, yes, this is a good time. Thanks for calling. That's the React and Node.js role, right?

Why it works: Alex confirms the time and names the role, which shows they remember exactly what they applied for.


Jordan: That's right. To start, could you tell me a little about yourself and your current work?

Alex: Sure. I'm a full-stack developer with about four years of experience, mostly with React on the front end and Node.js with PostgreSQL on the back end. Right now I'm at a logistics company, where I work on the dashboard customers use to track their shipments. Recently I led the move from a slow server-rendered page to a React app, which cut the page load time roughly in half. I enjoy the product side of the work, building things real users touch every day, and that's a big part of why your role caught my eye.

Why it works: It's under a minute, it matches the job's tech stack, it includes one concrete result, and it ends by connecting back to this role. It's not a life story or a read-out of the resume.


Jordan: Great. What made you interested in BrightPath specifically?

Alex: I looked at your product before applying. Your scheduling tool is used by small clinics, and I liked that the problems are very practical: double bookings, reminders, staff schedules. My current work is also about helping operations teams day to day, so it feels like a natural next step. And the job post mentioned you're rebuilding the front end, which is exactly the kind of project I've been doing.

Why it works: A specific reason tells the recruiter Alex didn't just mass-apply. Even five minutes on the company's website is enough to give an answer like this.


Jordan: Why are you looking to leave your current job?

Alex: I've learned a lot there, and I'm on good terms with the team. The product is fairly stable now, so most of my work is maintenance. I'm looking for a place where I can build new features and grow toward a more senior role.

Why it works: Alex talks about what they're moving toward, not what they're running from. No complaints about the boss, the pay, or the codebase.


Jordan: The role is mostly React and TypeScript, with some Node.js APIs. How comfortable are you with TypeScript?

Alex: Very comfortable on the front end. Our dashboard has been fully TypeScript for about two years. On the back end I've used it in a couple of newer services, but some of our older Node code is still plain JavaScript, so that's an area where I'd say I'm solid but still learning.

Why it works: It's honest and specific. Recruiters usually pass these notes to the hiring manager, and an accurate answer protects you in the technical round.


Jordan: What are your salary expectations?

Alex: Based on the role and what I've seen for similar positions in this area, I'm looking at around [your researched range]. I'm flexible depending on the full package. Could you share the budgeted range for this role?

Why it works: Alex gives a researched range, signals some flexibility, and asks for the company's range in return. Before the call, check salary sites and similar job posts so your number is grounded. If you're early in your job search and really unsure, it's also fine to say: "I'd like to learn more about the role first. Could you share the range you have in mind?"


Jordan: And what's your notice period? When could you start?

Alex: My notice period is one month, so I could start about four weeks after accepting an offer.

Why it works: A clear, direct fact. No need to over-explain.


Jordan: Do you have any questions for me?

Alex: Yes, a few. What does the interview process look like from here? And how big is the team I'd be joining?

Jordan: Next would be a one-hour technical interview with two engineers, then a final call with the engineering manager. The team is six developers plus a designer.

Alex: That's helpful, thanks. One more: what would you say makes someone really successful on this team?

Jordan: Honestly, people who communicate well. The team is partly remote, so clear updates and asking questions early matter a lot.

Why it works: Asking about the process shows you're serious. The last question gives Alex useful material to bring up in the next round.


Jordan: Great. I'll share your profile with the hiring manager and get back to you by the end of the week.

Alex: Sounds good. Thanks, Jordan, I enjoyed the conversation. Is email the best way to reach you if I have any questions?

Jordan: Yes, I'll send you a quick email now so you have my address.

Alex: Perfect. Have a great day!

Why it works: A warm, simple close, and Alex makes sure they have a way to follow up.

After the call

  • Write notes right away: the recruiter's name, the next steps, the timeline, the salary range if they shared one, and anything they said about the team.
  • Send a short thank-you email the same day:

Hi Jordan,

Thanks for the call today. I enjoyed hearing about the team and the front-end rebuild, and I'm excited about the next step. Please let me know if you need anything else from me.

Best regards, Alex

  • Prepare for what they told you. If the team cares about communication, have a story ready about a time you kept others informed or raised a problem early.
  • Follow up once if the date they gave passes without news. A polite check-in a couple of days later is normal and not pushy.

Common mistakes to avoid

  • Not knowing which job it is. Keep your application list handy.
  • Reading your resume out loud. The recruiter already has it. Give the highlights and the story behind them.
  • Talking badly about your current employer. It always raises doubts.
  • Answering from a noisy place. Reschedule rather than shout over traffic.
  • Saying "I have no questions." Two or three good questions go a long way.

The recruiter call is the easiest stage of the process to prepare for, and it decides whether you get to the rest. Treat it as a real conversation instead of a formality, and you'll come across as the candidate the recruiter is glad to pass along.

Thanks for reading. If this was useful, the newsletter below is the best way to catch the next one.

Keep reading

More essays