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

When I worked for a small research firm, we basically wouldn't have employment discussions with anyone who had a non-compete even if it seemed unlikely their current employer would go to the mat over it. Just the existence of a non-compete would have meant getting lawyers involved and it was just too much hassle and risk.

(It's also the case that one of our large competitor firms, at least at the time, put non-competes in place that effectively wouldn't let anyone who left work for any competitor. i.e. they couldn't do the same job at any other firm. And, apparently, they enforced these agreements rather vigorously.)



>When I worked for a small research firm, we basically wouldn't have employment discussions with anyone who had a non-compete even if it seemed unlikely their current employer would go to the mat over it. Just the existence of a non-compete would have meant getting lawyers involved and it was just too much hassle and risk.

Had a similar experience at my company. We worked as a subcontractor whose parent company lost a contract at renewal time to a rival. The rival did not sub out and instead approached our employees on site and hired one directly. The owners got in touch and told the new firm that we had a non-compete and their response was basically "Ok, that's fine. Let us know if you intend to enforce it. If not, we're hiring him. If so, we won't, but we're not subbing the work out to you. It really doesn't matter to us what you do, just let us know. If we don't here back from you by this time tomorrow we're not hiring him."

In the end I'm happy to say that management did the right thing and just let him go unmolested, but the hiring firm explicitly stated that his job wasn't worth the expense and hassle to them, and just threw the ball back at us.




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

Search: