I spent some time thinking about the kind of engineer I wanted to become.
Not only the job title. Titles change. Tools change. Even the market changes.
I was thinking more about the habits.
I wanted to become the kind of engineer people could trust with unclear problems. The kind who does not panic when something is messy. The kind who can read the logs, ask the right questions, explain the options and leave the environment better than it was found.
That sounds simple, but it is not automatic.
Technical skill matters. You need to know the tools. You need to understand cloud, security, networking, infrastructure, automation and operations. But skill without discipline can still create mess.
I kept coming back to a few qualities.
Be clear.
Write things down. Explain decisions. Do not hide confusion behind big words.
Be careful.
Check the subscription. Check the environment. Check the command before pressing enter. Understand the blast radius.
Be useful.
Solve the problem in front of you, but do not ignore the pattern behind it. If the same issue will come back next week, leave a note or improve the process.
Be teachable.
Cloud work changes too quickly for pride. There is always a new service, a new risk, a new mistake waiting if you stop learning.
I still fall short of this. Everyone does.
But having a picture helps. It gives me something to measure against when the work gets busy.
I do not want to only be fast. I want to be dependable.
That is a slower goal, but it feels like the right one.