Our mission: To be Earth's most customer-centric company.
What unites Amazonians across teams and geographies is that we are all striving to delight our customers and make their lives easier. The scope and scale of our mission drives us to seek diverse perspectives, be resourceful, and navigate through ambiguity. Inventing and delivering things that were never thought possible isn't easy, but we embrace this challenge every day.
By working together on behalf of our customers, we are building the future one innovative product, service, and idea at a time. Are you ready to embrace the challenge? Come build the future with us.
Apply now on amazon.jobs:
It’s Always Day 1
At Amazon, it’s always “Day 1.” Now, what does this mean and why does it matter? It means that our approach remains the same as it was on Amazon's very first day: We embrace new ways of doing things, strive to stay nimble, make decisions quickly, and always focus on delighting our customers. We have the scope and capabilities of a large company, and the spirit and heart of a small one.
In his 2016 letter to shareholders, CEO Jeff Bezos shared his thoughts on how to maintain a Day 1 mindset. Read the full letter here.
Our Leadership Principles
Our Leadership Principles help us keep a Day 1 mentality. They aren’t just a pretty inspirational wall hanging. Amazonians use them every day, whether they’re discussing ideas for new projects, deciding on the best solution for a customer’s problem, or interviewing candidates. Explore all of our Leadership Principles here.
Diversity and Inclusion
We value individual expression, respect different opinions, and work together to create a culture where each of us is able to contribute fully. Our unique backgrounds and perspectives strengthen our ability to achieve Amazon's mission of being Earth's most customer-centric company.
Our Affinity Groups bring employees together across businesses and geographies. With executive and company sponsorship, these groups play an important role in building internal networks for career development, advising Amazon business units, leading in service projects, participating in policy discussions, and reaching out to communities where Amazonians live and work. Since 2016, enrollment in Amazon’s affinity groups has more than doubled in more than 90 chapters worldwide.
Visit our Diversity & Inclusion page to learn more.
Our application and interview process differs from role to role, but the main ways we get to know you are through your online application, phone interviews, and in-person interviews. To check out a comprehensive list of interview preparation tips, visit our Interview Preparation pages on Amazon.jobs.
Key information and tips:
Search and apply to open roles on amazon.jobs.
At Amazon, we invest in the communities where our employees and customers live. Our contributions can be seen in many ways, and these are just some of our efforts to give back.
As a new college graduate or intern joining Amazon, you can have multiple opportunities to innovate and solve real-world, complex technical and business problems. We have career opportunities available for undergraduates and advanced degree students across the globe with diverse academic backgrounds.
Visit amazon.jobs to view positions in the following areas:
Helpful (16)
I have been working at Amazon full-time (Less than a year)
Pros
Big company with a small company feel. Very entrepreneurial. Management facilitates your ideas that push the business forward
Cons
Big company and yes sometimes it takes a while to find the information you are looking for. Global company and sometimes that information is with someone who is on other side of the world.
Helpful (1495)
Application
I applied through other source. The process took 4+ months. I interviewed at Amazon (Seattle, WA) in May 2013.
Interview
Called out of the blue, asked if I'd be interested in interviewing. Still not entirely sure how they got my name. Had first phone interview the next week, asked no personal questions, all technical in nature. Total of 3 phone interviews and an in-person trip out to Seattle.
Took about 4 months start to finish. The people in the in person interview were wonderful. Very smart, laid back, and understanding. Got lunch, small tour of campus, and learned what I'd be doing. Got the offer 2 business days after the in person interview.
Sadly, I signed a NDA and I respect the terms of that. As such, I can't give you any specific questions, but I'll gladly give you the best advice I have.
Phone Interviews :
Phone interviews are sucky by nature. Coordinating a call from west to east coast alone is painful, add the fact that phones just take away the benefits of body language, and just make it harder to hear, and you've got a recipe for disaster. But fear not! Here are some helpful hints, some of which are obvious, some of which are not.
1. Get ready ahead of time. I just mean, get to the area you'll be doing the interview beforehand. I'd recommend an hour or more, just to get your nerves ready. Breathe, get used to the surroundings, and get everything laid out ahead of time. Which brings me to...
2. I know it's a "programming" interview, but for the love of all things good, have a pen and paper ready and at your disposal. Bring a backup pen. Much like a printer, the pen will fail at the worst possible time. You may also need a laptop, as I was asked to do "on the fly" programming. But close anything and everything distracting. Speaking of...
3. Pick a spot where there are no distractions. You'll want your undivided attention on this interview. Don't have BookTweet or FaceSpace or MyGram or that crap open if you have a laptop. And I personally wouldn't pick a public space, you never know when an annoying parent will put their screaming child right beside you.
4. Breathe. Just breathe. Take a moment, stretch, and remember you got this. If you have trouble hearing, don't be afraid to ask again. Don't be afraid to say you don't know. Do as for clarifications, and state assumptions up front. Always re-state the problem as you understand it.
As for the content : For the love of God, know what a time complexity is, and how to determine it for any and all code you write. Know the time complexities of all sorts. Know all data structures, how to use them, and properties of each. (Insertion time, deletion, etc) Generally know what heck you're talking about. But don't talk too much. You don't want silence at any point really, but you certainly don't want to let the interviewer not get a word in. Know graph theory, tree theory, and all the fun stuff associated with more "complex" structures. Understand what your language does behind the scenes, as far as GC and compiling go. Know how your language use internal structures to manage the code/objects you write.
**Continued below**
Negotiation
As a recent grad, there wasn't much room for negotiation.
