The Hiring Contraction: What Actually Happened
Between 2022 and 2025, the tech industry went through its most significant structural correction in two decades. It wasn't just a cycle -- it was a reset in how companies think about headcount.
The ZIRP (zero interest rate policy) era created a hiring model where tech companies over-hired aggressively, treating talent acquisition as a competitive moat. When interest rates rose and revenue growth slowed, companies discovered they had more people than they needed. The layoff waves of 2023-2024 -- affecting hundreds of thousands of workers at Meta, Google, Amazon, Microsoft, and across startups -- weren't temporary corrections. They reflected a permanent shift in how tech companies staff.
What followed was arguably worse for many professionals than the layoffs themselves: the freeze. Companies stopped hiring for roles that previously had dozens of open positions. Senior engineers, product managers, data analysts, and UX designers who would have had multiple offers within weeks in 2021 found themselves in job searches lasting 6-12 months.
The result: a generation of tech professionals who experienced, sometimes for the first time, the reality that employment is not as secure as it felt. That realization is permanent. Even those who kept their jobs watched colleagues get laid off and absorbed the lesson: loyalty to a company doesn't guarantee the company's loyalty to you.
This isn't nihilism -- it's a rational recalibration. And it's driving a meaningful number of skilled people to ask: what would it look like to build something I control?
AI: Both the Threat and the Opportunity
AI's impact on tech careers is more nuanced than either the doomsayers or the optimists suggest. The truth is that AI is making some skills less valuable while making others dramatically more valuable -- and the line between the two is shifting fast.
What's becoming less valuable: routine code writing, basic data analysis, standard report generation, first-draft content creation, repetitive QA testing, and any task that follows a predictable pattern. If your job is primarily executing well-defined tasks, AI tools can now do 60-80% of that work. This doesn't mean immediate job loss, but it means the market rate for those skills is falling.
What's becoming more valuable: the ability to frame problems correctly, architect systems, make judgment calls with incomplete information, manage client relationships, translate between business needs and technical solutions, and -- critically -- the ability to use AI tools effectively to multiply your output. A consultant who can use AI to do the work of a three-person team is extraordinarily valuable. A developer who can use AI to ship in days what used to take weeks has pricing power.
This is where independence gets interesting. In traditional employment, if AI makes you 3x more productive, your employer captures most of that value -- your salary doesn't triple. As an independent professional, you capture the efficiency gain directly. You can serve more clients, deliver faster, or work fewer hours for the same income. The incentive structure for AI adoption is fundamentally better for independents than for employees.
The professionals I see thriving right now are those who treat AI as a force multiplier for their expertise rather than a threat to their jobs. They're the ones going independent -- because independence lets them capture the upside.
The Economics of Independence
Let's talk actual numbers, because the decision to go independent is ultimately a financial one.
A senior tech professional in a major European city might earn EUR 80,000-120,000 as an employee. As an independent consultant doing similar work, day rates of EUR 800-1,500 are common, which at 200 billable days per year translates to EUR 160,000-300,000 in gross revenue. Even accounting for self-employment taxes, health insurance, no paid vacation, and the overhead of running a business, the math usually works out significantly better -- if you can maintain a reasonable utilization rate.
The "if" is the critical word. Employee income arrives reliably on the first of every month. Independent income is lumpy, unpredictable, and zero when you don't have clients. The first year is almost always a financial step down as you build your pipeline. Many people underestimate how long it takes to reach sustainable income.
The break-even calculation most people miss: you need to factor in the time cost of sales, administration, accounting, professional development (no employer pays for your courses anymore), and the mental overhead of uncertainty. A reasonable expectation is that 60-70% of your time will be billable in a good year, with the rest going to running the business.
The location-independence angle changes the economics significantly. If you can earn Western European or US rates while living in countries with lower costs of living -- Portugal, Colombia, Thailand, Mexico -- the financial case for independence gets much stronger. An income of EUR 10,000/month goes considerably further in Medellin than in Munich. This arbitrage is one of the key reasons tech professionals combine independence with location flexibility.
What 'Independent' Actually Looks Like
"Going independent" isn't one thing. It's a spectrum, and understanding the options matters because each has different risk profiles, income patterns, and lifestyle implications.
Freelancing / contract work: You do the same work you did as an employee, but for multiple clients on a contract basis. This is the most common starting point and the lowest-risk path because you're selling skills you already have to companies that already need them. Platforms like Toptal, Upwork (for established professionals), and industry-specific networks can provide initial clients. The risk: you're still trading time for money, and you're one client departure away from a revenue gap.
Consulting / advisory: You sell expertise and judgment, not just execution. This means higher rates, shorter engagements, and work that's harder to commoditize. The shift from "I'll build this for you" to "I'll tell you what to build and why" is where the real economics improve. It requires deeper domain expertise and the confidence to charge for thinking, not just doing. This is where I operate with Adasight -- analytics consulting where the value is in the strategic direction, not just the implementation.
Productized services: You package your expertise into a repeatable offering with a fixed scope and price. "Analytics audit for EUR 5,000" instead of "consulting at EUR 150/hour." This is more scalable than pure consulting because you can systematize delivery, but it requires enough market understanding to know what package people will actually buy.
Products and SaaS: Building software, courses, or digital products. The most scalable model but also the highest risk and longest time-to-revenue. Very few people successfully jump from employment to product income without an intermediate consulting or freelancing phase that funds the transition.
Most successful independents I know combine two or three of these. Consulting provides the base income, a productized service adds predictability, and maybe a small product or content play builds long-term leverage.
Who This Is NOT For
I'd be dishonest if I didn't cover this. Independence is not universally better than employment, and the current wave of enthusiasm for "quitting your job" glosses over some real downsides.
You need financial stability and can't handle income volatility. If you have significant fixed obligations -- a mortgage, dependents, debt -- and no savings runway of at least 6-12 months of expenses, going independent is reckless, not brave. Build the runway first.
You don't enjoy selling or relationship-building. As an independent, you are the sales team. You need to find clients, pitch your services, follow up, negotiate rates, and maintain relationships. If networking and selling feel fundamentally misaligned with who you are (not just uncomfortable -- there's a difference), employment might be a better fit.
You thrive on team structure and mentorship. Working independently is often working alone. The camaraderie, mentorship, and collaborative problem-solving of a good team is hard to replicate. If those are important to your professional satisfaction and growth, weigh that seriously.
Your skills are highly specialized but narrow. If your expertise is deep in one company's proprietary system or a very niche technology with limited consulting demand, the market for your independent services might be too small. Generalists and people with transferable expertise across industries have an easier time finding independent work.
You're running away, not running toward. Leaving a bad job is not the same as being ready for independence. If the primary motivation is escaping a toxic workplace or a bad manager, fix that problem first -- maybe at a different company. Independence is hard enough without starting from a place of burnout and frustration.
The honest assessment: independence works well for self-directed professionals with marketable skills, some savings, a tolerance for ambiguity, and a genuine interest in building their own practice. For everyone else, there's no shame in being well-employed.