3 ms·
My first interview was at a marketing company in Boulder, CO. They stuck me on one side of a long table with all the other developers in the other side. They
by newshorts 7y ago
My first interview was at a marketing company in Boulder, CO.
They stuck me on one side of a long table with all the other developers in the other side.
They proceeded to grill me on obscure gotchas and had me white board fucking solves for shit like palindromes.
At one point one of the developers stood up and said “look, it’s so easy!” And proceeded to write out his obviously premeditated/optimized one liner on the white board.
I didn’t know enough to respond with something like “I don’t write over optimized one liners because even I won’t remember what the fuck is going on 6 months from now”.
I remember walking back to my car so ashamed and embarrassed.
Interviews are supposed to be a prediction of your fit in the culture and ability to contribute.
In the past 10 years I’ve written lots of code, but more importantly I’ve shown up as a member of my team.
In the end, those interviews are good tests. Tests of culture within the company you’re interviewing...
- neilv 7y agoThat's an awful experience, and, unfortunately, all too believable.
- sircastor 7y agoReading some comments here, and having recently gone through a number of interviews, I'm contemplating taking my own CS questions to which I know the answers to see how the interviewers solve problems, and what happens when they don't have the answers to a given problem. I'm not sure how it would be received