Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Ex Amazon here. I never heard of leetcode style interviews at Amazon.


As someone who's interviewed there and received offer (though for internship), for entry positions, internships + their lowest level of engineer (don't recall the name), I can confidently tell you they mainly use leetcode with some Amazon principle questions too


I literally interview on purpose with Amazon to waste their time (revenge for them mistreating my partner). After at least 10 full onsites, I can tell you that Amazon uses leetcode style interviews in every single one of those onsites.

Feels nice to come into their stupid contrived behaviorals and not even care about the “Star” method or their stupid leadership principals. I even straight up told them in one interview that their principals were stupid and victim blaming. I’m shocked that they haven’t blacklisted me yet - and doing so would be nice because Amazon recruiter spam is actually quite annoying.


I was in Amazon years ago and there wasn't a standardized set of questions. At the time I never heard of teams using leetcode style questions - things went downhill I guess.


I would also be a lot richer if I was able to create BS of this magnitude but I can't. Here's the practice test they gave me:

https://www.hackerrank.com/test/63ek10mhil5/60d306ab105867d8...


So what? The log parsing thing is a reasonable question, not some obscure bitshift find-a-binary-paindrome hack.


The so-what was just to confirm that Amazon do leetcode interviews, contrary to your statement.


If you call any coding test "leetcode like interviews" then YES


I'd consider

- a coding test in a short time frame (30-90 minutes)

- implementing some singular function that expects a singular answer

- expecting time/space complexity optimizations, often those not naively thought about in said short time frame

- in synthesized test environments (as opposed to something representing a real world environment)

to fall under "leetcode like interviews". Log parsing can fall into either camp depending on the prompt. Once it's asking you something esoteric like to locate a timestamp in Log(N) time it starts to fall into Leetcode territory.


Then I was right. And it seems there are a lot of sour grapes in this thread...


You're slowly getting it




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: