# Fast and slow ways to improve your reputation

DevFeed: [Fast and slow ways to improve your reputation](<https://devfeed.tech/articles/fast-and-slow-ways-to-improve-your-reputation-110691.md>)

Original publisher: [Read original article](<https://seangoedecke.com/how-to-get-assigned-interesting-work/>)

Published: 2026-11-01T00:00:00Z

Content type: article

Language: en

Sources: [Sean Goedecke](<https://devfeed.tech/sources/seangoedecke-com-rss-feed.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>)

Tags: [big-tech](<https://devfeed.tech/tags/big-tech.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [company](<https://devfeed.tech/tags/company.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [experience](<https://devfeed.tech/tags/experience.md>), [fast](<https://devfeed.tech/tags/fast.md>), [formal](<https://devfeed.tech/tags/formal.md>), [giving](<https://devfeed.tech/tags/giving.md>), [important](<https://devfeed.tech/tags/important.md>), [incentives](<https://devfeed.tech/tags/incentives.md>), [instead](<https://devfeed.tech/tags/instead.md>), [lead](<https://devfeed.tech/tags/lead.md>), [project](<https://devfeed.tech/tags/project.md>), [projects](<https://devfeed.tech/tags/projects.md>), [risk](<https://devfeed.tech/tags/risk.md>), [round-robin](<https://devfeed.tech/tags/round-robin.md>), [tech](<https://devfeed.tech/tags/tech.md>), [theory](<https://devfeed.tech/tags/theory.md>), [time](<https://devfeed.tech/tags/time.md>), [work](<https://devfeed.tech/tags/work.md>)

## AI overview

Managers often give high profile projects to engineers they already trust because project failure threatens their own reputation. This creates a cycle: experienced engineers get more chances to build a record, while others lack the experience to earn trust. The slower route is to ship small, low risk work reliably, make that visible, and gradually take on more responsibility. Faster routes carry more risk: build a relationship with a skip level manager without appearing pushy, create independent side projects that matter (which can waste time or irritate a manager), or impress trusted engineering colleagues who can recommend you. The latter works best on a healthy team. The article argues that appealing to fairness or career development alone is unlikely to change managers' incentives; position yourself so assigning you work serves their interests.

## Source excerpt

To get a good reputation in tech companies, you need to work on important projects. However, you need a good reputation first in order to get assigned important projects. Doesn't that make it impossible to get started? I get a lot of emails from engineers who are struggling with this problem. They go like this: I work with a strong senior engineer. I feel like my manager structures work so that strong engineer always gets the visible work, and the more they do, the more opportunities they get, while I sit on the sidelines. My manager agrees with me that it's time for me to start leading work myself, but every time a new project appears it always goes to the strong engineer. What do I do? This is a good case study for what I think of as "tech company theory of mind": understanding the actual incentives that motivate decisions in tech companies, instead of the formal process. According to the formal process, projects should probably be assigned round-robin to whoever has capacity and isn't currently working on one. But (as my emails complain) this is almost never how it works in practice. A vicious cycle Managers care about giving their employees chances to build a reputation, but they care more about developing their own reputation as someone who can deliver. High-profile projects are the best opportunity for new people to step forward and get known, but blowing up a project1 like that is the easiest way for a manager to tank their own reputation. They will thus typically hand these projects to someone they know can deliver, while simultaneously promising (including to themselves) that next time they'll take the risk of letting another person lead it. Of course it's a vicious cycle. The more you rely on one person, the more reliable they become and the less reliable their colleagues become, since they aren't getting the relevant experience. It's not very sustainable. However, the average manager tenure in big tech is only a couple of years2. Given that, it's rational