r/javascript • u/thecodeboss • Jul 21 '16
My Interviews with Amazon
https://thesocietea.org/2016/07/my-interviews-with-amazon/7
u/Stockholm_Syndrome Jul 21 '16
Based off of those offer threads in /r/cscareerquestions, the offer they gave you seems a bit low in terms of equity... Especially for a senior dev. Did they offer a signing bonus at all?
3
u/thecodeboss Jul 21 '16
Yes - there was a 20k bonus the first year (allocated with salary), 15k the second year, and nothing after that
1
u/tebriel Jul 22 '16
So they're just begging people to quit after three years then?
1
u/Stockholm_Syndrome Jul 22 '16
well no at that point your equity starts vesting like crazy
1
u/tebriel Jul 23 '16
That only works for some employers. I've worked at startups where you are allowed to buy stock options after so much time, and you get nothing when it goes out of business.
it's dumb. I'll take cash any day over "promises".
11
u/YvesSoete Jul 21 '16
There's this rule, you take the numbers you read on reddit about salary and do / 3 to get real world numbers
1
5
Jul 21 '16
which video series?
16
u/thecodeboss Jul 21 '16
For data structures, this was it. https://www.youtube.com/playlist?list=PL2_aWCzGMAwI3W_JlcBbtYTwiQSsOTa6P
I learned a ton from it. I didn't watch them all - but easily half of them.
1
u/SuperFLEB Jul 22 '16
You know, if you'd have told me I wouldn't mind learning from a video, say, 5 years ago, I'd have called you crazy. Books were the way to go-- videos are either tedious or shallow. But in the past two years or so, video programming training has really stepped up in quality, even the free stuff on YouTube, and I find I prefer video because it cuts out the a lot of the bullshit and boilerplate from the flow.
Now,if all these video training sites would consolidate, or at least offer ala-carte, so I didn't have to pick which little subset of training I wanted to drop my $100 a year on.
7
u/webdevbrian Jul 21 '16
Great write up.
Similar experience with a recruiter saying "oh yeah we can work with that" then going through the whole process only to find out they were barely 75% in the beginning range I gave. Happened to me only once, but I was beyond pissed.
Can't believe the recruiter you had did that to you too, and ever since then I make it abundantly clear that "please confirm with the company that this range is doable please" and I recite my story having gone through it in the past, and that the relationship I had with the recruiter at the time was tarnished forever, plus that I'll most likely be sharing the story to stay away from them and the company they work for.
(I also tossed you an invite on untappd :) )
1
2
Jul 22 '16
Wait, you said you wouldn't do it for less than 170k, but they offered you low 6s (let's say 120 all-inclusive) and you said you were making half that in OKC? So 60k? Man, that's ballsy.
2
u/thecodeboss Jul 22 '16
You pretty much hit it right on the head salary-wise. I too thought it was ballsy, but after digging into Seattle cost of living, it started to seem less ballsy and more necessary to maintain a nice standard of living.
19
u/franksvalli Jul 22 '16 edited Jul 22 '16
Thanks for writing this up! These questions that involve walking the DOM are always good practice. I imagine the back and forth could go like this:
I'll use jQuery's $('.someclass')
Ok, how about no jQuery?
I'll use document.querySelectorAll('.someclass')
Ok, how about if the browser didn't support qsa?
I'll use document.getElementsByClassName('someclass')
Ok, let's theoretically say the browser doesn't support that either.
Dammit! Ok, time to write the recursive DOM-walker.
These questions for senior JavaScript positions always seem to involve some sort of manual DOM traversal. I remember bombing an interview because I couldn't whiteboard a DOM contains function from scratch. If I had to figure that out on my own, I could've eventually done it in a normal work environment, but these folks assigned a lot of value to being able to whiteboard it, which I hate...
In a real job situation we've only used whiteboards for architecture diagrams, which is definitely a practical skill. Folks almost never write code on whiteboards except when actually administering other interviews...
5
Jul 22 '16
I remember bombing an interview because I couldn't whiteboard a DOM contains function from scratch. If I had to figure that out on my own, I could've eventually done it in a normal work environment, but these folks assigned a lot of value to being able to whiteboard it, which I hate...
I know what you mean. I had a whiteboard question about something silly (how would you reimplement a bind-like function yourself) and I blanked. Once I got onto the buss after the interview I smacked myself on the head because I figured it out ...
1
u/TeamHelloWorld Jul 22 '16
manual DOM traversal
Isn't this a tree traversal? I mainly code in JS and I've never had this as an interview question. My intuition is that dfs or bfs is what they want to hear. But then again, without looking at MDN I don't know if I can answer this.
2
Jul 22 '16
Yeah, it's basically tree traversal. And let's face it - each of us would do a "mdn + question" query in Google. We're not expected to know the answer to life, the universe and everything - we're expected to know how to ask the question, where to find the answer and know how to use it.
1
u/SuperFLEB Jul 22 '16
At least that's one place where whiteboarding can be advantageous. Your "code" isn't going to break because you wrote "node.methodWhoseNameIForget()".
3
1
u/TeamHelloWorld Jul 22 '16
The new trend is to use a jsfiddle-like editor and have a "pair-programming" session.
1
u/SuperFLEB Jul 22 '16
I've done that when I've interviewed people. JSfiddle with its Collaboration worked decently well (I was the remote person , so we had to have a screenshare of some sort). Lots of "finish this, replicate that, look at this code and talk about how it works" Just like whiteboarding, it usually devolved into more discussion and no completed code (or utter defeat and no code-- the joys of hiring for "entry level"), but that's par for the course, I think.
It worked pretty well, though, as a sort of whiteboard that didn't depend on handwriting skill.
1
u/TeamHelloWorld Jul 22 '16
it usually devolved into more discussion
I like this. I've practiced enough "puzzles" to grok most interview questions. I would rather talk about design and architecture. I think a lot of interviewers forget it's a two-way street.
19
u/chtulhuf Jul 21 '16
I’m sure some of you out there would kill me for not taking the opportunity to work at Amazon.
You didn't really want to relocate AND they offered you a lot less than originally agreed? You had all the reasons to not take that offer.
4
Jul 21 '16
Not agreed, was led to believe.
Nobody starts a conversation with "If you get this job, can we agree that 200k is a good number?"
1
u/BerserkerRedditor Jul 22 '16 edited Jul 22 '16
In addition, having worked for (some) and at (many more) quite a number of the large ell-known IT companies as well as at a (messy) startup, I don't understand that infatuation with large enterprises.
I see a huge disconnect between rhetoric and reality:
We pretend to love capitalism, personal responsibility, freedom - but when it comes to our own lives the majority of people flock to the least capitalistic, lowest freedom environment there is. They want a BIG entity to live under its umbrella, executing its commands.
No misunderstandings - I see nothing negative at all in this. In fact, it shows that humans like collaboration and to be and work with each other, finding safety among our pears, watching out for one another. But it's so very different from the marketing and PR of and for our societal model(s).
2
u/SuperFLEB Jul 22 '16
I think it's less a matter of personal responsibility, and more a matter of "I want to be the kind of person who I read about in the news and admire", and you can't really get that from some regional-level business that just does work all day. You can't get recognized for making Amazon's next big thing if you work at some small-fish shop in nowhere. At least if you're a cog in the right place, you're that much closer.
(Personally, I've never been that big on names, at least not so much as to sacrifice happiness chasing one. And I might be wrong, but it seems like a lot of the big "hotshot" places do try to dazzle with the cachet to distract from inadequacies or excuse cutthroat practices. Forget that... I'll work a solid 40 at a place I can stand, and self-actualize on my own terms.)
4
14
Jul 21 '16
It's odd that after you said you wouldn't do it for less than $170K they still low-balled you. In a way, it's awesome you were offered the job, but I would feel like they just completely wasted my time. I had a similar experience interviewing with Google although I didn't quite make it as far as you. Same thing came up for my wife and I about cost of living in the bay area. Ultimately it was a blessing in disguise that I wasn't offered the job because after spending a while looking at cost of living, commuting/traffic etc... I'm pretty sure they would have had to offer way more than they were considering.
4
Jul 21 '16
Same with me. I interviewed with Yelp and while I didn't get the job, I feel like it was better because of how expensive it is in the bay area. Still would've been a great opportunity.
Congrats on the interview OP. Thanks for the insight.
1
u/MahmudAdam Jul 21 '16
Similar interview process as Amazon?
3
Jul 21 '16
Yes, actually almost same exact, except for less back to back onsite interviews. Also was JS-based developer job but with PHP too.
2
Jul 22 '16
Who knows if they really low-balled him. A lot of places have wide pay fluctuations based on skill. Maybe Amazon was willing to pay 170 if he was a top tier but after the interview they decided he was "only" senior tier.
2
u/SuperFLEB Jul 22 '16
They want some rube blinded by the big name. That wasn't you.
Though I'm more surprised they waste all their time and money to lowball people. Plane rides and per-diems for every sucker you pull in seem like a waste when thrown after bad. Of course, I suppose a low enough ball can still make up for a few wasted trips.
4
Jul 21 '16
Well, I'm gonna play devil's advocate in this case.
Probably the 170K-200K was a possibility initially, but only if the candidate skills were in that range too according to interviewers' judgement (of course, this is a subjective evaluation, and $200K required skills will vary from company to company).
3
u/amznta Jul 21 '16
very few people make that much in salary at amazon. a number like that is possible in total compensation, which is a number amazon uses which incorporates salary, stock grants and bonuses. bonuses tend to be there for the first two years while you are granted very little stock, and then the next two years you'll get the bulk of the stock granted. AMZN trends upwards, so it's not a terrible deal, but you will get smaller paychecks after the first two years.
2
Jul 21 '16
I see! (as an European, I'm not familiar with USA salaries).
If that's the case then, I agree the recruiter should have mentioned that part of the 200K would be passive and not part of the actual paycheck.
5
0
Jul 22 '16
[deleted]
2
u/whompalicious Jul 22 '16
Seattle is not the Bay Area. Living expenses are a lot cheaper comparatively.
2
1
Jul 22 '16
According to this report, Seattle is the best place to live when considering salary vs. cost of living.
3
u/am0x Jul 21 '16
Low balled but stock options plus retirement and health insurance aren't cheap either. Also have to factor in paid vacation. If he were at $100k it would be more like $120-140.
1
u/rob132 Jul 21 '16
Yeah, but he said at the beginning that his requirements were X. If they come back with <x, then they wasted his time.
0
Jul 22 '16
[deleted]
2
u/am0x Jul 22 '16
Is Seattle considered "The Bay"? Cost of living in Valley is much, much higher.
I mean I make less for the same job title, but I live in a midwestern city (~2mil pop) where I can buy a house with a big yard for under $100 sq/ft near downtown.
1
1
u/franksvalli Jul 22 '16
Very good decision.. stay far, far away from the Bay Area, at least until the next housing crash. I just escaped recently... still looking for a good place to go to though.
1
u/kungfooboi Aug 04 '16
Thanks OP for the article, I found it very insightful.
I'm starting out a career in development but I was curious: what does your background in this industry look like for Amazon to reach out to you directly?
1
u/thecodeboss Aug 04 '16
Feel free to check out my LinkedIn - https://www.linkedin.com/in/alkrauss48. It has links to my personal site too.
3
Jul 22 '16
Thank you sharing this.
I'm a recent boot camp grad and in the middle of my job search. Everything you shared is consistent with how we were prepped, but it's great to see a real world example.
Whiteboarding is still a weakness for me, but I'm still working on it every day.
6
u/jewdai Jul 22 '16
apply to smaller companies. They need engineers too and pay nearly as well.
Additionally, it wont be as hard to stand out at a smaller organization than a larger one.
1
3
4
u/MWChapel Jul 21 '16
Low six figures is really not worth it.
7
u/Is_At_Work Jul 21 '16
That's the problem with big companies that attract talent, they will get people either way and get away with underpaying.
-8
u/YvesSoete Jul 21 '16
hahaha, let me guess, you're still a CS student, right?
9
u/Is_At_Work Jul 21 '16
... no. I'm a manager with 25 years of development.
Edit: I'm not on the US west coast though, and I've always worked at smaller companies. Maybe my judgement in this case is just wrong.
2
3
u/jewdai Jul 22 '16
Not sure if that's sarcasm.
I'm in NYC and most job offers i see are either a downgrade on my salary or like 5-10k more than I'm currently making. (which after takes is halved )
Why would I risk everything that I currently have for a measly 2.5-5k for what could be a disaster organization to work with?
Asking for $170k is not unreasonable given the demand and cost of living. Fuck bloomberg will pay $190k for a 3-5 yr experienced dev with a CS degree
2
u/MWChapel Jul 22 '16
Are you responding to my comment? If so, no, it's totally not sarcasm. Low 100's in Seattle would be entirely too tough to live on when you can get that in much cheaper locations in the US.
I wouldn't move to Seattle for low 100's.
0
u/milyway Jul 22 '16
an get that in much cheaper locations in the US. I wouldn't move to Seattle for low 100's.
I'm not aware about cost of life in Seattle, but isn't 100k a decent amount if you don't have a family?
2
u/_drif Jul 21 '16
I work at Capital One where they get away with this by having "senior" be mid-level and calling actual senior developers "principals". I was hired as an "associate" not knowing that meant Junior. grumble grumble
14
2
u/swanky_swain Jul 21 '16
The interview process sounded pretty good up until you mentioned whiteboard coding. Can you expand a bit on that part? I've only had one interview where I was required to write code on a whiteboard and it was a disaster. For one, I'm left handed so easily smudged and I'm also a horrible drawer, so even writing something simple was hard. I much prefer using a keyboard.
3
u/am0x Jul 21 '16
I'm blown away with how easy the code questions were, though I had a similar experience when interviewed for another fortune 50 (then) company but the questions were much more difficult.
4
Jul 22 '16
Easy is a lot different in person versus when you have time to think and Google a little bit. Also when you have time limits, things always take longer than you think.
5
u/am0x Jul 22 '16
Well I mean these were things I did daily as a junior dev at my first job for a company not even 1/50 the size.
1
u/chemisus Jul 22 '16
It's the talking it out as well. Having to explain basically line by line what you are doing and why you are doing it.
1
u/_drif Jul 21 '16
I wouldn't say easy so much as practical. They seem like things you might actually need to do. That circularly linked list could work really well for a bi-directional slider ;)
1
u/seekweb Jul 21 '16
Thanks for sharing, it was a great read. Congrats on the offer and ultimately making the decision that was right for you and your family.
1
1
Jul 22 '16
Good story. Having worked as a software engineer for 23+ years in the Seattle area, I think you made the right choice. I had a reverse type scenario happen (moving from Seattle to a small town in a low population state). I was offered a great position, and I could have lived like a king there.
In the end, I stayed here because of family.
1
1
u/sonoxram Jul 22 '16
Great read, I was surprised at how fast the recruitment process is at Amazon. Except for the one month period to find a date for the plane, it was all wrapped up in like 2 weeks.
1
u/ECrispy Jul 23 '16
Thanks for your detailed post, its very helpful. My only comment is the interview seemed pretty easy compared to what I've read/experienced. I interviewed for a senior dev role a few years back (not front end) and the phone+onsite interviews were much harder.
I guess the frontend specific role comes down to understanding browser/DOM in depth much more, whereas in the general role they test for stronger CS.
1
1
u/rr1pp3rr Jul 22 '16
It's fortunate that you didn't fall for their bait and switch in terms of your compensation. Amazon is a notoriously terrible company to work for, especially if you value your family time.
Great write up.
0
Jul 21 '16
[deleted]
2
u/thecodeboss Jul 22 '16
Nah - I didn't even try negotiating. The offer was pretty substantially far off from my initial range - and honestly, it became more of a "do we want to move to Seattle" type of talk vs a money talk. That said - if the initial offer was closer to what I was expecting, then there's a good chance I would have tried to negotiate.
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.