5 ms·
I used to interview Senior Devs when I worked for Amazon. It's strictly part of the interview training process not to ask purely algorithmic questions (and yet
by fieryscribe 7y ago
I used to interview Senior Devs when I worked for Amazon. It's strictly part of the interview training process not to ask purely algorithmic questions (and yet some still do). I chose not to and it gave me much better data points.
I chose my next role because they didn't ask me those questions and instead asked how I'd tackle problems.
Engineers have enough market power to change this if we choose. For some reason, we just choose not to.
- Frost1x 7y agoI think it's a character and pride issue. You know you can solve such problems (sometimes even enjoy them) but the conditions you're solving them under aren't at all remotely reasonable. Giving up admits defeat and what makes you a skilled engineer, part of your identity/character, is that you rarely, if ever, give up on a problem and love a challenge. I think we should view this as a different challenge all together instead of the one presented. Let's understand the presented challenge is silly and look at the problem as a need to change the presented challenge to something all together different utilizing our skills.
- PretzelFisch 7y agoWhat do you mean by purely algorithmic? You still had a code challenge as part of the interview yes?