4 ms·
This sort of interview is insulting. There are real problems to solve in business and elegant solutions to the 'next number in sequence' isn't one of them.
by jlcfly 11y ago
This sort of interview is insulting. There are real problems to solve in business and elegant solutions to the 'next number in sequence' isn't one of them.
- hackerboos 11y ago"Yesterday I went to a job interview, at a company in New York that had once built their stack (for managing online advertising) in Ruby but who are now transitioning all of their stuff to Clojure." I would have probably walked out or at least snarkily asked them if these types of algorithms are what's done day to day. The answer more than likely being no.
- recursive 11y agoThere's not really time in a 30 minute interview to pose a real business problem, much less have any meaningful representative work done, by which to judge the candidate.
- rhizome 11y agoWhy would you only allow 30min at the stage where the candidate is writing code? 30min is for the phone screen, in-person is when you're serious.
- ianstallings 11y agoAgreed. If I have you in the office I may talk to you for the rest of the day and I schedule accordingly.
- rhizome 11y agoAnd if you're LinkedIn you never communicate with them again.
- learc83 11y agoAnd by sticking to that limitation, you're seriously undermining the predictive power of your interview.
- recursive 11y agoYes, that's true. As a benefit though, I don't have to be a full-time interviewer, and can sometimes actually do my real work.
- iopq 11y agoThat's why it's really stupid to do that. You're testing something that's not going to be used at the job.