Latest / The Diversity Career Podcast with Fexingo: Inclusion, Equity, and Underrepresented Professionals / How NexGen Engineering Made Hearing Loss a Career Strength
Transcript
- Lucas: So there's a mid-size engineering firm in Austin called NexGen Engineering — about 800 people — and they've been running an interesting experiment for the past three years. They decided to hire deaf engineers not as a diversity checkbox, but because they thought deaf engineers might actually be better at certain tasks. And they were right. Luna: Wait — better at what exactly? Were they specifically recruiting for a skill set that correlates with hearing loss? Lucas: Yeah, they focused on visual pattern recognition. A bunch of their quality assurance work involves staring at data flows — network logs, code output, sensor readings — and catching anomalies. NexGen had noticed that some of their best visual inspectors were deaf, but it was anecdotal. So they partnered with a local university to test the hypothesis. They ran a controlled study where deaf and hearing engineers looked at simulated data feeds, and the deaf engineers detected subtle anomalies about 40 percent faster, with fewer false positives. Luna: That's a huge gap. What's the explanation? Is it because deaf people develop stronger visual attention due to relying on sight for communication? Lucas: Exactly. There's research showing that individuals who are deaf from birth often have enhanced peripheral vision and better ability to notice changes in visual scenes — it's a neural adaptation. NexGen realized they had a talent pool that was systematically overlooked because traditional hiring focused on verbal interviews and audio-heavy training. So they redesigned their onboarding and day-to-day communication around visual methods. Luna: What did that redesign look like? I'm picturing more than just adding captions to videos. Lucas: It went much deeper. First, every meeting room got light arrays — red and green LEDs that flash when there's a fire alarm or an urgent notification. They replaced all audio-based alerts with visual ones. Second, they embedded sign-language interpreters into every engineering team, not just for meetings with deaf employees but for all team stand-ups and brainstorming sessions. The interpreters became part of the team culture. And third, they built an internal communication platform that's text-first — not Slack with voice memos, but a tool where every message, every code review comment, is written out. They found that even hearing engineers preferred it because they could search conversations more easily. Luna: So they made the whole system more inclusive, and in doing so, they improved workflow for everyone. That's the classic universal design principle. Lucas: Right. But here's the part that surprised me: NexGen didn't stop at accommodations. They started actively recruiting deaf engineers from pipeline programs at Gallaudet and Rochester Institute of Technology. And they began showcasing their deaf employees in recruiting materials — not as a diversity story, but as a technical strength. Their pitch was: 'We are the best place in the world to work if you want to do visual data analysis, because our entire culture is built around that skill.' Luna: That's a powerful reframe. Instead of saying 'we welcome deaf applicants,' they said 'your deafness is an asset here.' That must have changed the dynamic for the deaf engineers themselves too. Lucas: It did. And I think this is where a lot of companies get inclusion wrong. They treat disability as a deficiency to be accommodated, not as a different way of processing information that could be a competitive advantage. NexGen's head of engineering told me that after they made these changes, the entire team's bug detection rate went up 30 percent — not just the deaf engineers. The hearing engineers got better because they were communicating more clearly and relying less on audio cues that can be missed in a noisy environment. Luna: That's a concrete metric. 30 percent improvement across the board. If I'm a CEO, that gets my attention. But what about the costs? Sign language interpreters, custom light systems, new software — that's not cheap for an 800-person company. Lucas: NexGen calculated the upfront cost at about $2 million over two years. But they also calculated that the improvement in product quality reduced customer support calls by 15 percent, and the reduced turnover — deaf engineers stayed at NexGen at a 90 percent retention rate compared to a 75 percent industry average for engineers — saved them about $1.5 million in recruiting and training costs. So the net cost was about half a million, which they considered negligible given the productivity gains. And that's not counting the patent they filed for a visual anomaly-detection algorithm that a deaf engineer invented partly because of the visual tools they built. Luna: That's remarkable. A deaf engineer created a new algorithm because the company's communication system was so visually oriented. So inclusion actually sparked innovation. Lucas: Precisely. And that's the takeaway I keep coming back to. When you design around a specific need, you often solve problems you didn't know you had. NexGen didn't set out to invent a new algorithm; they set out to make deaf engineers effective. The algorithm was a byproduct. Luna: If today's segment was useful to you — whether you're thinking about your own career or trying to build a more inclusive team — the reason this show stays ad-free is listener support. You can keep that going at buymeacoffee dot com slash fexingo. Just a simple way to say 'this helps,' and it genuinely does. Lucas: Yeah, that's exactly right. It's a small thing that keeps the lights on and lets us keep digging into stories like this. So if you're inclined, that's buymeacoffee dot com slash fexingo. Luna: Alright, back to NexGen. What's the broader lesson here for other companies? Because not every firm can afford a $2 million investment. Lucas: The broader lesson is to think of inclusion as a design problem, not a compliance one. NexGen started small — they pilot-tested with one team, measured the results, and then scaled. The key was their willingness to challenge the assumption that hearing is essential for the job. Most job descriptions for QA engineers list 'strong verbal communication' as a requirement, but NexGen realized that written communication and visual observation were actually more critical. So the first step is to audit your own job requirements and ask: is this criterion really necessary? Or is it just the way we've always done things? Luna: And the second step? Because that audit can feel overwhelming. Lucas: Start with one role or one team. Identify a task that relies heavily on a sensory skill — like hearing alerts or seeing visual patterns — and see if you can redesign that task to be more inclusive. Then measure the impact. NexGen's success came from data. They didn't just say 'it felt right'; they had numbers that proved it worked. That makes it easier to secure budget and buy-in. Luna: So the framework is: question assumptions, redesign one process, measure, then iterate. And along the way, you might discover unexpected strengths. Lucas: Exactly. And I think the timing is important too. We're recording this in July 2026, and there's been a lot of public discussion about return to office mandates and flexibility. NexGen's approach shows that when you focus on outcomes rather than presence or method of communication, you can find talent that competitors overlook. In a tight engineering labor market, that's a real edge. Luna: And for the deaf engineers themselves, what was the career impact? Did they advance into leadership roles? Lucas: Yes, actually. Three deaf engineers have been promoted to senior positions in the past year, and one is now a director of engineering. NexGen also created a mentorship program where deaf senior engineers mentor hearing junior engineers — reversing the typical flow. That was a deliberate move to signal that deaf employees are experts in visual thinking, not just recipients of help. Luna: That's a huge cultural shift — having deaf engineers mentor hearing ones. It breaks the stereotype that disability equals dependency. Lucas: It does. And it creates a feedback loop where hearing employees learn to appreciate different cognitive styles. One hearing engineer told me that working with a deaf teammate made him a better communicator because he had to be more explicit and visual in his explanations. He said he now sketches diagrams for everything. Luna: So the benefits ripple out. I wonder if we'll see more companies adopting this model. It seems like a natural fit for data-heavy fields like cybersecurity and financial trading. Lucas: We're already seeing some interest. NexGen has been approached by two financial firms and a defense contractor who want to learn about their approach. But the key, as always, is execution. It's not enough to hire a few deaf engineers and call it a day. You have to be willing to change your entire communication infrastructure. That takes commitment. Luna: And maybe a bit of courage to say, 'We’re going to bet that visual communication is better for everyone.' It's a bet that paid off for NexGen. Lucas: It did. And I think it's a bet more companies should consider. Because when you design for the edges, you often improve the center. Luna: That's a nice way to put it. Thanks, Lucas. Lucas: Thanks, Luna. And thanks to our listeners. If this story gave you an idea for your own career or your team, we'd love to hear about it. Reach out on the Fexingo Business network — we're always listening.