Experienced engineers who are doing awesome stuff, and so it can be a valuable experience learning from them.
Allows for end-to-end experience. You get to learn a lot from being involved and owning the whole development cycle.
Design meetings are very educational.
Expectations are high for how much you're asked to accomplish. You may not get much of a work-life balance if you want to stay at Amazon.
Work environment isn't necessarily geared towards a helpful team environment since everyone is trying to make sure they meet their deadlines and not be the member on the team who gets focused on by the manager, as managers have quotas they have to fulfill.
Unreasonable deadlines mean that the work completed is usually of subpar quality, which increases the on-call load. Often not enough work is done on OE due to it not necessarily leading to profits in the same way that new features do. This can mean rough on-calls.
Focus more on work being done well rather than quickly. If work isn't getting done on time, it's important to see why rather than look for a scapegoat and continue to push unreasonable deadlines to ensure profit margins. It's better to retain current talent and ensure the systems being worked on are handled by people with a lot of experience with them, rather than relying on turnaround and completely new engineers who have no idea what they're doing to meet unreasonable deadlines.
It was easy and to the point. The interviewer was sweet and allowed me enough time to think about how to approach solving the problems. The coding question asked was for an inventory and managing it. It was an easy solve with the right data structure
The interview process was quick, consisting of three panels: technical, behavioral, and system design aspects. The interviewers were friendly, approachable, and helpful. Overall, it was a very positive and smooth experience.
First was an exam of problem-solving with 2 questions. Then 4 interviews over 2 days, or all in 1 day after the exam passed, but I didn't join them; I just did the exam.
It was easy and to the point. The interviewer was sweet and allowed me enough time to think about how to approach solving the problems. The coding question asked was for an inventory and managing it. It was an easy solve with the right data structure
The interview process was quick, consisting of three panels: technical, behavioral, and system design aspects. The interviewers were friendly, approachable, and helpful. Overall, it was a very positive and smooth experience.
First was an exam of problem-solving with 2 questions. Then 4 interviews over 2 days, or all in 1 day after the exam passed, but I didn't join them; I just did the exam.