1. Applied online via the Careers section of their website. Really just did it on a whim, didn't think I'd be hired at all since I did not meet their "5 years minimum professional experience". 2. Was contacted to set up a phone interview screener. Was incredibly excited just to make it to this point! A guy asked me some general questions, nothing too big or difficult. Mostly it was in regard to a hypothetical situation: "What would you do if it turned out you didn't have enough time to complete the project?" (I was actually asked that multiple times throughout my interview experience. 3. Went great, said it was a "fascinating conversation". Three days later I got another email saying I had moved on to the next round. This time they asked for writing samples: developer guides, API reference docs, and "getting started" guides. I provided some of these from my current position, as well as some stuff I had done for school and other hobbies. Really didn't think my developer and API reference documents were too strong, so I figured it wouldn't be enough... buutt it was! 4. Got contacted, saying I passed the "writing test"! Woo. Great. Then I had to do ANOTHER phone interview with an editor on a similar team. She was really cool, obviously knowledgeable. She asked me a couple of questions that totally threw me off, but all I did was think out loud and it worked well. We worked through some of the hypothetical problems, etc. I accidentally name dropped a name of a project I was working on that was supposed to be secret, but she didn't notice and I sort of acted like it didn't matter. At this point, I'm super glad I even got to talk to these people. It was a great experience just to go through the rounds with some of the best people in the business. To make myself remain sane, I just assumed and told myself I didn't get the job. As a result, I started applying to other places, putting my feelers out, just so when I got the inevitable "sorry, but you aren't what we're looking for" email. 5. Well, I actually got invited for an on-site interview. Totally was blown away by that. They asked me a lot of questions in the invitation email: current salary (including all benefits, bonuses, etc.), my compensation expectations, start dates, all sorts of stuff. Funny thing is, I was on an airplane when I realized I had lost my keys in security. So I freaked out hoping to call the airport's lost and found. So I paid $9 or $10 for an hour of WiFi to look up the process I'd inevitably have to go through to get my keys. Well, my phone auto synced my email and bam: we want you to come interview. 6. So, scheduled the interview. Ended up lasting about 6 hours. I met 6 Amazonians. Mostly editors, writers, the hiring manager, and two developers. I'll be honest: it was the most difficult thing I've ever done in my life. However, I knew my stuff. I was prepared and comfortable. I made sure to keep things light. I would say throughout the day my interviews progressively got more difficult. I was also placed in a small, flouresecent orange room for all of my interviews, and by 4 PM my eyes were killing me. For the on-site interview: - KNOW YOUR TECHNICAL STUFF. You WILL speak to developers, maybe even two. Be prepared to talk about HOW you would document a feature or service. How would you start? What is your process? How do you scope a project? Where do you see documentation's role in the overall business strategy? - Be prepared to troubleshoot hypothetical questions. Frequently I was given a scenario to which I replied an answer. Almost every single time, especially with my last two interviews, I got "What if that didn't exist?" or, "What if you can't?" So, BE PREPARED TO BE ABLE TO PROBLEM SOLVE ON THE SPOT. It's tough and tiring, but you have to be able to do it! - I would seriously ask to be moved to a room with a cooler paint color or for them to dim the lights or something. It would've helped me relax, but I think it might've been part of the whole stress test. - The interviewers will type the entire time. If you find that distracting, just prepare yourself for it and maybe find a way to ignore it. 7. A day and a half after the interview, I got an offer email saying they were prepared to invite me to the team. I was elated, did a bit of negotiating, and bam, here I am. All in all: focus on situations! If they like your writing samples, they like your writing ability. Now they need to know how well you deal under stress. Think of scenarios and your past experience! And, always, always, always, connect your ideas and solutions to the hypothetical problems to either your schooling or your previous work experience. Concrete examples aren't as flimsy when the interviewers are going to inevitably let a tornado loose in the room. I can't wait to join the team. Overall experience was great. A+++ would interview with again.

The Amazon interview process is long but very well‑organized and helpful. It not only allows the company to identify the right candidate but also gives applicants a clear opportunity to understand if the role matches their career goals. I found the interviewers professional and respectful, and the overall experience left me with a positive impression.