3 ms·
I guess I don't understand why companies do this process. When I was hiring Senior engineers for Computer Vision and 3D rendering jobs my process was thus: 1.
by AndrewKemendo 9y ago
I guess I don't understand why companies do this process.
When I was hiring Senior engineers for Computer Vision and 3D rendering jobs my process was thus:
1. Post job and simultaneously search for engineers we thought were a good fit technically
2. Reach out to people I thought were qualified based on their specific previous work that was related to the job I was hiring for
3. Review submitted applications for relevant experience
4. If we thought it was a technical fit, we would do a <30 minute team phone call with some basic work history questions, description of role/salary and work logistics (remote, dev environment etc...)
5. If we were satisfied with that, send them a <10 hour total, paid, production project at an agreed upon hourly rate. If the candidate didn't have the required IDE etc...it would basically be pair programming
6. Review code, speed and communication
7. Send a hire/no hire decision immediately
From first contact through Steps 4-7 it would ideally take less than a week, depending on the candidate's schedule.
We were only burned on this process twice.
Once the guy kept trying to negotiate salary up over two weeks so that he could get a higher price somewhere else.
The second time, the guy did well with initial production, but over time he ended up using local college interns to write his code, who got other jobs and his commit speed fell off of a cliff.
Since we are a remote team, trust was paramount, and we trusted quickly by default. Nobody ever had complaints about the hiring process and we had a higher than average success rate for hiring fantastic developers and getting quality code into production quickly.
We never asked current salary because it wasn't relevant. I knew what I could pay and that's what was offered. If they asked for more and were worth it, then I would try and find money to make it happen, but generally it wasn't an option.
I would do it the same in the future.
- matwood 9y ago> The second time, the guy did well with initial production, but over time he ended up using local college interns to write his code, who got other jobs and his commit speed fell off of a cliff. Sounds like you should have moved him to management.
- warrenm 9y ago>We never asked current salary because it wasn't relevant. I knew what I could pay and that's what was offered. If they asked for more and were worth it, then I would try and find money to make it happen, but generally it wasn't an option. Thank you! Some honesty and forthrightness for a change. (It's something I put in a blog post (https://antipaucity.com/2013/03/25/what-to-offer-to-be-the-best-possible-employer-ever/#.Wt-MtdPwbgo https://antipaucity.com/2013/03/25/what-to-offer-to-be-the-b...) 5+ years ago ...yet have only seen done once in my career)