
When you are growing a DevOps career, it is easy to describe yourself in adjectives: motivated, curious, hands-on. Hiring managers have heard all of them. What stands out is a plain account of things you have actually completed. That is what a done list gives you, and in this post I want to chat through how to build one so that your skills, your training and your personal brand all rest on something solid. No jargon, no hype, just a habit that has helped plenty of engineers speak about their work with confidence.
Why adjectives do not carry you far
Think about the last time you read a profile that said “passionate about automation.” Did it tell you anything? Probably not. Now compare it with “set up a repeatable build for a small service, then trimmed the image and fixed three failing steps.” The second line is boring in the best way: it is specific, and a reader can imagine the work. A done list is simply a collection of lines like that, each one dated and each one finished.
This matters whether you are job hunting, asking for a promotion, building a following by writing and speaking, or changing roles inside the same company. Everyone in those situations needs raw material, and the done list is where it accumulates.
What goes on a career-focused done list
- Skills practised until they worked. For example: containerised a small app and ran it on two different machines.
- Problems fixed. A broken pipeline you repaired, with a sentence on the cause.
- Things you taught. A short internal session you ran, or a clear answer you gave to a junior colleague’s question.
- Things you published. A blog post, a short talk, a diagram shared with your team.
- Certifications and courses completed. Include what you built along the way.
- Feedback acted upon. A reviewer said your scripts lacked error handling, and you fixed it.
If you are working with containers, you will find that the same ideas apply to the technology itself. Articles like the one on typical container missteps that newcomers can sidestep become far more valuable when you log which of those mistakes you have actually fixed in your own projects.
Turning entries into your story
Here is the part many people miss. A done list is not the story; it is the evidence behind the story. Once a quarter, read through your entries and look for a thread. Maybe most of your finished items involve image building and delivery, and you realise you have quietly become the person people ask about containers. That is a personal brand forming from facts rather than from slogans.
The practical follow-up is to write about it. A short post titled something like “What I finished this quarter and what I learned” costs you an hour and gives readers a real sample of your work. If your area is images and registries, pairing your notes with guidance such as how engineering teams keep image management tidy shows that you can link experience to wider practice.
Using the list in conversations
Interviews. When asked, “Tell me about a time you solved a problem,” you will not freeze, because you have a dozen finished examples with dates and results.
Performance reviews. Instead of struggling to remember the year, bring a page. Managers appreciate specifics, and you spend less time arguing for your case.
Networking. People ask what you are working on. A confident, concrete answer drawn from recent entries sets you apart from the usual vague reply.
Mentoring. If you mentor someone, show them how you keep the record. You help them and you reinforce your own habit.
A tiny story about doing it badly, then better
Many engineers start with a grand plan: a beautiful tracker, categories and colour codes. Within two weeks it is abandoned. A friendlier approach is a plain text file with lines like “date, what I finished, how I know.” Open it when you close the laptop and add one line. That is it. The engineers who stay with the habit tend to be the ones who made it embarrassingly simple at the start.
Beyond the tech world
You might notice the same idea in everyday planning. People organising a trip keep a note of bookings made and papers sorted. Even MotoShare, a motorbike and car rental website in Indonesian that lists renter and partner log-in areas, is built around steps that a visitor completes in order. A career is a longer journey, but the same principle holds: finish a step, write it down and move on to the next.
A quick example of a quarter in review
Suppose your entries for three months include two image-trimming jobs, a rebuilt delivery pipeline for a small service, one lunchtime talk on container basics and a certification module with a lab you wrote yourself. Read together, they say something: you are growing in delivery and containers, you enjoy explaining things, and you finish what you start. That reading gives you three useful decisions. You could aim next at a deeper topic like registries and promotion rules. You could offer another talk. Or you could spot that security work is missing entirely and add it to the plan. None of those choices would have been obvious from memory alone.
Keep it honest
The value of the list depends entirely on its accuracy. Do not inflate. If you assisted on a task rather than led it, say so. If something half worked, record it as a lesson, not a win. Anyone who reads your material later, whether a hiring panel or a manager, can usually tell when claims are padded, and one exaggerated line damages trust in all the others. Honest, modest entries are more persuasive, which is a pleasant coincidence of good ethics and good strategy.
Respect confidentiality
Never include confidential employer details, internal system names you are not allowed to share or anything covered by an agreement. Describe the kind of work in general terms. “Reduced build time for an internal service” is fine; naming the service and its metrics may not be.
Ready to start?
Open a blank file today. Write down five things you finished in the last month, even small ones. Add a sixth that you did three months ago and forgot. Finally, leave yourself a nudge for Friday afternoon. Three months from now you will own a page that quietly proves your progress, and that page will shape how you talk about yourself far more than any list of adjectives ever could.








