Recruiter Phone Screen for an Internship: What to Expect

You got an email scheduling a 20 to 30 minute call "with a recruiter," and now you're wondering if you need to grind LeetCode by Thursday. You don't. This isn't the real interview yet, it's the first human gate, and a recruiter (often non-technical) is checking something much simpler than your coding skills. Below you get what this call is actually testing, the four or five questions it almost always asks, what to ask back, and the logistics traps that quietly sink students who knew the material cold.

Where the recruiter screen sits in the interview loop

The recruiter phone screen is one stage in a longer sequence, and knowing where it sits stops you from over-preparing the wrong thing.

For most internship pipelines the order runs like this:

• The automated screen, usually first. A timed coding test, a game-based assessment, or a pre-recorded one-way video. No live human, software collects your answers. That's the automated online assessment that usually comes first, and it's a separate stage with separate prep.
• The live recruiter call, which is this one. A real person on the phone (or video), usually short, mostly about fit and logistics.
• The technical or role interviews, later. This is where the depth lives: the deeper behavioral and role interview with the hiring manager or team, and for engineering roles, the technical round later in the loop.

The thing to get straight: this post is about the live human call, not the automated one-way video. If a link with a deadline showed up instead of a calendar invite, you're on the automated gate, and that's the other post.

What the recruiter screen is actually testing

Here's the part every "common phone interview questions" list skips. The recruiter on this call is often not the person who will judge your code or your case-study chops. Their job is narrower: confirm you're a real, qualified, interested human whose resume is true and whose logistics work, then decide whether to pass you to the team. That's it. Everything they ask is in service of those five checks: that you're a coherent communicator, that you broadly meet the basic qualifications, that you actually want this role and didn't mass-apply on autopilot, that your resume holds up to a light sanity check, and that the timeline and location line up.

What they're usually not doing on this call:

• A deep technical grilling. Save the heavy prep for the round where someone technical actually asks.
• The full behavioral interview. The "tell me about a time when" depth comes later.
• A final decision. This is a gate, not the finish line. The bar is "worth the team's time," not "perfect."

So calibrate. Be clear, be interested, get your logistics straight, and don't walk in braced for a whiteboard that isn't coming.

The four to five questions it almost always asks

These come up on nearly every recruiter screen. Each one has a full home elsewhere, so here you get the short version plus where the real answer lives. Don't re-prep the whole thing, just know the shape.

"Tell me about yourself"

The 30-second version, not your life story: where you are now, the one thing you've done that maps to this role, and why you applied. Keep it tight on a screen. For the full formula with worked examples, here's the complete tell-me-about-yourself breakdown.

"Why this company, why this role?"

This is the genuine-interest check, and one concrete sentence beats a paragraph of enthusiasm. Show you read the job description and know the specific thing the company does. "I applied because you're building the payments side and I've been working with Stripe's API in a side project" lands. "I love your mission and your culture" does not, because anyone could say it about anyone.

"Walk me through your resume"

Not a line-by-line read-back, they already have the page. Give a 60-second narrative that picks the two items that map to this role and connects them. Think of it as a guided tour, not a recital: where you started, the relevant thing you did, where you are now.

"What are you looking for, and what's your availability?"

This is a logistics question wearing an interview costume, so answer it concretely. Name your term and your exact dates in one sentence: "I'm looking for a summer 2027 internship, available from mid-May through mid-August." Vague "I'm flexible" answers create work for the recruiter and make you sound unsure. More on the availability trap below.

"Any questions for me?"

Never say "no, I'm good." On a recruiter call you want a couple of process-and-team questions ready. Which ones fit a recruiter (and which to save for later) is in the full guide to questions to ask at the end, and the recruiter-appropriate set is in the next section.

What to ask the recruiter back

The recruiter is the right person for process and timeline questions and the wrong person for deep team-technical ones. Asking "how do you handle service mesh routing" to a non-technical recruiter just lands flat. Asking what the next steps are lands well, because that's literally their job.

