Technical Phone Screen Interview: Format, Questions and a Minute-by-Minute Plan

What is a phone screen interview? Recruiter screen vs technical screen vs onsite

“Phone screen” covers two different conversations. The recruiter screen checks that the role, level, location and timing make sense for both sides; Meta's hiring page describes it as a call about your background, experience, long-term goals and interest in the company, and Google says to expect one or two shorter conversations with a recruiter by phone or video, which it says usually assess key skills for the role as well. The technical phone screen is an interview: an engineer watches you solve problems and reports whether you should go on to the loop.

The onsite, often virtual and usually called the loop, repeats the technical screen several times with different interviewers and adds system design and behavioral rounds. The table shows how the three stages differ, with published examples where the companies give them.

• Meta Careers: Hiring process
• Google Careers: Our hiring process
• Amazon Jobs: SDE III Interview Prep
• Microsoft Careers: How we hire

Technical phone screen at Amazon, Meta, Google and Microsoft

Company-specific advice online is mostly anecdote, so this section uses only what each company's own pages said on November 14, 2026. Some of those pages are not recent: Meta's minute-by-minute breakdown comes from a careers-blog post dated October 6, 2022, and Amazon's overview article is dated February 19, 2025. Formats differ by role and change over time; your recruiter's description of your process is the authority.

Two details are worth noticing. First, the stage is not always a call: Amazon's SDE II page lists an online assessment and then the loop, with no phone screen. Second, tools are changing: Meta's hiring page notes that select roles now include an authorized AI assistant inside CoderPad during technical interviews, while Google's interview tips state that Google Search and AI are not permitted during its interviews.

• About Amazon: Amazon interview process, from phone screens to interview loops
• Amazon Jobs: SDE III Interview Prep
• Amazon Jobs: Front-End Engineer Interview Prep
• Amazon Jobs: SDE II Interview Prep
• Meta Careers: Preparing for Your Technical Screen
• Meta Careers blog: Preparing for your software engineering interview at Meta
• Google Careers: Our hiring process
• Microsoft Careers: Technical interviewing

What a technical phone screen assesses

The published guidance is consistent across companies. Meta's 2022 blog post says interviewers pay close attention to how you solve the problem, which can matter as much as reaching the right answer, and it tells candidates to think out loud. Microsoft asks for clarifying questions and a plan before you implement, clean and bug-free code in a language you are strong in, no pseudocode, and testing before you call the solution done. Amazon's prep pages ask for syntactically correct code and attention to edge cases.

Put together, an interviewer leaves a screen with four notes. Did the candidate understand the problem before coding? Did they reach a reasonable algorithm and know its complexity? Does the code run, or nearly run? Could I follow them, and did they respond to hints? Candidates who code silently for twenty minutes leave the first, second and fourth notes blank even when the code is right.

• Understanding: restating the problem, asking about input size, duplicates, empty input and output format.
• Algorithm: a brute force stated in one sentence, then a better approach with time and space complexity.
• Code: real syntax, sensible names, no pseudocode; Meta's post says its interview editor has no syntax highlighting or auto-completion.
• Verification: tracing an example by hand, naming edge cases, fixing your own bugs before the interviewer points them out.
• Collaboration: saying what you are thinking, taking hints, and explaining your solution when asked.

• Meta Careers blog: Preparing for your software engineering interview at Meta
• Microsoft Careers: Technical interviewing

A minute-by-minute plan for a 45-minute screen

This plan follows the structure Meta published for its screen in a careers-blog post dated October 6, 2022: 5 minutes of introductions, 35 minutes of coding on two problems, and 5 minutes for your questions. Meta's current tech-screen page confirms a 45-minute conversation with an engineer but gives no breakdown, so treat the split as an example and ask your recruiter whether it still applies. The post describes the problems as short enough to explain in a few minutes and to solve in 10 to 30 minutes, so the budget below gives the first problem 17 minutes and the second 18.

For a 60-minute screen that is half behavioral, such as the Amazon formats above, expect about half an hour on Leadership Principles stories and one coding or design problem handled with the same four steps. In either format, if you still have no approach six or seven minutes into a problem, say your best current idea aloud and ask whether to proceed.

• Meta Careers blog: Preparing for your software engineering interview at Meta

How to think aloud: a script with a worked problem

