Amazon India Interview Questions: The Full SDE-1 Hiring Process

Amazon India's fresher hiring for Software Development Engineer (SDE-1) roles runs six stages: resume screening, a long proctored online assessment with debugging and coding problems, two technical interviews on data structures and algorithms, a Bar Raiser round with an interviewer from outside your hiring team who holds veto power, and a final HR/hiring-manager conversation. Every single one of those rounds — not just a dedicated "behavioral" slot — also probes Amazon's 16 Leadership Principles. If you're preparing for amazon india interview questions, the thing that trips up most freshers isn't the DSA (which is genuinely hard but well-documented), it's underestimating how much weight the Leadership Principles carry in every round, including the coding ones. This guide covers the process, real example questions per round, and reported CTC bands for 2026.

Amazon India's fresher SDE hiring process at a glance

Amazon recruits fresh graduates (B.E./B.Tech/M.Tech/MCA/M.Sc in CS, IT or allied branches, typically with 60%+ marks or a 6.5+ CGPA and no active backlogs at joining) mainly into the SDE-1 role. According to a breakdown by MyInternships.in, the 2026 process runs across six stages:

Stage	Format	What it screens for
Resume screening	Amazon Jobs portal / campus drive	Academic eligibility, relevant coursework and projects
Online Assessment	~3 hours, proctored	Debugging (6–8 questions), 2 coding problems, CS aptitude MCQs, work-style/work-simulation assessment
Technical Interview 1	45–60 min	DSA problem-solving, project discussion, one or two Leadership Principles
Technical Interview 2	45–60 min	Advanced DSA, core CS fundamentals, Leadership Principles
Bar Raiser	45–60 min	Cross-team calibration — technical depth plus Leadership Principles, with veto power over the offer
HR / Hiring Manager	20–40 min	Leadership fit, availability, offer discussion

Round 1: the Online Assessment

This is a long, proctored test — reportedly around three hours — combining several distinct sections rather than a single coding test.

What's actually in it

• Debugging questions (6–8): you're given broken code and asked to identify and fix the bug, testing whether you can read unfamiliar code under time pressure, not just write your own from scratch.
• Two coding problems: typically array/string manipulation, hashing, or basic graph/tree problems solvable in 20–30 minutes each at a fresher level — for example, "find all pairs in an array that sum to a target value" or "check if a binary tree is balanced."
• CS fundamentals MCQs: OS, DBMS, networking and OOP basics.
• Work-style / work-simulation assessment: scenario-based questions describing a workplace situation (e.g., a teammate missing a deadline, conflicting priorities from two stakeholders) and asking you to rank possible responses. This section is effectively an early, automated pass at Leadership Principles — answers that reflect Ownership and Customer Obsession score better than ones that simply avoid conflict.

Rounds 2 and 3: the technical interviews

Two back-to-back technical rounds, each 45–60 minutes, blend DSA problem-solving with Leadership Principles questions rather than separating them.

Example DSA questions

• "Given a string, find the longest substring without repeating characters." A strong answer starts by stating the brute-force complexity (O(n²) or O(n³)) out loud, then moves to a sliding-window approach with a hashmap tracking last-seen indices to get O(n), and talks through the two-pointer logic as they code.
• "Given a binary tree, print its level-order traversal." Good candidates immediately reach for a queue-based BFS and clarify edge cases (empty tree, single node) before writing code.
• "Design a data structure that supports insert, delete, and getRandom in O(1) average time." This is a step up in difficulty from the OA and tests whether you can combine a hashmap with a dynamic array — interviewers are watching whether you ask clarifying questions before diving in, not just whether you eventually get the right structure.

Example Leadership Principle questions woven into the same rounds

• "Tell me about a time you disagreed with a decision on a team project. What did you do?" (Have Backbone; Disagree and Commit) — a good answer describes the specific disagreement, how you raised it with evidence rather than just opinion, and what happened once a decision was made, including whether you committed to it even if it wasn't your preferred outcome.
• "Describe a time you went beyond what was expected of you in a project or internship." (Ownership) — strong answers include a measurable outcome (time saved, bug prevented, users affected), not just an adjective like "I worked really hard."
• "Tell me about the most difficult bug you've debugged." (Dive Deep) — interviewers want the specific steps you took to isolate the root cause, not just "I eventually fixed it."

