Frontend Engineer II
- Timeline
- Recruiter call + OA, then 4 rounds
- Compensation
- 35 to 45 LPA
Tips before you start
- DSA is a must. Trees, matrices, and arrays come up in every loop, say time and space complexity before you write a line.
- Round 1 is vanilla JS only. Reaching for React is a red flag. Build the base feature, then expect two live extensions.
- Time yourself. 60 minutes on livecode.com with no autocomplete goes fast, ship the happy path first, polish second.
- Use numbers in every behavioral answer. "40 percent less boilerplate" beats "we improved it."
- In system design, go requirements → component tree → API → trade-offs. Amazon's FE rubric weights structure heavily.
- Map every behavioral story to a Leadership Principle out loud, Have Backbone, Ownership, Deliver Results, Learn and Be Curious.
- Accessibility is graded. Keyboard operability, ARIA roles, and visible focus rings score points in the machine-coding round.
- Expand each question below for what the interviewer is testing, how to answer, working code, complexity, follow-ups, and references.
Interview rounds
5 rounds- 11
Online Assessment
60 min3/5HTML, CSS, and JavaScript output MCQs (10 questions)
Build a vanilla JS image carousel (OA coding task)
Overall experience
An Amazon Frontend Engineer II loop in Bangalore: recruiter call plus an online assessment, then four onsite rounds — vanilla JS machine coding on livecode.com, DSA plus JavaScript output on a shared doc, frontend system design on Miro, and a Bar Raiser mapped to the 16 Leadership Principles with a DSA follow-up. Compensation band reported at 35 to 45 LPA. Machine coding often starts with a 5-star rating and gets extended twice (half stars via clip-path, then keyboard and ARIA). DSA favourites include matrix staircase walks and graph cloning. System design focuses on a news homepage like Times of India with cursor pagination and breaking-news delivery. Validated from real public experiences and interview patterns. May vary by team and interviewer.