Interview experience
Twitter (X) Interview Questions
Overview
Section titled “Overview”X’s interview loop is leaner and less standardized post-2022 than old Twitter’s, with heavy emphasis on practical coding and a high-intensity culture check.
X (Twitter) interview process at a glance
Section titled “X (Twitter) interview process at a glance”| Round | Duration | What it tests |
|---|---|---|
| Recruiter screen | 30-45 min | Background, tech stack, and direct fit with X’s high-intensity pace |
| Technical assessment | 60-90 min | Automated coding challenge or longer real-world scenario |
| Technical phone screen | 45-60 min | Live coding with an engineer, often deliberately ambiguous prompts |
| Virtual/onsite - Coding (1-2 rounds) | 45-60 min each | DSA with a practical bent: caches, schedulers, concurrency |
| Virtual/onsite - System design (mid/senior+) | 45-60 min | Feed/timeline, search, or rate-limiting at platform scale |
| Behavioural / hiring manager | 30-45 min | Ownership, speed of execution, fit with a demanding culture |
Recruiter screen and technical assessment
Section titled “Recruiter screen and technical assessment”The recruiter screen (30-45 min) covers background, tech stack, and - candidates report - a fairly direct conversation about whether you’re comfortable with X’s long-hours, high-output culture. Most candidates then get a 60-90 minute automated coding assessment, sometimes stretched into a longer, more open-ended scenario rather than a plain multiple-choice-plus-two-problems test.
Common questions
- Implement an LRU cache
- Build a hit counter / rate limiter
- Task scheduler with a cooldown period
- Array/string problems at medium difficulty
Full round-by-round breakdowns are on the X interview experience page.
Technical phone screen
Section titled “Technical phone screen”A single 45-60 minute live coding round with an engineer. Multiple sources note that interviewers introduce ambiguity into the prompt on purpose - they’re watching how you clarify requirements and communicate your reasoning as much as whether you land the exact right answer.
Common questions
- Sliding-window / two-pointer array problems
- Thread-safe data structure design (concurrency, race conditions)
- Graph traversal (BFS/DFS) variants
- API-design-style prompts drawn from problems the team actually faces
Virtual/onsite: coding rounds
Section titled “Virtual/onsite: coding rounds”One or two further coding rounds in the loop, similar format to the phone screen. Reports consistently describe X moving away from trick-based brain teasers toward problems that mirror real backend/platform work.
Common questions
- Design a data structure supporting insert/delete/getRandom in O(1)
- Detect a cycle in a directed graph
- Concurrent queue or thread-safe counter implementation
- Longest substring / subarray pattern problems
Virtual/onsite: system design (mid-level and up)
Section titled “Virtual/onsite: system design (mid-level and up)”Reported as the most consequential round for mid-level and senior candidates: reasoning about latency, reliability, and scale at very high request volumes, using X’s own product surface as the prompt.
Common questions
- Design the home timeline / feed (fanout-on-write vs fanout-on-read)
- Design real-time tweet search across billions of posts
- Design a notification delivery pipeline (push, in-app, email)
- Design a rate limiter for a public API
Behavioural / hiring manager round
Section titled “Behavioural / hiring manager round”A shorter round (30-45 min) that closes the loop: ownership, how you operate with limited resources, and direct questions about pace and expectations. This is where the post-acquisition culture shift is most explicit in candidate reports - be ready to speak candidly to working at high intensity rather than treating it as a throwaway question.
Common questions
- Tell me about a time you shipped something with incomplete information
- Describe a decision you made under a tight deadline with limited headcount
- How do you handle direct or blunt feedback on your work?
- Why X, specifically now?
Sample answer frameworks for these are on the X HR interview questions page.
The post-acquisition intensity bar
Section titled “The post-acquisition intensity bar”This is the one genuinely distinctive thing about interviewing at X today: the company is dramatically smaller than pre-2022 Twitter (headcount fell an estimated ~80% during the 2022-2023 layoffs, before recovering to roughly 2,800 by end of 2024), and Musk’s initial “extremely hardcore” mandate - long hours at high intensity - has been echoed in multiple 2024-2025 reports about continued long-hours norms and stock/equity tied to performance. The March 2025 all-stock merger with xAI (valuing the combined entity above $100B) folded X’s engineering org further into an AI-first roadmap. Practically, this means interviewers are evaluating pace and resilience as directly as technical skill, and candidates who can’t speak concretely to thriving in a lean, fast-moving team tend to get filtered here rather than in the coding rounds.
Frequently asked questions about X (Twitter) interviews
Section titled “Frequently asked questions about X (Twitter) interviews”What is the X (Twitter) interview process in 2025-2026?
X’s loop is leaner than pre-2022 Twitter and reportedly runs: 1. Recruiter screen (30-45 min) - background, tech stack, and a direct check on fit with X’s long-hours, high-intensity culture. 2. Technical assessment (60-90 min) - an automated coding challenge, sometimes a longer take-home-style scenario. 3. Technical phone screen (45-60 min) - live coding with an engineer, often deliberately ambiguous prompts. 4. Virtual/onsite loop (2-4 rounds) - coding, system design (mid/senior+), and a behavioural round. Public reporting on exact round counts is thin and inconsistent post-acquisition, so treat this as a directional map, not a fixed script.
What questions are asked in X (Twitter) interviews?
Coding rounds lean on practical, job-relevant problems over trick puzzles: LRU cache, hit counter / rate limiter, task scheduler with cooldown, and concurrency-flavoured problems (thread-safe structures, race conditions). System design centers on X’s own domain: home timeline / fanout, real-time search (historically built on Earlybird), notification pipelines, and rate limiting at platform scale. Behavioural questions probe ownership, speed of execution, and comfort with a high-pressure, resource-constrained environment.
How many rounds are there in the X (Twitter) interview?
Most 2025-2026 reports describe 3-6 total touchpoints: a recruiter screen, a technical assessment, a technical phone screen, and a virtual/onsite loop of 2-4 rounds (coding, system design, behavioural). Exact counts vary by team and level, and public data since the 2022 acquisition and 2025 merger with xAI is sparser than for most FAANG peers - confirm your own loop with the recruiter rather than assuming a fixed number.
Does X (Twitter) still hire engineers in India?
Uncertain and much smaller than pre-2022. Twitter’s Bengaluru engineering presence was heavily cut during the 2022-2023 layoffs (headcount fell roughly 80% company-wide). Since the March 2025 xAI-X merger, most reported India engineering hiring (including a Bengaluru office) is under the combined xAI Holdings entity and skews toward AI/ML, infra, and backend roles rather than classic mass campus SDE drives - so don’t assume a traditional India campus-hiring pipeline exists for X specifically.
What is X’s engineering culture like after the Musk acquisition and xAI merger?
Widely and consistently reported as high-intensity: Musk’s late-2022 ‘extremely hardcore’ memo set an expectation of long hours at high output, and multiple 2024-2025 reports describe continued long-hours norms and performance-linked equity. In March 2025 X merged into xAI (all-stock deal, combined entity valued over $100B), pushing engineering priorities further toward AI-integrated product work. Interviewers reportedly screen directly for comfort with this pace during the recruiter screen and behavioural round.
How should I prepare for X (Twitter) interviews?
Drill practical coding patterns (LRU cache, rate limiters, scheduler/cooldown problems) rather than obscure puzzles, be ready to reason about concurrency and thread safety, and prepare one system design narrative around a large-scale feed/timeline or search system since that’s the most consistently reported design topic. For behavioural rounds, prepare concrete examples of moving fast with limited resources and owning outcomes end-to-end - and be candid that you’re aware of, and fine with, X’s demanding pace.