|
As another deaf developer (severe-to-profound loss), this is absolutely on point. A lot of the traditional techniques that work for most companies don't work for me, especially when it comes to pair programming. I strongly dislike group stand-ups, because I never know who's going to talk next. One of the other things I've found myself struggling with is when to tell someone that I have a hearing loss. I feel like if I do it in the first interview, I'll set off unconscious biases, and during the hiring meeting someone will think, "Well, he can't hear shit, which might make it harder to get things done over time", and I won't get the job. On the other hand, once I get that offer and accept, then they're already invested in me, and a little bit of extra effort would be worth it. I tend to go back and forth on it. Some interviews I say it straight up, others I wait until I get an offer, and sometimes I only mention it if I think it's interfering somehow with the progress of the interview or project (e.g., I find myself saying "what" a lot or mishearing what they said). It's a tough problem, and I wish I felt more confident about how other people would respond to that knowledge. I usually feel... safer?... when I've already secured the position, but honestly, I've never had a bad reaction to it from anyone, so maybe I'm just overthinking things. I'm rambling now. Anyway. Totally agree with the post. |
I completely understand this and have felt the same way, but the trade-off I ended up making in my mind to make me feel more comfortable with being up-front is that if they're not willing to be accommodating for the interview, working there is probably going to be living hell. I try to think of it as me interviewing them as well, to see how they're willing to work with me.