Good Team, Bad Deadlines
Good Team, Bad Deadlines
Flexible work hours. Good pay. Feel like a team player. Good opportunities. Good coworkers.
Not realistic deadlines. Too many meetings. A-team sucks. Not remote anymore. Upper management sucks.
Additional Ratings
Was this helpful?
Amazon Interview Questions
Amazon Interview Experiences
Software Engineer
This was a while back. There were 5 rounds on-site and 2 rounds remote. A few of the on-site interviews were with people in California. The process was long, and the interviewees were bored and tired, just looking for gotcha moments. Not great, reall
Software Engineer
Not easy, mostly on Hard DSA problems. Must prepare on OOPS, DBMS, and other concepts. Linked list, DP, and many other things which will help you for any type of interview in the future.
Software Engineer
There were three rounds: The first round was a pure behavioral question, covering topics like handling tied deadlines and making decisions with calculated risks. The second round was pure coding, including implementing an LRU cache and an easy Leet
Software Engineer
CanadaDecember 1, 2019This was a while back. There were 5 rounds on-site and 2 rounds remote. A few of the on-site interviews were with people in California. The process was long, and the interviewees were bored and tired, just looking for gotcha moments. Not great, reall
Software Engineer
IndiaJune 10, 2022Not easy, mostly on Hard DSA problems. Must prepare on OOPS, DBMS, and other concepts. Linked list, DP, and many other things which will help you for any type of interview in the future.
Software Engineer
New York, New York, United StatesApril 25, 2025There were three rounds: The first round was a pure behavioral question, covering topics like handling tied deadlines and making decisions with calculated risks. The second round was pure coding, including implementing an LRU cache and an easy Leet
