3 ms·

Whenever I interview I present myself as a developer with more than a decade of experience that wants $X / year and willing to go a bit lower for the right comp

Whenever I interview I present myself as a developer with more than a decade of experience that wants $X / year and willing to go a bit lower for the right company. Whatever other categorizations they might have for me, is on the company. Ultimately I don’t really care.

zabzonk 4y ago
Well, ditto. The most meaningless job title I ever wound up with was "Senior Systems Architect" - really only something they could put on my business cards so they could sell me for consultancy gigs. Bah! It's not what they call you, it's what they pay you - call by reference versus call by value, I guess.
- bryanrasmussen 4y ago
  >The most meaningless job title I ever wound up with was "Senior Systems Architect" hah, when I was employed by the Danish under ministry in charge of standardization (called IT og Telestyrelsen at that time) management people came through one day and asked what titles we wanted, and for various amusing reasons another guy and I said we want to be called "XML Architects". They gave us business cards too!
- mmmpop 4y ago
  > It's not what they call you, it's what they pay you This is correct because if I'm writing checks, the one making the most is generally my "senior" person. I suppose this doesn't scale well though, especially when you start talking about niche skillsets where being objectively "good" gets conflated with "useful at the moment."
DeathArrow 4y ago
>Whenever I interview I present myself as a developer with more than a decade of experience that wants $X / year and willing to go a bit lower for the right company I present myself as someone with plenty of experience in both writing code and software architecture. Someone they direly need and will help their business achieve its goals for at least X amount of money. Which would be a great deal for them even if it doesn't sound cheap in the beginning. Many told me it's too much. But a few have said yes. You should think about the largest amount you think you can obtain. And add 15 - 20 % on top. You will be surprised in finding that someone will say yes.

zabzonk 4y ago

Well, ditto. The most meaningless job title I ever wound up with was "Senior Systems Architect" - really only something they could put on my business cards so they could sell me for consultancy gigs. Bah! It's not what they call you, it's what they pay you - call by reference versus call by value, I guess.

bryanrasmussen 4y ago
>The most meaningless job title I ever wound up with was "Senior Systems Architect" hah, when I was employed by the Danish under ministry in charge of standardization (called IT og Telestyrelsen at that time) management people came through one day and asked what titles we wanted, and for various amusing reasons another guy and I said we want to be called "XML Architects". They gave us business cards too!
mmmpop 4y ago
> It's not what they call you, it's what they pay you This is correct because if I'm writing checks, the one making the most is generally my "senior" person. I suppose this doesn't scale well though, especially when you start talking about niche skillsets where being objectively "good" gets conflated with "useful at the moment."

DeathArrow 4y ago

>Whenever I interview I present myself as a developer with more than a decade of experience that wants $X / year and willing to go a bit lower for the right company I present myself as someone with plenty of experience in both writing code and software architecture. Someone they direly need and will help their business achieve its goals for at least X amount of money. Which would be a great deal for them even if it doesn't sound cheap in the beginning. Many told me it's too much. But a few have said yes. You should think about the largest amount you think you can obtain. And add 15 - 20 % on top. You will be surprised in finding that someone will say yes.