News for hackers. Stuff that matters.
Re:So I refused a white board technical test and was asked t... by AnimalMuppet on Tuesday June 21, 2016 @01:48PM (#11947742)
> White board interviews are humiliating, especially if the level is pitched wrong. As someone with a career prior to starting grad school I'm sick of being treated like a child in the interview process and being given diddly little graph traversal problems when I used to building entire systems.

White board interviews are humiliating? Why? Because your sense of pride says that you're better than that? Is your sense of pride going to decide it's humiliating if I ask you to work on a crappy little side project for a month?

And, you're used to building entire systems? Great. In our interview process, we've got maybe half an hour for this kind of problem. Are you going to build an entire real system for us in half an hour? If so, I definitely want to hire you. But if not (as I suspect), then toy problems are kind of all we've got to see how you interact with a problem.

> The problem here is a mismatch in expectations.

Very much so. You expect the interview to be at the level that you work at, and we don't have time to lay the shared foundation to see how you really operate at that level. If we tried, the interview would be a week, not two hours. We don't have time for that, even if you do.

Re:So I refused a white board technical test and was asked t... by deadgrey19 on Tuesday June 21, 2016 @02:32PM (#11948164)
Being asked to write yet another depth first search implementation (honestly, 5/5 interviews at a large corporation were the same question) that any second year student can do is humiliating when your daily bread is building complex distributed systems. I still did it, because (unlike the writer) I understand that you do need to establish a baseline. As I've said, I've sat on the other side of the table, asked the humiliating question and seen the candidate fail miserably. It's a necessary evil, but it's still humiliating.

A less humiliating but still valuable interview (IMHO) is a systems design question. It should still be a whiteboard exercise, but it's a better test of problem solving and engineering skills. I don't seriously begin any system work without first doing the very same thing on a whiteboard myself. It's a useful on the job skill and a useful way to test skills of communication and collaboration in describing the solution.

With respect, if you're putting your employees to work on "crapy little side project's" for a month, either the projects are not crappy and have potentially large impact on the firm, or, you're wasting valuable resources.

Re:So I refused a white board technical test and was asked t... by AnimalMuppet on Tuesday June 21, 2016 @03:01PM (#11948441)
The "side projects" are large impact for the firm (either defensive or offensive, that is, either "save the day" or opening new opportunities), but they can still be well beneath the talent/skill level of the programmer assigned to it. If the programmer is going to feel humiliated by that, then we probably don't have time for that programmer.
Re:So I refused a white board technical test and was asked t... by deadgrey19 on Tuesday June 21, 2016 @03:12PM (#11948548)
IMHO, a good manager would communicate the importance of the project along with the spec of the project. "Because I said so, so do it" is not a good strategy for highly skilled, highly competent, highly intelligent people. The "why" is every bit as important as the "what". Presumably you wouldn't "waste" a good programmer on a simple task if it wasn't important. Similarly a good programmer would understand that business priorities means that some projects are complex and interesting, some are important and boring.

As an employee, if the manager is not a skilled communicator, it's not the sort of place I want to work for. As a manager, if the employee is cannot understand business priorities, it's not the sort of employee that I want.