SDE 2 - Interview had about six total rounds, including the recruiter conversation
After my resume was shortlisted, a recruiter set up a 30-minute call with me to understand more about my background and my fit for the role.
Then was a technical screen over Zoom with the staff engineer where they asked a low-level design style coding question (not the typical LeetCode round) - you would be required to share your own IDE.
After clearing the technical round was the loop round with 4 rounds.
Share a project of your choice and explain the architecture, design decisions, and different aspects of the project. A principal software engineer took this interview for me, so there were a lot of questions related to the design choices, current drawbacks of the design, some improvements, etc.
Distributed cache with some follow-up questions. I practised using Hello Interview. In the interview, they didn't really ask to design it from the scratch. They have a system design diagram with some pitfalls (e.g. writes are slow) they would ask you targeted questions like what could you do to improve write efficiency. Then they ask follow-ups on your answer. Overall, it was more like a 60 minute discussion on your choices.
The following metrics were computed from 11 interview experiences for the Amplitude Software Engineer role in United States.
Amplitude's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for Amplitude's Software Engineer interview process in United States.