# Giving and taking credit in big tech companies

DevFeed: [Giving and taking credit in big tech companies](<https://devfeed.tech/articles/giving-and-taking-credit-in-big-tech-companies-54686.md>)

Original publisher: [Read original article](<https://seangoedecke.com/giving-and-taking-credit/>)

Published: 2026-08-02T00:00:00Z

Content type: opinion

Language: en

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

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

Tags: [big-tech](<https://devfeed.tech/tags/big-tech.md>), [giving](<https://devfeed.tech/tags/giving.md>), [manager](<https://devfeed.tech/tags/manager.md>), [take](<https://devfeed.tech/tags/take.md>), [team](<https://devfeed.tech/tags/team.md>), [tech](<https://devfeed.tech/tags/tech.md>), [visibility](<https://devfeed.tech/tags/visibility.md>), [work](<https://devfeed.tech/tags/work.md>)

## AI overview

In large tech companies, good work may go unnoticed because managers often rely on trusted engineers to judge technical contributions, and informal judgments can be unreliable on large or fast-changing teams. The article recommends making work visible through manager updates and internal technical posts, while sharing credit by thanking contributors and involving others in projects. That gives colleagues reasons to speak positively about the work and may reduce incentives to assign blame to a project's sole visible owner when complex failures occur. The author cautions against both relying on a manager to notice everything and hoarding credit; blame still follows when someone clearly caused a failure.

## Source excerpt

Engineers often complain that visibility should be their manager's job. In other words, they think engineers should be able to focus on the code, while their manager figures out who's doing well and rewards them. This attitude is an extension of the "school fantasy": the idea that your workplace should operate by the same rules as your school or university. After all, you didn't have to worry about "visibility" during your education. You simply did the assignments and tests you were given, and if you did well you were rewarded with a good grade. Many big tech companies encourage this attitude, because it helps them recruit smart graduates. They fashion their workplaces to look and feel like a university, even calling the physical space "campuses". But it's still work, not school. If you treat it like school, you are going to have a bad time. Taking credit The first lesson many new engineers learn is that you have to take credit for your work. If you silently jump in to help a struggling project and get it back on track, there's no guarantee of reward. Credit will naturally flow to the project lead, not you. In fact, if this project is outside of your direct team, it's likely you will be punished for it: to your manager, it will look like you're simply doing nothing at all. Even when your manager is watching your work, credit is largely uncorrelated with how well you did. That's because, unlike at school, you are the subject-matter expert on your own work. Software systems are so complicated that only the people who work on them can hope to understand them, and even that understanding is always imperfect. If even experts can't reliably estimate the difficulty of changes, how is your manager supposed to assess your technical performance? The answer is they aren't. They're simply not qualified to assess it. Instead, smart managers will find engineers on your team they trust and ask them how you're doing. On small teams that have worked on a single codebase for a long t