JOB ALERT - Amazon SDE-1 Hiring in Karnataka for Freshers - Apply Now
Interview Slot Details
Candidate Name: Withheld
Slot Time: July 18, 2025 – 10:00 AM
Mode: Online (Google Meet)
Role: Software Development Engineer - I
Company: Amazon (ADCI – Karnataka)
Real Interview Questions Asked – Freshers Role
👉 HOW TO GET A JOB IN A MONTH - GET HERE
📌 Technical Round – Core CS & Programming (12 Questions)
Q1. Explain Object-Oriented Programming and its principles.
Candidate Answer:
"OOP is a programming model based on the concept of objects. It includes principles like Encapsulation, Inheritance, Polymorphism, and Abstraction."
Feedback: Solid understanding. Could improve with real-world analogies.
Skill Assessed: Object-Oriented Design
Mistakes to Avoid: Listing without explanation or real-world mapping
Q2. Write a function in Java or Python to reverse a linked list.
Candidate Answer:
“In Python, I’d initialize a prev pointer as None, then iterate through the list while adjusting next pointers.”
Feedback: Knows the logic. Missed handling of edge cases.
Skill Assessed: Data Structures – Linked Lists
Mistakes to Avoid: Not covering null checks or loop condition errors
Q3. What are time and space complexities of your function?
Candidate Answer:
“Time complexity is O(n) and space complexity is O(1) as I’m reversing in place.”
Feedback: Correct and precise.
Skill Assessed: Complexity Analysis
Mistakes to Avoid: Confusing iterative vs recursive complexities
Q4. Compare Array vs Linked List.
Candidate Answer:
“Arrays are contiguous memory with fast indexing, while linked lists offer better insert/delete performance.”
Feedback: Good comparative insight. Could add real-world use cases.
Skill Assessed: Core CS – Data Structures
Mistakes to Avoid: Forgetting performance trade-offs in various operations
Q5. What are hash maps? Can you implement one?
Candidate Answer:
“Hash maps store key-value pairs using a hashing function. I can implement basic get/set/delete using arrays and handling collisions with chaining.”
Feedback: Strong conceptual clarity.
Skill Assessed: Hashing
Mistakes to Avoid: Not discussing collisions or load factor
Q6. Explain the difference between a stack and a queue.
Candidate Answer:
“Stack is LIFO, Queue is FIFO. Stack uses push/pop, queue uses enqueue/dequeue.”
Feedback: Correct. Could give practical applications like recursion call stack.
Skill Assessed: Data Structure Basics
Q7. How does memory management work in C vs Java?
Candidate Answer:
“C requires manual memory management using malloc/free. Java uses automatic garbage collection.”
Feedback: Accurate but superficial. Missed talking about memory leaks or GC roots.
Skill Assessed: System Knowledge – Memory
Q8. What is multithreading? Have you used it?
Candidate Answer:
“Yes, in Java using Thread class and Runnable interface. It allows concurrent execution of tasks.”
Feedback: Functional knowledge. Missed discussing synchronization issues.
Skill Assessed: Concurrency Basics
Q9. What is the difference between REST and SOAP APIs?
Candidate Answer:
“REST uses lightweight HTTP, JSON; SOAP is heavier with XML and stricter protocols.”
Feedback: Concise. Great for fresher level.
Skill Assessed: API Fundamentals
Q10. What is recursion? Can you give an example?
Candidate Answer:
“It’s when a function calls itself. Example: calculating factorial or Fibonacci.”
Feedback: Correct. Would be stronger with stack trace explanation.
Skill Assessed: Problem Solving – Recursion
Q11. Describe how you would build a scalable URL shortener.
Candidate Answer:
“I’d use hashing for short URLs, store in a database with indexing, and implement caching for speed.”
Feedback: Good start. Didn’t mention database partitioning or rate-limiting.
Skill Assessed: Systems Design Thinking
Q12. How do you test your code for reliability?
Candidate Answer:
“Write unit tests, use assertions, debug using IDE, and run test cases for edge inputs.”
Feedback: Practical. Missed continuous integration references.
Skill Assessed: Testing and QA Approach
📌 Behavioral Round – Amazon Principles (8 Questions)
Q13. Tell me about a time you solved a tough problem.
Candidate Answer:
“During college, I worked on a face detection project and fixed a major bug that crashed our model during image preprocessing.”
Feedback: Good story. Could add metrics or how it helped the team.
Skill Assessed: Ownership, Problem-Solving
Q14. Describe a time when you failed.
Candidate Answer:
“I once missed a deadline on a team project due to overcommitting. I learned to prioritize better and communicate proactively.”
Feedback: Honest and reflective. Great self-awareness.
Skill Assessed: Accountability
Q15. How do you handle ambiguity in requirements?
Candidate Answer:
“I clarify requirements by asking questions, documenting assumptions, and validating regularly with stakeholders.”
Feedback: Strong. Shows leadership potential.
Skill Assessed: Working in Agile, Ownership
Q16. Have you ever disagreed with a team member?
Candidate Answer:
“Yes, we had different approaches on a feature. I listened, shared my logic, and we agreed to test both and choose the better performing one.”
Feedback: Collaborative, not defensive.
Skill Assessed: Communication, Collaboration
Q17. Why Amazon?
Candidate Answer:
“The culture of innovation and the scale of impact are unmatched. I’m excited about the ownership and fast-paced development.”
Feedback: Genuine. Aligns well with Amazon values.
Skill Assessed: Cultural Fit
Q18. How do you stay updated with technology?
Candidate Answer:
“Through YouTube channels, newsletters like JavaScript Weekly, and solving problems on LeetCode.”
Feedback: Passionate learner.
Skill Assessed: Growth Mindset
Q19. Give an example of customer obsession.
Candidate Answer:
“I once built an internal tool that saved our college team 6 hours/week just to improve handoffs. It wasn’t required, but it made life easier.”
Feedback: Excellent Amazon-style thinking.
Skill Assessed: Customer Obsession
Q20. How do you balance speed and quality in development?
Candidate Answer:
“By writing minimal viable code and optimizing post-feedback. Also, I write test cases early.”
Feedback: Efficient mindset.
Skill Assessed: Delivery Excellence
📌 Situational Round – JD-Based Challenges (6 Questions)
Q21. You have to build a distributed storage system. What factors do you consider?
Candidate Answer:
“Scalability, fault tolerance, data replication, consistency, and cost.”
Feedback: Good. Missed CAP theorem.
Skill Assessed: System Design Thinking
Q22. You’re given a week to build a prototype. How do you proceed?
Candidate Answer:
“Break it into sprints, define priorities, and focus on MVP features first.”
Feedback: Practical approach.
Skill Assessed: Time Management
Q23. Mid-project, a requirement changes. What do you do?
Candidate Answer:
“Reevaluate scope, update timelines, discuss trade-offs, and keep documentation in sync.”
Feedback: Excellent flexibility.
Skill Assessed: Adaptability
Q24. You have a bug you can’t reproduce. What steps do you take?
Candidate Answer:
“Recheck logs, try different environments, and write test cases around the failing point.”
Feedback: Strong debugging mindset.
Skill Assessed: QA/Debugging
Q25. You’re working on a team with globally distributed members. How do you collaborate?
Candidate Answer:
“Through regular check-ins, shared documentation, async updates, and using collaboration tools like Slack and Jira.”
Feedback: Strong virtual team handling.
Skill Assessed: Remote Communication
Q26. How would you reduce latency in a prediction model pipeline?
Candidate Answer:
“By optimizing data input, using model compression, batching predictions, and caching frequent results.”
Feedback: Shows understanding beyond just code.
Skill Assessed: Optimization Thinking
📌 HR Round – Fit & Logistics (4 Questions)
Q27. Are you open to relocation to Karnataka?
Candidate Answer:
“Yes, I’m flexible with relocation for career growth.”
Feedback: Good. Shows commitment.
Q28. What’s your preferred joining timeline?
Candidate Answer:
“I’m available immediately post my final semester exams in August.”
Feedback: Clear and to the point.
Q29. Do you have any other offers in hand?
Candidate Answer:
“I’m in discussions but haven’t accepted any yet.”
Feedback: Transparent.
Q30. Any questions for us?
Candidate Answer:
“Yes – What does success look like for an SDE-I in the first 6 months?”
Feedback: Great closing. Shows curiosity and maturity.
Interviewer Summary
Technical Performance: 8/10
Communication: 8.5/10
Confidence: Medium-High
Recommendation: Shortlist for Offer Discussion
What the Candidate Missed:
-
Could improve system design structuring
-
Didn’t mention Git/version control experience
-
Missed CAP theorem and middleware details