Career Advice: Would you take a step back to advance forward?
I am currently a software engineer in the Netherlands with more than 7 years total experience. In my current role next to being hands on involved with coding and development work I am also the team lead for 5 developers. I have been recently offered a job in Switzerland as a software systems engineer. The company has 4 levels (high-low), Principal, Senior, Engineer II, Engineer I. Even though the interview process went perfect, they have placed me at the top of Engineer II. I am now in doubt what to do. It feels a step backward, considering I am already a team lead and have quite some experience as well as ownership.
A scenario I am thinking is accept it, start and then apply myself and grow to senior and eventually principle, but I could be looking at 1-3 years to reach the senior level and some more time to reach the Principal. I like to seek some advice and opinion. Have you been in a similar situation? What were your thoughts and what did you do?
Thanks!
23 comments
[ 3.6 ms ] story [ 48.5 ms ] threadThe next biggest question is, how will this affect you financially, not just the pay, but the final savings after all the taxes and expenses.
And I think third is the career trajectory, if you really want to be in management or are happy as an individual contributor.
There are lots of jobs out there. You can find a better fit if this isn’t the right one.
Would you say I should bring up my concern to them? I don't need promises or guarantees, but I would have liked to know what is their career trajectory and promotion system.
Many of my friends are making additional studies into management, or sales. Some landed Head positions.
Point is, I wouldn't say that it is a step back. It is rather a completely new step, a change. Could be for good of for not that good. Depends on how much time are you willing to invest? Maybe in your current position you will advance further if you wait. Also consider the language barrier. Sometimes it makes a bit of difference. ;)
So I don't think you're taking a step back at all (unless you are getting a salary cut as well, then yes, don't do it).
I did exactly the same: I was tech lead at company X (staff engineer) but then I quit to join company Y working just as a normal senior engineer. I got a 20% bump in salary raise... and now I have ahead more levels with the senior level to grown to (and also levels within the staff level as well)... whereas at company X I as already thinking about switching to management (I didn't want that either).
Also, I do always the same kind of job no matter where I am: if I can lead, I lead, if I can mentor I mentor... it doesn't really matter if that's my role or not.
If you're really a leader, then they will notice and will promote you within their imaginary and meaningless career path ladder.
Do you want to move to Switzerland?
Do you want to do the Engineer II job?
If all answers are yes, take it.
Why do you want to leave your current job? Money? Don't like the work? Don't like the people? Bored, and you want something different? Can't advance any further where you are?
If you're after money, look at the money (counting taxes and cost of living).
If you're after advancement/title/prestige/future income growth, the problem is that the future is uncertain. If you have decided that you're not going to get what you want where you are, I would not take a step backward to maybe get it in the future. I would continue where I was, and keep looking, and move when I could go somewhere where I actually did get what I was looking for.
If you move, please be aware that it may not be possible to move into leadership for a long time or never.
Also be aware that you adapt to the new culture after some time. Hence, returning requires readaption again.
If your goal is more leadership and less of an IC role, then what you're proposing is probably a step in the wrong direction.
If your goal is to live in Switzerland, then you just have to ask yourself if you're OK with the drop in order to achieve your goal.
If your goal is to make a change in type of programming being done (e.g. from web front-end to video games) then taking a title (and possibly pay) drop is reasonable. You're going from being an possible authority in a particular domain to someone who is learning. Your current skills and experiences will be highly valuable, you'll learn faster than others, but you'll still have a lot to learn. I don't know how things work in the EU, but here in the States most likely you'll find yourself needing to job hop again in 2-3 years in order to get back to where you originally were (or more).
Answering your actual question, though... I did make that leap in my career and it was worth it. The change I made wasn't so drastic as my example. I had an end goal in mind and came up with a path to get there. It took me a while, but each step was lateral (my current skills were highly applicable) and I learned a lot each step. My path was * video games * video game telemetry (databases and data ETL) * big data at Disney * biotech (where I am now).
TL;DR - what's your goal? Does this change get you closer to realizing it?
Money is more meaningful than titles. Would you be making more money as an Engineer II at the new company than as a team lead at the old company? If you aren't, then it's probably a step backward.
If you would be making more money, then this is a step forward. In fact, it's a great opportunity, because you can get even further in your career by getting promoted to the "senior" level at your new workplace.
My current employer will generally hire ICs or Senior leadership from outside. The “inside baseball” of the company makes it difficult to succeed in middle management/team lead roles.
If the money is good you need to decide whether leading people is important to you. If it is, that’s ok, but this provably isn’t the right gig. If you don’t care, this might be a good role.
Having held the principal title when I was 27, most gigs beyond that were steps down in terms of title, salary, or benefits. Doesn't really matter as long as the next people hiring you can see your current value given your previous trajectory.
My path is only unusual to the extent that I worked in small R&D labs and pre-VC startups so the value equation of a greenfield prototype hacker is really not what you know or have experienced, but "how fast can you learn because we just made the thing yesterday, QA'ed it today, and would like to ship tomorrow", "how fast can you go from napkin sketch to believable demo" and then "how fast can you ship clean code vs. that mess the CTO dreamed up at 3 AM?"
Your trajectory may be different.
Where are you moving from? Personally I'd think that going in low give you room to grow in terms of money/role.
Other than this, titles are irrelevant IMO. Probably they just put you into the title with the same salary band.