Skip to content
AssistedVoice
Phone screen interviews

Two calls before the onsite

A “phone screen” is usually two calls: 15–30 minutes with a recruiter on your background, pay, notice period and work authorisation, then 45–60 minutes of live coding with an engineer. On Zoom, Google Meet or Microsoft Teams, get first-person answers from your resume, and an approach and working code from a screenshot of the problem.

No credit card 30 minutes free Encrypted
Example: with a screenshot of “Find every unique pair in a sorted array that sums to a target” attached, the Code tab answers with this approach: Two pointers from either end of the sorted array: move the left one up when the sum is too small and the right one down when it’s too big. After a match, step past repeated values so each pair appears once.
  1. Call 1Recruiter screen15–30 min, fit and logistics
  2. Call 2, shown aboveTechnical screen45–60 min, live coding

Call 1 of 215–30 minutes, with a recruiter

The recruiter screen: fit and logistics

Commonly 15–30 minutes, and about 30 in one Meta candidate’s report. The recruiter checks that your resume holds together, that you have a specific reason for wanting the role, and that pay, notice period, location and work authorisation fit. One recruiter on Reddit called it a viability check, not a skill check. FinalCV (opens in a new tab); Argo Apply (opens in a new tab); Reddit, 2025 (opens in a new tab); Taro, 2025 (opens in a new tab)

How the call runs, in one guide’s model

  1. Step 1Small talk
  2. Step 2Your backgroundAbout 90 seconds
  3. Step 3Resume questions
  4. Step 4LogisticsWhere most screens are decided, the guide says
  5. Step 5Your questions
  6. Step 6Next steps

FinalCV (opens in a new tab)

What they ask, and what they’re checking

Questions from recruiter-screen guides and candidate reports. The wording varies by recruiter.
They askWhat they’re checking
About you
“Walk me through your background.”A short, clear version of your resume that matches what’s on paper. FinalCV (opens in a new tab); Argo Apply (opens in a new tab); Taro, 2025 (opens in a new tab); cswork, 2025 (opens in a new tab)
“Why this company, and why this role?”A specific reason for wanting this job, not one you could give anywhere. FinalCV (opens in a new tab); Argo Apply (opens in a new tab); cswork, 2025 (opens in a new tab)
“Why did you leave each job?”That the story holds together. Criticising a past employer, or being vague about gaps, counts as a red flag. FinalCV (opens in a new tab); Argo Apply (opens in a new tab); Reddit, 2025 (opens in a new tab)
Logistics
“What are your salary expectations?”Whether you fit the band. Guides suggest a researched range whose bottom you’d accept; a number far outside the band ends many screens. FinalCV (opens in a new tab); Argo Apply (opens in a new tab); Reddit, 2025 (opens in a new tab); Reddit, 2025 (opens in a new tab)
“What’s your notice period, and when could you start?”Whether you can join when the team needs you. One guide says that in India this is often the deciding question, for example a 90-day notice for a role that needs someone in 30. FinalCV (opens in a new tab); Argo Apply (opens in a new tab)
“Does the location, or remote work, suit you?”Whether you can work where the role is based. FinalCV (opens in a new tab); Argo Apply (opens in a new tab)
“Will you need visa sponsorship, now or in the future?”Work authorisation. One Reddit thread flags a common failure: saying “no sponsorship needed” on the application, then correcting it on the call. FinalCV (opens in a new tab); Argo Apply (opens in a new tab); Reddit, 2025 (opens in a new tab)
“Are you interviewing anywhere else?”Where you are in other hiring processes. FinalCV (opens in a new tab); Argo Apply (opens in a new tab); Taro, 2025 (opens in a new tab)

Not every first call is a recruiter

One CRED SDE-2 candidate’s first call, in December 2025, was a conversational chat in a hiring-manager style about their production tech stack, their use of AI tools and their work history. It was booked for about 30 minutes and ended in about 20. interviewexperiences.in, 2025 (opens in a new tab)

If the call is on Zoom, Google Meet or Microsoft Teams, press the answer shortcut when a question lands for a first-person answer drawn from your resume and the files you upload, such as the job description. If the recruiter rings your phone, that isn’t a video call, and Assisted Voice doesn’t apply.

Call 2 of 245–60 minutes, with an engineer

The technical screen: live coding, mostly

Usually 45–60 minutes of live coding in a shared editor or doc, with one or two LeetCode-style problems at most big-tech companies. At some companies and levels, part of the hour goes to behavioural or design questions. Meta Careers, 2022 (opens in a new tab); Google Careers (opens in a new tab); Amazon Jobs (opens in a new tab); GeeksforGeeks, 2025 (opens in a new tab)

