Twitter/X Software Engineer Phone Screen Questions
19+ questions from real Twitter/X Software Engineer Phone Screen rounds, reported by candidates who interviewed there.
What does the Twitter/X Phone Screen round test?
The Twitter/X phone screen typically lasts 45-60 minutes and evaluates core Software Engineer fundamentals. Candidates should expect 1-2 algorithmic problems, basic system design discussion at senior levels, and questions about relevant experience. The goal is to confirm technical competence before bringing candidates onsite.
Top Topics in This Round
Twitter/X Software Engineer Phone Screen Questions
Kutumb interview experience
In total, there were 2 rounds of interviews evaluating various skills as mentioned in each round below: \uD83D\uDC49 Round 1 - DSA and LLD (60 minutes): asked 1 DSA question(implement search...
PhonePe | Software Engineer | Dec 2024
Experience: 3+ Years Company: PhonePe Role: Software Engineer (3-5 yoe) Location: Bangalore Applied through referral __ Round 1: Machine Coding | 1.5 hr Activity tag logging system. Functionalities to build: 1. user should be able to add tags to...
AngelOne | SDE 3 | LLD Round
Design a simplified version of Twitter where users can post tweets, follow/unfollow another user, and is able to see the 10 most recent tweets in the user\'s news feed. ...
PhonePe | Software Engineer ( 3-5 YOE) | Reject
Graduation : Tier 1 non-cse Current : 3+ YOE Company: product based TC: ~34LPA Application : Applied via Referral for Bangalore Position. Round 1 Machine Coding Round ( Strong Hire ) The question was...
Twitter | Phone Interview | Backend
Suppose two players A and B play ping pong. The first player to get to 11 points wins the match. The players alternate after every 2nd serve (e.g. player A...
Twitter | Phone screen | k login requests
Got this question in a phone screen. I could only come up with a O(2n) soln. Was my time complexity + soln correct? I didn\'t get any feedback at the...
Twitter | Stage (Phone Screen )
//\xA0Write\xA0a\xA0method\xA0to\xA0find\xA0out\xA0how\xA0much\xA0total\xA0time\xA0was\xA0spent\xA0in\xA0each\xA0space,\xA0 //\xA0over\xA0all\xA0users. //\xA0action,\xA0space,\xA0user,\xA0timestamp static\xA0String\xA0[][]\xA0requests\xA0=\xA0{ \xA0\xA0\xA0\xA0{"create",\xA0"xyz",\xA0"1",\xA0"1619916081"},\xA0//\xA0Sat\xA0May\xA001\xA02021\xA017:41:21\xA0GMT-0700\xA0 \xA0\xA0\xA0\xA0{"join",\xA0"xyz",\xA0"2",\xA0"1619916681"},\xA0//\xA0Sat\xA0May\xA001\xA02021\xA017:51:21\xA0GMT-0700 \xA0\xA0\xA0\xA0{"create",\xA0"abc",\xA0"3",\xA0"1619916881"},\xA0//12:01 \xA0\xA0\xA0\xA0{"leave",\xA0"xyz",\xA0"2",\xA0"1619920281"}, \xA0\xA0\xA0\xA0{"join",\xA0"abc",\xA0"4",\xA0"1619920881"}, \xA0\xA0\xA0\xA0{"create",\xA0"ghi",\xA0"5",\xA0"1619923999"}, \xA0\xA0\xA0\xA0{"leave",\xA0"xyz",\xA0"1",\xA0"1619923881"}, \xA0\xA0\xA0\xA0{"leave",\xA0"abc",\xA0"3",\xA0"1619927481"},\xA0//12:07\xA0time\xA0spent\xA0=\xA06\xA0minutes \xA0\xA0\xA0\xA0{"leave",\xA0"abc",\xA0"4",\xA0"1619927481"}, \xA0\xA0\xA0\xA0{"leave",\xA0"ghi",\xA0"5",\xA0"1619958001"} }; For Userid = 3, total time spent is 12:07 -12:01=6 mins
Twitter Software Engineer Interview Experience
Application Process Applied off-campus on careers page. #### Interview experience Cannot disclose exact questions as signed an NDA. [Telephone screen] This round was data structures and algorithms based....
Twitter Phone interview
Q1) Median from Data Stream - https://leetcode.com/problems/find-median-from-data-stream/ \t Discussed all approaches - Brute Force, Heap, BST with time and space complexity. \t Followup - Stream has trillions of numbers \t (Discussed range...
Twitter Phone interview question
This question was not asked to me but I saw it in a different site. It has been asked sevral times from 2019-2020 in phone interview. We want to measure a...
Twitter | Phone | Task Assignment
Had a Twitter phone interview recently. The question was to implement a simple load balancer. Interviewer said solution should be clean and not to worry about opitmizing. I used java and a...
Twitter Interview | Set 1
Phone screen – I1. Fibonacci series without using an array – this is a typical favorite question w.r.t. Dynamic Programming where you will ask not to use Memoization or an...
Twitter phone screen
Question I was asked was: Given two maps in assertThat(map1, map2), write a function that can help the user with the comparison. The signature they gave was: <K,V> ??? diff (Map<K,V> left,...
Twitter Phone Screen Question
Similar to https://leetcode.com/problems/text-justification/ Implement a method split(example_text, limit); , where it takes 2 params - example_text and a limit, split the text into a list of strings which can contain atmost(nearest...
Twitter | Phone screen | Linear probing hash table
Build a linear probing hash table. Got a rejection for this. This is what I had built and it seemed to work for a fix bucket size. Is there anything...
Input: array of int output: array of int which is a number of continuous increasing count For example input: [100, 10, 50, 60, 20, 90, 110] output: [1, 1, 2, 3, 1, 5,...
Twitter | Phone Screen | RGB Stream
You have a set of users visiting your website. Each user picks a color represented by RGB. R, G, B can take values between 0 and 255. You have a stream...
Twitter | Phone | Tweet Counts
Location: San Francisco Date: Dec 2019 Result: Rejection Given 2 methods and an enum, java public void recordTweet(String tweetName, long time); public long[] getTweetCountsPerFrequency(Frequency freq, String tweetName, long startTime, long endTime); enum Frequency { \tMINUTE, \tHOUR, \tDAY } recordTweet("tweet1", 3498264982l (time in...
Twitter University Recruiting for Software Developer Intern
Current Position: Programmer at Americaneagle.com Location: Des Plaines, Illinois 1st Round - Technical Coding Challenge Duration to Complete - 10080 mins Coding Questions 1. Given an Apache-style web server log, calculate and report the success...
What to Expect in the Twitter/X Phone Screen Round
The Twitter/X Software Engineer Phone Screen round has a specific calibration purpose distinct from other rounds in the loop. Across 19+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Phone Screen round at Twitter/X show recurring patterns in difficulty and topic distribution. The Phone Screen round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Phone Screen Round Timing and Format
The Phone Screen round at Twitter/X typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at Twitter/X Software Engineer Phone Screen commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 19 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access