News for hackers. Stuff that matters.
Re:How we interview engineers at CircleCI by nunez on Monday March 26, 2018 @06:13PM (#16683121)
This question is a red herring. I hate this question because the only acceptable answer is to ask candidates about their experience and make a gut feel on that. Which only works if your gut feel is properly calibrated. Which often looks like unconscious bias.

Anything else is "too much work" on the candidate.

A take-home? "I don't have time to work on unpaid stuff!"

A pairing session? "I don't have time to work on unpaid stuff!"

Software engineering trivia? "Why are they asking me to build a linked list when I'd just use stdlib in real life?"

Asking about stuff on the resume? "They've never worked on ${thing}; how could they judge me on it?"

Re:How we interview engineers at CircleCI by JoeAltmaier on Monday March 26, 2018 @06:22PM (#16683182)
Or hire them provisionally, and decide 90 days later. For instance. There are lots of ways to compensate Engineering hires without asking them to do unpaid work.
Re:How we interview engineers at CircleCI by nunez on Monday March 26, 2018 @06:36PM (#16683297)
That is problematic for a number of reasons:

1. Hiring a new employee into an existing team permanently affects the team's dynamic and morale. Bringing in a bad fit can have undesired cascade effects. Bad team members can cause other good team members to leave earlier than intended, for example. You can counteract this by having the entire team interview the candidate, but this doesn't scale for teams larger than, say, three candidates, doesn't work at all for distributed teams and takes their time away from work that needs to get done.

2. Hiring an employee is also a legal risk. Firing people in "protected" classes is touchy and can take a while, for example: https://www.entrepreneur.com/article/62846. You're also opening yourself up to unnecessary lawsuits that just add more of a headache for Legal to deal with...if you have legal. (Early-stage startups typically don't have legal teams.)

3. Hiring engineers is expensive beyond their base salaries. Firing bad engineers can be a huge waste of money.

If you're an early stage startup, you're better off hiring contractors for point work and taking time to find the best hires that you can. Later-stage or profitable companies can afford to not hire "false positives". At worst, a potentially-good candidate you're on the fence about can come back in six or twelve months and try again.

Re:How we interview engineers at CircleCI by JoeAltmaier on Tuesday March 27, 2018 @12:09PM (#16689866)
Contracting is a good idea - I was contracted for a week at a startup to see if it would be a good fit. We were both happy with the arrangement. The team found out if they could work with me; I could see their prototype at work and help sort out the issues.