3 ms·
I see a lot of drawbacks to the consulting project: 1) Anti-moonlighting clauses 2) Time commitment from both parties 3) Tax/thought overhead to signing agre
by bri3d 13y ago
I see a lot of drawbacks to the consulting project:
1) Anti-moonlighting clauses
2) Time commitment from both parties
3) Tax/thought overhead to signing agreements and getting paid. This way I'm a 1099 everywhere I interview. There's a reason I'm not an independent consultant full-time.
4) Different challenges. How do you objectively, fairly evaluate candidates when they're given a different issue to fix or different feature to implement?
But I agree that work-samples are essential to good hiring.
A staged, small-challenge approach (like Thomas Ptacek / Matasano use) seems better to me from the standpoint of an interviewee for a few reasons:
1) Less overall time commitment.
2) Fail-fast. If I blow the first hour(s?) long screen, I'm done. No weeks of work involved.
3) Consistent, fair evaluation. Presumably a set of "canned" challenges are used and the time taken and quality of output can be evaluated directly against the performance of others.
- sliverstorm 13y agoSpeaking of moonlighting clauses, can you imagine the legal shitstorm if you were to moonlight for a direct competitor? There's no angle in which that doesn't look bad.
- Jemaclus 13y agoMy company's direct competitor contacts me on a weekly basis to try and poach me. I'm super, super highly qualified for that job, and I could probably leverage a massive raise... but I would feel so, so dirty for doing that. It's nice to know I still have morals. ;)
- sliverstorm 13y agoIt's fine to go to a direct competitor, I think. I'm just saying working for both at the same time would be... well, probably career-ruining in my line of work. I believe our little industry has an unwritten rule of 2-week minimum cooldown when switching companies.