Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

How many "systems" do you think your run-of-the-mill startup has?

What is the alternative? As most of things in life, the answer is "it depends". It depends on the size of the company, the type of candidate they are looking, the industry, and so on.

But let's assume we are talking about the average startup that is neither looking for superstar candidates nor only looking for fresh graduates from Stanford. For those cases, I believe that one simple programming task, that exercises some of the technology required can be used as a screening filter. The task should not take more than 2 hours to reach a working state. If the solution presented by the candidate is satisfactory, then you go to the interview to discuss the solution and how they got to the solution, the things that were easy/hard, and so on. Then you ask about the things that are missing, and the candidate's evaluation on how they would like to tackle.

Is that a satisfactory alternative?



I feel like we are talking past each other.

> How many "systems" do you think your run-of-the-mill startup has?

These dont need to be production systems, they can in fact be simple systems used just for interviewing.

So in your alternative, how long does an engineer really spend on interviewing the candidate?


In my alternative, the engineer needs to:

- Check out the code and review the solution.

- Give a pass or "call for interview".

Let's say that is half-hour of work.

Only for the candidates that get called-in, you can have an hour-long interview. Make it two hours if if you want. It will still save the interviewer time, and allow a better use of the time together.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: