You are probably not ten years late
There is a particular anxiety that appears when people move into technology after doing something else first.
They look at somebody who started coding at fourteen, got the degree, joined the graduate scheme and now seems to have a decade’s head start.
Meanwhile, perhaps you spent your twenties working in hospitality.
Sales.
Driving.
Retail.
Construction.
Music.
Running shifts.
Looking after customers.
Doing something completely unrelated to React.
It is easy to conclude that all of that time was somehow lost.
I do not think it was.
Technical experience matters
Let me get one thing out of the way before this becomes motivational nonsense.
Experience matters.
If somebody has spent ten years becoming extremely good at software engineering, they know things you do not know because they have done the work.
You do not neutralise that with "life experience".
There is no inspirational shortcut around competence.
But technical competence is not the only thing clients buy.
That matters too.
A business problem rarely arrives looking technical
A client does not usually walk in and say:
I require a beautifully normalised data model and a correctly implemented caching strategy.
They say:
The website is rubbish.
Or:
We keep losing enquiries.
Or:
My staff are doing this manually and it is driving everybody mad.
Or:
I paid somebody to build this and I have absolutely no idea what they have done.
That is the real starting point.
The job is partly technical.
It is also diagnostic.
What is actually wrong?
What matters most?
What can wait?
What can they afford?
What are they trying to achieve underneath the thing they have asked for?
That requires more than syntax.
I have learned a lot from jobs that were not "tech"
If you have worked with the public, you know that people do not always explain themselves clearly.
If you have managed people, you know that the obvious solution on paper can fail because somebody has to actually use it on Monday morning.
If you have worked in a business with tight margins, you know the difference between "nice to have" and "we genuinely need this".
If you have dealt with difficult customers, you know that being technically correct is not always the same as resolving the situation.
Those are useful skills.
They travel.
Consulting is mostly translation
This is the bit I think career changers often underestimate.
A good consultant moves between worlds.
The client speaks in symptoms.
The technical system speaks in constraints.
The job is to translate one into the other without making either side feel stupid.
That means listening properly.
Summarising.
Asking better questions.
Explaining trade-offs without hiding behind jargon.
Occasionally saying:
I know that is what you asked for. I do not think it is what you need.
And being able to explain why.
That is not junior work.
It is judgement.
You are allowed to not know things
One of the most useful changes in my own thinking has been becoming more comfortable with not immediately knowing the answer.
I would rather say:
I need to check that.
than improvise expertise.
Technology changes too quickly for anybody sensible to know everything.
The real skill is knowing how to find out, how to test what you found, and when the answer matters enough to get another specialist involved.
Confidence is not pretending there are no gaps.
It is being able to operate despite them.
The imposter feeling does not vanish when you become competent
This is another slightly inconvenient truth.
You can know a lot and still walk into a new problem thinking:
I have absolutely no idea how I am going to do this.
That is not necessarily evidence that you are an imposter.
Sometimes it is evidence that the problem is actually new.
I quite like that stage.
The bit before I know what I am doing is often the most interesting bit.
You research.
You test.
You ask.
You build a mental model.
Eventually the fog clears.
Then comes the less glamorous stage where you have to finish the thing.
Do not compete on being the youngest person in the room
You cannot win that forever.
There will always be somebody younger.
Faster.
More current on a particular framework.
That is fine.
Compete on being useful.
Can you understand the business?
Can you communicate?
Can you make sensible decisions?
Can you finish?
Can you explain what you did?
Can the client trust you when something goes wrong?
Those attributes age rather well.
The career you had before this one is part of the toolkit
You do not need to invent a perfect origin story where every job was secretly preparing you for digital consultancy.
Sometimes a job was just a job.
But you did learn things.
About people.
Pressure.
Money.
Time.
Responsibility.
Failure.
What customers actually care about.
What managers say they want versus what the operation can support.
Do not discard that because it does not fit neatly on a technical CV.
Use it.
Become an operator
The point is not to feel like a developer.
Or a founder.
Or a consultant.
Those labels are less interesting than the work.
Take a messy problem.
Understand it.
Work out what good looks like.
Use the right tools.
Bring in expertise where you need it.
Communicate clearly.
Finish.
Then do it again.
At some point, without a ceremony, you stop feeling as though you are trying to break into the industry.
You are simply operating in it.