Amazon's own guidance and multiple prep resources (e.g. Exponent, IGotAnOffer) consistently recommend preparing 6–8 STAR stories in advance, each mapped to two or three Leadership Principles, with specific, quantified outcomes rather than vague claims.

Round 4: the Bar Raiser

The Bar Raiser is Amazon's most distinctive round and the one freshers are least prepared for because it isn't documented as clearly outside the company. The interviewer is deliberately drawn from a completely different team, has no stake in filling your specific role, and is specifically trained to check whether you'd raise Amazon's overall hiring bar — not just whether you're good enough for one team's immediate need. Crucially, the Bar Raiser has the authority to veto a hire even if every other interviewer wants to move forward.

What actually happens in this round

Expect a mix of a moderately hard DSA problem and deep behavioral probing — the Bar Raiser often re-asks about a story you already told an earlier interviewer, specifically to check for consistency and depth. If your "Dive Deep" story from Technical Interview 1 sounds different or shallower when the Bar Raiser asks a follow-up, that's a red flag they're specifically listening for. The fix is simple but often skipped: know your own stories cold enough that you can answer follow-up questions three levels deep, not just recite a rehearsed two-minute version once.

Round 5: HR / hiring manager

The final round covers availability, relocation, and overall leadership fit, and is also where compensation and offer logistics get discussed. It's shorter and lower-stakes than the technical and Bar Raiser rounds, but a poor fit signal here (evasiveness about availability, disinterest in the role) can still stall an otherwise strong loop.

CTC and pay bands reported for Amazon India SDE-1 freshers in 2026

Amazon does not publish a single official fresher CTC figure, and reported numbers vary by source, role and whether the hire is through campus or lateral/off-campus channels. Treat the following as reported ranges rather than confirmed company disclosures:

• Base salary: reported around ₹17–22 LPA for SDE-1.
• Sign-on bonus: reported around ₹2–6 LPA, typically paid across the first one to two years rather than upfront in full.
• RSUs (stock): reported around ₹6–12 LPA face value at grant, vesting over four years on a back-loaded schedule (commonly cited as roughly 5% / 15% / 40% / 40% across the four years), meaning your actual Year-1 and Year-2 realized compensation runs meaningfully below the headline total.
• Total CTC: commonly reported in the ₹28–34 LPA range for SDE-1, though this figure blends base, sign-on and stock face value in a way that overstates what you'll actually see in your bank account in year one — don't plan your finances around the headline number.

Because the RSU vesting schedule is back-loaded, it's worth working through CTC vs in-hand salary and thinking specifically about early-career cash flow before accepting, rather than anchoring purely on the total package figure recruiters quote.

A worked example: answering a Leadership Principles question with real depth

Question: "Tell me about a time you had to make a decision without all the information you wanted." A weak answer: "During my internship, I had to build a feature without complete requirements, so I made some assumptions and built it anyway." That's vague and has no outcome.

A strong answer: "During my final internship sprint, my mentor was on leave and I needed to decide whether our export feature should support CSV only or also Excel, with no one available to confirm the requirement. I looked at the three most recent support tickets referencing exports, saw two explicitly asked for Excel, and decided to build both formats behind a feature flag so I could ship CSV on time and add Excel without a redeploy. It shipped on schedule, and when my mentor returned, she confirmed Excel was in fact the higher-priority one 60% of our target users needed." This answer shows real judgment (using available data instead of guessing blindly), a concrete decision, and a verifiable outcome — exactly the structure Amazon interviewers are trained to probe for under principles like Ownership and Customer Obsession.

How to prepare given the time you have

If you have a month: build a bank of 40–50 solved DSA problems across arrays, strings, trees, graphs and dynamic programming, and separately draft 6–8 STAR stories mapped to specific Leadership Principles with quantified outcomes. If you have a week: prioritise the STAR stories (they're reusable across every round including the OA's work-simulation section) and do timed practice on medium-difficulty problems rather than trying to cram new topics. Whatever your timeline, rehearse your resume walkthrough and practice answering "tell me about yourself" in a way that naturally sets up your strongest stories, and think through how to negotiate salary before the HR round given how back-loaded Amazon's RSU structure is.

The freshers who do best in Amazon India's process treat the DSA rounds and the Leadership Principles rounds as one interview, not two. An interviewer who sees you code cleanly and explain your reasoning with the same rigor you use for your STAR stories is exactly who the Bar Raiser is looking to pass.