Hacker News new | past | comments | ask | show | jobs | submit login

I accept the Amazon specific revision that "in the eyes of the reviewers, you did not meet the bar." The rest of the advice follows just as naturally from this premise. The only variable that is eliminated is the current application pool, which the candidate has no control over anyway. Performed ability level, interviewer perception, and "resume traits" are the variables any candidate should manipulate to increase the odds of being hired. The first two are very noisy, the later can also be a function of effort (the same information can be presented better or worse in a resume).

I reject the notion that Amazon's hiring practices are neither implicitly nor explicitly comparative. The notion of hiring candidates that "raise the bar" is explicitly comparative to existing employees. That said, I do not know the details of Amazon's hiring philosophy. I do know that internal promotion within Amazon is quota constrained and therefore implicitly comparative.




> I reject the notion that Amazon's hiring practices are neither implicitly nor explicitly comparative.

You are absolutely right on that. The core question that needs to be answered at each interview debrief is "when the next review process roles around, do we believe this candidate will end up in the upper half of the stack rank for their role/level?" It's a little more complicated than that as Amazon's stack rank is a two-dimensional rank that looks both at contribution-in-level and perceived growth potential, but in the end it's still a judgment call of "is this candidate better than half the people currently in this role."




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

Search: