3 ms·

I was in a similar boat with my last job doing Support/QA/Custom Development for 2 years while the "official" devs went off and made a new version of the produc

I was in a similar boat with my last job doing Support/QA/Custom Development for 2 years while the "official" devs went off and made a new version of the product. About a year and a half in i brought it up and they agreed to move me out of support, but the pay raise wasn't nearly adequate for the duties expected. And I regretfully agreed to half raise now, half a raise later... (24k to 32k total) and ended up getting dev/support removed leaving me with QA (devs wanted dev back and I wasn't invited to the party). I promptly left the company and found a much better job doing Dev for 55k, which sadly burnt some bridges with people i liked. They will likely agree that you should be moved more officially into a dev position, but since you're moving up within the same company you shouldn't expect to get paid what you think is adequate for the duties. Giant pay bumps are an extreme rarity when moving up in the same company. This isn't just an IT problem, but it is why developers don't generally stay at the same company for more than 2-3 years. Have a friendly conversation with the right people about it, but make sure you have terms laid out that you can agree to in the long run with them, otherwise start looking elsewhere.

techmarketerguy 12y ago
Did you have any trouble finding that new position, coming from an "official" non-dev job? Or was it pretty straightforward once you showed them what you could do? I know getting your foot in the door is hard as a junior developer, so I'm inclined to stay here if they switch my title and duties.
- darkwulph03 12y ago
  I was worried about it since I only have my Associates (no plans to go back), but I code A LOT in my free time. I didn't realize it at the time, but I have the benefit of living in an area that has high demand and low supply of good developers. That helps a lot and I had 2 offers off the bat. I didn't even know the language i was hired to use, just had to show i knew how to code and solve problems. If they can't offer what you want long term, take what they are willing to give. Having a dev title for a year or so will help, but there isn't anything stopping you from searching shortly after you take what your current company offers. Then once you get an offer from somewhere else, you can see what your current company will do to keep you, but make sure you are willing to take the other job before you do that (doesn't always end well).
  - techmarketerguy 12y ago
    Awesome, thanks for the advice!
- djb_hackernews 12y ago
  If you really did build all of those things and can talk about them confidently you shouldn't be calling yourself a junior developer and definitely not a marketer/content writer if you are looking for a dev role.
  - techmarketerguy 12y ago
    Thank you. I definitely have an impostor complex about development, but you're right that I should drop the "technical marketer" title
tehwebguy 12y ago
> I promptly left the company and found a much better job doing Dev for 55k, which sadly burnt some bridges with people i liked. If those bridges are burnt because you left (or even joined a competitor) you are much, much better off. Employment is a transaction, your former employer chose not to pay you market rate.

techmarketerguy 12y ago

Did you have any trouble finding that new position, coming from an "official" non-dev job? Or was it pretty straightforward once you showed them what you could do? I know getting your foot in the door is hard as a junior developer, so I'm inclined to stay here if they switch my title and duties.

darkwulph03 12y ago
I was worried about it since I only have my Associates (no plans to go back), but I code A LOT in my free time. I didn't realize it at the time, but I have the benefit of living in an area that has high demand and low supply of good developers. That helps a lot and I had 2 offers off the bat. I didn't even know the language i was hired to use, just had to show i knew how to code and solve problems. If they can't offer what you want long term, take what they are willing to give. Having a dev title for a year or so will help, but there isn't anything stopping you from searching shortly after you take what your current company offers. Then once you get an offer from somewhere else, you can see what your current company will do to keep you, but make sure you are willing to take the other job before you do that (doesn't always end well).
- techmarketerguy 12y ago
  Awesome, thanks for the advice!
djb_hackernews 12y ago
If you really did build all of those things and can talk about them confidently you shouldn't be calling yourself a junior developer and definitely not a marketer/content writer if you are looking for a dev role.
- techmarketerguy 12y ago
  Thank you. I definitely have an impostor complex about development, but you're right that I should drop the "technical marketer" title

tehwebguy 12y ago

> I promptly left the company and found a much better job doing Dev for 55k, which sadly burnt some bridges with people i liked. If those bridges are burnt because you left (or even joined a competitor) you are much, much better off. Employment is a transaction, your former employer chose not to pay you market rate.