The technical side kept making more sense to him than everything around it. He assumed strong work would speak for itself; over time he learned that visibility, relationships, and plain self-advocacy mattered just as much. He also had to relearn how he gave feedback. His instinct, when he spotted a problem, was to just say so, directly. If he were wrong, he'd want someone to tell him the same way. Not everyone heard it that way.
"I had to learn that being right is not helpful if the way that you present something cannot be heard by your target audience," he says.
The person who first put a name to any of this wasn't a doctor. It was a relative of his wife's, who recognized certain traits in Lee and said so, plainly. He started reading about autism on his own. The more he read, the more he wanted a real evaluation, not just a guess. Finding a specialist who tests adults turned out to be harder than he expected.
He finally got evaluated in his late thirties, while working as a software engineer at Meta. Two answers came back at once: autism, and a sensory processing disorder.
Meta was hard on him in its own way. He'd raised concerns about how some experiments were being measured, and while people in data science tended to agree with him, saying it over and over didn't earn him trust inside his own team.
"I'm not saying I did it wrong," he says, "but I didn't do it in a way that could be heard."
He'd also joined during the pandemic, onboarding fully remote, and spent months trying to get matched to a team. Nine years of learning Amazon's unwritten rules turned out to count for very little somewhere else. In a podcast interview, he put it simply: he "didn't have a great time there." On LinkedIn, he was even more direct: "I did not succeed at Meta."
At Google, the technical side went well; he reached Staff Engineer. But a new problem showed up: expectations that were too vague to act on. A manager might say "do more of this" or "do less of that," and Lee would make what seemed to him a reasonable adjustment, only to find out later that far more had been expected. At one point that gap put his job at risk. What actually turned things around was a performance improvement plan with real numbers attached: specific goals, dates, measurements. He met them, then went past them.
He also started describing his own output as "spiky": long stretches of research that produce almost nothing visible, followed by one large result. Left unexplained, that pattern can look like nothing is happening. Now he asks his managers directly, up front, which kind of task this is: keep investigating until he has the answer, or spend two days, report what he's found, and move on.
None of this followed a straight line from diagnosed to fixed. What helped was a collection of smaller things. At Google, he joined an employee group for autistic staff, where he could ask people a simple question: has this happened to you, and what did you do about it? He worked with occupational therapists, who helped him notice hunger, fatigue, and other signals that hyperfocus tends to bury. A manager once suggested he add a short TL;DR to the top of his messages, since Lee tends to over-explain things, wanting to be fully understood. It helped. These days he also turns off Slack notifications when he needs to focus and protects meeting-free stretches for deep work.
At Netflix, where he works now, clarity showed up from day one. New hires get a rough outline of what they should accomplish in their first week, first month, first quarter. For Lee, that's been steadying; he can check the outline and know where he stands. He compares it to a curb cut in a sidewalk: built for wheelchair users, but useful to anyone pushing a stroller or pulling a suitcase. Clear expectations work the same way. They may matter most for autistic employees, but they make things easier for almost everyone.
McKeeman speaks publicly now about both sides of his career, engineering and autism.