A lot of the frustration I typically hear in this camp is something like “well I shipped a huge refactor that cleaned up all the code, why does no one appreciate that?” One particular interaction that got me thinking was a few years ago listening to an acquaintance telling me how he spent months meticulously cleaning up the data pipeline and making it perfect, and how no one appreciated this work. Like, as an enginee…
How I influence tech company politics as a staff software engineer
51–60 of 216 posts
Re: How I influence tech company politics as a staff software engineer
#52Earlier quoted context omitted.
That's the crux. I don't want a career in a large tech company.
Is working in a small tech company any different?
Conversely, if you're mediocre, there's nowhere to hide.
Or maybe instead of saying there aren't politics at small companies, it's more accurate to say that there are politics, but they're simple--everyone strives to make the (hopefully benevolent) dictator, I mean founder, happy. If your founder is awesome, life is good. If your founder is not awesome, well, everyone is going to have a bad time anyway.
Re: How I influence tech company politics as a staff software engineer
#53this involves you getting a chance to work on it in the first place. why would you in particular be getting to work on those projects?
you have to first align yourself with VP and become their bitch. someone who they can trust. you should always follow prison strategy of finding the biggest bully in the yard and becoming their bitch. only then you get to even sniff work thats important. don't even think that you will be given important projects if you show off your technical acumen and skills. that strategy usually backfires and puts a target on your back both from ur peers and superiors who now see you as a threat.
just remember ppl who got into managment positions have no technical skills anymore and are highly insecure of that fact. they will murder you if they even have a little bit of inkling that you are someone who is technically proficient that can drive projects with little help.
Re: How I influence tech company politics as a staff software engineer
#54It seems like this post can be summarized as follows: 1. If your manager has something in particular they want you to do, you should do it. 2. If your manager doesn't have something in particular they want you to do, you should figure out what they will want you to do in the future , and make any necessary preparations so that it will be doable when they want it. I'd say it's good advice. The only thing I would add i…
Re: How I influence tech company politics as a staff software engineer
#55It seems like this post can be summarized as follows: 1. If your manager has something in particular they want you to do, you should do it. 2. If your manager doesn't have something in particular they want you to do, you should figure out what they will want you to do in the future , and make any necessary preparations so that it will be doable when they want it. I'd say it's good advice. The only thing I would add i…
Or better options - just do the job you were hired for and go home or find that rare job (if possible) where engineering has a bigger role than politics. It is not pleasant to play a guessing game trying to please some manager, just because they’re your boss. Life is too short for stupid games
Re: How I influence tech company politics as a staff software engineer
#56Earlier quoted context omitted.
In case you can share an alternate strategy to make a career in a large tech company, please do, would be interested.
you should do everything possible to make a career in a small company. after three decades as SWE it is my #1 (there is not even remotely close #2) advise for everyone in the early stages of their career
Re: How I influence tech company politics as a staff software engineer
#57Man, I must not have worked at dysfunctional enough companies. I can't relate to the opening remarks in this article at all. I'm used to really open communication from the top down and, even when we build in a direction I disagree with, we've discussed things enough that I'm at least interested in seeing why someone else I consider intelligent sees the world so differently. Perhaps it has to do with only working for…
i am guessing you never got promoted at work?
Re: How I influence tech company politics as a staff software engineer
#58IMO the best you can do: - Ship often to prod (don’t do theoretical work). - Ship wins (as defined by generally acceptable metrics.) - Have someone in management or a PM who is good at selling your wins Even here, though, you will run into problems. There is always a new VP or leader looking to make an impact. Because you maintain the current systems your team is engaging in WrongThink and new VP has shiny new RightT…
Looking back on my career, one of the single biggest changes I could have made to improve my success was escaping teams with bad PMs as fast as possible.
Great PMs improve everything, but they're hard to find. I spent too much time sticking around on teams where bad PMs were driving us in the wrong direction and failing to interface effectively with the rest of the management team. As soon as something changed that removed those PMs from the situation, everything improved.
Re: How I influence tech company politics as a staff software engineer
#59IMO the best you can do: - Ship often to prod (don’t do theoretical work). - Ship wins (as defined by generally acceptable metrics.) - Have someone in management or a PM who is good at selling your wins Even here, though, you will run into problems. There is always a new VP or leader looking to make an impact. Because you maintain the current systems your team is engaging in WrongThink and new VP has shiny new RightT…
Re: How I influence tech company politics as a staff software engineer
#60A lot of the frustration I typically hear in this camp is something like “well I shipped a huge refactor that cleaned up all the code, why does no one appreciate that?” One particular interaction that got me thinking was a few years ago listening to an acquaintance telling me how he spent months meticulously cleaning up the data pipeline and making it perfect, and how no one appreciated this work. Like, as an enginee…
The easiest way to do that is to speak the same language everyone else is. Your product manager probably speaks in dollars (or euros, renminbi, etc). If you provide a good-faith estimate (ballpark ranges are totally fine) that increased test coverage or whatever your technical objective is will cost 200 dev hours, and save 400 dev hours on an annual basis, or reduce the rate of support tickets by 15%, or allow for X future business scenario to be supported or whatever, you'll generally have way better luck. My favorite "trick" is taking tech debt work, and framing it in a way so, not only do I not have to push for it as "tech work", but my PM will actually put it on the roadmap proactively because it just makes sense from a business perspective.
It also gets easier over time. You might get some skepticism at first, but if you have a history of delivering accurate estimates and results over months or years, you'll build trust with stakeholders such that what might've taken a round of meetings to convince them before, can now be a 10-minute conversation.