You are exceptional at your job. Your code is clean, your architecture decisions are sound, your debugging is faster than almost anyone on the team. You've been at the company for three years. You've been told you're "on track." And yet, when the engineering manager position opens up, it goes to someone with two fewer years of experience and a noticeably less impressive technical track record.
If this has happened to you — especially as an international professional in a US tech environment — there's a good chance you're experiencing what we at ELA call the Technical Credibility Trap. You've built your reputation entirely on technical output, and the criteria for management advancement are almost entirely non-technical. The game changed, and nobody told you.
What Actually Gets IT Professionals Promoted to Management
A 2023 study of engineering manager promotions at mid-to-large US technology companies identified the top five factors cited by decision-makers in promotion decisions. Technical competence ranked fifth. The top four were:
- Stakeholder communication quality — the ability to translate technical concepts to non-technical audiences and to understand non-technical stakeholders' concerns
- Cross-functional influence — the ability to move projects forward across teams without formal authority
- Meeting leadership presence — how the candidate shows up in group settings, particularly when there's disagreement or ambiguity
- Upward communication — how effectively the candidate communicates status, risk, and decisions to leadership
This doesn't mean technical skills don't matter — they remain the table stakes that get you considered. But they are not the differentiator at the management level. Communication is.
The Translation Problem
The most common communication gap we observe in technically excellent international IT professionals is what we call the Translation Problem: the inability or reluctance to translate technical information for non-technical audiences without feeling that you're dumbing it down or being condescending.
Here's a truth that might be liberating: most business stakeholders — VPs, product managers, finance partners, even many CTOs — do not need or want technical precision in most conversations. They need to understand: what are we building, why does it matter, what could go wrong, and when will it be done? Everything else is context they'll ask for if they need it.
When a technically excellent engineer can answer those four questions clearly, concisely, and without jargon, they become 10x more valuable to the organization than an equally skilled engineer who can't. Not because the business value changed — but because they can now participate in the decisions that determine the business value.
The exercise we use with IT clients: take any technical topic you're currently working on and explain it to an intelligent non-technical person in 60 seconds. Not a dumbed-down version — a translated version. The precision is still there; the vocabulary is accessible. Practice this weekly and you will develop a communication fluency that most engineers never build.
The Meeting Presence Gap
In a meeting of 10 people, how often do you speak? When you do speak, do you lead with your conclusion or build to it? When someone says something technically incorrect, how do you handle it?
For many international IT professionals, the answers are: infrequently, I build to it, and I either stay quiet or correct very gently. All three of these tendencies are understandable and often culturally appropriate. All three of them, in a US tech meeting, mark you as a contributor rather than a potential leader.
Leaders in US tech meetings speak more, not less. They lead with recommendations. And when someone says something incorrect, they correct it — professionally but clearly — rather than letting it stand in the record.
This is particularly challenging for engineers from cultural backgrounds that prize consensus and indirect communication. We don't ask clients to abandon their values. We teach them how to be direct in a way that feels congruent with who they are — because there are many ways to be direct, and some of them are entirely compatible with warmth, respect, and collaborative spirit.
Writing for Leadership Visibility
One of the highest-leverage communication investments any IT professional can make is in the quality of their written upward communication: project status updates, post-mortems, architecture proposals, incident reports.
The pattern we see most often from technically strong but communication-underinvested engineers is the "data dump" update: a long list of technical details that accurately describes what happened but doesn't tell the reader what to do with the information. Leadership-ready writing tells the reader what to know, what to feel, and what to decide — in that order.
Compare: "The migration to the new database completed successfully. Some latency issues were observed during the cutover window, approximately 340ms increased over baseline for a period of 23 minutes. These have since resolved. We identified three areas for improvement in the migration playbook."
vs. "The database migration completed successfully with no data loss. We had a 23-minute window of elevated latency (340ms above baseline) that is now fully resolved and was within acceptable SLA parameters. We've documented three improvements to the playbook for next time — happy to share if useful."
Same facts. The second version lands as confident, self-aware, and leadership-oriented. It tells the reader: everything is fine, here's the signal-to-noise-filtered version, I'm on top of it, and I'm being proactive about improvement. That's what leadership writing sounds like.
The 1:1 with Your Manager: Using It Strategically
Most international engineers treat their 1:1s with their manager as status check-ins: here's what I'm working on, here's where I'm stuck. This is a missed opportunity.
Your 1:1 is the primary venue for building your promotion case — not in a manipulative way, but in an honest, strategic way. Use it to: ask about organizational priorities so you can connect your work to them explicitly; surface the cross-team communication work you're doing that might not be visible; ask directly about what skills or experiences you need to develop for the next level; and flag risks you're seeing, framed as "here's what I'm seeing and here's how I'm thinking about addressing it."
Each of these behaviors demonstrates the non-technical competencies that promotions are actually based on. Your manager is forming a picture of you every week. You can either hope the picture that forms is accurate, or you can participate in painting it.
The Long Game
The transition from individual contributor to manager in tech typically takes 3–5 years for most professionals and sometimes longer for international professionals navigating communication barriers. But we've seen clients compress that timeline dramatically — not by working harder technically, but by shifting where they invest their development energy.
Priya had been passed over for management three times. In eight weeks of ELA coaching, she shifted her meeting contribution pattern, rewrote her upward communication style, and built a clear framework for her promotion conversation. She got the offer on her first interview after coaching.
The technical skills got her to the starting line. The communication skills took her across it.