4 ms·
You're exactly right. If you get some dork that wants you to code during an interview then walk out immediately. That's not how the real world works. That sa
by mikerichards 11y ago
You're exactly right. If you get some dork that wants you to code during an interview then walk out immediately.
That's not how the real world works.
That said, as a senior software engineer, you should be able to get on a whiteboard and brainstorm and defend some architectural designs.
Even then, it's so much more important that you're all on the "same page" and can collaborate on problem solving, rather than they hoping your freaking Richard Feynman and will solve cold fusion for them
- chad_strategic 11y agoAmen, I swear there where a 100 times I should have walked out of interviews. Most of the time, I would have been more than happy to burn the bridge.
- nine_k 11y agoWhy, coding an utterly simple problem during an interview is fine. The purpose of doing this is to show the process of thinking and the ability to produce, explain, and modify simple code. BTW ability to identify the missing pieces and google for them can also be checked, for it's valuable. Any thing that's longer than 10-15 lines should be a quiet-room task or a do-it-at-home task.
- tezzer 11y agoI disagree completely. Every once in a while someone will slip through phone screens, etc. who does not have the foundational knowledge I want in someone who works for me. Asking them to write code to traverse a tree or implement strcpy in the language of their choice shows me if they lack the basic skills to continue taking up my time. Then we can work our way up the stack to debugging, design, architecture, and domain-specific knowledge.
- jghn 11y agoUh, we have candidates code. We also let them use their laptop and consult any resources they want. What's wrong with that?