Academic snapshot
Marks: 65% throughout common; cells may want 8.0+
Degree: B.E. / B.Tech / M.Tech / MCA
Backlogs: None active at apply
Year: Final-year; some recent grads off-campus
D. E. Shaw is a global investment and technology firm known for quantitative research, software engineering, and systematic trading. In India, its Hyderabad technology teams build the platforms and research systems that power the firm’s trading and analytics operations.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | 60-min test then two technicals + HR in 1-2 days | Difficulty |
| Off-campus careers | Resume + possible phone/video screen | Same technical bar |
| Referral | Higher visibility | Hidden tests and whiteboards remain |
| Internship conversion | Already inside | Still not a formality |
Off-campus is not easier coding. FACE Prep notes that large walk-in style drives are less common than at mass hirers. deshaw.com/careers (filter Hyderabad) is the standing door.
Is 8.0 CGPA required? Campus cells often behave as if yes. FACE Prep’s 2026 table prints 65% throughout (10th, 12th, and graduation individually), no active backlogs, streams CSE/IT/ECE/EEE/MCA/M.Tech. A 7.8 with 66% boards who never coded DP will not be saved by a cell exception. An 8.4 who cannot justify O(n log n) dies in Tech I.
Use both numbers: meet the PDF/mailer, then assume the room wants more.
Backlogs: none at application on most drives. “I will clear it next month” is a common reject.
What helps the screen: contest IDs you can defend, one systems or research-y project, math coursework if SDA. Five hackathon stickers you cannot explain are noise. See certifications after fundamentals.
Academic snapshot
Marks: 65% throughout common; cells may want 8.0+
Degree: B.E. / B.Tech / M.Tech / MCA
Backlogs: None active at apply
Year: Final-year; some recent grads off-campus
Skills they actually filter
Primary: Hard DSA + timed quant
Languages: C++, Python, Java
Exam filter: D. E. Shaw Online Test
Differentiator: Justify complexity, then relocate
Good fit: You enjoy hard problems without a leaderboard addiction only, you can write code by hand, you like math enough to not panic at a puzzle, and you will live in Hyderabad. You can explain why an investment-tech firm is interesting without faking “I always wanted to trade.”
Harder path: You only grind TCS-style aptitude; you need an IDE to reverse a list; you refuse Hyderabad; you answer Why D. E. Shaw with “highest CTC.”
This is proprietary systems and research infrastructure, closer to a quant fund’s engineering than to Infosys staffing. That is the point. If you wanted a consumer app with your name on the icon, say so somewhere else.
CGPA chances (campus cell view):
| CGPA / marks | Selection chances | Notes |
|---|---|---|
| Below 65% stage-wise | Form risk | FACE Prep line |
| 65-75% / below 8.0 | Cell-dependent | OA still brutal |
| 8.0-8.9 | Common shortlist band | Tech I decides |
| 9.0+ | Helps the filter | Does not write your DP |
Download 2026 D. E. Shaw placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
There is no public official archive of live papers. Sets on this site train the 60-minute mixed clock, 0.25 skip rules, and whiteboard DSA.
| Round (typical) | What to practice |
|---|---|
| OA quant / verbal / reasoning | Speed + skip under negative marks |
| OA technical MCQs | C/C++, OS, networks, complexity |
| OA coding | 1-2 DP / graph-style problems |
| Tech I | Lists, trees, graphs, sorting, complexity |
| Tech II | Harder DSA, projects, junior design |
| HR | Why this firm, Hyderabad |
| Theme | What to drill next | Why they ask it |
|---|---|---|
| Interval / subsequence DP | LCS, LIS, matrix chain | OA coding |
| Graphs | BFS, DFS, shortest paths | Tech I-II |
| Linked lists | Reverse, cycle, merge | Tech I |
| Quant 2-step | Time-work, P&C, probability | OA |
| OS MCQ | Scheduling, memory | OA + Tech |
| Puzzles | Logical elimination | OA + SDA |
| Project failure modes | Throughput, correctness | Tech II |
Two days: 60-minute mixed OA.
Two days: paper-coded DSA (one DP, one graph).
One day: OS + C++ MCQ.
Weekend: 2024, 2025, or 2026 plus a mock Tech I with a friend.
If the PPT said SDA, add probability sets. If it said SDE, do not skip OS.
Campus hiring is a compressed four-round day. Off-campus adds waiting.
Campus recruitment
Selective college list (IITs, BITS, NITs, some Tier-2). Same 65% line on FACE Prep notes across campuses.
Careers / off-campus
deshaw.com/careers, Hyderabad filter. Resume must show DSA and projects, not only CGPA.
Referrals
Better than cold apply. You still sit the test.
Eligibility screen
65% stage-wise, no backlogs, stream. Cell may add 8.0. This is a gate. The OA is the first hard filter.
D. E. Shaw Online Test (~60 min on FACE Prep 2026)
| Family | What it rewards | Fail mode |
|---|---|---|
| Quant | Two-step arithmetic, P&C | One-formula muscle memory |
| Verbal | Short RC, elimination | Vocabulary cramming only |
| Reasoning | Puzzles, syllogism | Pride on one item |
| Technical MCQs | C/C++, OS, networks, Big-O | Only LeetCode, no textbook |
| Coding | DP / recursion+memo | Syntax without logic |
0.25 negative. Skip. Mark. Return. Empty coding IDE from chasing a perfect MCQ score is a common fail.
Time boxing: glance at coding constraints in minute one so you know if n is 1e5. Sweep sure MCQs. Leave 20-25 minutes for code. Submit compiling logic, not a blank.
Other published families (longer quant + separate 2-3 coding) need a different clock. Read the mail.
Technical Interview I (30-60 min)
Implement, do not narrate only. Lists, trees, graphs, sorts, hashing, heaps. Complexity is a required sentence. Paper or shared editor.
Technical Interview II (30-60 min)
Harder DSA, sometimes junior design (“high-throughput events,” failure modes), project viva. SDA: probability, stats, teasers. Panels can include the team you would join.
HR (20-40 min)
Why this firm vs Google vs a bank, Hyderabad, timeline, how you handle not knowing. Compensation talk may happen here. It is a real round.
| Phase | Duration | What happens |
|---|---|---|
| Campus PPT / test | Drive day | Mixed OA |
| Tech I + II + HR | Same day or next | Compressed |
| Off-campus screen | Days to weeks | Resume / video |
| Offer | Days after loop | Letter + Hyderabad |
Total: campus often 1-2 weeks including results. Off-campus 2-6 weeks if you even get the first screen. Do not calendar a same-day offer as a promise, even though some loops are that fast.
If you only remember three numbers: 0.25 negative, two technicals, ₹30-50 LPA chatter.
Longest increasing subsequence or a matrix-chain cousin: naive recursion passes the sample, memoised DP is the actual answer, and you should say O(n²) vs better if you know it. Students who write a 40-line wrong recursion and never test n=1 waste the coding section.
Minute 0-2: open coding, read constraints, write function signature and a 3-line brute you might not use.
Minute 2-18: quant + reasoning items you can finish in under 90 seconds. Skip any puzzle that needs a grid you have not seen.
Minute 18-28: verbal RC if the passage is short; else sentence completion.
Minute 28-38: technical MCQs (Big-O, pointer output, page fault).
Minute 38-58: coding. Memo table, base cases, one extra test.
Minute 58-60: submit. Do not reopen a 0.25 trap.
If your invite is the longer PapersAdda-style family (hard quant 90-120 minutes plus a separate coding paper), split days: one mock is only quant, the next day is only 2-3 coding problems. Mixing those clocks in one sitting trains the wrong sport.
A usable sentence has three parts: (1) what the loop does to each element, (2) what extra structure costs, (3) the product. Example: “Each index is pushed and popped at most once on the stack, so the next-greater pass is O(n) time and O(n) extra memory in the worst case.” Saying “it is O(n) because stacks are fast” is how follow-ups start.
If you change the algorithm after a hint, restate the new bound. Interviewers at this firm notice when the story and the code disagree.
Pick one project and answer, out loud, without slides:
That list is closer to D. E. Shaw Tech II than a memorised URL-shortener template. Quant/SDA candidates should add: what distribution did you assume, and what if the tail is fatter?
Four guesses at 25% confidence: expected value is ugly once 0.25 is in play. Two sure MCQs beat five coin-flips. Students who “attempt 90% because that is what IBPS PO taught them” import the wrong exam into this hall. IBPS and D. E. Shaw share a 0.25 number and almost nothing else.
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.
If a D. E. Shaw invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for D. E. Shaw sits around ₹30-50 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): FACE Prep-style campus notes: CSE, IT, ECE, EEE, MCA, M.Tech; about 65% throughout 10th, 12th, and graduation individually; no active backlogs at application. Many campus cells still pre-filter near 8.0 CGPA. Skills in hard DSA, math, and puzzles matter after the academic gate. Always verify the college mailer or deshaw.com/careers.
What you are training for: Typical campus loop: 1. Eligibility screen, 2. Online test (~60 minutes: aptitude, verbal, reasoning, technical MCQs, coding; 0.25 negative on MCQs), 3. Technical Interview I (DSA, CS fundamentals), 4. Technical Interview II (harder DSA, projects, design thinking), 5. HR (Why tech at an investment firm, Hyderabad). Often finished in one or two campus days. Off-campus: careers plus possible referral and a video screen.
Short version of the prep split: Split time about 40% medium-hard DSA (DP, graphs, trees) you can code on paper, 20% timed quant/reasoning with negative marking, 20% CS MCQ (C/C++, OS, networks), 15% puzzles/probability if SDA, 10% HR and Hyderabad. Languages: C++, Python, Java. Weekly full mocks on this site.
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the D. E. Shaw previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most D. E. Shaw drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at D. E. Shaw usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why D. E. Shaw?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a D. E. Shaw-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the D. E. Shaw story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed D. E. Shaw papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many D. E. Shaw papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in D. E. Shaw-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Figures are candidate-reported as of August 2026. Private firm, wide band.
| Role band | Typical CTC (reported) | Notes |
|---|---|---|
| India software / systems fresher | ₹30-50 LPA | Hyderabad-centred |
| Public guide cluster | ₹25-50 LPA | SDE vs more quant-leaning |
| Internship | Stipend, not CTC | 8-12 week programs exist |
Confirm base, bonus, and any joining components on the letter. Do not annualise intern pay. Hyderabad in-hand vs a Bengaluru product offer is a rent conversation, not a slide.
How to read ₹30-50 LPA: the floor is not every intern conversion; the ceiling is not a Twitter screenshot. Ask for the split.
Growth: engineer → senior on work quality. If you want a 400-person academy, this is the wrong firm.
Proctoring platforms change. Practise on paper and in a plain editor. A new C++ version is not a reason to rewrite algorithms in the hall.
Keep graphs and DP. Add negative-marking aptitude and OS MCQs. Cut 45-minute system-design theatre aimed at L5. Tech II’s design ask is junior: throughput, failure, a component, not a URL shortener for the planet.
Campus labs and HackerRank-style hosts. Off-campus links can take time. Keep marksheets ready (10th, 12th, grad). Referral mails should not be your only plan.
Software, systems, analyst/quant, intern flavours. The PPT is the syllabus.
Campus: eligibility → ~60-min mixed OA → Tech I → Tech II → HR, often in one or two days. Off-campus adds resume/video screening. Quant tracks change Tech II, not the existence of two technicals.
Four on 2026 FACE Prep notes. Some loops add managerial. The PPT wins.
Yes. Free D. E. Shaw placement papers PDF and 2024-2026 style practice are on this site. Start with the 2026 PDF or the archive.
Yes, 0.25 per wrong MCQ on standard notes. Skipping is cheaper than a coin-flip. Coding is about logic.
SDE: DSA and systems. SDA/quant: probability, stats, puzzles, math. Confirm the role name.
About 65% throughout 10th, 12th, graduation; listed engineering/MCA streams; no active backlogs. Cells may want 8.0+. Verify the notice.
Candidate-reported ₹30-50 LPA (August 2026). Some guides say ₹25-50. Written offer wins.
Usually yes for India tech. HR will ask. Be honest.
About 40% hard DSA on paper, 20% timed aptitude with negative marks, 20% CS MCQ, rest puzzles/HR. Details: preparation guide.
C++, Python, Java. MCQs still like C/C++ and OS.
Shared high bar. Different OA shapes and Why stories. Arcesium is a spin-out, not the same recruiter. Write three Whys.
Skip MCQs for 0.25 reasons. Then write working DP and list code on a board with complexity. Rehearse Why Hyderabad.
Selective drives include some Tier-2 campuses on FACE Prep notes, still Hyderabad-centred. Off-campus careers stays open. The test does not get easier.
No. Location and “why an investment-tech firm” are real. Treat it as round four.
Recurring public colour: one or two DP problems (subsequence, memoised recursion, matrix-chain cousins). Graphs still matter for interviews.
Yes, via deshaw.com/careers. Referrals help screens. Keep transcripts ready.
Both. OA may be an editor; Tech I often wants working code you can write without autocomplete. Twenty minutes of paper lists a day is not optional if your only muscle is Copilot.
Campus visits concentrate on strong colleges, including some Tier-2 on FACE Prep notes. Off-campus careers is still a door. The OA and technicals do not get a handicap because of the college name on the form.
Online test in the morning, two technicals, HR before you have processed the DP. Takeaway: stamina and skip rules. Do not schedule a night-before new course.
Careers apply, wait, possible video screen, then a similar technical ladder. Referrals move the resume. Takeaway: the bar does not drop because you applied from home.
Second technical leans math. Students who only prepared graphs feel ambushed. Takeaway: read the role name twice.
Clocks and themes, not a leaked LCS prompt. The invite wins.
Days 1-3: 60-min mixed mocks with 0.25 scoring.
Days 4-6: paper DP + graph daily.
Days 7-8: OS/C++ MCQ + project script.
Day 9: mock Tech I + HR.
Day 10: sleep.
Not “highest package.” True: you like hard correctness, internal systems, sitting next to research, Hyderabad is acceptable. If you also sit Google, say why this room is different.
Rank before HR. Hyderabad is the default India story. If you will only join Bengaluru, say it early.
More: interview experience.
20 minutes a day without an IDE. Indent. Compile in your head. This is the Tech I sport.
All four are selective finance-tech-adjacent. D. E. Shaw’s public fresher colour is the short mixed OA + two technicals + Hyderabad. Shared DSA morning, different Why. Do not tell Arcesium you “already know D. E.” Shaw so it is the same.”
09:00 60-min OA.
11:00 review guesses.
16:00 45-min Tech I.
17:00 HR (Why, city).
Night: sleep.
Weeks 1-2: DP and lists on paper, 20-min quant. Week 3: first 60-min mock, too many 0.25 hits. Week 4: skip rules. Week 5: mock technical with a friend who asks complexity. Week 6: campus test, coding submitted with 8 minutes left, Tech I on a list, HR on Hyderabad already decided. No paid “quant personality” course required.
Screenshot apply. Check spam. Do not start WSL after the link arrives. Recode your OA the same night; Tech I can be soon.
If you also sit Goldman the same month, keep shared DSA and write two Whys. More: interview experience.
Only if the slide said analyst/quant. Otherwise skim and return to DP.
Interviewers in this track punish memorised CAT tricks that you cannot derive. If you cannot finish the table, say what you would compute next. Silence is worse.
You do not need a distributed-systems course. You need to sound like someone who has read one OS chapter and written one slow program.
Public notes describe 8-12 week India internships in technology and neighbouring functions, still with a serious screen. An intern summer does not skip Tech I. It may add “what did you ship” to Tech II. Convert the internship into two numbers and one mistake, not a slide of logos. If you did not intern here, do not fake proximity to the firm.
Cold careers PDFs die on generic “proficient in C++ and teamwork.” Referral mails die on the same resume if the human cannot find a hook in 20 seconds.
Samsung SWC is often one hard problem, three hours, all tests. D. E. Shaw OA is often one short mixed hour then talking technicals. Nagarro is finish 2/2 or 3/5 coding for a services-product engineering bar. Shared DSA practice is fine in the morning. The afternoon mock must match the clock you will actually sit. Students who only have 3-hour SWC stamina sometimes under-attempt the 60-minute D. E. Shaw paper, and students who only have Nagarro 90-minute pairs sometimes never hand-write a DP recurrence. Train the invite you have.
No new DP pattern. Re-read your project README. Write the Why paragraph once. Sleep. Print or screenshot the test instructions if the TPO sent any (calculator, languages, negative mark). Eat. The compressed four-round day punishes heroes who “one more LeetCode hard at 2 a.m.”
Weeks 1-4: paper lists/trees + 20-minute quant, three days a week.
Weeks 5-8: DP family + weekly 60-minute mixed mock with 0.25 scoring.
Weeks 9-10: OS/C++ MCQ + project failure-mode script.
Weeks 11-12: two full campus-day simulations (OA morning, Tech I afternoon).
If your college is not on the visit list, add careers applications and one referral conversation in week 8. Do not wait for a PPT that may never come.
Goldman Sachs · Bloomberg · Arcesium · BlackRock · Morgan Stanley