A recruiter-appropriate set to pull two from:

• "What does the rest of the process look like, and roughly when should I expect to hear about next steps?"
• "What does the team this intern would join actually work on day to day?"
• "What do you see in someone who does really well in this internship?"

Save the deep technical and culture questions for the people who can actually answer them. The fuller list, sorted by what you're trying to learn, is in questions to ask at the end of an interview.

The logistics traps that quietly sink students

This is where prepared students still lose the call, because they prepped questions and forgot the boring stuff. Run through these before you dial in.

Availability, start date, and term. Know your exact dates and say them in one sentence. If your spring semester ends May 8 and you have a family thing the first week of June, work that out before the call, not live on the phone.

Location and format. Know whether the role is in-office, hybrid, or remote, and whether you can actually be there. If it's on-site in another city, have a real answer about whether you'd relocate for the summer. Don't guess on the call and walk it back later.

The basics of the role you applied to. Students mass-apply and genuinely forget which job this call is about. Pull up the exact job description before the call and skim it. Knowing the role's name and what it does is the floor, and missing it is the fastest way to read as uninterested.

Phone or video setup. A quiet room, a charged phone, good signal or headphones, and the name and time confirmed. If it's video, also handle the camera and lighting, and dress for it: what changes on camera covers the on-screen part. A dropped call or a barking dog mid-answer is an avoidable own-goal.

Salary and logistics, framed as process. If pay comes up, treat it as a process question, not a negotiation. It's fine to ask what the range is, or to say you're flexible within reason. You don't need a scripted number, and you shouldn't invent one.

The work-authorization question. Some recruiters ask about your authorization to work. Answer honestly and briefly, and move on. This guide can't give you visa or legal guidance, and the specifics depend entirely on your situation. For anything beyond a short, honest answer, talk to your school's career office or international student office, who can advise you on your actual circumstances.

A quick pre-call and during-call checklist

Two short lists you can copy. Run the first before you dial, the second while you're on.

Before the call:

• The exact job description open in a tab.
• Your start date and term written in one sentence you can read aloud.
• A quiet room, charged phone, headphones, signal checked.
• Two questions for the recruiter written down.

During the call:

• Confirm the logistics: term, dates, location, format.
• Keep answers tight. It's a short call by design, so don't monologue.
• Take the "any questions for me?" slot. Ask your two.
• Note the next steps and rough timeline they give you.

Frequently asked questions

How long does a recruiter phone screen last?

Usually about 15 to 30 minutes. It's short by design, so keep your answers tight and don't try to cram your whole story into every question. If you're running long on the opener, you're probably over-answering.

Is a recruiter phone screen an interview?

Yes, it counts, but it's the lightest, earliest round. Think of it as a fit-and-logistics gate rather than the technical or hiring-manager interview. You can absolutely get screened out here, so take it seriously, but you don't need to prep it like the final round.

What does a recruiter ask in a screening call?

The staples above: tell me about yourself, why this company and role, a walk through your resume, and what you're looking for, plus logistics like availability and location. Deep technical questions are rare on this call, because the recruiter is often non-technical.

What should I ask a recruiter in a phone screen?

Process and timeline ("what are the next steps and when?"), what the team works on day to day, and what a strong intern looks like to them. Save the deep team-technical and detailed culture questions for the later rounds with people who can actually answer them.

What if the recruiter asks about salary or work authorization?

On salary, treat it as process: it's fine to ask the range or to say you're flexible within reason, with no scripted number. On work authorization, answer honestly and briefly. This guide doesn't give visa or legal advice, so for your specific situation, talk to your school's career office or international student office.

Before your next recruiter call, do two things: write your start date and term in one clean sentence you can say out loud, and pull up the exact job description so the role's basics are fresh. Those two moves clear most of the traps above. Then, while you wait to hear about next steps, browse internships and keep a few more applications moving.