The Failed Expert - second-hand-tigers/badocter-career-learnings GitHub Wiki
Learning Hub โบ Career Learnings Directory โบ Dr. Docter's Career Learnings โบ Pop Culture Career Lessons
The Failed Expert
Many engineers and scientists start their careers believing that developing more technical skills is the only development that matters. I thought that way and missed out on job offers because of it. The ones who succeed realize that the non-technical skills need just as much attention, and a true expert must become a master of both. Jurassic Park's Dennis Nedry is the cautionary tale: an A+ in technical skill, and a 25% F overall.
Jurassic Park, film, 1993
Dennis Nedry is Jurassic Park's chief system engineer โ he developed the park's entire control system, from dinosaur containment to security to the phone system, and he understands the whole system better than anyone else because nobody else was ever brought in to learn it alongside him. By any purely technical measure, he's genuinely good at his job.
He's also a clear illustration of what happens when technical skill isn't paired with anything else. Nedry airs his frustration about pay and workload, but as a personal grievance in a public argument with Hammond rather than as a business case, and gets nowhere. Instead of escalating it properly, he takes a bribe from a rival company to steal embryos, and sabotages the park's security and power systems to cover his escape.
The park system collapse that follows โ fences down, dinosaurs loose, people in danger, and no way to call for help โ traces directly back to the only person who fully understood how any of it worked, using that position for personal gain instead of institutional benefit.
Grading Nedry on All Four Dimensions
Every one of Nedry's failures maps directly to non-technical organizational expectations of experts (see Technical Career Stages):
- acting ethically โ Fail (Leadership โ an ethics failure will get immediate disciplinary action: likely termination and possible criminal prosecution)
- owning and addressing his own mistakes โ Fail (Leadership)
- caring about the team โ Fail (Interpersonal)
- mentoring โ Fail (Leadership, Interpersonal)
- succession planning โ Fail (Business, Leadership)
- communicating priorities, challenges, and wins effectively โ Fail (Interpersonal)
- ambassador/advocate of technology โ Fail (Business, Interpersonal)
- business financials โ Fail (Business)
Not only is he failing on these expectations, but he is also placing traps in the system to lock out and taunt the team (e.g., "you didn't say the magic word"). None of those fails has any relation to his technical performance as an elite individual contributor. On that dimension alone he is outstanding: say 100% A+, giving him the benefit of the doubt despite Hammond's complaints that the system is buggy. In a Stage 3 performance review that roughly equally weights Leadership, Business, Interpersonal, and Technical, Nedry's scores in the four dimensions are 0/0/0/100: Overall 25% F.
A full performance review is beyond the scope of the script. Nedry clearly states he is unappreciated and the exchange between him and Hammond in the control room (YouTube) doesn't reflect well on either one of them. In the exchange, Nedry cites his technical accomplishments and clearly thinks he is an A+. Hammond cites Nedry's business and leadership failings (i.e., he underbid the job and is not taking ownership to fix his screwup) and clearly thinks Nedry is an F. They are both using different internal scorecards that are hitting different performance dimensions that only make up a part of the whole. Both are completely failing at the interpersonal dimension โ no sign of critical listening on either side and failure to recognize this is a discussion that should have been in private.
How it relates to my approach to life and career
I've watched a milder, non-criminal version of this pattern play out more than once in real careers: someone becomes the only person who can run a critical system, gets comfortable being indispensable, and never quite gets around to documenting the system or training a backup โ sometimes because they're genuinely too busy, or because their supervisor doesn't prioritize it, or because being irreplaceable feels safer than it should. Stress Management & Resilience already makes the point from the other direction: if nobody can cover your role while you're on vacation, that's a succession-plan vulnerability, not a compliment. Nedry is what that vulnerability looks like when someone actually decides to exploit it, rather than just neglects to fix it. The everyday version doesn't involve theft or sabotage โ it just involves a team that quietly can't function the day the one person who understood the system leaves, retires, or moves on, which is exactly the outcome mentoring and succession planning exist to prevent (see Mentoring Integration with Stage Development).
At any Career Stage, a 0/0/0/100 split adds up to a poor overall performance rating. Plenty of Stage 1 and Stage 2 engineers have crashed and burned on performance reviews because they ignored the non-technical dimensions, so this is not just a Stage 3 problem. I failed on non-technical performance as a co-op and again as a grad-school intern, and missed out on a job offer both times (see I Learned This One the Hard Way). Once you are competent in non-technical skills at Stages 1 and 2, you still need to keep growing them. Stage 3 holds non-technical performance to a higher standard: you are expected to be as expert in the non-technical dimensions as you are in the technical one. These are skills that need to be developed across your career, starting yesterday.
Effective managers will provide clarity on the grading criteria and work with the employee to align on the development plan to turn the situation around. The message and plan must make it stick that Technical performance is not the issue and further Technical development alone will not improve the overall score. Once the plan is aligned on, it is the responsibility of the employee to accept the feedback and drive toward the development plan objectives โ if you haven't accepted the feedback that you have a problem, it is unlikely that you can make progress fixing it (see Teammates or Competitors? and Setting and Accomplishing Development Goals).
References
Related: Technical Career Stages ยท Setting and Accomplishing Development Goals ยท Teammates or Competitors? ยท Mentoring Integration with Stage Development ยท Dread Pirate Roberts Succession Plan ยท Stress Management & Resilience ยท The Needs of the Many
License: ยฉ 2026 William Docter. This work is licensed under a Creative Commons Attribution 4.0 International License (CC BY 4.0). You may copy, redistribute, remix, and build upon this material, including for commercial purposes, provided you give appropriate credit to William Docter and indicate if changes were made. Film and television dialogue quoted for commentary remains the property of its rights holders and is not covered by this license. The Second-Hand Tigers logo is not covered by this license. All rights in it are reserved.