Identity Drift: Can You Say What You Are Becoming?

Most IT professionals are taught to improve their skills. Almost none are taught how careers actually compound. That gap is where drift begins.

Career drift rarely looks like failure. It often looks responsible:

• More learning. More delivery. More effort.
• More certifications. More responsibility.

But if that effort is not converting into clearer direction, recognised value, stronger visibility, and better future options, your career may be moving without enough architecture.

That is the pattern this series explores. Five layers, one at a time, where drift most commonly appears in IT careers: identity, skills, value, visibility and leverage. Not to motivate. Not to inspire. Not to give generic advice. But to give you a structured way to examine what is actually happening in your career.

It starts with the layer most professionals skip entirely.

Can you explain what you are actively becoming, not just what you currently do?

If this question feels uncomfortable, that may be the point.

Your job title describes what you do. It does not describe what you are becoming.

You may hold a title like service desk analyst, cloud engineer, IT support specialist, systems administrator, or junior developer. Those titles describe where you currently sit inside an organisation. Nothing more.

They do not tell you what problems you are becoming trusted to solve. They do not tell you what capability you are building over time, what professional direction your work is forming, or what you want to become known for.

That gap is where identity drift lives. Identity drift is not a crisis. It is a quiet, gradual condition where your career is moving but not toward anything you have deliberately named. The concern is not having a job title, which is not wrong in itself. The concern is when the title becomes the only language you use to understand yourself professionally.

The evidence usually shows up in how you introduce yourself. If your answer is mostly a list of tools, roles, and responsibilities, that is a title answer. If your answer names the kind of problems you are building toward solving, the context you want to operate in, and the standard you want your work to be known for, that is an identity answer.

In most career conversations, the first answer comes easily. The second rarely does.

There is one question that reveals this gap immediately:

Can you describe your professional identity in one sentence without using your job title?

If that sentence does not come easily, your role may be giving you activity without direction. You can explain what you do. But not what you are becoming.

What identity drift looked like in my own career

I spent years being good at my work without being fully clear about what I was building toward.

I had experience across IT operations, service delivery, cloud environments, identity management, and operational risk. What I did not have was a clear answer to this question: what kind of professional am I deliberately becoming?

I could describe what I did. I could name the tools I used, the environments I had worked in, and the problems I had solved. But I could not articulate a direction. A problem space I was moving toward owning. A standard I was building toward.

That is identity drift. And it is more common among capable, experienced IT professionals than most career conversations acknowledge.

If you have never been asked to answer that question, what kind of professional are you deliberately becoming, you are not behind. You have just been operating in a system that rarely asks it.

This series is asking it.