Twitter/X Software Engineer Interview Questions
52+ questions from real Twitter/X Software Engineer interviews, reported by candidates.
Round Types
Top Topics
Questions
Twitter Phone Interview
Twitter Phone Interview - Duration: 1 hr Platform: Hackerrank - codepair 1. Write a collection of data structure that is fast (should run in o(1) time amortized) for each of the follwoing operation...
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...
Cloudflare interview experience
Status: 4 YOE Position: Software engineer Location: Remote, US Date: July, 2024 TPS: 3 sum extending to 4 sum Coding Round: I was asked to complete the below function for different cases: 1. Global count to check...
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. ...
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...
Round 1: Coding 1 hour in Hackerrank tool https://leetcode.com/problems/design-twitter/description/ **Round 2: High Level Design Round Desing Stock Brokerage Site Users can have multiple watchlist and each watchlist can have multiple stocks in it. Stocks can...
Linked List https://leetcode.com/problems/design-linked-list/ Normal Recursion(Given 1 LL) Simple Recursion Nothing else https://leetcode.com/problems/swapping-nodes-in-a-linked-list/ https://leetcode.com/problems/plus-one-linked-list/ https://leetcode.com/problems/convert-binary-number-in-a-linked-list-to-integer/ Modifying the LL But the number of Nodes will be same Reversing the Linked List https://leetcode.com/problems/reverse-linked-list/ https://leetcode.com/problems/reverse-linked-list-ii/ https://leetcode.com/problems/palindrome-linked-list/ https://leetcode.com/problems/reverse-nodes-in-k-group/ https://leetcode.com/problems/print-immutable-linked-list-in-reverse/ Reordering the Nodes https://leetcode.com/problems/partition-list/ - IMP https://leetcode.com/problems/reorder-list/ https://leetcode.com/problems/swap-nodes-in-pairs/ https://leetcode.com/problems/rotate-list/ https://leetcode.com/problems/odd-even-linked-list/ Delete Nodes https://leetcode.com/problems/remove-nth-node-from-end-of-list/ https://leetcode.com/problems/remove-duplicates-from-sorted-list/ - if asked to...
After solving lot of DSA problems, I\u2019ve noticed some key patterns that are important for coding interviews. At the end of this article, I have also included links to some...
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...
I\u2019ve been in the interview loops with Goldman Sachs since the last week of August. Throughout this time, multiple recruiters have reached out for two different roles. Given that I...
New Relic SSE | Hyderabad
Recently I was interviewed with New Relic for SDE 3, it consists of 4 rounds 1. OA on coderpad \t \t3-4 coding questions \t \t3-4 SQL questions \t* \tbasic JAVA and Kafka multiple choice...
New Relic | SSE P3 | Hyderabad
Current companty: MAANG SDE 2 YOE: 5 Interviews have 4 rounds 1. OA \t Coding questions (2-3) easy \t JAVA questions \t Kafka related questions \t SQL queries: hard 2. DSA round: Convert list into spiral matrix 3. System...
Question 1: Acme RotationsArchaeologists on planet Acme just uncovered an ancient temple! Above. At the entrance, there is an inscription written in lowercase English lett...
Twitter | Online Coding Round | Word Search
YOE: ~6.5 years Location: Bangalore After clearing Telephonic screening round, I had HM call. Post that online coding round was scheduled. I was asked to solve #LC word search. I was able...
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 | Onsite | Bad expressions search
This is roghly the question. You are given a list of "bad expressions" ahead of time. You can preprocess them, or do whatever you need. You are to implement a...
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 | OA | Suggestion engine
Given a list of sentences build a suggestion engine, where if we provide an input word it returns the most frequent next word from the input list. For Example: [["Alice", "jumped", "into",...
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....
What Twitter/X Looks for in Software Engineer Interviews
Twitter/X Software Engineer interviews are calibrated against the level and scope expected of the role. Across 52+ verified candidate reports on LeakCode, the consistent signals interviewers look for: clear problem decomposition before coding, explicit complexity reasoning, structured handling of edge cases, and the ability to articulate trade-offs between two reasonable approaches.
The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the solution. It is the path to the solution: did you ask clarifying questions, did you state your approach before coding, did you handle edge cases without prompting, and did you communicate your reasoning throughout. Reports tagged "no hire" frequently cite a working solution with poor communication; reports tagged "strong hire" cite clear thinking even when the final solution was incomplete.
How To Use This Question Set
Real interview reports are a calibration tool, not a memorization target. Companies update their question pools every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage use: identify the patterns that appear repeatedly in Twitter/X Software Engineer reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.
Filter the questions below by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of Twitter/X's pool. Reports tagged with quantified difficulty (e.g., "medium-hard") are higher-signal than reports without difficulty tags.
Round-by-Round Expectations
Twitter/X Software Engineer loops typically span 4-6 rounds across phone screens and on-site or virtual on-site interviews. The structure varies by company: some run 1 recruiter screen + 1 technical phone + 3-4 on-site rounds; others run 1 recruiter screen + 1 OA + 4-5 on-site rounds. The recruiter screen is logistics and culture-light; the technical phone screen is medium-difficulty coding; the on-site loop covers coding, system design (at L4+ levels), and behavioral rounds.
Each round is designed to surface a specific signal. Coding rounds: correctness, code quality, complexity reasoning, communication. System design rounds: requirements clarification, design judgment, operational thinking. Behavioral rounds: ownership scope, leadership, ambiguity tolerance, conflict navigation. Strong candidates explicitly hit each signal dimension out loud during the round; weak candidates focus only on solving the prompt.
Common Interview Mistakes At This Combination
Reports tagged "no hire" at Twitter/X Software Engineer commonly cite: jumping into code without clarifying requirements, coding silently for 10+ minutes without verbalizing approach, missing edge cases (empty input, single element, very large input, overflow), and producing a working solution that the candidate cannot explain or refactor when probed. Strong candidates avoid these patterns by following a consistent template: clarify, verbalize approach, code with narration, test with examples.
Behavioral and design rounds have their own failure modes. Behavioral: stories that use "we" instead of "I" diluting individual signal, stories with no quantified outcome, defensiveness when probed about failure. Design: not asking clarifying questions, not stating requirements out loud, designing for a single server when the prompt clearly implies scale, ignoring operational concerns (deployment, monitoring, rollback). These show up in roughly half of Twitter/X Software Engineer interview retrospectives on LeakCode.
See All 52 Twitter/X Software Engineer Questions
Full question text, answer context, and frequency data for subscribers.
Get Access