More than 150,000 tech workers have been laid off in 2026, and the number keeps climbing. Meta restructured its middle management layer. Intel announced its fourth round of cuts in eighteen months. Dozens of AI startups quietly reduced headcount after failing to convert proof-of-concept budgets into enterprise contracts. If you work in tech right now, the question "should I leave before I'm pushed?" is not paranoia — it is a reasonable thing to think about.

But panic-quitting is as damaging as staying too long. Leaving a job that is actually fine because you read a few alarming headlines can cost you months of career momentum, put you back on the job market in a saturated period, and leave you explaining a short tenure in every interview for the next two years. The decision deserves more than a gut check after a bad week.

This article gives you a practical framework: eight specific signals that indicate it really is time to move on, three signals that look real but usually aren't, and a guide to leaving cleanly when you do decide to go. Whether you are actively frustrated or just running a quiet background process on your career, these are the distinctions that matter.

8 Signs It Is Time to Leave

These are not abstract concepts. Each one has a real pattern — and knowing how to recognize it in your specific situation is what separates a good decision from a reactive one.

Sign 1

You have stopped learning

Not boredom — stagnation. There is a meaningful difference between a slow quarter and a genuine learning plateau. The test: think back over the last six months and identify something significant you learned about your craft, your domain, or how to operate at a higher level. If nothing comes to mind, that is a signal worth taking seriously.

What this looks like A mid-level engineer at a Series B fintech company spent fourteen months shipping features in a codebase they understood completely. New tickets were variations on solved problems. The architecture decisions were made. The domain was familiar. They were competent and comfortable, and their skills were not growing. They left for a role where they had to learn a new distributed systems pattern inside the first month. Within a year, their scope had doubled.
Sign 2

Your compensation is below market and they will not negotiate

Being paid below market is not unusual — it happens at nearly every company over time as the market moves. The version that should make you leave is when you have raised it directly, provided data, and been told no without a credible timeline. A gap of more than 20% combined with no meaningful response is a clear signal that the company is either unwilling or unable to pay you what the market says you are worth.

What this looks like A product manager at a 400-person SaaS company discovered through conversations with peers and public compensation data that their base salary was $35,000 below market for their scope and experience. They raised it with their manager and then with HR, citing specifics. They were told the company was "committed to competitive pay" and given a 3% merit increase at review time. They left three months later for a $45,000 base increase and a meaningful equity refresh.
Sign 3

The culture has shifted away from your values

Companies change, especially between funding rounds or leadership transitions. The startup you joined for its flat structure and engineering ownership can look very different after a VP of Sales becomes CEO, or after a private equity firm takes a controlling stake. If the company you work for today is not the one you joined, and the gap between what you care about and how the place actually operates has become persistent, that is a legitimate reason to look.

What this looks like An engineering lead joined a developer tools company specifically because engineers drove the roadmap. Two years later, a new Chief Revenue Officer had reorganized the product team under Sales, and the engineering team was spending 40% of its time on custom enterprise integrations that had no path to the core product. The culture had not failed — it had changed. The engineer left for a company where the engineering-driven value was still genuinely practiced.
Sign 4

Your manager is actively harmful to your career

There is a difference between a manager who is not great and a manager who is costing you. The harmful version takes visible credit for your work in senior leadership contexts, excludes you from high-visibility projects, gives feedback in your reviews that contradicts what they have told you directly, or withholds information that would help you do your job well. If you have tried to address it with them and the behavior has continued, this is not a coaching challenge — it is a structural problem.

What this looks like A data scientist discovered, after missing a promotion, that their manager had told the review committee their work "needed more visibility" — while the manager had been the one consistently presenting that work to leadership on their behalf, without attribution. The data scientist raised it. The manager apologized and nothing changed. They transferred to a different team six months later, got the promotion in the next cycle, and reflected that they had waited a year longer than they should have.
Sign 5

You are being reorged into a role you did not choose

Reorgs happen. Most of them are disruptive but survivable. The version that warrants serious thought about leaving is when the new role materially changes your scope, your domain, or your career trajectory in a direction you did not agree to — and when management presents this as a fait accompli rather than a conversation. Being moved from a product engineering role into a platform team, or from individual contributor work into a quasi-management role you didn't want, without genuine discussion is worth escalating. If escalating doesn't move anything, it is worth leaving.

What this looks like A senior software engineer at a late-stage startup was moved from the growth team — where they had been doing full-stack product work they loved — to an infrastructure reliability role as part of a cost-cutting reorg. They were told this was a "growth opportunity." It was not a role they had applied for or wanted. They asked to be reconsidered for the growth team or another product-facing role. There were no openings. They left within ninety days.
Sign 6

