|
|
|
|
|
|
by crackercrews
1372 days ago
|
|
|
> You get the feeling that this was likely due to his race and so you don’t hold it against him. What would cause someone to get this feeling? Does a candidate just have to indicate that he wanted bigger projects but didn't get them? Seems like the exact same thing that would happen to someone who was not ready for bigger projects. Would you do the same thing for a dev with a strong southern accent who worked at a company with mostly left leaning employees? |
|
|
Abso-fucking-lutely. In fact I've actually done something similar, when you work in the somewhat affluent urban blue specs on the political map you will find genuinely talented engineers, usually self-taught too, who grew up in a small town/village and just don't have the usual pedigree of a CS degree from a random college and tech internships. I felt so bad for this one guy we hired, dude was and still is a fucking wizard at networking -- he literally runs his own ISP now as a side hustle but in the interview he didn't even have to say it, it was clear from how defensive he was saying stuff like "I know you would be taking a chance on me", "I would be fine with a probationary period" that he was getting rejected other places. So we had to interview him differently to set him up to show off what he was good at because random whiteboard algo problems wasn't it.
So it's not exactly textbook discrimination, but it is recognizing the systematic disadvantages this guy had as a result of who he is.