Academic snapshot
Baseline: ~6.5 CGPA / 60% across 10th, 12th, graduation
On-campus SDE JDs: Often 7.0
Average selected: Often 7.5-8.5 (candidate-reported)
Backlogs: None active at selection
Amazon is a global technology leader in e-commerce, cloud computing (AWS), digital streaming, and AI. In India, Amazon is a top recruiter for software engineers, known for its rigorous hiring process. Amazon India’s tech teams work on high-impact products like Amazon.in, Alexa, Prime Video, and AWS.
Explore: Online Assessment · Coding Questions · Interview Experience · Preparation Guide · Certifications & Career · Download PDF
Amazon does not publish one universal CGPA cutoff for every India SDE drive. What students actually see depends on on-campus JD wording vs off-campus portal / hackathon routes. Treat the numbers below as candidate-reported (job posts, placement cells, interview write-ups as of August 2026) - not a guarantee from Amazon HR.
Class 12: Most drives expect 60%+, kept consistent with 10th and graduation. A few campus SDE drives list 65%+. There is no separate Amazon “PCM only” rule beyond what your engineering degree already implies.
Is 6.5 CGPA good enough? It meets the commonly reported minimum baseline. Many on-campus SDE JDs still list 7.0. Off-campus, a 6.5 with a crushing OA can beat a 8.0 with a weak OA - Amazon’s filter after the academic gate is almost entirely DSA + Leadership Principles.
If you sit between 6.5 and 7.0 and your campus JD says 7.0, talk to the placement cell early - some colleges hard-filter before Amazon sees the list. Parallel-path off-campus (Jobs portal, referral, HackOn/WOW) so one numeric floor does not end your Amazon attempt for the year.
Academic snapshot
Baseline: ~6.5 CGPA / 60% across 10th, 12th, graduation
On-campus SDE JDs: Often 7.0
Average selected: Often 7.5-8.5 (candidate-reported)
Backlogs: None active at selection
| Hiring route | Typical CGPA floor | Percentage equivalent | What actually filters you |
|---|---|---|---|
| On-campus (college drives) | Often 7.0 on SDE-1 JDs | ~65-70% | Placement cell list + OA + interviews |
| Off-campus (Amazon Jobs, referrals, HackOn, WOW) | 6.5 commonly cited baseline; many posts have no hard published cutoff | ~60% | Resume screen + OA (coding + work sim + LP MCQs) + loop |
| Class 12 (both routes) | - | 60%+ (sometimes 65%+ at select campuses) | Should stay consistent with 10th and graduation |
| CGPA range | Rough chances | Reality check |
|---|---|---|
| 6.5-6.9 | Low-medium | Eligible at baseline; you need strong DSA + LP stories |
| 7.0-7.4 | Medium | Matches many on-campus SDE JD floors |
| 7.5-8.5 | High | Where a lot of selected candidates cluster |
| 8.5+ | Very high if tech + behavioral hold | CGPA alone never clears Bar Raiser |
Download 2026 Amazon placement papers
2026 pattern in detail
2025 placement papers
2024 placement papers
Previous year question papers
Amazon “papers” for freshers are less about aptitude booklets and more about OA coding patterns, work-simulation judgment, and interview-style DSA. Practicing 2024-2026 sets is useful when you treat them as pattern trainers, not as a question bank you will see verbatim. Download the free PDF, time yourself, then review solutions the same day while the mistakes are still fresh in your notes.
| Stage | What previous papers / mocks train |
|---|---|
| OA coding | Arrays/strings, sliding window, graphs (BFS/DFS), heaps, bit tricks, light DP |
| Work simulation | Email triage, debugging choices, customer vs deadline trade-offs |
| LP MCQs | Choosing the “Amazon-like” response (ownership, customer, dive deep) |
| Tech interviews | Explain + code + optimize; edge cases under follow-ups |
| Design / Bar Raiser | OOP for SDE-1; depth on ownership stories |
Free downloads and year pages:
Amazon hires SDE freshers through campus placement cells, the Amazon Jobs portal, referrals, internship → PPO, and challenge programs like HackOn and WOW. The interview loop after OA is where Amazon feels different from most Indian service-company drives: Leadership Principles show up early, and Bar Raiser is a real veto round.
| Piece | What you face | Pass bar (practical) |
|---|---|---|
| 2 coding problems | Medium-hard DSA on HackerRank / Amazon platform | All / nearly all test cases; partial credit rarely saves you |
| Work simulation | Emails, debugging, priority decisions | Judgments aligned with customer + ownership |
| Behavioral / LP MCQs | Choose responses tied to Leadership Principles | Consistent “Amazon-like” choices |
Languages: Java, C++, Python (and often C). Shortlist rate candidates often cite is roughly 15-25% of OA takers - treat coding correctness as non-negotiable.
Student tip: Read both coding prompts fully before coding. Many people burn 40 minutes on problem 1, leave problem 2 half-tested, then rush the simulation. Budget time like a contest: sketch → code → tests → move on.
| Minute | Move |
|---|---|
| 0-5 | Skim both coding statements + constraints; pick the one you can finish |
| 5-40 | Code problem A; run sample + think of 2 hidden edge cases |
| 40-75 | Code problem B; do not chase a clever O(n) if O(n log n) already clears tests |
| 75-100 | Work simulation / debugging scenarios - read carefully, pick ownership-heavy options |
| 100-120 | LP MCQs + final pass on failing tests if the platform allows |
If your invite is the long variant (coding + extended workstyle), stretch the same proportions across 3+ hours and take a short stretch break between blocks so decision quality does not tank.
Work simulation in plain words: You might get an inbox where a customer is blocked, a teammate wants a risky shortcut, and a manager asks for a status. Amazon-shaped answers escalate with data, protect the customer, and take ownership of the next step - not “wait for someone else” and not “ship broken to look fast.”
Deeper OA breakdown: Amazon Online Assessment.
Video call with a shared editor. Expect 1-2 DSA problems (graphs, bit masking, sliding window, heaps show up a lot). You must:
Interviewers care as much about how you debug as about the final snippet. If a test fails in your head, narrate the fix instead of going silent. Freshers who code correctly but cannot explain why the graph needs a visited set still get dinged.
Warm-up habit before the call: One easy array problem in your language of choice so syntax is warm, then close Stack Overflow - interview pace rewards recall, not tabs.
Often split: one medium-hard DSA (DP on trees, heaps, graphs) plus ~20-30 minutes of Leadership Principles using STAR. Classic prompts:
Weak answers sound like team resumes (“we shipped”). Strong answers sound like you owned a metric, a bug, or a trade-off. Keep a sticky note with your top four stories during the loop so you do not freeze and invent fiction - Bar Raiser will notice inconsistencies later.
Freshers fail this round by jumping to Kafka and Redis with no requirements. Start with actors → data → APIs → bottlenecks. For a bookstore: Book, Inventory, Cart, Order, Payment; then talk about what breaks if two users buy the last copy. That single concurrency question separates “I watched a YouTube design video” from “I can reason.”
A senior / principal engineer, usually outside the hiring team, runs a mix of DSA, light design, and deep LP probing. They are paid to protect Amazon’s hiring bar. Expect follow-ups like:
You can clear every coding round and still fail here if stories are shallow or inconsistent with your resume. Bar Raisers often push until the story either gains texture or collapses - practice with a friend who interrupts every 30 seconds.
Background check basics, location (Bangalore, Hyderabad, Chennai, and other India hubs), joining date, and CTC structure (base + bonus + RSUs). Know the ₹25-32 LPA SDE-1 band so you do not negotiate from vibes. Have a clean answer for notice period / final exams, and one thoughtful question about the team’s customers (retail, AWS, devices) - it beats “what is the work culture?”
| Phase | Typical duration | Notes |
|---|---|---|
| OA window | 1-5 days to complete after invite | Some unproctored; still treat as exam conditions |
| Interview loop | 1-2 weeks | Tech + LP + design + Bar Raiser |
| Bar Raiser slot | Often mid/late loop | Can be rescheduled; stay flexible |
| HR / offer | Same day to a few days | Written offer + BG check follow |
| End to end | ~2-4 weeks common | Off-campus can be faster or slower |
| Component | Focus | Prep move this week |
|---|---|---|
| Coding Q1-Q2 | Graphs, window, bits, DP | Two timed mediums back-to-back |
| Work simulation | Prioritize, customer, debug | Practice “what would Amazon do?” aloud |
| LP MCQs | 16 principles vocabulary | Map each principle to one story |
Shortlist mail can land in days or take longer. Use the gap:
If you are rejected at OA, do not burn the week doomscrolling. Tag the failure: coding WA, timeout, or weak simulation choices. Fix that bucket for two weeks, then re-apply via portal / HackOn / next campus cycle when eligible.
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 Amazon invite is 3-8 weeks out, treat this hub as the map and the nested 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 Amazon sits around ₹25-32 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): Amazon eligibility for freshers 2026 is candidate-reported, not one official published cutoff. Common baseline: 6.5 CGPA (60%) across 10th, 12th, and graduation; many on-campus SDE-1 job descriptions list a 7.0 CGPA floor; Class 12 is typically 60%+ (sometimes 65%+ at select campuses). Degree: B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related fields. Final-year students and recent grads (within ~1 year). No active ba.
What you are training for: Amazon placement process for SDE freshers typically runs: 1) Online Assessment (OA) - 2 coding problems + work simulation + Leadership Principles MCQs (often 90-120 min, some invites run longer), 2) Technical Interview 1 (DSA), 3) Technical + Behavioral Interview 2 (DSA + Leadership Principles), 4) System Design / Managerial round, 5) Bar Raiser (mandatory on most SDE loops), 6) HR / offer discussion. Campus and off-campus timelines usually land in about 2-4 weeks from OA to offer.
Short version of the prep split: Split prep roughly 50% DSA (graphs, sliding window, bit manipulation, DP - 150+ LeetCode Amazon-tag problems), 20% system design / OOP basics for SDE-1, 20% STAR stories for all 16 Leadership Principles, 10% mocks and communication. Practice timed OAs with coding + work simulation. Use Java, C++, or Python consistently.
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the Amazon 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 Amazon 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 Amazon 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 Amazon?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. 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 Amazon-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 Amazon story (eligibility, rounds, salary). Use those pages for reps. If a card 404s on your campus mirror, the explore links at the top of this page are the same destinations.
If you do one thing after reading this: schedule three timed Amazon papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Amazon papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Amazon-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed Amazon paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Amazon. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Amazon, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Amazon mistakes, you are collecting content, not preparing.
Sit one more mixed Amazon set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Sit one more mixed Amazon set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on location, level, RSUs, and year.
| Level | Experience | Base (typical) | Total package (typical) | Notes |
|---|---|---|---|---|
| SDE-1 | New grad | ₹18-22 LPA | ₹25-32 LPA | Fresher target band for this hub |
| SDE-2 | ~1-3 years | ₹28-36 LPA | ₹38-48 LPA | Heavier design ownership |
| SDE-3 | ~4-7 years | ₹45-65 LPA | ₹65-90 LPA | Senior scope |
| Principal | 8+ years | ₹90+ LPA | ₹1.2 Cr+ | Architect / tech lead track |
| Role | Level | Total package (reported) | Focus |
|---|---|---|---|
| Support Engineer | Entry | ₹10-14 LPA | Strong CS fundamentals |
| QA Engineer | Entry-mid | ₹12-20 LPA | Testing + automation |
| Product Manager | Mid-senior | ₹35-65 LPA | Product sense + tech |
| Operations Manager | Mid | ₹20-32 LPA | Ops + analytics |
Locations: Bangalore, Hyderabad, and Chennai are the usual fresher tech hubs; be ready for relocation questions.
Total CTC for freshers is rarely “one number equals monthly cash.” Candidate-reported packages in the ₹25-32 LPA band usually mix:
When classmates compare offers, compare base + first-year cash separately from four-year RSU face value. That alone prevents a lot of panic math during HR.
Student implication for 2026: prep like a product-company loop (LeetCode + stories), not like a service-company aptitude day. If your college gets fewer Amazon slots, invest early in portal applications and challenge programs instead of waiting for one campus date. Diversity and women-focused programs (including WOW) remain active routes - use them when eligible instead of treating campus as the only door.
Typical fresher SDE path: Online Assessment (2 coding + work simulation + LP MCQs) → Technical Interview 1 (DSA) → Technical + Behavioral Interview 2 (DSA + Leadership Principles) → System Design / Managerial → Bar Raiser → HR / offer. Campus and off-campus both feed into a similar loop after OA. End-to-end is often 2-4 weeks.
Count 5-6 stages for most SDE freshers: OA plus roughly four interview conversations (two technical/LP-heavy, one design/managerial, one Bar Raiser) and HR. Exact labels vary by college placement email, but Bar Raiser is the Amazon-specific constant.
Yes. Free Amazon placement papers PDF and previous-year practice sets (2024-2026) with solutions live on placementpapers.app - including the 2026 PDF and year pages. No paywall for the core downloads.
Most fresher OAs include two DSA coding problems, a work simulation (emails / debugging / decisions), and Leadership Principles-style MCQs, often in a 90-120 minute window on HackerRank or Amazon’s platform (some invites feel longer once every section is counted). Languages: Java, C++, Python. Aim to clear coding test cases completely.
From student reports (not one official Amazon PDF): baseline about 6.5 CGPA (60%) across 10th, 12th, and graduation; many on-campus SDE-1 JDs list 7.0; Class 12 usually 60%+ (sometimes 65%+). Degrees: B.Tech/B.E./M.Tech/MCA in CS/IT/ECE-related fields. Final year or recent grad (~1 year). No active backlogs. ~1 year max gap commonly reported. Off-campus Jobs / HackOn / WOW posts often skip a hard published CGPA cutoff - performance still decides.
SDE-1 new-grad total package is commonly ₹25-32 LPA in India (base often ₹18-22 LPA), plus bonus / RSU details on the letter. Location and college tier move you inside the band. Always verify against your offer, not blog averages alone.
SDE-1 is the fresher / early level (about ₹25-32 LPA total). SDE-2 usually expects ~1-3 years and pays higher (often cited around ₹38-48 LPA total) with more system design, mentoring, and feature ownership. Interview depth - especially design - scales with level.
C, C++, Java, and Python are typically accepted. Java and C++ are most common among selected candidates; Python is fine if you are fast and clear. Do not switch languages between OA and interviews.
A mandatory loop interview for most SDE hires: ~45-60 minutes with a senior/principal engineer who does not own the team’s headcount the same way a hiring manager does. Mix of DSA, design, and deep LP questions. They check whether you raise the bar - ownership, customer obsession, honest trade-offs - not whether you memorized definitions.
Write STAR stories from real work. Cover Customer Obsession, Ownership, Bias for Action, Dive Deep, Deliver Results, and Invent & Simplify at minimum, then fill gaps across all 16. Quantify results. Practice follow-ups. Use the Leadership Principles guide for prompts.
Scenario section after/alongside coding: emails, bugs, priority calls. You pick actions that balance customer impact, ownership, and delivery. It is scored - do not “save all time for coding” and click randomly at the end.
HackOn is a student hackathon / challenge route that can unlock interviews. WOW is a women-focused hiring program with challenges, interviews, and networking. Both are useful off-campus paths; you still need OA-ready DSA and LP stories afterward.
Rough fresher framing (candidate-reported bands): Amazon ₹25-32 LPA SDE-1, LP-heavy culture, AWS exposure. Google often higher total bands with a fierce algorithm bar. Microsoft competitive packages with comparatively strong WLB reputation on many teams. Pick on role, team, learning, and offer details - not brand tweets.
When the OA link lands, block a half-day. Coding plus work simulation plus LP MCQs regularly overrun the “one hour coding contest” mental model. Every week: Amazon-tag DSA + one STAR story spoken out loud. Bar Raiser rewards depth, not buzzwords.
Candidate reports expect no active backlogs at selection. A gap of about one year between stages is commonly accepted if you can explain it cleanly; longer gaps need a coherent story (exam year, health, family) and still do not replace OA performance.
Most fresher SDE offers assume joining an India hub - Bangalore, Hyderabad, Chennai, and other offices depending on team. Hybrid policies vary by org. In HR, state location preferences honestly and show flexibility if you can move; rigid “remote only” answers are a poor fit for many new-grad teams.
An SDE-1 applicant who applied on 13 April 2025 wrote that after the 2 May hiring-interest form, “I immediately received another mail containing the Online Assessment (OA) link, with instructions to complete it within 5 days” (Medium). They sat the unproctored OA on 4 May - two DSA questions plus Work Simulation and Leadership Principles sections - then saw the first interview rescheduled on the day itself.
What juniors should copy: once you submit interest, assume the OA window can open immediately. Keep a working setup ready (Java/C++/Python muscle memory, quiet room, stable network). Unproctored is not casual - protect coding pace and simulation judgment. Build calendar slack for same-day interview moves.
Another SDE-1 candidate posting in July 2025 after an APAC SP IND Tech invite said the full OA “got me more than 3.5 hours to complete,” spanning coding plus lengthy Workstyle and Work Simulation blocks tied to ownership, delivering results, and earning trust (LinkedIn).
Practical takeaway: block a half-day, not a quick coding hour, when Amazon’s assessment link lands. Students who only mock two LeetCode mediums get blindsided by decision fatigue in the non-coding sections. Practice choosing responses that show ownership and customer impact even when every option looks “fine.”
Write-ups on placementpapers.app often follow: clear both OA codes → DSA on a shared editor → LP deep dive in the same hour → bookstore-style OOP design for SDE-1 → Bar Raiser probing ownership metrics and “what you would do differently.” Patterns repeat more than exact questions. Read fuller narratives on Amazon interview experiences and keep a personal log of which LP each mock interviewer stressed - you will spot weak principles quickly.