Case Study 1 — The Candidate Who "Lacked Confidence"
A composite case, assembled from the common experiences of Western hiring panels interviewing East Asian candidates. Names and details are illustrative.
The situation
A fast-growing American software company is opening an R&D center in Japan and hiring its first local engineering lead. The interview panel flies in from Seattle: three engineers and a VP, all sharp, all well-intentioned, all completely confident that they know how to spot talent. They run their standard loop — the same behavioral interview they use in Seattle, scored on the same rubric, with "communication and leadership presence" as one of the weighted dimensions.
Two candidates reach the final round. Hiroshi is a fifteen-year veteran with a quietly extraordinary track record: he led the team that shipped a notoriously hard real-time system at his previous employer, mentored a generation of junior engineers, and is exactly the kind of deep, steady technical leader the new center needs. Daichi is younger, slicker, recently back from two years at a U.S. startup, and fluent in the self-presentation the panel is used to.
In the interviews, Hiroshi credits his old team for nearly everything. Asked about the famous real-time project, he says, "It was a strong group — my manager set good direction, and I was fortunate to work with talented people. I helped coordinate the architecture." Asked about his leadership, he says, "I tried to support the younger engineers as best I could." He is warm, precise, and almost impossible to get to claim a personal win. Daichi, by contrast, leans in: "I architected our entire pipeline," "I drove the team to ship," "I'm the person who makes hard calls." The panel finishes the day and their gut is unanimous: Daichi has "leadership presence"; Hiroshi is talented but "seems to lack confidence" and "may not have the executive presence to lead the center." They are leaning toward Daichi.
They are about to hire the weaker candidate and pass on one of the best engineering leaders in the country — and the error is invisible to them.
The 'before': how it looked through the panel's operating system
Run the interviews through Seattle's software and the panel's read is reasonable. In their world, an interview is where you sell yourself; a strong leader claims their impact, owns their decisions, and projects confidence. "I" is the language of accountability — "I drove this" means "I'll own the outcome." Someone who can't or won't claim their achievements reads as either insecure or as not actually having done much. So when Hiroshi deflects to his team and undersells himself, the panel hears exactly what that behavior would mean if a Seattle candidate did it: low confidence, weak presence, not leadership material. And when Daichi performs confident ownership, the panel hears a leader.
Every word of that interpretation is fluent — in the wrong language.
The 'after': what was actually happening
Hiroshi was not lacking confidence. He was displaying, with great skill, exactly the profile his culture trusts most in a leader — and the panel was grading it as failure.
- Modesty is a leadership virtue here, not a deficit. In a Confucian-influenced, group-first culture (Chapters 2 and 6), a leader who loudly claims personal credit grabs face at the team's expense and signals immaturity. The respected leader attributes success to the group and to those above and below him. Hiroshi's deflection wasn't weakness; it was him demonstrating that he leads the way a trustworthy senior person should.
- "We" is not evasion — it's how he describes real leadership. When Hiroshi said "I helped coordinate the architecture," he was, in his idiom, telling the panel he led the architecture. The information was there; it was wrapped in the humble packaging his culture requires. The panel heard the wrapping and missed the substance.
- Daichi's polish was the warning sign, not the green flag. Daichi's fluent self-promotion wasn't necessarily fake — but in this context it marked him as someone operating partly outside his own culture's norms, and possibly as someone his future Japanese team would find off-puttingly self-aggrandizing. The very quality the panel loved could undermine him with the people he'd lead.
- The panel's "presence" rubric measured the wrong thing. "Leadership presence," as the panel defined it, was really fluency in American self-presentation. That's a genuine skill for some roles — but it has almost nothing to do with whether someone can lead an engineering team in Osaka, and weighting it systematically under-rated the better leader.
Hiroshi's modesty was, in his system, a display of exactly the maturity the role needed. The panel had been grading expert behavior as a flaw — because they were using a rubric built for a different operating system and never noticed they were holding a rubric at all.
The deeper point
This is the chapter's interview trap in a single hire. The panel didn't fail because they lacked information about Japan — though they did. They failed one level below that: they never noticed that "a good candidate sells themselves" was a cultural belief rather than a fact about talent. Because that assumption was invisible, they couldn't switch it off, and so they nearly hired confidence over competence.
And notice Theme 2, quietly present: the fix is not "in Asia, prefer the quiet one." It's subtler. In a different Asian context — a more direct-exchange Indian engineering culture, say (Chapter 30) — the calibration would differ again, and even within Japan, individuals vary. The real lesson isn't a new stereotype to swap in for the old one. It's that "gut feel for confidence" is not a talent detector; it's a culture detector, and a hiring panel that trusts it blindly will systematically misjudge anyone whose culture presents competence differently than Seattle does.
The better approach
The panel doesn't need to stop valuing communication, and they shouldn't hire purely on a hunch that "modest = strong." What they need is to make their own self-presentation bias visible so they can assess actual substance under either style.
- Replace self-promotion questions with descriptive, behavioral ones. Not "Why are you the best leader?" but "Walk me through what you did, step by step, on the real-time project — what decisions were yours?" Description lets a modest candidate show substance without boasting.
- Strip "presence" of its cultural loading, or weight it carefully. Define what leadership actually requires for this role and team, and don't let "speaks confidently in the American style" stand in for it.
- Check references and track record, not just interview affect. Hiroshi's fifteen-year record and the engineers he mentored tell the true story far better than forty-five minutes of self-presentation.
- Ask how the team would experience each candidate. A leader who'll manage Japanese engineers should be assessed partly on how those engineers would receive him — where Daichi's self-aggrandizement might be a liability, not an asset.
Scripts the panel could use: - (to Hiroshi) "I don't need you to sell yourself — just walk me through that project as if you were explaining it to a new teammate. Where exactly did you make the call?" - (internally, recalibrating) "Let's separate 'communicated confidently in the way we're used to' from 'would actually lead this team well.' Score those two things separately." - (to both) "Tell me about a time the team was stuck. What did you personally change?"
Panels that make this one adjustment — assessing described substance instead of performed confidence — routinely discover that the candidate they'd written off as "lacking presence" is the strongest leader in the pool, just speaking a different professional dialect.
Discussion questions
- Identify the exact moment the panel's own culture became invisible to them. What belief did they mistake for a fact about talent?
- Make the strongest case you can for Hiroshi's modesty as evidence of strong leadership rather than a lack of it.
- The fix isn't "always prefer the quiet candidate." Why would that be just another stereotype — and what's the actual skill the panel needs?
- Where in your own hiring (or in interviews you've sat through) might "confidence" or "presence" have been scoring cultural self-presentation rather than ability?
- Daichi's polish could be a genuine asset in some roles and a liability in others. How would you tell which?
Portfolio link. In your Cultural Intelligence Portfolio, add an entry to your "Behaviors I might misread" list: a candidate who credits the team and understates their role may be displaying competence-plus-maturity, not weakness — assess described substance, not performed confidence. Then draft three descriptive, behavioral interview questions you could use to read a modest candidate fairly. You now have a concrete tool to stop hiring confidence over competence.