Ask HN: When should the dev team get involved in the hiring process?

Re:Ask HN: When should the dev team get involved in the hiri... by nurturelabs on Wednesday March 17, 2021 @09:51AM (#26491214)

We do it using paid try outs - mastered by Automattic.

It works this way: 1. Basic screening 2. Small take home assignment 3. Code review and 1-1 interview 4. Paid try-out for 3/4 weeks

This works very well for hiring Junior level developers. We have found gems using this technique.

Need a service to do it for you - try OutTeam. - https://outteam.nurturelabs.co/

[ Parent | on HN ]

Re:Ask HN: When should the dev team get involved in the hiri... by softwaredoug on Wednesday March 17, 2021 @11:28AM (#26492566)

Yes I'm curious how this works. I don't expect a dev to be productive for some time, maybe months. And for isolated, self-contained tasks, like those that make a good intern project, it takes time & effort for the dev team to set those up so someone can be successful at it.

[ Parent | on HN ]

Re:Ask HN: When should the dev team get involved in the hiri... by nurturelabs on Wednesday March 17, 2021 @04:37PM (#26496484)

Generally the tryout projects are the projects the company is already working on and make the candidate work parallelly on them. After the try-out period is over they assess their work by comparing it with current team's work (obviously factoring in they were not working full-time)

[ Parent | on HN ]

Re:Ask HN: When should the dev team get involved in the hiri... by vp8989 on Wednesday March 17, 2021 @10:33AM (#26491787)

This sounds interesting. It feels like you would have to have a super smooth on ramp to productivity, otherwise you are getting terrible signal from the try outs.

Ie. you don't want to hire dev A because it took them just 2 weeks to figure out how to deploy a change to Prod instead of 4.

[ Parent | on HN ]