Quick Bridge: Most technical leaders build their promotion case in the final weeks before asking. By that point, the decision is already forming somewhere else. This post explains how promotion decisions actually work, what the research shows about visibility and sponsorship gaps, and what to do in the twelve months before a formal ask to actually shape the outcome. Most promotion conversations go like this. The employee walks in prepared. They have gathered their wins. They know what they want and why they deserve it. They make their case clearly. Then they hear "not yet." What they almost never know is that the real decision about their promotion happened weeks or months earlier. In a calibration meeting. With managers comparing peers against each other and against limited budget. Among people who may not know their name. This is the part nobody tells you about. Why Promotion Decisions Don't Happen in Promotion Conversations Most people assume the promoti...

Quick Bridge: "Force multiplier" is no longer a compliment your manager pays you in passing. It is now an explicit line on senior and staff engineering leveling rubrics at major tech companies. This post breaks down what that criterion actually asks for, why the work behind it is invisible by design, and the specific narration habits that get it credited before someone else's launch takes the win. I once spent the better part of a year in meetings that had nothing to do with my own team's roadmap. My job that stretch was to learn how localization worked at my company from beginning to end, then negotiate a completely different process with every internal team and outside vendor that touched it. I did not write the software that ultimately automated most of the steps. My own team did that part. My job was defining the new process, negotiating it across departments that had never had to agree on anything before, and evaluating what the savings would actually be once it...

Why Software Engineers Are So Hard to Lead (And What to Do About It) Quick Bridge: Engineering managers rarely talk about this out loud. The overconfidence that derails code reviews, the semantic precision that stalls every planning meeting, the principled refusal to do the things that would actually get someone promoted. This post names all three patterns, explains what is driving each one, and gives you specific language for the conversation that starts to change things. There is a conversation I have had more times than I can count. An engineer on my team is doing genuinely good work. By any technical measure, they are one of the stronger contributors. Their promotion has been stalled for two years. When I ask them what they think is getting in the way, they describe the features they built, the problems they solved, the systems they improved. They do not mention that the people who make promotion decisions have almost no visibility into any of it. That gap, between what an enginee...

Quick Bridge: You have been doing the work that should put you in line for a management role, and somehow you still weren't in the room when the decision got made. I was a senior individual contributor when I decided I wanted to move into management. Every one-on-one, I told my manager where I wanted to go and what I could take on to get there. Eventually I interviewed for two management roles outside the company, at the same time I was quietly building toward one inside it. I was offered both. I wasn't fully sold on either one, so I brought all three options back to my manager. He asked me to talk to his boss, and their boss, before I made a decision. That is when I found out my manager's boss had no idea I wanted to move into leadership at all. That conversation shifted something for me. I had spent a year building visibility with exactly the wrong people. My manager liked having me as an individual contributor and had quietly put me in for a different promotion ...

Quick Bridge: Fifty-six percent of organizations do not view quality engineering as a strategic function. Yet engineering leaders spend sprint after sprint frustrated by the same QA problems: test counts that do not answer the risk question, compressed timelines that go unchallenged, and communication gaps that nobody names. This post explains why the QA communication problem is structural, what changed when Jesse led his own QA team directly, and what three conversations shift the dynamic without a reorganization. The complaint I hear about QA is never that the engineers are bad at their jobs. It is that the conversations never get to the right level. You ask for status. You get counts. You ask what the risk is. Nobody can answer. That gap is not accidental. It is structural. And most of the industry is living inside it. According to the Capgemini/Sogeti World Quality Report 2025-26, only 37% of organizations report strong cross-functional collaboration between QA and enginee...

Quick Bridge: Most technical leaders are waiting for someone to give them permission to lead. The problem is that the permission rarely comes. And in most rooms, most people are quietly relieved when someone else steps up and decides. This post shows you how and why people follow someone who does not have the title, and gives you the specific moves to start doing it this week. The Leadership Vacuum in Every Meeting Room There is a number that should change how you see every meeting you walk into. Only 6% of Gen Z and millennial professionals say achieving a leadership position is their primary career goal, according to the 2026 Deloitte Global Gen Z and Millennial Survey. Separately, DDI research found that 71% of people report that taking on a leadership role contributed to their stress levels. Read those two numbers together. In most rooms, in most meetings, in most project teams, the overwhelming majority of people are quietly hoping someone else will step up and own the deci...

Quick Bridge: When a leader steps up, teams often stall. Not because the people are weak. Because the context behind the critical work left with the leader. Most delegation conversations are about tasks. Almost none are about the reason those tasks exist. Here is what actually happens when that gap meets team growth — and how to close it before you need to. The Pattern No One Talks About Leaders get promoted. Teams get bigger. And somewhere in the transition, a quiet kind of failure starts. It does not show up in performance reviews. It does not show up in the first quarterly report. But over time, something shifts. The team that was humming before the change starts losing ground. Visibility fades. Internal relationships that used to matter stop getting attention. The work that kept the team on the map slowly goes dark. The reason is almost never the quality of the work. The reason is what the departing or scaling leader was carrying in their head that never made it into anyon...

Quick Bridge: When a company grows a manager's team by half or more, the assumption is that the manager just needs a better system. What actually happens is a slower problem: the real conversations that made you an effective leader stop occurring before you notice they've stopped. This post covers what research says is driving the megamanager era, what specifically breaks first, and how to think about protecting the leadership that actually matters when your headcount grows. The average American manager now oversees 12.1 direct reports, up from 8.2 in 2013, a 47% increase in twelve years, according to Gallup's latest workplace research. Fortune's coverage this spring called it the "megamanager era," tracing it to a deliberate corporate strategy: three years of middle-management flattening, accelerated by AI cost-cutting and a relentless push to rationalize headcount. The result is that managers who once had eight reports now have fifteen or twenty. Coache...

Quick Bridge: Most engineering leaders are still optimizing for the skills that got them their last promotion. AI has quietly changed which skills are scarce. Execution depth is becoming a baseline. Here are four diagnostic questions to tell you whether you are already in the trap, and four moves for getting out. The engineering team structure most of us grew up in is actively inverting. For decades, the standard ratio in software companies was roughly six engineers for every one product manager. In early 2026, Andrew Ng publicly described teams proposing a ratio of one product manager to every 0.5 engineers. He called it the product management bottleneck. [1] AI has made coding approximately 10x faster. The constraint is no longer how to build. It is deciding what to build. For engineering leaders, that shift is not abstract. It is a direct career signal. The Technical Leader Promotion Gap AI Is Widening Most engineering leaders were promoted because they were the best te...

Quick Bridge: If you applied for an internal leadership role and lost to an outside hire, the interview is not where you lost it. Leaders usually know who they want before the posting goes up, based on relationships built long before any role opened. This post shows why being internal is not the same as being known — and what actually builds the kind of cross-functional reputation that gets you tapped before a role ever appears. Most people know the hidden job market exists. Research consistently shows that 70 to 80 percent of job openings are never publicly advertised. Lou Adler surveyed more than 3,000 LinkedIn members and found that 85 percent of all jobs are filled via networking — before they are ever posted, before most candidates know to look. Most people file this away as an external job search problem. They assume it does not apply inside their own company. It does. And the people who understand that are the ones who get tapped. When a leadership role opens internally, most ...