I&#x27;d be quite biased against you, honestly. Most engineers have huge monitors to take in a large amount of code in their head at once. How do you catch up? Text to speech seems like a slow way to input information, especially if people were nesting brackets and such.<p>On the other hand, that challenge would make it extra tough for you start in the first place and there&#x27;d be some positive bias as well. So I&#x27;d wonder if we got a superhero here.<p>I guess there&#x27;s no point in interviewing. What would I look for? Passion? Most blind people would give up and find another job, so there&#x27;s more than enough passion. Problem solving? Why not solve a real problem?<p>What I&#x27;d do is stop interviewing and give you some really tough code. It would be the actual job, take about three days on average, and even pay three days salary upon completion. Maybe something shorter might take 1 day, but it&#x27;s not big enough to cover the question of whether you can modify other people&#x27;s code.