News for hackers. Stuff that matters.

A comment on Fixing impostor syndrome in coding interviews. Parent comment

Re:Fixing impostor syndrome in coding interviews by curmudgeon9 on Monday March 12, 2018 @02:22PM (#16570211)
The way Google does project assignment after a lengthy interview process strikes me as a bait-and-switch. Feels like they're hoping you've invested so much time in the process that you won't turn down a role you would have never applied to in the first place.
[ Parent | on HN ]
Re:Fixing impostor syndrome in coding interviews by emodendroket on Monday March 12, 2018 @02:54PM (#16570425)
Would you care to elaborate? I'm not familiar with the process.
[ Parent | on HN ]
Re:Fixing impostor syndrome in coding interviews by southphillyman on Monday March 12, 2018 @03:08PM (#16570522)
You interview to get into Google at a specific level (new grad, SWE III, etc). They don't reveal which project you will be working on until the offer stage though. So it's possible that you can be in the interview process for months only to find out you'll be working on some kind of old legacy maintenance role.
[ Parent | on HN ]
Re:Fixing impostor syndrome in coding interviews by emodendroket on Monday March 12, 2018 @03:34PM (#16570745)
Yikes. That stinks.
[ Parent | on HN ]