It's your prerogative. Nobody said anything about "exfiltrating." Showing someone X doesn't mean that X isn't owned by its owner anymore. These aren't semantic arguments.
You're going to have a hard time expressing what exactly is the violation when everyone has signed the same NDAs and CIIAs! 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.
Okay, now if I only "work" for Google, which like 200,000 people do, and they've signed the same exact agreements as you... It's your prerogative!
> criminally or civilly
It's your prerogative! You can leetcode instead!
I am not saying this is you. But there are many developers, arguably the majority, who complain tirelessly about the status quo of interviewing. And given one opportunity after another to change that status quo - doing the stuff Simon says, doing the stuff I am saying - they make no effort! They vamp about how it's impossible.
They think their social local mobile trip planning startup website code is sensitive. They think their 15 layers of Dagger dependency injections is sensitive. It's not. If you want to change the status quo from leetcoding, 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.
All I am saying is, the reason this hasn't happened yet is because most people spend a year at BigCo and UnicornCo doing nothing of any substance. I mean maybe that's going to change. But it's really tough, nobody is being honest with how truly tremendously mismanaged and ZIRP-fueled large employers are. It hasn't been this way forever, but it has for at least 10 years, and it means some crazy things have happened in the job market that made no sense.
Copying work code to a non-work device to show during an interview is exfiltrating code. Well staffed security orgs at large companies have insider threat teams that look for this type of thing, in addition to monitoring for exfiltration of company documents and other materials to personal devices.
> 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
doctorpangloss|2 years ago
You're going to have a hard time expressing what exactly is the violation when everyone has signed the same NDAs and CIIAs! 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.
Okay, now if I only "work" for Google, which like 200,000 people do, and they've signed the same exact agreements as you... It's your prerogative!
> criminally or civilly
It's your prerogative! You can leetcode instead!
I am not saying this is you. But there are many developers, arguably the majority, who complain tirelessly about the status quo of interviewing. And given one opportunity after another to change that status quo - doing the stuff Simon says, doing the stuff I am saying - they make no effort! They vamp about how it's impossible.
They think their social local mobile trip planning startup website code is sensitive. They think their 15 layers of Dagger dependency injections is sensitive. It's not. If you want to change the status quo from leetcoding, 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.
All I am saying is, the reason this hasn't happened yet is because most people spend a year at BigCo and UnicornCo doing nothing of any substance. I mean maybe that's going to change. But it's really tough, nobody is being honest with how truly tremendously mismanaged and ZIRP-fueled large employers are. It hasn't been this way forever, but it has for at least 10 years, and it means some crazy things have happened in the job market that made no sense.
strictnein|2 years ago
Copying work code to a non-work device to show during an interview is exfiltrating code. Well staffed security orgs at large companies have insider threat teams that look for this type of thing, in addition to monitoring for exfiltration of company documents and other materials to personal devices.
dmoy|2 years ago
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