Join 1k+ other forward-thinking professionals who receive the weekly newsletter, where I provide actionable strategies, insights and tools to escape the grind and build influential, future-proof careers. Sign up to get a FREE copy of my 5-Stage playbook to multiply your impact and build a career that AI can't replace.
Why Strong Engineers Lose Influence Without Knowing It
|
By every metric that's supposed to matter, he was the obvious choice. Five years without a miss and systems running in production that newer engineers treated like scripture. The kind of engineer other teams request by name for cross-functional projects. So when the promotion committee passed him over, he didn't react with anger. He reacted with something worse: genuine confusion. "I don't understand what else they want from me." What he didn't know (what almost no one in his position ever knows) is that the question was never about him. It was about who else in the room was prepared to answer for him and that room was empty. The Decay You Don’t NoticeThis pattern repeats constantly. The technically strong engineer who invests everything in the work and almost nothing in the relationships that determine what the work actually earns them. Research on professional networks shows why this is so dangerous. Social psychologist Robin Dunbar’s work on relationship maintenance found that without regular interaction, professional ties decay to acquaintance-level within 12 to 18 months. A 2022 study in Organization Science found that engineers promoted to staff-equivalent roles maintained active relationships with 2 to 3x more senior stakeholders than those who stalled not because they networked more, but because they let fewer relationships decay. Professional relationships are not static. They do not stay where you leave them, preserved and retrievable on demand. They are always in motion toward you or away from you. Every relationship you have right now is in one of three states. Where Influence Actually LivesDeepening relationships are where your influence compounds. Both people are actively studying each other's priorities, pressures, blind spots. This is the architect who champions your design approach in a review you were not invited to. Who tells you the VP’s real concern before you present. Who pulls you into the incident response because they trust your judgment under pressure. It does not require constant contact. It requires consistent contact, and the kind of attention that compounds. Holding relationships feel solid because they are comfortable. But comfortable and solid are not the same thing. Picture the engineering manager you grab coffee with quarterly. You have a pleasant conversation and have genuine mutual respect for one another. Would they go out of their way for you, unprompted? Would they spend political capital to advocate for your promotion? Most holding relationships cannot pass that test. They work until you need them to work for you. Then they reveal that they actually pleasant, but structurally weak. Drifting relationships are the silent influence killers. The contact intervals stretch. The context gaps widen. You stop knowing what they are working on. They stop thinking of you when opportunities surface. The danger is not that people turn against you. It is that they stop thinking about you at all. The Heads-Down TrapDrift is almost always invisible until it is irreversible. The senior engineer who goes heads-down for two years building a critical system, ships it and gets the recognition. Then surfaces to discover the new VP of Engineering does not know them, the team leads they once influenced have reorganized, and the cross-team architecture forum moved on without their voice. They were well-liked and they did strong work but the work itself created the false sense of security. Strong delivery felt like enough, it was not. The work got them here but the relationships that were supposed to carry them forward did not wait. The AuditList the ten people whose opinion of you matters most to your career right now. Assign each one a state: deepening, holding, or drifting. Then ask the harder question: how many of those assignments were intentional? If more than three are drifting, you do not have a performance problem. You have an influence problem wearing the mask of stability. Your technical systems have a health score, so does your network. The difference is you probably only monitor one of them. That's all for this week. |
The Influential Engineer
Join 1k+ other forward-thinking professionals who receive the weekly newsletter, where I provide actionable strategies, insights and tools to escape the grind and build influential, future-proof careers. Sign up to get a FREE copy of my 5-Stage playbook to multiply your impact and build a career that AI can't replace.
Hello Reader, There's a particular kind of engineer who never misses a deadline. They deliver exactly what was asked, exactly when promised. They are consistent, dependable and reliable to a fault and somehow, zero influence on anything that matters. This isn't a competence problem. It's a range problem. When people can predict you perfectly, they stop paying attention to you. You become essential and invisible at the same time. You're in the room but not in the conversation, executing but...
Hello Reader, Some years ago, I watched a senior engineer named David present the most technically flawless migration plan I had ever seen. He had spent six weeks mapping every dependency across four microservices, documenting rollback scenarios for each phase, and building a custom monitoring dashboard to track the cutover in real time. His architecture review deck was twenty slides of precision. When he finished presenting to the leadership team, the room went quiet. The kind where twelve...
Hello Reader, Three years ago, I watched a senior engineer named David lose a promotion he had earned six times over. He was the kind of developer every engineering organization depends on but rarely celebrates. His code reviews were surgical. His incident response times were the fastest on a team of fourteen. In the third quarter alone, he resolved more production incidents than any other engineer in the department, including two high severity outages that if left unaddressed for another...