r/javascript • • Jul 21 '16

My Interviews with Amazon

https://thesocietea.org/2016/07/my-interviews-with-amazon/
331 Upvotes

107 comments sorted by

View all comments

56

u/thecodeboss Jul 21 '16

OP here. I know this topic has probably been posted many times - or at least something similar, but I still want to share my experiences with interviewing, being offered a job, and eventually turning down said offer with Amazon.

I'm posting this to /r/javascript because this position was for a Senior Web Dev position specializing in JS. /r/compsci seemed to like it, so I wanted to share it with you guys too.

This one goes out to all of you in a similar position who are interviewing, and want to know step-by-step someone else's full experience. And even if you're not actively interviewing with a tech giant (or anyone, for that matter) - I hope it still benefits you somehow.

5

u/MahmudAdam Jul 21 '16 edited Jul 21 '16

Any insight on what the interview (in particular, the coding portion) would be like for a junior developer?

16

u/amznta Jul 21 '16

Largely the same, but the expectations will be different. I can't speak for all of Amazon, but typically questions in my org stay the same, but the interviewer is looking for different things in the answers. Senior devs like the OP are being assessed for their systems design knowledge as much as their coding/algo ability, with much more emphasis on seeing the bigger picture and delivering end-to-end solutions that encompass knowledge beyond just writing code. More junior positions will focus more on basic coding knowledge and the likelihood that they'll be able to contribute relatively quickly and be a good candidate for advancement to the next level. Most importantly, junior devs are assessed on their ability/willingness to learn, admit when they don't know an answer, and demonstrate a curiosity and drive to become better engineers.

4

u/MahmudAdam Jul 21 '16 edited Jul 21 '16

If I may ask, how much of the coding interview involves general knowledge of JavaScript, HTML, and CSS vs. questions relating to algorithms and data structures?

7

u/amznta Jul 21 '16

It will depend entirely on the position you're interviewing for, the team that owns the loop, and the interviewer asking the questions. I do a ton of front-end interviewing and all of my questions are front-end specific - I try and model them after real-world front-end problems with multiple possible approaches/solutions. They tend to be algorithmic in nature, but not just "do this CS201 exercise in JavaScript". Think more like "how would you implement jquery's "closest" method?"

HTML and CSS aren't topics I spend too much time on. I focus on DOM APIs (or jquery if the candidate prefers) and knowledge of JS-the-language (prototypes, closures, callbacks/promises/async, best practices, etc). I usually ask one simple question with follow-ups for HTML and CSS because those topics are both much easier to teach/learn and also mostly solved problems for us. We tend to need JS engineers who know the front-end domain, not HTML/CSS wizards.

1

u/j1330 Jul 26 '16

Could I ask you what you would consider a good answer regarding the implementation of that function? I'm also curious if you would "solve" the problem in a kind of isolated context, or if you would look for certain design patterns or something to fit the function into a larger structure.

1

u/madcaesar Jul 22 '16

I never understood the how would you implement something that a framework does and has for years. It's like a graphic designer being asked how would you assemble a printing press :/ if I had to I'd Google it and figure it out, but why would I ever waste time on this?

4

u/SuperFLEB Jul 22 '16

Because you're both the designer and the pressman in that analogy. Your framework might do 90% of what you need, when you need 100%.

Or, you might need to start scraping bare metal to optimize when you have to push 1000 of something that the developer never pushed past 50. You might need to duck-tape together two disparate libraries with different modes of operation. You might have to dig into The Ancient Evil that Just Works to fix a bug or wire in a feature sometime.