[dmoy]

> Like if you work for Google, and I work for Google, you can fathom, well I can look at code you've written for Google.

wait how does that work in the context of an interview though? You're by definition interviewing somewhere where you don't currently work

> you're going to have to screen share a "diff" here or there, and show people concretely what the hell you've been doing for a year at BigCo or UnicornCo. I cannot predict the future and I cannot generalize, but in my experience, the likelihood of criminal, civil or even the far more realistic reputational and cultural repurcussion is extremely small

Ah, nvm

No thanks, I'm not gonna do that

[icedchai]

It is more common than you think. I've had candidates submit code samples with proprietary code from their current employer during interviews. One example: some files from a telco billing system. Right or wrong, there is essentially zero risk for this sort of thing.

[lkjdsklf]

There's certainly more than 0 risk.

I do hiring at my company. If a candidate showed me non-public code during an interview, they're an immediate no hire. Interview is immediately over. This isn't my personal preference or anything either. It's specifically in our interview training.

It demonstrates a clear inability to protect company IP. That's a big deal. Especially if you're a publicly traded company.

[icedchai]

It's near zero. Did you report the candidate for this? Actually, have you ever had it happen in any interview you've done?

[rhtgrg]

Yeah this reads like satire. I hope it is, anyway.