4 ms·
We ask a couple difficult algorithms questions in our interviews but I also think that is pretty indicative of the day to day work you might have to be doing at
by cardine 10y ago
We ask a couple difficult algorithms questions in our interviews but I also think that is pretty indicative of the day to day work you might have to be doing at positions we hire for.
If someone is offended by being asked to code something like this then they are probably going to be offended by the work they'll have to do once they start employment.
Of course there are other parts of our interview as well, but I've found an initial interview with a difficult algorithms problem does a great job filtering out bad programmers. Once we've filtered out the bad programmers we'll do a second interview that involves code from a project we've used in production before.
- namaemuta 10y ago> If someone is offended by being asked to code something like this then they are probably going to be offended by the work they'll have to do once they start employment. I don't agree with you because it's not the same context. In a day to day job context, you can focus on doing it correctly while in an interview there are a lot of factors that can affect your focus/creativity/attention.
- adrianratnapala 10y agoIn my experience it is the opposite. At a whiteboard inteview, you can focus on the code and the algorithm. In the real process, you might on any given day also have to wrangle with your build system, meetings, the structure of existing code, the test setup, colleauges who need help, debugging tools. Now that might be an argument for why a whiteboard interview is inadequate. But not for why an whiteboard interview is distracting.