There is no magic number, but staying long enough to ship, maintain and learn from real work, often around 18 months to 3 years early on, usually serves you better than hopping every year. Switch when you have stopped learning, your pay has fallen clearly behind, or the environment is harming you, not just because others are moving.
What people tell me
People around me seem to switch companies every year and talk about big salary jumps. I have been at my current company for a bit over a year. I am learning, but slowly, and the pay is average. I keep wondering whether I am falling behind by staying, or whether switching too often will make my CV look bad. I do not know what a sensible timeline is.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- Early in your career, tenure buys depth: you see your own decisions play out in production. That is hard to get in under a year.
- Frequent short stints are not automatically a red flag, but a pattern of many under a year invites questions.
- Good reasons to move: learning has stopped, pay is well below market after asking, or the environment is damaging you.
- Weak reasons: fear of missing out, one bad week, or a peer's salary post.
- Decide with a checklist every six months rather than on impulse.
The honest answer: it depends on what you are getting
A fixed rule like "switch every two years" ignores the only question that matters: is this job still giving you what you need right now? That usually means some mix of learning, money, stability and the right kind of experience for where you want to go.
That said, patterns do matter, so here are some rough reference points.
Rough ranges, not rules
| Tenure | How it tends to look | What you usually get |
|---|---|---|
| Under 1 year | Fine once, with a reason; a pattern raises questions | Onboarding, a few features, not much ownership |
| 1 to 2 years | Normal, especially early career | Shipped work, some ownership, first real mistakes |
| 2 to 4 years | Solid | Depth, owning a system, maintaining your own decisions |
| 4+ years | Solid if you grew; a risk if you did the same thing all along | Deep context, possibly leadership, possibly stagnation |
The biggest learning that short stints miss is seeing your own work age. When you build something and then maintain it for a year, you learn why the shortcuts hurt. People who leave every 10 months often never get that lesson.
Why switching can pay off
Switching is often where larger salary increases happen, because new employers price you at today's market while internal raises tend to move in smaller steps. A move can also give you a bigger scope, a better team, or a technology you cannot get where you are.
Those are real benefits. They just come with costs:
- You start again on trust and context, which takes months.
- You lose the credit you built with your manager and team.
- A new job can be worse than the old one in ways you cannot see from the interview.
- Several short stints in a row can make hiring managers ask whether you will stay long enough to be worth training.
Good reasons to move
- You have stopped learning for six months or more, and asking for new work has not helped.
- Your pay is well below market, and you have asked properly. How do I ask for a raise as a software engineer? covers that step.
- The environment is harming you: constant overwork, disrespect, or a manager you cannot work with.
- The company is unstable and the signs are clear.
- You need a different kind of experience, for example moving from a service-based company to a product company. See How do I switch from a service-based company to a product-based company?.
Weak reasons to move
- A friend posted about a big jump.
- One stressful sprint.
- A vague sense that you "should" be somewhere bigger.
- Escaping a skill gap that will follow you to the next job anyway.
A six-monthly check
Instead of deciding in a bad moment, put a reminder in your calendar every six months and score each item from 1 to 5:
| Question | Score 1 to 5 |
|---|---|
| Am I learning things I could not learn easily elsewhere? | |
| Is my pay within a reasonable range of the market? | |
| Do I trust my manager and team? | |
| Is my scope growing? | |
| Would this job look good on my CV for the next role I want? | |
| Is my health and life outside work okay? |
If most scores are 3 or above, stay and push for growth where you are. If several are 1 or 2, and they were also low six months ago, start looking seriously. The blog post Fourteen Questions Worth Answering Before You Change Jobs goes further.
How to explain short stints
If you already have one or two short roles, do not hide them. Give a one-line, non-dramatic reason: "The team was dissolved after a restructure", "The role turned out to be mostly support work, and I wanted to build". Then move on to what you achieved. Interviewers mostly want to know you will not leave them in six months for no reason.
A 30-day plan if you are unsure
| Week | Action |
|---|---|
| 1 | Fill in the six-monthly check honestly. Write down what you want from the next two years |
| 2 | Talk to your manager about growth and pay. Note the response |
| 3 | Look at 10 to 15 job listings for the role you want next. List the skills you lack |
| 4 | Decide: stay with a growth plan, or start applying with a clear target |
Browsing open roles and companies is a cheap way to test the market without committing.
Common mistakes
- Leaving before you have shipped anything meaningful. You leave with little to talk about in interviews.
- Staying years past the point of learning, out of comfort or fear.
- Switching for money alone into a worse team, then switching again within months.
- Not asking internally first. Sometimes the growth you want is available if you ask.
If you are still stuck
How do I negotiate my salary when switching to a new developer job? covers the money side if you do move. If you want to talk through your particular trade-offs, join Sefism for free and use your joining credits to ask a question or book a 1:1 session.
Was this answer helpful?
Read next
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.