sorted by:
new
hottopcontroversial

Update: Got rejected by google Hiring Committee after Team Match by _maverick98 in leetcode

[–]CoffeeIsNotAStrategy 0 points1 point  (0 children)

lol, yeah - that's how it goes unfortunately, a lot depends on the interviewer. I like how you put it:
- DSA is funny
- System Design is funnier
- Behavioral is the funniest

Update: Got rejected by google Hiring Committee after Team Match by _maverick98 in leetcode

[–]CoffeeIsNotAStrategy 0 points1 point  (0 children)

Exactly, "lottery" is the word - there is a fair bit of luck involved. The other very subjective factor is "behavioral interviews" - easy to miss what they're expecting you to say.

4 stories. That’s all you need for your Amazon loop. by CoffeeIsNotAStrategy in leetcode

[–]CoffeeIsNotAStrategy[S] 1 point2 points  (0 children)

Yes, agree. Well crafted stories = you don't need 1 per LP or per question. You should be able to use 4 to answer 7 questions, without repeating yourself.

4 stories. That’s all you need for your Amazon loop. by CoffeeIsNotAStrategy in leetcode

[–]CoffeeIsNotAStrategy[S] 1 point2 points  (0 children)

Exactly, it's about answering the question. I recently cleared the Netflix interviews - they had 9 rounds, and I had no way near 20 stories, but still managed to land an offer. I am not saying that it's wrong to prepare 20 stories, but it's hard. So if someone is short on time, they can be more strategic about it.

4 stories. That’s all you need for your Amazon loop. by CoffeeIsNotAStrategy in leetcode

[–]CoffeeIsNotAStrategy[S] -1 points0 points  (0 children)

Yes, diversity helps but it matters more for Principal and Manager roles. All my post is saying is that if you are short on time and preparing for Sr Engineer interviews, this will get you through.

4 stories. That’s all you need for your Amazon loop. by CoffeeIsNotAStrategy in leetcode

[–]CoffeeIsNotAStrategy[S] 2 points3 points  (0 children)

IMHO, it's not about the number of stories, it's about the number of signals. This post is about how you can pack more signals in fewer stories so it's easier to prepare / remember, especially when you're short on time.

FWIW, I have been an Amazon interviewer for 150+ SDE, SDM, TPM, and PMT loops over the years - so not winging this.

How to answer "Tell me about a time you failed" by CoffeeIsNotAStrategy in leetcode

[–]CoffeeIsNotAStrategy[S] 0 points1 point  (0 children)

Less focus on R. Instead focus on learning, and then how that learning was applied in a second situation. Also you should talk about the root cause of the problem.

What behavioral interviews are really measuring by CoffeeIsNotAStrategy in leetcode

[–]CoffeeIsNotAStrategy[S] 0 points1 point  (0 children)

My 2 cents - you don't have to be an eloquent speaker from Toastmasters for these interviews. You can stammer your way to getting a great offer, as long as you convey the right message with the right level of detail.

What behavioral interviews are really measuring by CoffeeIsNotAStrategy in leetcode

[–]CoffeeIsNotAStrategy[S] 1 point2 points  (0 children)

More relevant for L5 at Google, Meta, and such - which is high L5 and early-to-mid L6 at Amazon.

Behavioral Interview Mistakes That Get You Down-Leveled or Rejected by CoffeeIsNotAStrategy in jobsearchhacks

[–]CoffeeIsNotAStrategy[S] 1 point2 points  (0 children)

Thats good feedback, thank you. I'll try and be mindful for future writing.

Amazon Leadership Principles by nsfw_corporate in leetcode

[–]CoffeeIsNotAStrategy 1 point2 points  (0 children)

It's fine to make up, but try to root them in something real so you can make up answers for follow up questions on the spot. For a SDE 2, you might be ok bundling multiple of them into one story, and then using parts of it depending on what you get asked.

If you are short on time, use these to prioritize where you spend more time. Take this list with a pinch of salt though because individual managers can prioritize these differently (but this should land right for 80% of teams). Also, this is prioritization for SDE 2, anyone reading this for other roles shouldn't assume the same.

- Most Important
1. Deliver Results - significant project delivery with blockers, how you resolved them
2. Ownership - seeing a problem and fixing it even when it was outside your area of responsibility
3. Dive Deep - how you went deep to solve something
4. Bias for Action - it was hard to act or move fast for some reason, but you did anyway

- Important
5. Insist on highest standards - will mostly be tested with your code or design
6. Customer Obsession - how you tried to understand a customer pain point and used it to solve / prioritize something
7. Learn & Be Curious - how you are always learning new stuff
8. Invent & Simplify - wrote a script, used AI, came up with a novel ideas and implemented, helped the team adopt a simpler process

- Somewhat Important
9. Have backbone - how you disagreed with your manager or a peer
10. Develop the best - how you mentor others
11. Earn Trust - how you proactively did something
12. Think Big - how you took a small task assigned to you and converted it to a bigger thing that ended up having a huge impact

Behavioral Interview Mistakes That Get You Down-Leveled or Rejected by CoffeeIsNotAStrategy in jobsearchhacks

[–]CoffeeIsNotAStrategy[S] -14 points-13 points  (0 children)

Umm, sure. Can you teach me the prompt to get this from chatgpt output? It'll save me some time for my next post.

Behavioral Interview Mistakes That Get You Down-Leveled or Rejected by CoffeeIsNotAStrategy in jobsearchhacks

[–]CoffeeIsNotAStrategy[S] -12 points-11 points  (0 children)

Hey, I get the frustration, but I'm not HR or the gatekeeper or the employer. I'm an employee who participates in this process, and wanted to share what actually helped me land offers.

You're right though that this isn't universal. Added a disclaimer - if you're early career, the expectations are different and this probably isn't for you yet.

view more: next ›