Impact Over Titles

Early in my career at a massive outsourcing firm, my manager gave me a piece of feedback that stuck with me:

“You are doing a great job for the customer, but you need to be more visible in the company if you want to grow.”

It sounded like standard career advice, but it revealed a toxic culture of promotion hacking.

In that environment, I watched people speedrun their careers, jumping from Junior to Lead Developer in just four years. They didn’t do this by writing great software; they did it by checking the right boxes on a corporate ladder and making sure management saw them doing it. The loudest voices got promoted, while the actual stability of the code they left behind barely mattered. They were optimizing for their titles, not their impact.

Today, I’m an Engineering Manager at a mid-sized product company (about 50-60 engineers), and the engineering culture here is fundamentally different. In a product company, you simply can’t fake your impact. Because we all work on the same core systems, everyone feels the results of your work. Career growth isn’t about gaming a checklist or bothering your manager for a promotion. It’s about how your work actually improves the product and makes life easier for the rest of the engineering team. Real impact is what matters. But moving to an impact-driven culture highlights a new problem. What happens to the quiet, “shy” engineers?

Every team has developers who quietly fix the nasty memory leaks, write solid documentation, and keep production stable. They do the real work, but they hate “bragging”. In a world full of promotion hackers, these reliable engineers easily get overshadowed by the squeaky wheels.

The Visibility Framework for Quiet Engineers

As an Engineering Manager, I realized that visibility is still necessary, but it has to be the right kind. To help quiet engineers grow without forcing them to become sleazy self-promoters, we use a simple three-part framework:

  1. Shift the Mindset: “Self-Promotion” to “Knowledge Distribution”
    Quiet engineers hate self-promotion because it feels like ego. So, we change the framing.
    When you share how you solved a hard problem, you aren’t bragging - you are distributing knowledge.You are potentially saving the next engineer 10 hours of debugging.
    We shift “visibility” from empty noise into a valuable act of helping the team.

  2. Make Impact Visible Through Artifacts
    Squeaky wheels make a lot of noise in meetings, but reliable engineers build things that last. I encourage my team to leave a paper trail of their impact through durable artifacts:

    • Slack Posts: Instead of posting “Look at this hard thing I did,” they say, “Here is a new tool I built that will save your squad time,” or “Here is the root cause of yesterday’s bug, and how to avoid it.”
    • ADRs: Writing down an architectural proposal before writing the code. It proves you are thinking about the big picture and invites collaboration rather than working in isolation.
    • Postmortems: When things break, quietly fixing them isn’t enough. Writing a blameless postmortem explaining why it broke and how we fix the system going forward shows incredible leadership.

  3. The Manager-Engineer Contract
    Visibility is a two-way street. It is the engineer’s responsibility to actually write these artifacts and hit “send.” But it is the manager’s responsibility to create an environment where that behavior is rewarded. If I, as an EM, still hand out promotions to the loudest person in the room who writes zero documentation, the framework falls apart. I have to actively look for these artifacts and use them as the foundation for performance reviews.

How to Actually Ask for a Promotion

If you are reading this and thinking, “I want to grow and get promoted, but I genuinely don’t know how to increase my impact,” the answer isn’t to ask for a promotion checklist. The answer is to change the questions you ask your Engineering Manager or Tech Lead during your 1-on-1s.

Instead of asking, “What boxes do I need to check to reach the next level?” try asking questions calibrated for real business value:

  • “What are the biggest bottlenecks our team is facing right now that I can help solve?”
  • “Are there any upcoming projects where I can take more ownership and get a few more ‘swings at the bat’?”
  • “How can I align my daily work more closely with the company’s highest priorities?”
  • “Is there any critical ‘glue work’ or tech debt that no one wants to do, but would massively help the team if someone owned it?”

When you ask these questions, you are signaling to leadership that you are ready to solve their problems and the company’s problems, rather than just advancing your own title. Ironically, taking on those exact problems is the fastest way to earn that promotion.

If your growth depends on being loud, your culture is broken.