Often a video call. Despite the name, many technical screens run over video. Google describes its screens as phone or video interviews, one 2025 Google candidate’s ran 45 minutes over Google Meet, and Stripe’s runs over Zoom with your screen shared. Google Careers (opens in a new tab); GeeksforGeeks, 2025 (opens in a new tab); Stripe (opens in a new tab)

Sometimes a test first. A Codility test came before the screen in one Microsoft report. Assisted Voice isn’t for online assessments. Taro, 2025 (opens in a new tab)

On Zoom, Google Meet or Microsoft Teams, capture the problem with the screenshot shortcut, and the Code tab gives an approach and working code. If the hour turns to behavioural questions, press the answer shortcut for a first-person answer from your resume. If it turns to design, the Diagram tab draws the components and data flow as the question is asked.

Meta’s 45 minutesThe E4–E5 screen as Meta describes it, in CoderPad with an engineer
  1. 0:00

    Introductions · 5 minutes

  2. 0:05

    Two problems · 35 minutes of coding

    Problem 1about 15–20 min
    Problem 2about 15–20 min

    Written without syntax highlighting or autocomplete. Candidates budget about 15–20 minutes a problem, and one guide says spend no more than 20 on the first.

  3. 0:40

    Your questions · 5 minutes

  4. 0:45

    Call ends

Meta Careers, 2022 (opens in a new tab); Meta Careers (opens in a new tab); Personal blog, 2024 (opens in a new tab); interviewexperiences.in, 2025 (opens in a new tab); Reddit, 2025 (opens in a new tab); Hello Interview, 2026 (opens in a new tab)

Technical screens, company by company

How long the call is, where you write code, and what fills the hour. Formats change by team, level and year.

Company guides and individual candidate reports, not official policy for every team.
CompanyLengthWhere you codeWhat’s in the hour
MetaE4–E5 · Meta’s guide (2022), reports from 2025Length: 45 minutes, about 35 of them codingWhere you code: CoderPad, with no syntax highlighting or autocompleteTwo coding problems. One 2025 candidate got Valid Word Abbreviation and Binary Tree Vertical Order Traversal; the second is also on a 2026 guide’s list of Meta’s most-asked problems. Meta’s hiring FAQ says outside AI tools aren’t allowed; only the tools inside its interview environment may be used.Meta Careers, 2022 (opens in a new tab); Meta Careers (opens in a new tab); interviewexperiences.in, 2025 (opens in a new tab); Hello Interview, 2026 (opens in a new tab); Meta Careers (opens in a new tab)
MetaE6 · guides and one report, 2024–26Length: About an hourWhere you code: Not stated in these sourcesCoding plus a behavioural block. The guides conflict on the split: about 35 minutes of coding and 25 of behavioural in one, 25 and 15 in another. One 2024 E6 candidate had 45 minutes: two problems, then questions about past work.Hello Interview, 2026 (opens in a new tab); Personal blog, 2024 (opens in a new tab); Reddit, 2024 (opens in a new tab)
GoogleSWE L3–L4 · 2025–26Length: 30–60 minutes, per Google; 45 in a 2025 reportWhere you code: A shared Google Doc, explaining your thinking as you writeUsually one problem with follow-ups. One 2025 candidate was asked for every unique pair in a sorted array that sums to a target, then a follow-up on duplicates. Candidates describe a 2025–26 pilot that adds a separate Googleyness screen. Google’s virtual-interview guide says using AI during an interview means disqualification.Google Careers (opens in a new tab); GeeksforGeeks, 2025 (opens in a new tab); Blind, 2025 (opens in a new tab); LinkedIn, 2026 (opens in a new tab); Reddit, 2026 (opens in a new tab); Google (opens in a new tab)
AmazonSDE III · Amazon’s prep page (undated)Length: 60 minutesWhere you code: Amazon’s Livecode tool. Amazon expects syntactically correct code, not pseudocode.With a senior leader: half Leadership Principles, half coding and system design. Amazon’s remote-interview page says interviews run on Zoom or Amazon Chime; Assisted Voice works on Zoom, not Chime. Business Insider reported internal guidelines telling candidates not to use GenAI tools during interviews unless explicitly permitted.Amazon Jobs (opens in a new tab); Amazon Jobs (opens in a new tab); Business Insider, 2025 (opens in a new tab)
AmazonSDE II and graduate · reports, 2025Length: 60 minutes for SDE II; 30 in one graduate inviteWhere you code: Not stated in these reportsSDE II candidates describe one DSA problem and two Leadership Principles questions, such as T9 predictive text with a trie alongside Customer Obsession and Ownership, or a Next Greater Element II variant. One graduate invite said coding only, but a commenter had two LP questions on an AWS screen.interviewexperiences.in, 2025 (opens in a new tab); Reddit, 2025 (opens in a new tab); Reddit, 2025 (opens in a new tab); Reddit, 2025 (opens in a new tab)
MicrosoftSDE-1 and SWE · reports, 2025Length: 45–60 minutesWhere you code: After a Codility test, in one reportOne candidate had 15 minutes on intro and projects, then 45 on two problems, one a combination-sum variant: fill a work-schedule string so its digits add up to the weekly hours. Another had data structures, OOP, DBMS and live coding. Microsoft’s Candidate Code of Conduct says candidates should show their own skills in assessments and interviews, without outside assistance unless explicitly permitted.Taro, 2025 (opens in a new tab); interviewexperiences.in, 2025 (opens in a new tab); Microsoft Careers (opens in a new tab)
UberSDE-2 · reports, 2025–26Length: About an hourWhere you code: HackerRankOne coding problem plus about 15 minutes of high-level design, scored on coding and on design and architecture. Reported problems include Sliding Window Maximum and a Number of Islands II variant.Reddit, 2026 (opens in a new tab); interviewexperiences.in, 2026 (opens in a new tab); interviewexperiences.in, 2025 (opens in a new tab)
StripeSWE · Stripe’s guide (undated), a 2025 reportLength: About 45 minutes technical, plus 15 for intros and questionsWhere you code: HackerRank, or your own IDE shared over Zoom, in any language. Docs and Google are allowed, AI tools aren’t.One practical, multi-part problem, graded on how far you get, correctness, testing, debugging, code design and communication, with readability ahead of performance. Stripe’s sample moves money between bank accounts so each ends with at least 100. One 2025 candidate got a three-part cost calculation and had under 10 minutes left after part three.Stripe (opens in a new tab); cswork, 2025 (opens in a new tab)

In India, the first round often isn’t a screen

Reports from several Indian product companies open with a machine-coding round or a third-party screen instead of the classic call with an engineer. The SDE 2 interviews page covers how machine-coding rounds run.

How far the screen’s result travels

At most companies the screen is a gate to the onsite. At a few, the same result also sets your level, or stays in the file for the final decision.

  1. 1Technical screen
  2. 2Onsite loop
  3. 3Hiring decision
  • Gate

    Its job ends at the screen: pass and you’re invited to the onsite, fail and the process stops.

  • Sets your level

    Some guides and candidates say the result can also change the level you interview at. The evidence is thin.

  • Counts in the packet

    The screen’s feedback stays in the file the final decision is made on.

    • Google, 2025 pilot. A recruiter told one candidate that screen feedback counts in the final evaluation, and a Google employee in the thread called it a pilot. An EU candidate interviewed in August 2025 saw no change. Blind, 2025 (opens in a new tab)
    • Google, 2026. A 2026 post says the ratings from both screens, coding and Googleyness, go into the packet. One candidate with borderline Googleyness feedback was still sent to the onsite. LinkedIn, 2026 (opens in a new tab); Reddit, 2026 (opens in a new tab)
The onsite bar is higher
Meta says onsite coding is harder, with a more exacting evaluation. A 2026 E6 prep guide says the problems stay around LeetCode medium, but the bar for polish rises. Meta Careers, 2022 (opens in a new tab); Hello Interview, 2026 (opens in a new tab)
Google’s onsite under the pilot
One candidate’s recruiter described 2 coding rounds plus 1 Googleyness round, down from 3 coding plus 1 Googleyness. Blind, 2025 (opens in a new tab)

Where candidates slip on the technical screen

From interviewers, company guides and candidate reports.

FAQ

Questions, answered

Contact us
  • The recruiter screen is a 15–30 minute call about your background, why you want the role, and logistics: pay range, notice period, location and work authorisation. The technical screen comes next, usually 45–60 minutes of live coding with an engineer, with behavioural or design questions at some companies and levels.

Sources

