At that point, I was thinking a lot about career progress.
Not in a motivational poster way. More in a practical way.
What am I learning?
What can I prove?
What kind of work do I want to be trusted with next?
Those questions felt more useful than just asking for a better role. A better role needs evidence. Not only certificates or a CV line, although those help. Evidence can also be project notes, diagrams, lessons learned, examples of problems solved and people who can speak honestly about your work.
I was starting to understand that progress needs a trail.
If you do the work but never capture it, you make it harder for others to see your growth. You also make it harder for yourself to remember the details later.
Cloud work is full of details that fade quickly.
What was the problem?
What options did we consider?
Why did we choose that design?
What risk did we reduce?
What would we do differently next time?
These are the details that turn experience into a story you can explain.
I do not mean exaggerating. I dislike that. I mean being able to speak clearly about real work.
There is a difference between saying “I worked on Azure” and saying “I helped review access, logging, backup and exposure risks in an Azure environment, then turned the findings into practical fixes.”
The second version is clearer because it shows judgement.
That was the lesson I was learning: career progress is not only about doing more. It is also about understanding what the work means and keeping enough evidence to explain it properly.
I still think that is true.