The company's financial health is visibly declining

You don't need access to the cap table to see the signs. Watch for: a freeze on backfill hiring after departures, cancellation of team travel or budgeted projects, a reduction in contractor headcount, executive departures that are not explained, and internal all-hands where questions about runway or revenue are deflected. Any two of these together is a yellow flag. Three or more is a signal to start looking, not out of panic, but out of rational planning. The best time to start a job search is before you have to.

What this looks like An engineering manager at a Series C startup noticed in Q1 that three departing team members were not replaced, two planned product hires were quietly cancelled, and a company offsite was moved from a destination location to a local half-day. In the same quarter, the Head of Finance left and was not replaced. They started interviewing in February, received an offer in April, and were in a new role when the company's RIF was announced in May.
Sign 7

You have been passed over for promotion multiple times without clear feedback

Once can be timing. Twice with specific, actionable feedback that you can demonstrably act on is a signal to work harder and smarter. Twice or more with vague feedback, shifting goalposts, or no feedback at all is a signal that the path at this company is likely not going to open. The version that should move you to leave is when you ask directly for the criteria for the next level and cannot get a clear answer that stays consistent from one review cycle to the next.

What this looks like A senior designer was told in their first promotion review that they needed to "demonstrate more strategic thinking." They shipped a design system used across the product and led two cross-functional projects. In the second review, they were told the same thing. They asked their manager to define what "strategic thinking" looked like at the next level with specific examples. They received a three-paragraph response that was more aspirational than concrete. They left and were promoted to staff designer in their next role within fourteen months.
Sign 8

You dread Sunday nights

This one is deliberately last, because it is the most common and the least diagnostic on its own. Everyone has bad stretches. But if Sunday evening has become a reliable, months-long experience of low-grade dread about Monday — not because of a specific project or deadline, but as a baseline ambient feeling about the job itself — that is your body telling you something that your spreadsheets may not have confirmed yet. At a certain level of duration and intensity, this is a real signal and it is worth listening to, even if you cannot yet point to a single concrete failure mode.

What this looks like A staff engineer described it as "not one thing." The work wasn't terrible. The manager was fine. The comp was fair. But for six months, Sunday nights were characterized by a specific tightness in the chest. They eventually connected it to a slow but persistent loss of autonomy as the company scaled, a creeping mismatch between how they wanted to work and what the company was becoming. They left, and the Sunday dread went away in the first week at their new company.

3 Signs That Look Real But Usually Are Not

The signs above are worth acting on. These three are worth questioning before you do anything drastic.

Stay?

You are bored — but you have not tried changing anything

Boredom is real, but it is not automatically a reason to leave. Before attributing it to the company, ask: Have you asked for a harder project? Have you proposed a new initiative? Have you raised your desire for broader scope with your manager explicitly? Most companies will accommodate a direct request for more challenge from a high performer — and you will not know whether yours is one of them unless you ask. If you have genuinely tried and been told no, the signal is real. If you have not tried, you may be leaving a good situation unnecessarily.

Stay?

You had one bad quarter

Every company has rough quarters. Every team has a period of chaos, leadership transition, or re-prioritization. A single difficult stretch — a project that went sideways, a reorg that landed badly, a quarter with high attrition — is not evidence of a structural problem. The question is whether it is an event or a pattern. If you have been at the company for more than eighteen months and the difficult quarter is genuinely anomalous, wait it out and reassess. If it is the fourth consecutive difficult quarter, treat it as a pattern.

Stay?

The grass looks greener but you have not researched the alternatives

A competitor's job posting looks exciting. A colleague who left posts a LinkedIn update about their new role. A recruiter sends you a message with a flattering subject line. None of these are evidence that a move would make you better off. Before you conclude the grass is greener, do the work: research the company's culture in depth, talk to people who work there, understand the actual day-to-day. Our Culture Directory and culture fit interview questions guide are good places to start. Leaving one situation without understanding what you are walking into is a reliable way to recreate the same problems in a new building.

How to Leave Well

The decision to leave is only half the work. How you leave matters significantly, both for your own integrity and for the practical reality that tech is a small industry where reputations travel.

Give the right amount of notice

Two weeks is the conventional minimum. For senior individual contributors or managers, three to four weeks is more appropriate, particularly if you have direct reports, open hiring processes, or projects in critical phases. Giving more notice than required is almost always remembered positively. Giving less than two weeks is remembered negatively, and sometimes has formal consequences depending on your employment agreement.

