When to look for a new job without looking like a job hopper

Question

One year ago I got my first job in IT (in some area A), and so far everything is going well. However, after graduating university, I wanted to work in a different area (let's call it area B), but I accepted this job offer because I didn't want to risk and keep looking for something different. I couldn't afford spending several months searching for a job that I'd really like. I'm still very interested in area B, and I want to start looking for a job there, but I see some potential issues:

1. I've worked for my current company for only one year, and it's my first job in IT, so applying for a new job now might make me look like a job hopper. On the other hand, areas A and B are quite different (e.g. like QA and web design), so working for too long in area A reduces my chances to find something in area B. What, based on your experience/observations, would be the right moment to start looking for a new job instead of the job that was taken just for money and experience?
2. Is it ok to honestly say during a job interview that I want to quit my current job because I always wanted to do B and have never been really interested in A? Or should I make up a better reason?

P.S. I'm living in the EU, if it matters.

Answer 1

The unfortunate truth of software development is that moving around is sometimes a necessity. Staying with the same tech stack for a long time can be disadvantageous.

Personally, as a general rule of thumb, I "omit the negative" in an interview. Don't speak in negatives, about the old job, about people, about anything really. You should always be looking forward and appear to have goals.

Something like: "I've always wanted to do B. It's fascinating that some example of you knowing about it through personal exploration. That sort of thing really moves me."

Something like this. In short, enthusiasm. It would be naive to assume anyone's first job is their IDEAL job. But people eventually move toward their ideal. So best not talk about the steps before and talk about the steps ahead.

If I were you, I would switch and then stay at the new job for at least 2-3 years... (closer to three) and that should brake any hint of job hopping.

Answer 2

To try to answer your specific concerns:

Basically the news is all good.

"One year ago ..

So, it is basically the norm to leave your first job after a year, assuming you're good. A year is forever in software. This is a non-issue.

Some more on that ..

Looking at the comments below. It would appear that amazingly ...

... the median tenure even at Apple is less than two years. Whoa!

(That would seem to be for all programmers, not just "newbies"; your first job is even shorter.)

This random statistic from the internet emphasizes that it's a non-issue if you have "only" stayed a complete year.

"different area ..

In software, every time you sit down to work, it's a different area. The very definition of being a skilled programmer is that you can instantly pick up and excel in any field.

I urge you to immediately get away from "A" to ANY field .. whether B, C or D or E.

Do not hesitate to take a contract with less $ if it gets you out of the "A" type-casting.

You don't want to be this guy: ¹

"What would be the right moment to start looking...

Sunday night.

"I couldn't afford spending several months searching..

With this point, you definitely face a serious problem, which you must fix if you have not already.

You can only get programming jobs from a position of strength.

To work in the dynamic, high-pay, high-risk field of software you MUST have a couple months reserve money on hand so that at any moment you can walk, and then leisurely look for your next contract.

If you have not achieved this "iron reserve," ² do that FIRST and then enact your plan.

"Is it ok to honestly say during a job interview that I want to quit my current job because I always wanted to do B and have never been really interested in A? ...

It would be remarkably naive to actually say that:

1. It implies that you believe software is a "single field" skill. This is the one single thing you never, ever want to imply as a programmer.

2. The fact that you want another job is a non-issue. A sports team does not have to explain "why they want to win"; you don't have to explain "why you want to advance your career."

3. In general NEVER SAY ANYTHING NEGATIVE, IN ANY WAY, ABOUT ANYTHING. Your first job was "fantastic and challenging, but you're ready for the next challenge".

And note the critical point in a comment above: You'll need to have a good answer to the inevitable follow up "So why did you take a job in A?"

Fill your answer with overwhelming positives. "It was a great chance that came up straight away. Mr. Smith is super-nice and Ms. Jones is a fantastic Pascal programmer. Since high school I've been looking for challenges so I grabbed it.

For God's sake: never, ever, mention "money problems". Or indeed any problems.

To repeat it's totally OK and good to mention that you love the NEW field, but never knock the OLD field A in any way.

---

¹ Brilliant actor Russell Johnson is often given as an example of a fantastic actor who's career was killed by being type-cast in one role.

² Courtesy that important figure in Software, Napoleon Bonaparte.

Answer 3

You should work wherever you feel motivated for.
It not only increase your creativity and performance, but also get you a non-stressfull life.

I've worked for my current company for only one year, and it's my first job in IT, so applying for a new job now might make me look like a job hopper

One year is not a big thing, better change now than later.

Is it ok to honestly say during a job interview that I want to quit my current job because I always wanted to do B and have never been really interested in A? Or should I make up a better reason?

It a legtimate reason, but you should demonstrate during the interview that you have the skills to get the job done in area B.

Answer 4

The times where you work 40 odd years at the same company,retire and bite the dust are long gone.

Work on projects, not at companies.

Be a freelancer, an employee, a contractor, be whatever is asked for you to be to get that project or job you want, whenever you feel like you want it, wherever in the world it might take you.

Don't like what you do?

Find something else you want and do that.

The result will be a CV full of experience in fields that you excell in because you loved doing them.

Experiences you mostly couldn't acquire by staying at the same company for years on end.

You're constantly challanged with new circumstances, clients, projects, colleagues and other requirements that become routine at the same company quickly.

That's not job hopping, that's taking opportunities.

It's also how the world works today.

Job hopping can still be a thing in some professions but nowadays companies like software developers or creative businesses for instance ramp up and downsize according to project needs or their immediate financial situation.

Getting a job and being after few months on the market again is not uncommon.

Even permanent contracts are far from what they used and are promoted to be.

Oh yes, more and more industries hire freelancers, not employees for obvious benefits to the company, be prepared for that reality.

On top, in todays global economy jobs don't come to you, you go where the jobs are and move on once the project is done or stick around for round two, maybe three...

A nice side effect is, provided you're good at what you do, that each time you start a new gig you can raise your salary due to more experience and you can quickly get up that ladder (read jonior,mid,senior,lead).

Even management positions are often short or mid term for diverse reasons.

Another side effect is that you never have to answer or fear JOB HOPPING questions.
Your contract only ever was for a SET AMOUNT OF TIME from the get go.

Granted, this is not for everyone and arguably not a stable life to have a family, so do it while you're young and free as they say.