good chemistry is complicated, and a little bit messy -LW |
|
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
He explained that, "for future reference" it was "expected" of programmers to keep real-world samples of their code from proprietary jobs, and that he had stuff he had worked on for a number of large companies. I'll bet his company lawyer wasn't in the room when he said that, or he'd have gotten taken out and spanked. I spent many years as a hiring manager. If someone brought proprietary code into an interview, they'd get flunked on the spot. And it did happen a few times. You don't start a trust-based relationship by demonstrating how easily you'll break legal agreements. At my current job, we ask candidates for a code sample for a generic problem we pose. That keeps things safe and neutral, and helps prevent misrepresentations over authorship. (And we follow-up with some problem solving at a whiteboard for candidates who make it through written screening.)
In reply to Re: Code Samples and Previous Employers
by dws
|
|