3 ms·
Assuming the engineers aren’t forced to re-interview for their own jobs in the common Google acquisition fashion.
by pinewurst 5y ago
Assuming the engineers aren’t forced to re-interview for their own jobs in the common Google acquisition fashion.
- vntok 5y agoOf course they should be interviewed back, what's the alternative? Hey team, so this is Steve from another department in another company. He's been assigned to our team, so. Of course we're handling text in the Chromium engine and Steve's backgound is in threat analysis, but I guess we'll figure something along the way. Welcome, Steve
- jacobr1 5y agoThe alternative is that they basically keep working on the same things. Maybe now there is some integration project.
- jcims 5y agoEspecially since they likely have 2-3 years of services contracts to burn through and don’t really have an org they directly overlay with inside Google. Enterprise security to an extent but also not.
- deleted 5y ago[deleted]
- zem 5y agothat is already how google works. you get hired as a generic software engineer, and you pick up domain skills on the job every time you join a new team. someone working in threat analysis within google could absolutely put in for a transfer to the chromium engine team, and they would be expected to spend the first month or two getting up to speed on the codebase and specialised algorithms it entailed.
- sulam 5y agoIn an acquisition of this size, it’s not typical to interview. HTC engineers did not have to interview AFAIK and having been at Fitbit I can say for sure that no engineers had to interview. Interviewing happens with startups. When there aren’t interviews the assumption is that Perf will take care of non-performers.
- TameAntelope 5y agoThe domain experts are best-in-class. The engineers probably would need to be re-interviewed. Heh.