Changing Careers? Do You Really Start From Zero?

Maybe you don’t like your career. Maybe it burns you out. Maybe you are pretty good at what you do, but the thought of doing the same thing for another ten years is not particularly exciting.

Fine. You want a change.

But then comes this rather irritating question. What about all those years you spent learning your present job? Are you supposed to throw them into the dustbin and start all over again?

This is one thing about career changes that has always bothered me. We talk about starting afresh as though changing an industry or a job description means that the experience you have built until now has suddenly become worthless.

I don’t think it works that way.

Moving from individual contribution to management, creating new business verticals and even making myself redundant at work taught me something interesting. In all these situations, the kind of work changes. Sometimes quite dramatically. But the person doing the work does not suddenly lose everything he or she learned in the previous role.

A complete career change is obviously a much bigger jump. You may have to learn an entirely new set of technical skills. You might even have to go back to being a beginner in some areas.

But a beginner at what, exactly?

I can think of four things you might already have, even before you make that jump.

1. Your soft skills don’t belong to your industry

Let me start with a simple example.

Imagine someone who has spent ten years managing a restaurant. Now this person decides to move into an operations role in a completely different business. Perhaps an online retail firm.

Of course, they need to understand the new industry. But think about the kind of problems they’ve already dealt with.

A customer is furious because an order went wrong. Two employees call in sick just before the evening rush. The kitchen and service teams are blaming each other for a delay. There is a supplier who promises a delivery and then disappears.

Now, the actual problems in an online retail operation will be different. But are the abilities required to handle people, resolve a conflict, organise work and make a decision under pressure completely different?

Not really.

I have seen this distinction in my own career as I moved from being an individual contributor towards managing teams and business verticals. The work stopped being only about what I could personally deliver. It became about what I could get a team to deliver and how I could make that happen repeatedly. It was no longer just about grit and hustle. I also had to figure out how to build business processes that could get things done with or without me.

That is not the same as changing industries. But it is a useful example of how a skill that served one kind of work becomes valuable in another.

Here is another example. Take a software engineer who is exceptionally good at explaining technical problems to a customer. Now that engineer decides to get into a customer-facing product or consulting role.

Sure, there are things to learn. But the ability to simplify a technical issue, ask the right questions and keep a frustrated customer from becoming an even more frustrated customer is already there.

Communication. Negotiation. Planning. Dealing with people who don’t agree with you. Making decisions when you don’t have all the information you want.

We call them soft skills. Frankly, there’s nothing particularly soft about them when things start going wrong.

Now don’t misunderstand me. Being good with people does not make you qualified to practise medicine, build a bridge or give legal advice. Some professions have formal qualifications and technical capabilities that you simply cannot negotiate your way around.

My point is a little different. When you change careers, you may become a beginner at the new technical work. That doesn’t mean you become a beginner at being effective in a workplace.

2. All that industry knowledge can be used laterally

I find this one especially interesting.

When we work in a particular industry, we pick up a ridiculous amount of information which never appears in our job descriptions.

We learn which customer complaints actually matter. Which part of the process fails every Friday evening. Why the sales team promises something the operations team hates. Why a seemingly small change to a form or a report suddenly causes trouble for five other departments.

None of these things may appear as a skill on your résumé. But you know them because you’ve lived with those problems.

Let’s take a hypothetical example.

Imagine a person who has spent years running operations in a warehouse and now wants to move into product management for logistics software.

They may not know how to write a product requirements document. They may not know the terminology used by a software engineering team. All of that needs to be learned.

But when someone proposes a shiny new dashboard, this person may ask a question the software team has missed completely: who is actually going to use it when fifty parcels are waiting to be shipped and the warehouse floor is in chaos?

That question can be worth quite a lot.

In B2B product management, I have found it far more useful to understand the customer’s actual problem than to blindly build whatever solution the customer asks for. A person who deeply understands an industry’s day-to-day problems has a head start in asking those questions.

Or look at someone moving from sales in one sector to market research or business analysis in another. They may already understand how buyers object to prices, which promises are difficult to fulfil and why a customer who says yes in a meeting may still never sign the contract.

The product changes. The buyer changes. The application of that knowledge changes.

The experience need not disappear.

But here is the catch. Some industry knowledge doesn’t travel well. The regulations may be different. The customers may behave differently. What worked beautifully in one organisation may fail in another.

You have to separate the principles you learned from the habits you picked up.

That, in my opinion, is the real skill here. Not claiming that your ten years of experience are automatically useful everywhere, but figuring out which parts of those ten years can solve a completely different problem.

3. Your old skills can acquire an entirely new value

This is where I think people sometimes undersell themselves.

Let’s say you have spent years running a team. You know how to break down a complicated task, document a process, train people and make sure that the work gets done without having to chase everyone ten times a day.

Now you’re trying to enter a new field.

