Software Engineer Interview Experience - United States
Process
The call was by recruiter and promised a compensation which I doubt they can really make it. HM enjoyed my working experience, and asked if I would like to join her team.
The process included a phone coding challenge.
Questions
Two coding questions (the first question has two subproblems) in 50 mins (yes, interviewer joined late with no introductions and no greetings). Need to write the code in coderpad, resolve all the symbol errors, write test cases in code and testing your code by yourself.
The interviewer named Juli** didn't show any respect to interviewer, no greetings, muted himself, very bossy, just place his orders to you.
Was this helpful?
Interview Statistics
The following metrics were computed from 11 interview experiences for the Amplitude Software Engineer role in United States.
Success Rate
Amplitude's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Experience Rating
Candidates reported having mixed feelings for Amplitude's Software Engineer interview process in United States.
Amplitude Work Experiences
- 1.0no futureSoftware Engineer • Former EmployeeSan Francisco, CaliforniaFebruary 5, 2024Pros: No new innovation, sales aren't growing, and people are leaving, and that's the pros.Cons: The culture is toxic, and the stock is dead.
- 4.0AlrightSoftware Engineer • Current EmployeeSan Francisco, CaliforniaJune 20, 2023Pros: They are good people to work with.Cons: Unsure about direction of the products
- 5.0A couple of tough years, but the future is brightSoftware Engineer • Current EmployeeSan Francisco, CaliforniaMay 24, 2024Pros: Every tech company has gone through a rough patch in the last few years. Amplitude is no different. However, the product and customers speak for themselves. They are excited to use what we have built, and even more excited for what we are building. It is rare that you get so much unsolicited positive feedback on a product, but that is the norm here.Cons: What Amplitude is trying to do is clear to me. That does not always come through in our company strategy, though, which changes a lot. We end up building the same, valuable things but under different names and organizations for not much reason. All things considered, that is not the worst problem to have.
