11

How do you get noticed more for what you actually do at work? (I work as a software engineer to give more context) Like, this whole summer I feel like I've been churning of work / tasks that were important, without messing it up and with no guidance because most people were away or really slacking / not caring because management was away. On the other hand some colleagues seem to be slacking, ie picking up the easiest tasks, and then acting like it's really complicated and acting as if they are actually solving an important issue

I'm not really good at communicating and asserting myself but I really don't want to be in a situation where the people who are doing less stuff and are less invested than me are more rewarded. What should I do to be sure my work and efforts are noticed?

thro_away_
  • 111
  • 3

5 Answers5

31

I really don't want to be in a situation where the people who are doing less stuff and are less invested than me are more rewarded. What should I do to be sure my work and efforts are noticed?

Those are two completely different things, so step one: stop conflating them.

I really don't want to be in a situation where the people who are doing less stuff and are less invested than me are more rewarded.

No one wants to be in that situation. Everyone is in that situation. So step two: Get used to it, and stop caring. The question that should be on your mind is not "do my undeserving no good slacker coworkers deserve their bonuses?" The question on your mind should be "am I getting an adequate compensation for the amount of work I'm putting in?" The answers to those two questions have nothing to do with each other.

Put another way: the only way to control what bonuses your slacker coworkers get is to sabotage and badmouth them. Do you want to work at a company that encourages that kind of behaviour? Worry about what you're getting, not what anyone else is getting. Make yourself look good by enabling everyone around you to share in your success.

I'm not really good at communicating and asserting myself

Step three: get better at both. Once you are past entry level, software engineering is about communication, not writing code. You will not rise in your profession until you are able to communicate clearly with everyone in the organization.

Write more emails. Write more design documents. Write a blog. Answer questions on StackOverflow. Volunteer to give talks internally or to the public. There are lots of ways to practice communications.

When I was a junior engineer at Microsoft I was given a joke award -- a singing fish -- for being the guy on the team who wrote the longest, most detailed, most technical and most complete responses to design and implementation questions. It was a cute joke and I took it in the humour that it was intended, but it was also quite serious. That silly achievement was no accident; I deliberately set out to be known in the company as the guy to go to when you had a technical question about JavaScript, and that got noticed.

What should I do to be sure my work and efforts are noticed?

Start at the technical level. Are your tasks tracked in a change management system? Are your code changes tracked in a source code management system? If not, you have bigger problems than recognition. If they are, then you can use these as the basis of a weekly report on what you've accomplished this week and what you plan to accomplish next week.

Do you have code reviews? If not, again, you have bigger problems; start encouraging a culture of code reviews. Code reviews are a great way to showcase your work to your management and peers.

Do you have status meetings? Talk about what you've done in those meetings, where you're stuck, and how you can help other people get themselves unstuck. Do you have skip-level meetings with management? If not, start taking your manager's manager out to lunch a few times a year. Ask them if you are on track for your career goals, and if not, what you can do to improve. This effort will be noticed.

Eric Lippert
  • 7,777
  • 2
  • 26
  • 33
  • And when someone as known as Eric Lippert talks to you about getting known, you'd better drink his writings. For sure, I do. Just replace software engineer by any job that has a level other than entry level. – gazzz0x2z Sep 01 '16 at 12:53
  • 3
    Best answer, but to add to it. You need to know your managers style, so that they take your accomplishments in the correct tone. There is a series of techniques/training called "managing up". Brief overview. https://hbr.org/2015/01/what-everyone-should-know-about-managing-up – Simon O'Doherty Sep 02 '16 at 05:47
  • what do code reviews have to do with the management? I never heard of a high level manager doing code reviews 2) about asking his manager's manager about career goals and how to improve why would that be the proper person to ask? He probably knows only what his immediate manager has informed him about his evolution.
  • – smith Sep 02 '16 at 20:59
  • @smith: The question is about recognition; code reviews are about communicating the values of the organization to a group. Does management come to code reviews? Probably not. Does management run reports on who participates in code reviews? Maybe. Does management ask your peers at review time whether your comments are helpful in code reviews? If they're smart, they do. – Eric Lippert Sep 02 '16 at 21:20
  • @smith: Everyone on your management chain is the right person to ask about your career, in a properly functioning management chain. And if you're angling for a raise, a promotion, or an award, do you think that being known as friendly, helpful, engaged, smart, motivated and ambitious to senior management helps or hinders that process? – Eric Lippert Sep 02 '16 at 21:22
  • @smith: If the only thing your managers manager knows about you is what your manager told them, you have a big problem. The best advocate for you is you; don't cede that to someone else who has their own agenda. – Eric Lippert Sep 02 '16 at 21:23
  • I am not arguing that what you say are reasonable. But what I think you describe are not normal management. But very good management and that is rare I think – smith Sep 02 '16 at 21:25
  • 1
    @smith: Well if the question is "how do I succeed in an environment full of bad management who make bad decisions?" then I don't know; I'd need to know more about the nature of the bad management before I gave any suggestions. – Eric Lippert Sep 02 '16 at 21:28
  • Then you have been lucky if you only worked in places that management is organized and cares. I don't think that is the case of the average company. If it were this SE would not have a reason to exist – smith Sep 03 '16 at 08:56
  • 2
    Upvoting for "Once you are past entry level, software engineering is about communication, not writing code." Far too many programmers and software engineers fail to understand this. Churning out code is only half of the job. – goat_fab Dec 18 '19 at 16:29