You're likely ready to switch after one to two years when you can name what you've delivered and what the next role offers that this one can't. This guide gives you a readiness test, the wrong reasons to leave, and how to explain a short stint in interviews.
You're probably ready to switch after one to two years when you can name two or three things you've actually delivered, and when the next role would give you something this one can't, such as more scope, a skill you can't practice where you are, or a team that will push you. If your main reason is that this month has been miserable, wait a little and run the test below first. A bad quarter feels like a verdict, but it usually isn't one.
Key takeaways
One to two years is long enough to form a real opinion about a job and short enough that you might doubt whether you gave it a fair shot. In the first few months, a lot of what you feel is onboarding noise: unfamiliar tools, unclear priorities, a manager you're still learning to read. By the second year, the novelty is gone. What's left is either real growth or the slow realization that you've been doing the same work with a slightly different title.
That ambiguity is why this decision feels so loaded. You're not a fresher who needs a first job at any price, and you're not a senior person with a decade of track record to lean on. You have some experience, and you're trying to decide whether it's enough to move on with. The answer depends less on the calendar and more on what you can show and what you're aiming for.
Start with a blank page and write down three things you've shipped, fixed, owned, or improved. Be specific. If you have numbers, use them. If you don't, describe the scope: how many people relied on the work, what broke before you touched it, what changed after. Then read each item out loud and ask whether you can explain it without apologizing for the size. If you keep shrinking your own contributions, you may not be ready to sell yourself yet, and that's a signal worth taking seriously.
Next, look at the direction. Pull up three job postings you'd actually take, not dream jobs you'd never qualify for. Compare the requirements to your list. The gaps tell you what you need, whether that's a skill, a type of responsibility, or a domain. A gap you can name is manageable. A vague sense that you're 'not senior enough' is harder to act on, so push yourself to make it concrete.
Frustration is useful information, but it's a poor plan. If you're leaving because of one manager, one reorganization, or a commute that suddenly feels impossible, pause. Ask yourself whether the underlying problem would come with you. A new employer with the same vague priorities, the same unclear ownership, or the same unrealistic deadlines will produce the same frustration within a few months. Sometimes the fix is a direct conversation, a transfer, or a clearer scope of work, and those are worth trying before you start a search.
Pay is a legitimate reason, and being underpaid for your level is one of the more honest motives you can have. Just check whether the offer you're considering actually solves that problem. A title bump that comes with a similar salary band is a lateral move with a nicer label, and you'll want to know that before you resign.
Here's a hypothetical example. Imagine Maya, a support analyst about eighteen months into her first full-time role. She's tired of having her tickets reassigned by a lead who changes priorities every week. Her first instinct is to leave for anything with a better team. Before applying, she writes one sentence: she wants to move into operations work where analyzing ticket patterns is the core job. That reason survives a bad Monday. It also tells her exactly which postings to look at, and which ones to skip.
Interviewers will likely ask why you're looking to move after a relatively short time. Don't get defensive, and don't pretend the question isn't fair. Give a clear answer in two or three sentences: what you did in the role, what you learned, and what the next role offers that fits your direction. Keep the tone neutral. Describing your current employer as a problem to escape makes you sound like a risk, even if your complaints are reasonable.
Be careful about generalizing how employers react to short tenures. Practices vary a lot by industry, company size, and role type. Some interviewers care a great deal about stability, others mostly want to know whether you can do the work in front of them. Don't build your entire strategy around a rule you heard from a friend or read in a comment thread. Your best protection is a strong, specific story about what you've done, because that holds up regardless of how any single interviewer feels about tenure.
If you want a structure for that story, the same logic used for behavioral interviews works well here. Pick a real example, describe the situation and your action, and name the result. Then connect it to why this particular role is the logical next step. A strong answer sounds like someone who has thought about their path, not someone who needs a way out.
Update your resume before you reach out to anyone. Lead each bullet with an outcome, then tailor the document to each posting so the relevant evidence appears first. A generic resume makes a short tenure look thinner than it is, while a targeted one makes the same experience look purposeful. If you're unsure how to do that for a specific role, our guide on tailoring a resume to a job description walks through the process step by step.
Ask one or two people you've worked with for a reference or a sentence about your work that you can use. A former manager, a peer who saw your output, or a stakeholder from another team can all be useful. Ask them ahead of time and tell them what you'd like them to speak to. A generic 'great to work with' helps less than a specific comment about how you handled a hard problem.
If your gap analysis showed a skill you need, a short course can help you close it on paper, but its real value comes from using it on something you can talk about. Build a small project, document what you did, and be ready to explain your decisions. Qelsa's courses section is a good place to find structured learning for a specific skill. Qelsa’s Readiness Score does this comparison for a specific role. It scores how prepared you are from 0 to 100 and shows which skill gaps are holding the number down. Treat it as a starting point, not a verdict on whether you should leave.If you want help turning your notes into a clear story for interviews, the in-app career agent can help you organize your evidence and practice how you'll describe it.
Sometimes the honest answer is not yet. If you're close to finishing a project that will be a strong portfolio piece, or you're a few months from learning a skill your target roles require, a short extension can make your next move considerably stronger. Staying also gives you time to fix the problem you're trying to escape, whether that's negotiating a different scope, asking for a mentor, or moving to a team with better work.
If you decide to wait, don't let it become drift. Pick a checkpoint date, usually a few months out, and write down what you need to see by then: a completed project, a new responsibility, a clearer answer from your manager, or a skill you've started using. When you reach the date, reassess honestly. One way to make this concrete: note your Readiness Score for your target role now, then check it again on that date. If the gaps have closed, you’ll see it. If the list is complete and you still want to leave, you'll be moving with a plan instead of a reaction. Leaving with a plan is almost always easier than leaving in a hurry.
A practical next step is to run the readiness test this week, then look at real postings to see whether your evidence matches the roles you want. You can browse current openings on Qelsa jobs and compare requirements to your list. If the gaps are mostly about skills, Qelsa courses. is a reasonable place to start. Once you know where you stand, you'll be in a much better position to decide whether to move now or prepare for a few more months.
Not automatically. A one-year move is easier to defend when you can point to concrete outcomes and a clear reason for the change, such as a defined step up in scope or a skill the new role will build. Interviewers vary in how much they focus on tenure, so the strength of your story matters more than the number of months on your resume.
Keep it short and specific. Say what you accomplished, what you learned, and what the new role offers that fits your direction. Avoid criticizing your current employer, even if your frustrations are valid. A calm, forward-looking answer usually works better than a long explanation of what went wrong.
It depends on whether a promotion is realistic and whether it would change your direction. If your manager has a clear path and a timeline, waiting can make sense. If the promotion is vague or depends on things outside your control, use your checkpoint date to decide whether to keep waiting or start a search while you still have leverage.
That's useful information. Start by listing tasks you handled, then ask what changed because you did them, even on a small scale. If you still can't find outcomes, talk to your manager about the work you're doing, or take on a project with visible results before you start applying. Your resume and interviews will be much stronger with concrete examples.