4 ms·
This is really not that hard to do right in my opinion. This is what we did for a "homework assignment" after a 30 minute phone and 30 minute team screen were a
by AndrewKemendo 8y ago
This is really not that hard to do right in my opinion. This is what we did for a "homework assignment" after a 30 minute phone and 30 minute team screen were already done:
1. Supervisor had candidate sign mutual-NDA, work for hire at $X/hr rate & IP assignment agreement on docusign.
2. Potential future supervisor gave the candidate access to a repo and assigned a production task that should take less than 10 hours to complete.
3. Candidate does the assignment, communicates with supervisor via email/repo where necessary and a check gets cut for the hours worked.
4. Hire/No Hire decision made
Should take less than a week in total.
- ghaff 8y ago>Supervisor had candidate sign mutual-NDA, work for hire at $X/hr rate & IP assignment agreement on docusign. This would be a violation of the candidate's employment contract at many companies.
- icedchai 8y agoPerhaps, but totally unenforceable... It's a non-issue. Developers are not slaves, and you cannot prevent them from doing outside work while looking for other jobs.
- wirrbel 8y agoDon't know about the US but here it would be reason enough for my employer to terminate me right away. This is the default for employments. For work on the side, I need to ask my employer for permission. My employer will then be concerned that all labour protection laws will not be violated, which for example means that my employer must accept that I might not be able to work overtime for them, with a side contract, because I would surpass a 10h per day threshold To cut the long story short: I would politely declined that model, even though I think it is sensible.
- sixstringtheory 8y agoIn terms of hours per day worked, what is the actual difference between doing an unpaid take-home test? Signing a contract is just being honest about the time it's going to take to learn about the candidate. What about onsite interviews, do you have to tell your supervisor that is the reason you are taking off work? Would they be OK with that?
- wirrbel 8y agoOne major problem is that the employer has the right to monetize work products that are close enough to your jobs work. So if my side project is writing a novel, there isn't much danger and the employer must basically grant the permission.if it is related to coding things get trickier. With a contract for coding I would basically transfer monetization rights to you. for that I would have to ask my employer. So I would not do take home exams that could appear to be consulting work etc. Of it appears to be a test, it is fine(r). Note that this is tricky for open source work too, you are doing on the side. (At least in my legislation). Contributions that are closely related to my work topics I usually ask for a permit according to company policy. For completely unrelated stuff (writing that interpreter in prolog, etc.) I assume my employer is disinterested (they really are). I cannot assume that for contract work with another company. Anyway, a judge, given a CONTRACT with another company that was not approved has the easiest case in front of them. This is the situation I want to avoid. I wouldn't bet on a judge to dive into the details on what stuff was coded in this situation. You mention the on-site interview. This is easy. It is not a consulting or contracting gig. So I don't need to get a side-work permit, and they are treated as any of my other absences when I don't supply a reason.
- icedchai 8y ago"Side-work permit"? Is that actually a thing?
- perl4ever 8y agoI don't know if that's a thing per se, but my former employer (Fortune 500 non-FAANG) quite definitely claimed any code I wrote during my employment whatsoever. I did one time formally ask (just to see what would happen) whether I could volunteer at the Red Cross, which demanded I sign a boilerplate intellectual property agreement saying anything I made as a volunteer belonged to them. The letter of my employment agreement was incompatible as all IP I made belonged to my employer. The question went all the way up to the corporate counsel, who presumably said "obviously a troublemaker wasting my time with this sh*t" and responded "NO". I thought about writing the CEO because it was absurd you technically couldn't volunteer with the Red Cross, but of course, there were most likely lots of people who simply ignored the issue and/or ignore what they sign. There were certainly people in my division who appeared to be flagrantly violating the prohibition on an outside business while employed, but no doubt had the sense not to specifically ask permission.
- iaw 8y agoIt's a double red flag: 1) If a potential hire is willing to violate their current employment contract they'll be willing to violate any contract you have with them. 2) If a company is happy to trounce into a legal gray area because it's "unenforceable" it may indicate some ethical questions about their leadership.
- paulie_a 8y agoIt's a non flag. Personally I don't even think about a trivial employment contract. They are basically boilerplate garbage akin to a EULA. Sure I'll sign it and then ignore it. The only time I was called out on an employment contract I very diplomatically told them to fuck off. And that was the end of it.
- dnh44 8y agoI totally agree, but I also think it's unprofessional behaviour to ask or expect someone to break the terms of an existing contract. Especially at the start of a new business relationship where building trust is really important.
- icedchai 8y agoI've had people submit code samples from their existing employer, with copyrights, "do not disclose" notices, and everything. I thought that was a red flag...