X (Twitter) Frontend Interview
What frontend candidates typically face at X (Twitter) — feed/realtime UI, coding, design, and prep. Composite/unofficial.
- interview-experience
- x
Composite, unofficial guidance based on publicly shared candidate reports and common X (formerly Twitter) hiring patterns for frontend / client roles. The company and process have changed significantly across years — treat older posts carefully and confirm with your recruiter. Not affiliated with X.
Typical loop
| Stage | Focus | Format |
|---|---|---|
| Recruiter | Role, level | Call |
| Technical screen | Coding | Shared editor |
| Onsite / virtual loop | Coding, design, behavioral | Often compressed vs classic Big Tech |
| Decision | Varies | Internal |
Expect feed, realtime, and media-heavy UI themes when the role is consumer client. Process length and rigor vary more than at steadier orgs — verify.
Coding rounds
Medium DSA still commonly reported:
- Arrays, strings, hashes
- Graphs/trees
- Practical JS coding
Practice: Two Sum, LRU Cache, Merge Intervals, Number of Islands, Valid Parentheses.
Frontend focus
- Home timeline virtualization
- Composer + media attach
- Live metrics / streaming updates
- Typeahead for people/hashtags
- Dark mode, density, a11y basics
Practice: Infinite Scroll Feed, Autocomplete, Accessible Modal.
System design
- Home feed (Design a News Feed)
- Post detail + replies thread
- Notifications
- Search typeahead (Design Autocomplete)
Discuss: cursor pagination, “new posts” pill, media CLS, websocket vs polling, mute/block client filtering edges.
Behavioral
Ownership, operating in ambiguity, shipping under changing priorities. Be factual; avoid drama.
Preparation plan (4–8 weeks)
- JS + React perf
- DSA
- Feed machine-coding + design doc
- Mocks
- Logistics / confirm process with recruiter
Takeaways
- Prep like a social feed + realtime company.
- Double-check current loop — historical blogs go stale fast.
- Algorithms remain useful insurance.