You put in way more work than preparing for interviews for a raise that is often less than job hopping.
You want me to grind for two years for a raise when I can just be a C player and get it from someone else with stories about being an A player?
You put in way more work than preparing for interviews for a raise that is often less than job hopping.
You want me to grind for two years for a raise when I can just be a C player and get it from someone else with stories about being an A player?
Promotions are overrated and if you are in software you should be making a comfortable living from the beginning.
More money can be helpful, but it isn't worth the stress of chasing promotions and playing the political games required at higher levels.
Interviewer: “mr. so-and-so, I see that you worked as XXXXX at YYYY for ZZZZ number of years, can you tell us about the core reason your career stagnated and you were not promoted in all that time there?”
* assumes you somehow got the interview…
I've also had interviews where I had to explain long gaps in employment, another topic many assume will be uncomfortable or a red flag. It all comes back to telling a good story at the end of the day, explain what you learned, why you were in that position, and how you are better for it.
I cannot over-stress how important this is.
Being on a bad team will drain you fast, no matter how interesting the work is.
Meanwhile, churning out widgets is something you can do if you enjoy the people you're doing it next to.
I haven’t needed to look for employment in the past year or so, but I’ve heard some terrible things about the job market, enough that I’d be surprised if it was still possible given how slow hiring seems to be.
TL;DR: got here first | overworks | never ever does anything that could possibly be construed as challenging authority, such as having original ideas in front of someone ranked higher than you, or trying to help create some semblance of process.
Being absurdly incompetent at writing maintainable code that had serious, consequential, misunderstandings of the material needed to implement it? That's fine.
it's a feature, not a bug, to do just good enough a job to rush exec misunderstandings into prod, as long as anything wrong with it can be dissembled verbally, unless someone else wants to dig into the code.
This would have sounded horribly cynical and bitter and loser-speak when I was younger. Now that I saw it first hand, it clarified for me why people do startups and turnover is high, given it was a $300K/year job if you just show up 20 hours a week, and 40 hours a week for a month or two a year.
Younger me: lesson here is either care, and do a startup, or don't care and do the family and skiing or whatever.
Your plan of "I should go bank money for a few years so I can leave and do my own place safely" panned out great.
Your plan of "wow...standards are this low? People will see it and care, certainly if you're doing extremely impactful work" was completely wrong.