Software Engineer Interview Experience - San Francisco, California
Process
Based on the official interview guide, if you pass the resume screening, you should receive an email with a link to an online assessment, which we’ll cover below. But based on candidate experience, some still do receive a call.
During this call, the recruiter will discuss your interests to see what group or team would be best for you. They will also use this conversation to confirm that you've got a chance of getting the job at all.
You should be prepared to explain your background and why you’re a good fit for Amazon.
Questions
Given an array of integers arr[] of size n, the task is to rotate the array elements to the left by d positions.
Was this helpful?
Interview Statistics
The following metrics were computed from 34 interview experiences for the Amazon Software Engineer role in San Francisco, California.
Success Rate
Amazon's interview process for their Software Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having mixed feelings for Amazon's Software Engineer interview process in San Francisco, California.
Amazon Work Experiences
- 3.0Good Tech, Bad CultureSoftware Engineer • Current EmployeeSan Francisco, California, United StatesMay 7, 2025Pros: Tech and stack is good. If you find a good team, you can learn something transferable to other jobs.Cons: Oh, where do I start? Close to no raises with the new comp adjustments. Impossible to move up. Hostile culture.
- 2.0It depends on the team, but the company culture is badSoftware Engineer • Current EmployeeSan Francisco, California, United StatesFebruary 24, 2025Pros: Day 1 green card (if you have 1 year of working experience using your current tech stack). Easy interview for new grads. Well-established onboarding process. Easy to transfer to another team.Cons: Too much politics. Frugality: My manager wants us to take BART home from SF after team events and doesn’t want to reimburse Uber. Many nice folks get managed out just because there is a quota for PIP. Reorg every year, and there is no productivity benefit from these reorgs. It seems like just a way for managers to show their impact. There are principal engineers blocking all projects by raising the bar to show their impact. No one can disagree with them. 7/24 on-call, with many alarms at midnight. There are alarms just because the CEO complains that he couldn’t use some service as he expected, while there is very little traffic in the same use case.
- 2.0Great pay at a garbage placeSoftware Engineer • Former EmployeeSan Francisco, California, United StatesMay 27, 2023Pros: The pay is really good.Cons: The culture is really bad.
Amazon Interview Questions
