Quote:
Originally Posted by sugar and spice
Programming is a weird field because the typical interview dress code is assumed to be business casual or even casual. Suits aren't really done in most parts of the field, even for interviews. It isn't uncommon to find places who'll cut a candidate for dressing too formally because they assume it means she'll be too straight-laced to work for them. (Which is hella stupid, but whatever.) So yeah, for a normal job interview, this outfit would have been far too casual—in tech . . . eh. It depends on the company. I know of plenty of companies where that would have been fine as an interview outfit (and others where it wouldn't). She gambled and lost. It happens.
Cutting an otherwise stellar candidate because they had a run in their stockings is idiotic—I guess maybe if it was a male interviewer/an all-male office, they might not know that if you put them on in the morning you've got a 50/50 chance of having a run in them by the end of the day? But I suspect that her lateness was the biggest issue—either she didn't actually warn them that she was going to be late, that message was not noted/passed on from whomever she did tell, or when she told them that she was going to be “a few minutes” late, they assumed 5, not 20.
|
Yeah, she totally gambled. When my partner interviewed at the company he's at now, which is in the tech field, the recruiter was very clear NOT TO WEAR A SUIT AND TIE to this interview (that was one of the companies where someone wearing that would be considered a "bad fit"). If this was one of those jobs, then the recruiter may have told her. That said, her outfit was kind of eh for architecture and design, too. If someone came dressed like how she was, I wouldn't count it against her.
What I WOULD hold against her, however, was being late. And that's what the issue more than likely was. She learned a painful lesson--made more painful by the fact that when you Google her, this is what will come up.
Hybrid Mode
