Amazon SDE 1 Interview Questions for Freshers (2026)
Amazon SDE 1 interview questions for freshers cover more than a list of DSA problems. Campus and off-campus candidates usually face an online assessment, then live rounds that mix coding with Leadership Principles. The algorithms are mostly medium. The part freshers under-prepare is the spoken round: you are graded on stories from college, internships, and projects, and "I don't have work experience" is not a strategy.
This is the 2026 shape of that process. Drives differ by college, country, and whether you applied off-campus. Your email is the schedule. Amazon interview questions is where to check what candidates are posting this week.
What freshers are actually interviewed on
| Stage | What it usually contains | What a fresher is graded on |
|---|---|---|
| Online assessment | Two coding problems, plus a work-style survey. Some 2026 links add a bug-fixing module | Code that passes hidden tests, and consistent judgment on the survey |
| Technical rounds | One or two DSA problems each, sometimes a light design or a project deep-dive | Correct medium, explained, plus whatever is on your resume |
| Leadership / bar raiser / hiring manager | Principles, conflict, ownership | A real scene from a project, internship, or club — not a slogan |
On-campus and off-campus do not have two different syllabi. The OA comes first either way. The live questions are the same families. The difference is logistics and how hard they press on your résumé, because off-campus interviewers did not sit through your college's pre-placement talk.
The OA has its own guide: Amazon SDE 1 OA questions 2026. If your link mentions an AI assistant and broken starter code, read the bug fixing round before you treat it like two blank-file LeetCode problems. Do not skip the work-style survey. Freshers fail it by answering every scene as "I will do it all myself tonight."
Amazon SDE 1 interview questions for freshers: DSA
Live coding for SDE 1 freshers sits at easy-medium and medium. You need to write it in a shared editor, talk while you write, and test an edge. You do not need rare DP.
Arrays, strings, and hash maps
This is the largest family. Be able to produce, from a blank file:
- Two-sum and a frequency map
- Subarray sum equal to
kwith prefix sums - Sliding window (longest substring without a repeat, minimum window)
- Merge intervals
- Product of array except self, or another "one pass forward, one pass back" trick — know it, do not build a religion around it
If the interviewer wraps it in a story about orders or logs, rewrite it as arrays before you code. That translation is the skill.
Stacks and queues
Valid parentheses, next greater element, a queue using stacks, and min-stack. These show up because the code is short and the bugs are real. A worked Amazon example at this altitude — more design than puzzle — is the stack with O(1) getMiddle. You may not get that prompt. You should be able to talk about a stack's invariant the same way.
Trees
Traversals, height, mirror, lowest common ancestor, and check if a tree is a BST using a full min/max range. Distance between two nodes is a reported Amazon coding problem and a fair fresher question: LCA plus depths, with the case where one node is the ancestor of the other.
Graphs
BFS and DFS only, until those are boring. Number of islands, cycle in a directed graph, course schedule, clone a graph. Minimum steps means BFS. Do not reach for Dijkstra unless the edges have weights and you were asked for a weighted answer.
Light design and projects
Some rounds never leave DSA. Some ask you to design a parking lot, a library, or an LRU cache at the level of classes and operations, or they put your project on the screen and ask what you would change.
If you have a project on your résumé, you will be asked:
- What you wrote versus what your teammate wrote
- The schema or the main data structure
- One bug you found
- What breaks if there are 100x as many users
If you cannot answer those four, take the project off the résumé. Interviewers would rather see a small project you understand than a distributed system you demoed once.
For the class-design version, skim how to crack LLD interviews. Freshers are not expected to run a 45-minute high-level design the way SDE 2 candidates are. They are expected not to freeze if someone asks "what are the classes?"
Basic dynamic programming
One knapsack-style or staircase-style problem is enough to not panic. If DP is the only thing you study, you will fail the tree round. Keep it to a weekend, after arrays and graphs work.
Leadership Principles when you do not have a job yet
Amazon asks principles in live rounds even for freshers. The work-style survey was the written version. The interview is the spoken one.
You do not need a production outage. You need a scene:
- A course project where the demo was tomorrow and a teammate's part did not work
- An internship bug you reproduced instead of guessing
- A club or volunteer deadline you cut scope on
- A time you disagreed with a teammate and what you did after the decision
- A time you broke something and told someone before they found it
Eight scenes is enough. Each one: what was happening, what you chose, what happened next. Ninety seconds. The shape in effective storytelling in hiring manager interviews works even when the scene is a final-year project. Drop the clichés. "I am a quick learner" is not a scene. "I rewrote the import the night before the demo because the CSV had duplicate ids, and I added a check so we would notice next time" is a scene.
Map them roughly onto principles interviewers actually ask freshers:
| Principle | A fresher-scale scene |
|---|---|
| Ownership | You picked up the module nobody wanted, and you say what "done" meant |
| Dive Deep | You did not stop at "it crashes"; you found the input that did it |
| Deliver Results | You cut a feature to make the deadline and named the feature |
| Bias for Action | You made a call with incomplete info and limited the blast radius |
| Earn Trust | You told the team early that your part was late |
| Disagree and Commit | You argued, you lost, you still built the other approach |
| Customer Obsession | A user of your project — a classmate, a campus user — hit a real bug |
Do not invent metrics. "The page felt faster" is honest. "I improved latency by 60%" is a follow-up you cannot answer if you never measured it. Freshers get caught here constantly.
A four-week plan
Week 1. Arrays, strings, hash maps. Two problems a day, 35 minutes, in the language you will use on HackerRank and in the interview. No new language this month.
Week 2. Trees and graphs, plus the OA mock from the SDE 1 OA guide: two problems, a timer, then ten work-style scenes answered in writing so you can see if you contradict yourself.
Week 3. Stacks, intervals, one weekend of basic DP, and four project answers written down for every project on your résumé. Say them out loud once.
Week 4. Eight Leadership Principles stories. Two mock interviews that start with a story and then a coding problem, because that is the live round. Two days before the interview, reread stories and templates for BFS, binary search, and prefix sums. Open Amazon interview questions and only add a problem if the pattern is one you have never written.
If you are also interviewing at companies that use a human screen instead of an OA, Atlassian Karat interview questions is the "talk while you code" version of week 1 and week 2.
Frequently asked questions
Are Amazon SDE 1 interview questions for freshers different in India?
The structure campus candidates in India describe — OA, then DSA rounds, then a principles round — matches what new grads describe elsewhere. The problems are not a separate "India-only" list. College drives can add a group discussion or a stricter résumé screen. The prep on this page covers the technical and principles rounds either way.
How many DSA rounds are there?
Usually one or two live coding rounds after the OA, sometimes with a managerial round that is mostly principles and your projects. The recruiter or the placement cell has the count for your drive. Do not copy another college's number.
What language should a fresher pick?
The one your college course and your projects already use, if you can write BFS in it without notes. This is a bad month to switch from C++ to Python because a blog preferred Python.
Do freshers get system design?
Sometimes a light low-level design or a deep dive on your project. Rarely a full high-level design. Prepare classes and your résumé. Leave the subscription-service outline to SDE 2 prep unless an interviewer has explicitly scheduled a design round.
What if I have no internship?
Use a course project, a bug you fixed, or a club deadline. The principle questions do not require an employer. They require a choice you made. If you truly have no story, you have a project problem, not an interview problem: build something small enough that you can answer the four résumé questions above, and put that on the page.
Final thoughts
Amazon SDE 1 interview questions for freshers are a coding assessment, a handful of mediums you can talk through, and Leadership Principles stories at student scale. The DSA list is not long. The mistake is treating the spoken half as optional because you have not had a job.
Start with the OA guide, keep eight true scenes, and check live Amazon interview questions the week of your drive. Good luck.