Last reviewed . Candidate reports are paraphrased, and formats vary by team, location and year.

  1. Preparing for your software engineering interview at MetaMeta Careers, 2022 (opens in a new tab)
  2. Preparing for your technical screenMeta Careers (opens in a new tab)
  3. How we hire: the interview processGoogle Careers (opens in a new tab)
  4. SDE III and senior SDE interview prepAmazon Jobs (opens in a new tab)
  5. Engineering team screen: candidate guide (PDF, hosted by a third party)Stripe (opens in a new tab)
  6. The recruiter phone screen: what the first call checksFinalCV (opens in a new tab)
  7. How to prepare for a recruiter phone screenArgo Apply (opens in a new tab)
  8. Not passing the initial screen? (r/cscareerquestions)Reddit, 2025 (opens in a new tab)
  9. Rejected by seven companies after the recruiter screen (r/cscareerquestions)Reddit, 2025 (opens in a new tab)
  10. Meta software engineer interview experience (US, January 2025)Taro, 2025 (opens in a new tab)
  11. Meta E6 (staff) software engineer interview guideHello Interview, 2026 (opens in a new tab)
  12. Meta MLE interview preparation guide, with screen formats by levelPersonal blog, 2024 (opens in a new tab)
  13. Meta software engineer screening interview (US)interviewexperiences.in, 2025 (opens in a new tab)
  14. Meta E4 software engineering experience, passed the full loop (r/leetcode)Reddit, 2025 (opens in a new tab)
  15. Google interview experience for software engineer (SDE-2) 2025GeeksforGeeks, 2025 (opens in a new tab)
  16. Has Google’s interview process changed?Blind, 2025 (opens in a new tab)
  17. 2026 updates to Google’s SWE phone interviewLinkedIn, 2026 (opens in a new tab)
  18. A borderline Googleyness phone screen, and still an offer? (r/leetcode)Reddit, 2026 (opens in a new tab)
  19. Amazon SDE-2 phone screen experienceinterviewexperiences.in, 2025 (opens in a new tab)
  20. Amazon SDE 2 phone screen (r/leetcode)Reddit, 2025 (opens in a new tab)
  21. Amazon graduate SDE phone interview (r/leetcode)Reddit, 2025 (opens in a new tab)
  22. AWS phone interview, SDE 2, Dublin (r/leetcode)Reddit, 2025 (opens in a new tab)
  23. Microsoft software engineer interview experience (Redmond, 2025)Taro, 2025 (opens in a new tab)
  24. Microsoft SDE-1 phone screen (US)interviewexperiences.in, 2025 (opens in a new tab)
  25. Uber SDE2 business phone screen: an hour of coding plus design and architecture (r/leetcode)Reddit, 2026 (opens in a new tab)
  26. Uber SDE-2 interview experience (business phone screen)interviewexperiences.in, 2026 (opens in a new tab)
  27. Uber SDE 2 phone screen experienceinterviewexperiences.in, 2025 (opens in a new tab)
  28. Stripe software engineer interview: a three-part Python screencswork, 2025 (opens in a new tab)
  29. Atlassian Karat screening, P40 (April 2025)interviewexperiences.in, 2025 (opens in a new tab)
  30. Atlassian P40 SDE interview experienceinterviewexperiences.in, 2025 (opens in a new tab)
  31. Atlassian interview experience for SDE 3, P50 backend roleGeeksforGeeks, 2024 (opens in a new tab)
  32. Atlassian Karat round (r/leetcode)Reddit, 2025 (opens in a new tab)
  33. Flipkart SDE-2 machine coding: library management systeminterviewexperiences.in, 2025 (opens in a new tab)
  34. Flipkart SDE-2 interview experienceRoundz, 2025 (opens in a new tab)
  35. CRED SDE2 (rejected)LeetCode Discuss, 2025 (opens in a new tab)
  36. SDE-2 interview experience at CRED (rejected), December 2025interviewexperiences.in, 2025 (opens in a new tab)
  37. Swiggy SDE4 (L9) interview experienceRoundz, 2025 (opens in a new tab)
  38. Five common problem areas from 600 technical interviewsinterviewing.io (opens in a new tab)
  39. Completed Meta’s E6 loop: thoughts afterwards (r/leetcode)Reddit, 2024 (opens in a new tab)
  40. Atlassian P60, September 2025 (rejected)LeetCode Discuss, 2025 (opens in a new tab)
  41. Guidelines for virtual interviews at Google (candidate guide)Google (opens in a new tab)
  42. Hiring process FAQMeta Careers (opens in a new tab)
  43. Remote interviewAmazon Jobs (opens in a new tab)
  44. Amazon’s guidelines on AI use in job interviews (press report)Business Insider, 2025 (opens in a new tab)
  45. How we hire (Candidate Code of Conduct)Microsoft Careers (opens in a new tab)

Two calls, one onsite invite

Your first 30 minutes are free. After that it’s $5 an hour, pay as you go, with no subscription.

Start free — 30 minutes, no card
No credit card 30 minutes free Encrypted