If all you tell people is that you managed a team for eight years, they may quite rightly wonder what that has to do with the job you’re applying for.

But if you show them how you identified a broken process, fixed it, trained people to take it over and made the operation work without depending on you every single day, that is a different conversation altogether.

One idea that has helped me think about career growth is making myself redundant at work.

It sounds like a terrible career strategy, doesn’t it? Why would I want to make my own job unnecessary?

But the argument was that if all the knowledge sits in my head and every small decision needs me, I have created a bottleneck. If I document the work, use technology to remove repetitive tasks and train someone else to handle it, I have created room for myself to take on something more useful.

Think about what that means in a career change.

The ability to document a messy process might become useful in operations consulting. The ability to automate repetitive reports might be useful in a different business function. The ability to train a team might be what makes someone valuable in a new customer-success role.

Same underlying capability. Different application. Different value.

Here’s another example.

Suppose a schoolteacher wants to move into corporate learning and development. They may not understand corporate training budgets, internal stakeholder politics or how a particular company measures learning outcomes.

But they already know something rather important: how to explain a difficult concept to somebody who doesn’t understand it, how to recognise when an explanation is failing and how to change the approach until the person gets it.

Now the next employer may want evidence that this ability works with adults in a corporate environment. Fair enough. A transition project, a certification or some practical experience might still be necessary.

But describing this person as somebody starting from zero would be rather silly.

I would look at a career-change résumé this way: don’t just tell me where you worked. Tell me what problems you learned to solve. Then show me how those problems, or some version of them, exist in the career you want to enter.

And yes, sometimes you will discover that the gap is much bigger than you expected.

That’s fine. Better to know that before resigning.

4. The network you built doesn’t disappear with your designation

Networking is one of those words that makes me think of people going around exchanging visiting cards, connecting on LinkedIn and then messaging someone three years later with a rather awkward ‘Hi, hope you’re doing well.’

For me, networking is not merely collecting contacts. It is about connecting people, ideas and problems so that something useful comes out of the relationship.

One interesting programme I came across did something simple. Employees from different cities were paired up and given opportunities to interact, with a senior mentor in the mix. The purpose was to help people get to know colleagues they otherwise would probably never have spoken to.

Why does this matter for someone changing careers?

Imagine you’re in finance and you want to move into operations. Perhaps somebody you’ve worked with in operations can explain what that job actually involves. Maybe they can tell you which skills you are missing. They may even warn you that the role you have romanticised is mostly about putting out fires, fixing escalations and handling calls at odd hours.

That is valuable information.

Or take a person leaving hospitality for a customer-success role in a software firm. A former client might work in software. A colleague might know someone who made the same move. A supplier might be able to introduce them to an organisation where their ability to handle customers is genuinely useful.

Will every introduction lead to an opportunity? Of course not.

And I really wouldn’t recommend treating everybody you know as a potential job referral. That’s a fairly efficient way to make people avoid your calls.

But there is a difference between exploiting a contact and building on trust that already exists.

The people you worked with know how you behave when things are difficult. They know whether you deliver what you promise. They know whether you help others or disappear the moment the work gets unpleasant.

A new employer may not know any of those things about you. Some of the people in your existing network do.

That reputation is worth carrying into the next chapter of your career.

But let’s be clear. Career change still has a price.

By now I may be sounding as though career changes are simple. They’re not.

A person moving from finance to software engineering may need substantial technical training. Someone moving into medicine or law may need years of formal education. An experienced manager switching industries may have to accept a lower designation or salary while learning the new domain.

And sometimes the biggest problem isn’t the skills at all.

Maybe you hate your company, not your career. Maybe you are bored with your current role, not the industry. Maybe the problem is the manager you work for or the kind of projects you’ve been doing for the last three years.

These are different problems. Changing companies, changing roles and changing careers are not the same solution.

Even work we enjoy can become boring after a while. I’ve found that one way to move forward is to free ourselves from work we’ve already mastered so that we can take on something more challenging.

Sometimes that might be enough. You don’t necessarily need a new industry. You need a different kind of problem to solve.

But suppose you’ve thought about all this and still want to move.

What would I do?

I would make two lists.

The first one would not be a list of my job titles or years of experience. It would be a list of the things I actually know how to do: the problems I can solve, the people I can work with, the kinds of situations I’ve learned to handle and the industry knowledge I can take somewhere else.

The second would be everything the new career needs. Qualifications. Technical skills. Experience. Domain knowledge. Perhaps a new network.

Then I would compare the two.

Some things would overlap. Some would not. Some would need a little adaptation, while others would require serious work.

At least now I’m dealing with a specific gap rather than a vague fear that I’m throwing away my entire career.

And that, for me, is the point.

If you decide to change careers, you may be starting a new role, in a new company, with a new set of people and problems.

But you’re not necessarily starting from scratch.

The more useful question is: what have I already built that can help me do something entirely different?

I would figure that out first.