3 ms·
But you aren't hiring Apple's process, you are hiring someone who used to be there. Why do you assume he value you seek is particular to that person, and not to
by sukilot 12y ago
But you aren't hiring Apple's process, you are hiring someone who used to be there. Why do you assume he value you seek is particular to that person, and not to the Apple environment?
Witness the massive number of startup teams that get acquired and assimilated and then do nothing of note after.
- LoSboccacc 12y agothat's true as well, I wasn't aiming at a blanked statement covering every case, just adding one more thing to consider: the risk of hiring a passive engineer that goes task by task should be lower when poaching from highly demanding employer. acquihires are indeed risky, you have to factor in both the culture change and the sudden shift in middle management directives, but onboarding an apple engineer isn't the same as purchasing a whole company.