Latest / The Diversity Career Podcast with Fexingo: Inclusion, Equity, and Underrepresented Professionals / How Airbnb Built Inclusive Hiring For Neurodivergent Talent
Transcript
- Lucas: If we've helped you think through a career move or decision this week, I want to pause for just a second to ask for your support. A couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo. It’s not about the money, it’s about keeping the signal to noise ratio high so we can keep digging into the real mechanics of how work is changing. Luna: Yeah, exactly. And thank you to everyone who has already chipped in. It makes a tangible difference in the research we can do. So, let's get back to the core issue: why do so many talented engineers miss out on jobs they are perfectly qualified for? Lucas: Because the interview process itself is often a filter for anxiety rather than ability. Take Airbnb. Around twenty twenty-one, they realized their engineering hiring was leaking top-tier talent, specifically neurodivergent candidates. The standard whiteboard coding interview, where you stare at a blank screen while someone watches you struggle with syntax in real time, is a nightmare for people with autism or severe social anxiety. Luna: It feels like a test of performance art, not engineering. Does the data actually show that removing those barriers improves output? Lucas: It does. Airbnb decided to overhaul their process by introducing a 'take-home' practical assessment instead of the live whiteboard session. Candidates were given a realistic problem—like optimizing a search algorithm or debugging a broken feature—and asked to solve it over forty-eight hours. No timer ticking down. No interviewer hovering. Just pure problem-solving. Luna: That sounds much closer to how developers actually work in the office anyway. Lucas: Exactly. And here is the specific detail that matters: after rolling this out, Airbnb saw a thirty percent increase in offers accepted by neurodivergent candidates. But more importantly, the retention rate for those hires was higher than the average. They weren't just getting bodies in seats; they were getting people who stayed and thrived. Luna: So the metric shifted from 'can you perform under pressure' to 'can you deliver quality work?' Lucas: Precisely. The thing is, most companies cling to the whiteboard interview because it’s cheap and fast to administer. You don’t need to prepare complex scenarios. But as Lucas points out, speed isn’t the only metric. When you remove the artificial stressor, you start seeing the actual engineering capability. One candidate described it as finally being able to 'think out loud' without feeling judged for the pace of their thoughts. Luna: That resonates. I’ve spoken to several developers who said they ace the take-home but freeze up in the live setting. Is this just an Airbnb case study, or are others following suit? Lucas: It’s spreading, but slowly. Google and Microsoft have made similar shifts toward asynchronous interviews. But for mid-sized firms, the inertia is strong. The fear is always the same: 'What if they cheat?' Or 'What if it takes too long to grade?' Luna: Those are valid concerns, though. If I give someone four hours to write code, how do I know they didn’t copy it from Stack Overflow? Lucas: Good question. The solution isn’t to ban take-homes; it’s to structure them correctly. Airbnb added a brief follow-up discussion where the candidate walks through their logic. Not a grilling, but a conversation. 'Why did you choose this database?' 'How would you scale this?' That reveals whether they understood the problem or just pasted a solution. It turns the assessment into a collaborative review, which is actually how peer programming works in teams. Luna: So the interview becomes a proxy for team fit rather than a solo obstacle course. Lucas: Right. And let’s look at the financial side. Replacing a neurodivergent engineer costs the company roughly one hundred fifty thousand dollars in lost productivity and re-hiring fees. If a new hiring model increases retention by even ten percent, the ROI is massive within two years. It’s not just a nice to have diversity initiative; it’s a cost-saving measure. Luna: That’s a compelling argument for CFOs who might otherwise view DEI as a soft cost. How do you convince a hiring manager to change a process they’ve used for ten years? Lucas: You lead with the pipeline problem. Tech firms are reporting record shortages in specialized roles. If you’re filtering out twenty percent of the talent pool because they can’t handle a whiteboard, you’re fighting with one hand tied behind your back. Airbnb’s leadership framed it as an access issue. 'We want the best engineers. Are we sure our current gatekeepers aren’t blocking the best ones?' Luna: I love that framing. It puts the responsibility on the company, not the candidate. Lucas: It does. And there’s a secondary benefit: bias reduction. Whiteboard interviews are notoriously biased toward extroverts who talk well while thinking. Introverts, or non-native English speakers, often get rated lower despite writing superior code. The take-home model levels the playing field by focusing on the artifact—the code itself—rather than the performance of the presentation. Luna: So the code speaks for itself. Less room for unconscious bias to creep in during the interaction. Lucas: Exactly. Though, Luna, it’s worth noting that the follow-up interview still requires some human judgment. But at least that judgment is based on technical clarity and communication style, not on who can hold eye contact the longest. Luna: True. Eye contact is a terrible proxy for analytical rigor. What about the preparation burden on the candidate? Forty-eight hours is a significant time commitment. Lucas: It is. And Airbnb compensates for that. They offer a stipend, usually around one hundred dollars, to acknowledge the candidate’s time. It’s a small amount, but it signals respect. It says, 'We value your expertise enough to pay you for the effort.' Contrast that with the old model, where candidates worked for free for two hours of unpaid screening. The shift in tone is palpable. Luna: That reciprocity changes the dynamic entirely. It feels less like an interrogation and more like a professional exchange. Lucas: It does. And for the employer, it provides a richer dataset. Instead of a binary pass/fail on a LeetCode problem, you get a portfolio piece. You see how the candidate structures files, writes comments, handles edge cases. It’s a much better predictor of daily performance than solving a contrived graph theory problem in twenty minutes. Luna: So the takeaway for job seekers is: seek out companies that use these methods. But how do you spot them early in the process? Lucas: Look at the job description language. If it mentions 'collaborative coding,' 'practical assessments,' or 'no whiteboards,' that’s a green flag. Also, check Glassdoor reviews. Candidates are increasingly vocal about interview experiences. If you see patterns of complaints about 'stressful' or 'unfair' interviews, run. If you see praise for 'respectful' and 'practical' processes, apply. Luna: Practical advice. And for hiring managers listening, the lesson is to audit your own gates. Are you filtering for culture fit or cultural add? Lucas: Yes. Culture fit often means 'someone like us.' Cultural add means 'someone who brings a perspective we lack.' By changing the interview format, you invite different kinds of minds into the room. And in tech, different minds solve different problems. A neurodivergent engineer might spot a security vulnerability that five neurotypical engineers miss because they’re looking at the system holistically rather than linearly. Luna: That holistic view is invaluable. It reminds me of how blind lawyers excel at legal research—they focus on the text and logic without being distracted by courtroom theatrics. Lucas: Spot on. It’s about leveraging cognitive differences as strengths. The old hiring model treats those differences as liabilities to be managed. The new model treats them as assets to be unlocked. Airbnb’s experiment shows that when you stop trying to make everyone fit the same mold, you end up with a stronger, more resilient team. Luna: It’s a powerful reminder that inclusion isn’t just about fairness; it’s about competence. We’re missing out on brilliance by insisting on outdated rituals. Lucas: Absolutely. As we look ahead to the rest of the year, I’m curious if you think other industries will adopt this shift, or if tech will remain the pioneer in dismantling these barriers.