4 ms·

I won't say there's no bias (I'm sure it exists everywhere), but I think it's not an "expensive image" that gets you promoted as much as confidence. Many peopl

by dack 5y ago

I won't say there's no bias (I'm sure it exists everywhere), but I think it's not an "expensive image" that gets you promoted as much as confidence. Many people who grew up rich have a natural confidence to them (because they are protected if they lose their job, have been told they'll be someone important one day, given lots of help in life), and that helps a lot in giving a vibe that you'll succeed. The great thing is that the confidence can be gained even if you didn't grow up in the same circumstances, it just takes more work.

giantg2 5y ago
I've gone the other direction. The company has screwed me over enough that I know life is shitty and all the stuff teachers and parents tell you growing up is a lie. The confidence didn't help me anyways (due to politics) as I'm 9 years in and only a midlevel dev, even though I've worked in roles above my current one (senior dev, tech lead, ASC). Most of the people in the office talk about fancy expensive things. If you don't participate in that lifestyle, there's little connection.
- Twixes 5y ago
  Okay, so really the question is, why are you still at that company and not looking around to switch to a better one?
  - giantg2 5y ago
    I have a family to support and have no options (the tech was FileNet and later Neoxam, and the wife refuses to relocate).
    - dack 5y ago
      Hey, sorry to hear about your predicament. A lot of companies hire remotely these days, or are totally remote (Gitlab comes to mind). Two things I would recommend if you are open to advice: 1. Consider the possibility that you have some skills to grow to achieve more senior levels. Confidence helps, but it's not enough on it's own. 2. Interview at other companies that don't require you to relocate to see what you're worth - switching jobs is (sadly) one of the easiest ways to get promoted or a pay raise. Good luck!
      - giantg2 5y ago
        1. I'm not posting for senior roles. I know I have more to learn about the new technologies since I'm switching stacks. It's not just confidence that makes me think I was performing at that level. The olny reason I wasn't officially given the title is because of politics and poor leadership by my superiors. I had people from other teams calling me a tech lead, a commendation letter from another team due to my involvement in an enterprise wide upgrade, my supervisor said she wanted me to get the highest performance rating but couldn't make it happen (political reasons), and everyone on the team treated me like the tech lead and even called me that. For the senior developer year, it was pretty similar but since we had an official tech lead hired on I let him handle half the elevations and half the interaction with other teams. My manager even said when he gets a new task that's highly technical and difficult, he gives it me or the tech lead. I met some people from outside my team offsite by chance. We were talking about work stuff pretty regularly. They where surprised when I said I was only a midlevel dev. They thought I was a senior dev or tech lead based on the things I was saying and doing. I had the same thing happen on the next team I went to where some techleads in the department were surprised that I was only a midlevel. Also I was the ASC for that application and recieved excellent reviews from everyone about that role. That role is supposed to be for people who are a senior dev or higher. Unfortunately there were political issues in that group too. So after two years of working like this, my supervisor (different one) tells me that I could be promoted but I have to work extra time everyday. Now I'm fine putting in some extra hours to make a date or run an elevation. I'm not just going to work extra hours above company policy as a normal thing. Why would I take a 13% increase in hours for a 7% raise? That's taking a rate cut for a position with more (official) responsibilities. 2. I'm probably not worth anything since I have to learn the new stacks. They have me in AWS tech, which is ok. I got certified, but that doesn't mean much since I dont get a lot of chances to use it. I get some experience in Java and Python ECS and Lambdas. Some Dynamo, Cloudwatch, SNS, SQS, etc. A lot of this is stuff like synthetic alerts or increasing test coverage, which sucks. But then they also throw me on no/low code stuff like Splunk and Tableau, which also sucks. I'm never going to become an expert if the type of work is constantly changing and there are big gaps between when I last used that skill and when I'm asked to do it again.
        5y ago

by dack 5y ago

giantg2 5y ago

I've gone the other direction. The company has screwed me over enough that I know life is shitty and all the stuff teachers and parents tell you growing up is a lie. The confidence didn't help me anyways (due to politics) as I'm 9 years in and only a midlevel dev, even though I've worked in roles above my current one (senior dev, tech lead, ASC). Most of the people in the office talk about fancy expensive things. If you don't participate in that lifestyle, there's little connection.

Twixes 5y ago
Okay, so really the question is, why are you still at that company and not looking around to switch to a better one?
- giantg2 5y ago
  I have a family to support and have no options (the tech was FileNet and later Neoxam, and the wife refuses to relocate).
  - dack 5y ago
    Hey, sorry to hear about your predicament. A lot of companies hire remotely these days, or are totally remote (Gitlab comes to mind). Two things I would recommend if you are open to advice: 1. Consider the possibility that you have some skills to grow to achieve more senior levels. Confidence helps, but it's not enough on it's own. 2. Interview at other companies that don't require you to relocate to see what you're worth - switching jobs is (sadly) one of the easiest ways to get promoted or a pay raise. Good luck!
    - giantg2 5y ago
      1. I'm not posting for senior roles. I know I have more to learn about the new technologies since I'm switching stacks. It's not just confidence that makes me think I was performing at that level. The olny reason I wasn't officially given the title is because of politics and poor leadership by my superiors. I had people from other teams calling me a tech lead, a commendation letter from another team due to my involvement in an enterprise wide upgrade, my supervisor said she wanted me to get the highest performance rating but couldn't make it happen (political reasons), and everyone on the team treated me like the tech lead and even called me that. For the senior developer year, it was pretty similar but since we had an official tech lead hired on I let him handle half the elevations and half the interaction with other teams. My manager even said when he gets a new task that's highly technical and difficult, he gives it me or the tech lead. I met some people from outside my team offsite by chance. We were talking about work stuff pretty regularly. They where surprised when I said I was only a midlevel dev. They thought I was a senior dev or tech lead based on the things I was saying and doing. I had the same thing happen on the next team I went to where some techleads in the department were surprised that I was only a midlevel. Also I was the ASC for that application and recieved excellent reviews from everyone about that role. That role is supposed to be for people who are a senior dev or higher. Unfortunately there were political issues in that group too. So after two years of working like this, my supervisor (different one) tells me that I could be promoted but I have to work extra time everyday. Now I'm fine putting in some extra hours to make a date or run an elevation. I'm not just going to work extra hours above company policy as a normal thing. Why would I take a 13% increase in hours for a 7% raise? That's taking a rate cut for a position with more (official) responsibilities. 2. I'm probably not worth anything since I have to learn the new stacks. They have me in AWS tech, which is ok. I got certified, but that doesn't mean much since I dont get a lot of chances to use it. I get some experience in Java and Python ECS and Lambdas. Some Dynamo, Cloudwatch, SNS, SQS, etc. A lot of this is stuff like synthetic alerts or increasing test coverage, which sucks. But then they also throw me on no/low code stuff like Splunk and Tableau, which also sucks. I'm never going to become an expert if the type of work is constantly changing and there are big gaps between when I last used that skill and when I'm asked to do it again.
      - 5y ago