Academic snapshot
Marks: 7.0+ CGPA / 70% when printed (candidate-reported)
Degree: B.Tech / B.E. / M.Tech / MCA
Backlogs: None active
Year: Final-year and recent grads (about 1 year)
Twitter (X) Placement Papers 2026
Twitter (now X) is a real-time social platform (founded 2006) known for large-scale feeds, fan-out, and distributed systems. HQ sits with X Corp. in the US. India engineering hiring exists but is limited and irregular compared with Google or Meta campus seasons.
HQ: San Francisco, USA (X Corp.)
Brand: X (formerly Twitter)
Status: Private (headcount/revenue not disclosed like a public company)
Website: x.com ↗
Explore: Online Assessment · Coding Questions · Interview Experience · Preparation Guide · Certifications & Career · Download PDF
Who can apply to Twitter (X) in 2026?
Section titled “Who can apply to Twitter (X) in 2026?”Who this hub is for
Section titled “Who this hub is for”- For: Students targeting Software Engineer (and adjacent data/product-engineering) roles on real-time systems: feeds, ranking, delivery, ads infra. India loops, when they exist, are usually off-campus.
- Not the same track: Pure sales, support-only, or content-moderation ops. Those bars do not map to this OA → DSA → design loop.
- Experienced hires: Mid-level loops add deeper distributed-systems design or a hiring-manager round and different CTC. Use fresher sections as a base.
On-campus vs off-campus
Section titled “On-campus vs off-campus”| Route | What usually changes | What stays the same |
|---|---|---|
| Campus (rare in India) | Batch OA window, college CGPA list when printed | Coding bar, interview depth |
| X Careers / LinkedIn | Resume screen volume; sometimes no hard published CGPA | Still expect OA + two tech rounds |
| Referral | Better visibility | You still need passing OA code |
| Intern → full-time | Conversion interviews may skip a stage | You still defend projects and code |
Off-campus does not mean easier coding. It often means more applicants fighting the same 60-90 minute filter. If your CGPA sits near 7.0, spend energy on mocks, not on hunting a mythical lower cutoff blog post.
Degree, projects, and “is 7.0 enough?”
Section titled “Degree, projects, and “is 7.0 enough?””Is 7.0 CGPA enough? It matches the commonly reported floor when a JD prints one. Selection still hinges on OA correctness and interview narration. A 7.1 with clean timed coding beats a 9.0 that freezes on edge cases. Twitter/X often has no universal public cutoff. Top colleges may enforce their own.
Branches: CS/IT/ECE/EE dominate shortlists. Related streams show up when DSA is solid.
Gaps and backlogs: Active backlogs are a hard blocker on most fresher posts. Recent grads within about 1 year are the usual window. Lying about CGPA is an integrity fail in HR.
What helps the resume screen: One project you can defend end-to-end, contest or open-source signal when real, any internship with ownership language. Certificates are optional. See certifications only after fundamentals are solid.
Branch & skills
Preferred: CS / IT / ECE / EE and related
Languages: Python, Java, C++, C
Focus: DSA, distributed systems lite, real-time product sense
Differentiator: Feed / fan-out / rate-limiter sketches
Detailed eligibility criteria breakdown
Section titled “Detailed eligibility criteria breakdown”| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.0+ / ~70% when the JD lists it | Not always printed off-campus |
| Degree | B.Tech / B.E. / M.Tech / MCA | Related computing degrees on many posts |
| Branch | CS, IT, ECE, EE | Strong DSA can help adjacent branches |
| Year | Final year + recent grads (~1 year) | Intern conversion paths also appear |
| Backlogs | No active backlogs | Clear them before paperwork |
| Coding languages | Python, Java, C++, C | Stick to one for OA + interviews |
Twitter (X) CGPA criteria
Section titled “Twitter (X) CGPA criteria”The minimum CGPA required when printed is commonly 7.0+ CGPA / 70%. Treat it as a shortlisting filter, not the hard bar. Coding speed decides whether you see an interviewer.
| Academic Level | Minimum (typical) | Notes |
|---|---|---|
| 10th | 7.0+ / 70% when listed | Consistency across years |
| 12th | 7.0+ / 70% when listed | Diploma holders evaluated similarly |
| Graduation | 7.0+ / 70% | No active backlogs at hiring |
| Backlogs | None active | Cleared backlogs generally accepted |
Twitter placement papers - last few years
Section titled “Twitter placement papers - last few years”Download 2026 Twitter (X) placement papers
2026 pattern in detail
2025 placement papers
2024 placement papers
Previous year question papers
Twitter/X does not publish one permanent official paper set. “Previous year papers” on placementpapers.app are pattern trainers for the first filter and early technical rounds, not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Online coding | Timed accuracy: 3-4 medium-hard DSA in 60-90 min |
| Technical 1 | Live coding narration: brute force → optimize → edge cases |
| Technical 2 | Harder DSA plus feed / cache / rate-limiter lite |
| Managerial | Project ownership, design thinking, teamwork |
| HR | Why X, location/remote, integrity, CTC band |
Themes that keep repeating (2024-2026)
Section titled “Themes that keep repeating (2024-2026)”- 2024 cycles: Medium-hard OA with arrays, strings, trees, graphs, DP. Students who skipped timeboxes left an easy problem incomplete while chasing a hard graph.
- 2025 loops: Write-ups still describe coding-heavy OAs on HackerRank / Codility / Mettl, then DSA + project deep-dives. Domain chat around timeline fan-out, rate limiting, and caching shows up after you clear the code bar.
- 2026 prep expectation: Keep medium-hard DSA warm. Expect design rounds to stay fresher-depth (actors, APIs, bottlenecks), not staff-level distributed systems. Treat PDF packs as pattern catalogs. Own the sliding-window and graph BFS templates, not a memorised “Twitter tagged” story.
Public write-ups on X India’s exact OA blueprint are thinner than for Google or Meta. That is why this hub stresses pattern trainers and “verify your invite.” When in doubt, practice three mediums under 75 minutes and keep a feed sketch ready.
How to use one paper set in a single sitting
Section titled “How to use one paper set in a single sitting”- Timed: run a full 60-90 minute mock (3-4 coding prompts) in the language you will use on test day.
- Untimed review: rewrite the cleaner solution; list three edge cases you missed.
- Map each miss to a theme (window / hash / tree / graph / DP) and pull two cousins from coding questions.
- Spend 15 minutes explaining a home timeline or rate limiter out loud like a teammate.
- Log one STAR story the session reminded you of (unclear requirements, a production bug, a PR conflict).
Related problems to practice
Section titled “Related problems to practice”| Theme you saw in a set | What to drill next | Why Twitter asks it |
|---|---|---|
| Sliding window / unique chars | Variable window, at-most-K | Text / search / filter UX |
| Graph BFS / DFS | Connected components, shortest path | Follow graphs, delivery paths |
| Hash map counting | Frequency, two-sum family | Fast lookups in feeds |
| Heap / top-K | Merge K lists, trending | Ranking / trending topics intuition |
| Rate limiter lite | Token bucket in plain words | API abuse, fairness |
Twitter hiring rounds in 2026
Section titled “Twitter hiring rounds in 2026”Twitter/X hires freshers mainly through the careers portal, LinkedIn, and referrals. After resume screen, the shape is product-company style: timed coding OA, two technicals, team fit, then HR.
Application methods
Section titled “Application methods”Off-campus / careers
Primary route. Apply on X Careers. Follow the invite for platform and duration.
Campus recruitment
Limited. Some top colleges may still see a drive. Placement cell coordinates the batch OA.
Referrals
Employee referrals improve visibility. You still need passing OA code and clear interviews.
1. Resume / eligibility screen
Section titled “1. Resume / eligibility screen”Recruiter checks degree, CGPA floor when printed (7.0+ / 70% commonly reported), backlogs, and year of passing. Projects, open-source, and internships help when volumes are high. This is a gate, not the hard filter. Coding is.
2. Online coding (60-90 min)
Section titled “2. Online coding (60-90 min)”Candidate reports commonly describe a 60-90 minute assessment with 3-4 coding problems. Some invites add short CS MCQs. Platforms: HackerRank, Codility, or Mettl. Confirm yours.
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Coding | 3-4 problems | Full window | Arrays, strings, trees, graphs, DP |
| CS MCQs | 5-10 when present | Short block | OOP, DBMS, OS |
Languages: Python, Java, C++, C. Pass bar: fully passing solutions beat a brilliant half-answer. Roughly 15-20% of a large OA batch advancing is a common rumour, not a promise.
Student tip: Spend 4-5 minutes skimming all prompts. Bank the solvable two first. Invent two edge cases before submit.
Example timing for a 75-minute OA
Section titled “Example timing for a 75-minute OA”| Minute | Move |
|---|---|
| 0-5 | Skim all statements; mark easy wins |
| 5-30 | Problem 1: restate → brute → optimize → code → tests |
| 30-55 | Problem 2 the same way |
| 55-70 | Problem 3 (and 4 if present) or harden edge cases |
| 70-75 | Revisit flagged tests |
Deeper OA notes: Twitter online assessment.
3. Technical interview 1 (~45-60 min)
Section titled “3. Technical interview 1 (~45-60 min)”Video or onsite shared editor. Expect 2-3 DSA problems plus a short project warm-up. Patterns: sliding window, hash maps, tree/graph BFS, DP on strings.
You should:
- Clarify constraints (null inputs, duplicates, unicode)
- Narrate brute force → bottleneck → target complexity
- Code in your chosen language without syntax stalls
- Walk edge cases and complexity at the end
Silent staring after a failed mental test case is a common reject signal even when the idea was right.
Example narration (longest substring without repeating characters): “Brute force is check all substrings O(n²). Better: sliding window with last-seen index map, advance left when duplicate appears. Empty string returns 0; single char returns 1.” That 40-second plan already signals interview readiness.
4. Technical interview 2 (~45-60 min)
Section titled “4. Technical interview 2 (~45-60 min)”Harder DSA and/or fresher-depth design. Typical prompts:
- Home timeline: fan-out on write vs fan-out on read
- Rate limiter for posting APIs
- URL shortener with click analytics
- Cache invalidation when a tweet is deleted
Start with users → data → APIs → bottlenecks. Plain language beats “we will use Kafka” with no requirements.
Worked mini-outline - rate limiter:
- Actors: client, API gateway, limiter, tweet service.
- Rule: N posts per user per window.
- Store: counter + expiry (token bucket in words is enough).
- Failure: over limit → 429 with retry-after, no silent drop.
- Scale later: only after the above is clear.
5. Managerial / team fit (~45 min)
Section titled “5. Managerial / team fit (~45 min)”Project ownership, how you debug with incomplete specs, collaboration. Some global loops (including X Corp. Japan write-ups) add a technical presentation: pick a system you owned, explain challenges in ~20 minutes, then Q&A. English is often the working language.
6. HR (~30 min)
Section titled “6. HR (~30 min)”Why X (not “cool brand” only), location or remote constraints, notice period / exams, teamwork STAR stories. Know the ₹35-45 LPA fresher band so CTC talk is grounded.
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA (coding) | 60-90 min | Timed accuracy |
| 2 | Technical 1 | ~45-60 min | Code + narration |
| 3 | Technical 2 | ~45-60 min | Harder DSA / design lite |
| 4 | Managerial | ~45 min | Ownership, fit |
| 5 | HR | ~30 min | Logistics, integrity |
Timeline from application to offer
Section titled “Timeline from application to offer”| Phase | Typical duration | Notes |
|---|---|---|
| Apply / resume screen | 1-2 weeks common | Off-campus can sit longer |
| OA completion → shortlist | Days to a week | Some packets wait ~1 month |
| Interview loop | ~1-2 weeks | Tech 1 → Tech 2 → Managerial → HR |
| Offer / paperwork | Days after final round | Written offer wins over verbal |
| End to end | ~3-4 weeks often | Can stretch off-campus |
How Twitter differs from a generic SaaS interview
Section titled “How Twitter differs from a generic SaaS interview”- Real-time feed / fan-out / rate-limit vocabulary shows up more than retail or payments metaphors.
- Communication is graded: think out loud, ask clarifying questions.
- India campus volume is thin. Do not treat this hub as a guaranteed August drive.
- English-heavy loops appear in global teams.
Weekend mock that matches a real loop
Section titled “Weekend mock that matches a real loop”Saturday 10:00: 75-minute OA (three mediums, two must fully pass).
Saturday 12:00: review misses into an error log (window vs graph vs DP).
Saturday 16:00: 90-second feed sketch + 90-second rate limiter, spoken, no notes.
Sunday 11:00: 45-minute live coding with a friend or a timer and a shared doc.
Sunday 12:00: Why X + one STAR + location answer, recorded once.
Two weekends of that beat twelve nights of random “Twitter tagged” lists. If no opening is live, keep the same mock and run a Google or Meta loop in parallel. Do not freeze your calendar on a brand that is not hiring this month.
Documents pack
Section titled “Documents pack”Resume one page, 10th/12th/degree scans matching the CGPA story, ID, GitHub or contest links if they are real. Name and percentages must match the form.
Night-before checklist
Section titled “Night-before checklist”- Charger, ID, resume PDF
- One language chosen (Python or Java, not both)
- Two STAR stories and the feed sketch already spoken once today
- Sleep. A 9 a.m. OA after a 3 a.m. mock is how easy array items go wrong
- Confirm the invite timezone if the loop is global / English-only
Where to practise for Twitter (X)
Section titled “Where to practise for Twitter (X)”Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
How students actually prep for Twitter (X)
Section titled “How students actually prep for Twitter (X)”Week-by-week calendars live on the preparation guide. This section is the focus split so you do not study like you are sitting a 90-minute mixed aptitude paper.
Time split that matches the filter
Section titled “Time split that matches the filter”| Bucket | Share | What “done” looks like |
|---|---|---|
| Timed DSA / OA | ~45% | Three mediums in 75 minutes, two fully passing |
| Design lite | ~25% | 90-second feed or rate-limiter sketch |
| CS one-liners | ~10% | OOP, SQL, OS, CN you can say aloud |
| Project + HR | ~20% | 60-second story + Why X + location answer |
If you already clear OA and fail narration, invert 45/20 for two weeks. If you freeze on design, stop hiding in LeetCode hard.
This week, not “someday”
Section titled “This week, not “someday””- One full timed mock from coding questions plus online assessment.
- Two medium problems submitted end-to-end in Python or Java.
- Speak a feed or rate-limiter sketch once without notes.
- Record “Why X” once. Cut fillers. Record again.
- Error log: three DSA misses, one design blank, one STAR story.
What not to waste time on
Section titled “What not to waste time on”- Memorising “Twitter tagged” dumps as if they will reappear
- Starting a second coding language the week of the OA
- Staff-level distributed systems for a fresher cabin
- Ignoring live-opening checks and prepping for a drive that is not posted
- Quoting Meta CTC in HR without reading your own letter
Feed sketch students should rehearse
Section titled “Feed sketch students should rehearse”Home timeline for 1 user:
- Actors: poster, follower, timeline service, cache.
- Write path: store tweet; fan-out to follower inboxes or fan-out on read for celebrity accounts.
- Read path: merge, rank, paginate.
- Failure: cache miss → origin; deleted tweet → tombstone, no ghost card.
- Scale later: only after the above is clear.
That 90-second sketch beats a memorised microservices diagram.
English-ready without over-practising TED talks
Section titled “English-ready without over-practising TED talks”If the loop is global, answers in complete sentences. State diagrams on a shared doc beat a mumbled “then we scale.” You do not need a Japan-style 20-minute presentation for every India invite, but the habit of explaining a system you owned is the same muscle Technical 2 uses.
Offer-stage discipline
Section titled “Offer-stage discipline”- Confirm the entity (X Corp. vs a contractor letter)
- Read location or remote language; do not assume 2020-era WFH
- 10th/12th/degree % must match
- Verbal “we are moving forward” is not an offer PDF
- Keep a Google/Meta/Amazon loop live until the letter arrives. India campus volume is too thin to bet a whole season on one brand.
Last-mile notes for Twitter prep
Section titled “Last-mile notes for Twitter prep”A note on mocks vs. random problem lists
Section titled “A note on mocks vs. random problem lists”Random Twitter problems feel productive. Timed mocks are what move the needle. If you only have an hour tonight, sit 40 minutes of a previous-year Twitter set and spend 20 minutes on the three misses. That loop beats an untimed 8-problem grind you will not remember tomorrow.
How to use this page the night before
Section titled “How to use this page the night before”Do not reread the whole Twitter hub. Skim eligibility once, open your error log, and recast the two STAR stories you will actually say. If the drive names an OA platform, click around it for five minutes so login panic is not your first round.
Twitter fresher CTC in India (2026)
Section titled “Twitter fresher CTC in India (2026)”Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on level, location, hiring year, and written components (base / bonus / equity).
| Track | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Software Engineer Intern | ₹1.0-1.2 lakh/month stipend | Final-year internships |
| Software Engineer (fresher) | ₹35-45 LPA | Primary band for this hub |
| Data / product engineer (entry) | Similar band when posted | Not every year |
| Senior / mid-level (indicative) | ₹50-70 LPA+ | Not the fresher default |
Confirm base, joining bonus, and any equity language on the written offer. Do not treat blog midpoints as guarantees.
Benefits students actually care about
Section titled “Benefits students actually care about”Policies vary by year and entity (X Corp. vs local contract). Candidates commonly care about:
- Health insurance and wellness support
- Equity / RSU language when the letter includes it
- Remote or hybrid norms (ask; do not assume Twitter-era WFH)
- Learning budget after joining (manager-dependent)
How to talk CTC in HR
Section titled “How to talk CTC in HR”Know the ₹35-45 LPA fresher context, ask how the package splits, and clarify joining date vs final exams. One calm clarifying question beats aggressive negotiation with no market anchor.
What’s changed in Twitter hiring lately
Section titled “What’s changed in Twitter hiring lately”Rebrand and thinner campus
X Corp. is private. India campus volume is irregular. Verify live postings before a long prep cycle.
DSA after resume still wins
60-90 minute coding OAs on HackerRank / Codility / Mettl remain the first filter.
Real-time product vocabulary
Feed, fan-out, rate limiter, and cache invalidation show up more than generic SaaS metaphors.
English and ownership
Global loops may run in English and ask you to present a system you owned.
Net for 2026: do not wait for Twitter/X to become a high-volume Indian campus company. If a posting is live, double down on timed DSA and one feed sketch. If it is not live, keep Google/Meta/Amazon loops warm.
Common questions about Twitter hiring
Section titled “Common questions about Twitter hiring”Papers & process
Section titled “Papers & process”Can I download Twitter placement papers PDF for free?
Yes. Free Twitter (X) placement papers PDF and 2024-2026 style DSA practice are on placementpapers.app. Start with the 2026 PDF or the archive.
What is the Twitter placement process for freshers?
Typical path: Online coding (60-90 min) → Technical 1 → Technical 2 → Managerial / team fit → HR. Off-campus is the main India route. Campus batches often finish in about 3-4 weeks when they exist.
How many interview rounds does Twitter usually have?
Most fresher SWE loops report four to five stages (OA + two technicals + managerial + HR). Senior loops may add deeper design. Count the mailer.
What does the Twitter Online Assessment look like?
Often 60-90 minutes with 3-4 medium-hard coding problems. Platforms: HackerRank, Codility, or Mettl. Optional CS MCQs on some invites. Details: online assessment.
Does Twitter still hire freshers on Indian campuses?
Rarely and irregularly after the rebrand. Most students apply off-campus. Confirm a live opening before you treat this as a default Big Tech drive.
Eligibility & offer
Section titled “Eligibility & offer”What eligibility / CGPA do fresher SWE drives usually expect?
Commonly reported floor when printed: 7.0+ CGPA / 70%; CS/IT/ECE/EE-related degrees; final-year or recent grads (~1 year); no active backlogs. Off-campus, coding profile often outweighs the printed number. Your posting overrides this page.
What is Twitter fresher salary in India?
Candidate-reported Software Engineer CTC often lands around ₹35-45 LPA (as of August 2026). Intern stipends around ₹1.0-1.2 lakh/month. The written offer is the only number that matters.
Do I have to relocate?
HR usually checks location or remote constraints. Answer honestly. Do not assume Twitter-era full remote still applies.
Prep & Twitter-specific
Section titled “Prep & Twitter-specific”How should I prepare for Twitter?
Split time roughly 45% DSA, 25% feed/rate-limiter design lite, 20% timed OA, 10% project/HR. Clear timed coding mocks first. Details: preparation guide.
Which programming languages are allowed?
Python, Java, C++, and C are the usual set. Confirm on the invite. Do not switch languages the week of the OA.
What product topics should I revise?
Home timeline / fan-out, rate limiter, URL shortener, cache invalidation at fresher depth: actors, data, bottlenecks, failure modes in plain language.
Twitter vs Google vs Meta for freshers?
All three care about DSA. Twitter/X is smaller, more real-time, and less predictable on Indian campuses. Google/Meta have larger regular loops. Share DSA prep; customise product stories.
Any pro tip that actually changes outcomes?
Confirm a live opening first. Bank two fully passing OA solutions. Rehearse one feed or rate-limiter explanation out loud. Communication is part of the grade.
Where can I read real interview experiences?
Start with Twitter interview experience on placementpapers.app, then cross-check recent community write-ups for your target level.
What certifications help before joining?
For campus/off-campus SWE, DSA + OA mocks + one strong project beat certificate stacks. See certifications.
What recent candidates reported
Section titled “What recent candidates reported”Fresher SWE loops (2024-2025)
Section titled “Fresher SWE loops (2024-2025)”Profile patterns that got selected: B.Tech CSE/IT, roughly 7.0-8.5 CGPA, one internship or a strong project, steady DSA rather than last-week panic.
Online assessment: Timed coding on HackerRank, Codility, or Mettl. Clean, fully passing solutions beat partial cleverness. Students who triaged prompts early kept two or three problems alive.
Technical rounds: Coding such as sliding window, graph BFS, hash-map frequency, DP on strings. Domain chat around feeds and rate limits. Project deep dive: stack choice, hardest bug, what you would rebuild.
Managerial / HR: Why X? Working with unclear requirements? Conflict on a team? Location comfort? Keep answers short: situation → what you did → result.
What hurt other candidates: coding before clarifying constraints; treating HR as a formality; system-design jargon without a simple bottleneck story; optimising one hard OA item while leaving an easy problem incomplete.
Story-shaped notes
Section titled “Story-shaped notes”Story 1 - X Corp. Japan (May 2025 hire, Findy): Applied in December when Japan engineering hiring went public. Weekly applications ran in the hundreds. Packet waited ~one month to interview invite. Beyond a technical phone screen, the standout gate was a technical presentation: pick one system you owned, explain challenges in 20 minutes, then ~10 minutes Q&A. High marks came from giving X engineers new insights. Process was entirely in English, including state diagrams. Source: Findy interview.
Takeaway: ownership stories and English clarity can matter as much as a LeetCode rating. India loops may not copy the presentation round, but the habit of explaining a system you built still helps Technical 2.
Story 2 - Off-campus SDE (composite, India): OA with two fully passing mediums → Tech 1 sliding window with complexity narration → Tech 2 rate-limiter in plain English → HR teamwork STAR. What helped: connecting a college notification project to fan-out without forcing the brand name.
After you clear OA
Section titled “After you clear OA”- Re-solve every miss from your last two mocks cold.
- Speak two STAR stories and one conflict story without notes.
- Sketch a feed and a rate limiter on a blank doc.
- Warm one tree/graph medium in your interview language.
- Sleep. Do not open a new advanced DSA topic.
More fresher narratives: Twitter interview experience.