Thinking aloud does not mean narrating every keystroke. It means saying four things at the right moments: what you understood, what you plan and why, what a tricky line is for, and how you know the code works. The example shows those four moments as comments around a classic problem, merging overlapping ranges. The code was run with Python 3.12 and printed the three results shown in its last lines.

Prepare sentences for the awkward moments too, because a long silence gives the interviewer nothing to evaluate. The phrases below fit most coding interviews and keep the interviewer in the loop.

• To buy thinking time: “Let me take thirty seconds to think about the data structure.”
• When stuck: “I see how to do it in O(n^2). I suspect sorting helps; I am looking for what stays true after the sort.”
• When taking a hint: “So the last kept range is the only one that matters. That removes the inner loop.”
• When you spot a bug: “This breaks for touching ranges; I need less-than-or-equal here.”
• When time is short: “I will finish the working version first and describe the optimization afterwards.”

# Interviewer: "Merge the overlapping time ranges in this list."
#
# Clarify: "Is the input sorted? Do (2, 6) and (6, 8) count as overlapping?
#           Can the list be empty? May I return a new list?"
# Plan:    "Brute force compares every pair, O(n^2). If I sort by start, each range
#           can only overlap the last one I kept, so one pass is enough:
#           O(n log n) time for the sort, O(n) extra space. Shall I code that?"
def merge_ranges(ranges: list[tuple[int, int]]) -> list[tuple[int, int]]:
    merged: list[tuple[int, int]] = []
    for start, end in sorted(ranges):          # "Sorting tuples orders by start."
        if merged and start <= merged[-1][1]:  # "<= because touching ranges merge."
            last_start, last_end = merged[-1]
            merged[-1] = (last_start, max(last_end, end))  # "max: one range may contain the next."
        else:
            merged.append((start, end))
    return merged


# Test aloud: unsorted input with touching ranges, empty input, a range inside another.
print(merge_ranges([(9, 11), (1, 3), (2, 6), (6, 8)]))  # [(1, 8), (9, 11)]
print(merge_ranges([]))                                  # []
print(merge_ranges([(1, 10), (2, 3)]))                   # [(1, 10)]

Phone screen interview questions by role

What the problems look like depends on the role. Only four rows below rest on a published company page, and each describes one company, not the industry. For every other role and company, the honest answer is to ask the recruiter which formats to expect; asking is normal, and Meta's hiring page itself tells candidates to review the preparation information their recruiter provides.

Whatever the role, a screen draws on fundamentals you have not used recently. A spaced-repetition app such as RecallDeck can keep definitions, complexities and standard trade-offs fresh, but it does not replace solving problems aloud against a clock.

• Meta Careers: Preparing for Your Initial Interview (front-end engineering)
• Meta Careers: Preparing for Your Initial Interview (machine learning)
• Data structures and algorithms interview questions
• System design interview questions
• Frontend developer interview track
• Backend interview track

Phone screen interview tips: setup checklist and what to do after

Most setup advice comes directly from the companies. Meta suggests a quiet place, a good connection and headphones so both hands are free for coding; Google suggests checking your microphone, video and Wi-Fi and keeping a notebook and pen nearby. Add the checks below the evening before, alongside the general day-before checklist.

Afterwards, act while the memory is fresh. Amazon's February 2025 article says to expect a decision within two business days after a phone screen; the other pages we read do not give a number, so ask the recruiter when you will hear and tell them about any competing deadlines.

• Open the editor link early and type a few lines; practice beforehand in a plain text editor without autocomplete.
• Choose the language you know best, as Meta and Microsoft both advise, and tell the interviewer at the start.
• Have your resume and the job description open, with a 60-second introduction and two questions ready.
• Close chat apps, notes and AI tools unless the company has said a tool is allowed.
• Keep water, a charger and a backup connection, such as a phone hotspot, within reach.
• Right after the call, write down each problem, where you lost time, and what hint you needed.
• Send a short thank-you; Meta lets candidates message each interviewer through the career profile.
• Re-solve the screen's problems the next day from a blank editor, whatever the outcome.

• The day-before technical interview checklist
• How to answer “Tell me about yourself” as a software engineer
• Coding online assessment: HackerRank and CodeSignal
• Meta software engineer interview preparation plan
• Google Careers: Interviewing at Google, best practices, advice, and tips

Quick answers

Frequently asked questions