Write a real transition document

This is the most practical thing you can do for your team and your own reputation. Document your active projects, their current status, open decisions, key stakeholders, and any institutional knowledge that lives only in your head. Include the gotchas — the vendor who responds better to email than Slack, the undocumented dependency in the build system, the recurring issue in the quarterly report and how to fix it. Making your successor's first weeks better is something people remember for years.

Do not vent on the way out

The exit interview is not a therapy session, and LinkedIn is not a safe place to process your frustrations. If there are systemic problems worth raising, raise them clearly and professionally in the exit interview without theater. Burning bridges in tech is remarkably easy and remarkably costly. The CTO you worked under may be an angel investor at your next company. Your former manager may be a reference before you expect them to be. Leave as if you might work with every person there again, because you almost certainly will.

Negotiate your exit if the situation warrants it

If you are leaving partly because of a reorg that changed your role without your agreement, or because of a compensation gap the company could have closed, it is reasonable to ask whether a severance arrangement is possible. This is a professional conversation, not a demand. Many companies — particularly larger ones — have discretion to offer enhanced packages for departures that are at least partly the company's responsibility. You will not always get a yes, but you will not get a yes without asking.

Where to Look Next

If any of the eight signs above describe your current situation, the best time to start looking is now, while you are still employed. An active job search from a position of employment is almost always more productive than one conducted from unemployment — you have more leverage, less urgency, and more time to be selective about fit rather than just accepting the first reasonable offer.

Culture fit is worth taking as seriously as the role itself. A technically excellent company with a culture that conflicts with how you work best is not a good move, regardless of the title or the comp. Read the startup vs. big tech comparison if you are deciding between those tracks. Read the remote work negotiation guide if remote is a requirement for you. Use the culture fit interview questions to pressure-test what a company tells you against how it actually operates.

Then browse what is actually open. The Culture Directory profiles 118 companies with verified culture values, employee review summaries, and the things you don't usually find in a job posting. And the jobs board surfaces roles from those same companies, filtered by the values that matter to you.

Find a company that actually fits how you work

Browse roles from 118 companies with culture context — remote, flat, engineering-driven, learning-focused, and more.

Browse Open Roles → Explore the Culture Directory →

Frequently Asked Questions

How do you know when it's time to quit your tech job?+
The clearest signals are: you've stopped learning for more than six months, your compensation is more than 20% below market and the company refuses to negotiate, your manager is actively blocking your career advancement, or you've been reorged into a role you didn't agree to. A single bad quarter is rarely enough reason. A sustained, multi-signal pattern usually is.
Is it bad to leave a tech job after one year?+
It depends on the reason. Leaving after one year because you discovered a serious culture mismatch, a toxic manager, or a company with deteriorating financial health is reasonable and most employers understand it. Leaving after one year simply because you had a rough quarter or because a competitor announced higher salaries is worth questioning first. The one-year mark is also often relevant for equity vesting — check your cliff date before handing in notice.
How do you quit a tech job without burning bridges?+
Give at least two weeks' notice, ideally three to four for senior roles. Write a thorough transition document covering your key projects, open decisions, stakeholders, and any gotchas for whoever takes over. Offer to help with interviews for your replacement. Say goodbye to colleagues individually where you can. Avoid venting about the company or its leadership on the way out — the tech industry is smaller than it looks.
Should you negotiate when leaving a tech job?+
It is reasonable to ask whether the company will offer a severance package if you are being pushed out during a reorg, or if your departure is partly driven by compensation gaps the company could have addressed. However, if you are leaving purely voluntarily for a better opportunity, there is generally little to negotiate — you are the one choosing to go. Focus your negotiation energy on your incoming offer instead. For guidance on negotiating flexibility in your next role, see our remote work negotiation guide.
What are the signs a tech company is about to do layoffs?+
Common warning signs include: a freeze on backfill hiring after departures, cancellation of team offsites or budget cuts to non-essential spending, senior executives departing, declining revenue metrics being communicated internally, a reduction in contractor headcount (contractors are often cut first), and an increase in internal reorganizations. None of these alone is definitive, but multiple signals at once warrant attention and active job searching.
How long should you stay at a tech job before leaving?+
The general guideline is at least two years, which allows you to complete a meaningful project cycle, demonstrate impact, and typically pass your equity cliff. Less than 18 months raises questions that you will need to address in future interviews. More than four years without a promotion or significant scope increase — especially if you have raised it with your manager — can indicate a career growth problem worth addressing by moving on.