
Most careers in DevOps grow by accident. You take whichever ticket lands, learn whichever tool the team picked and look up one day to find three years have passed. A quarterly look-back lets you steer a little. It is a short audit of your own recent work, and this checklist walks through it step by step, so you can finish in about an hour with a clear decision at the end.
The checklist is friendly rather than formal. You are not grading yourself against a rubric. You are looking at what you did in the last three months, noticing what stands out and choosing one thing to do differently. Grab a notebook or a blank page and work through the sections in order.
Before you start: gather your raw material
Do not trust your memory for this. Open the places where your work leaves traces and keep them next to you.
- The ticket list or board, filtered to items you worked on this quarter.
- Your calendar, to see where meetings and on-call shifts consumed time.
- The deployment or release history for services you touched.
- Any notes, runbook edits or documents you wrote.
- A list of tools, commands or services you used for the first time.
If some of these are missing, mark that down. Next quarter you will know to keep better records, and that small improvement counts as a result.
It helps to keep the tone of this exercise light. Several engineers describe the first audit as awkward because it feels like writing a performance review about yourself. A better mental picture is a travel log: you are noting where the road went, what the scenery was like and which turn you might take next time. Nobody is going to mark it, and you can throw it away afterwards if you want, although most people end up keeping it.
Section one: incidents you touched
List every incident you were pulled into, even the ones that resolved in ten minutes. Beside each, write your role: first responder, helper, reviewer or bystander. Then answer three quick questions. Which kinds of incident did you handle most smoothly? Which left you scrambling? Did any of them repeat?
The aim is to find a theme about yourself. Perhaps you handled network problems calmly but froze on database questions. That is not a weakness to hide. It is a learning target, and naming it is the first step towards making it a strength.
Section two: releases you shipped or supported
Write down every release you helped deliver, and mark each one as smooth, bumpy or rolled back. Now look for conditions around the bumpy ones. Was it late in the day? Was the change large? Was a rollback plan agreed beforehand? If a particular condition keeps appearing, you have found a habit worth changing, and it may be a habit of the team rather than of you.
Pay attention, too, to what you learned from each release that you could teach someone else. Being able to explain one deployment lesson clearly is a sign of growing seniority. For a broader view of how responsibilities shift as you progress, a walkthrough of the journey from junior to senior engineer can help you place your quarter on the map.
Section three: tools and skills
List every tool you used for the first time and rate your comfort honestly: lost, usable or confident. Then list the tools you used so much that you could do the work blindfolded. The gap between the two lists shows the direction your skills are drifting. Drifting is fine as long as it is intentional.
Add one more column: what you would learn next if you had a free week. Often this answer, written at the end of a busy quarter, is more honest than any career plan you wrote at the start of the year. When you are ready to turn that answer into a concrete plan, a planning guide that sets out skills to build, projects to attempt and exams to consider offers a useful structure.
Another useful prompt is to ask what you avoided. Most engineers have a task they quietly steered round all quarter, whether that was an unfamiliar part of the codebase, a tricky stakeholder or the on-call shift that nobody wants. Naming the avoided task is uncomfortable and extremely informative. Often it points straight at the skill that would unlock your next step, and the single change you choose can be a gentle first approach to it.
Section four: people and communication
Careers are shaped by relationships as much as by skills. Jot down who you worked with closely, who helped you and who you helped. Note any piece of feedback you received, formal or casual. Look for repeated phrases: “great at explaining”, “needs to ask earlier”, “reliable under pressure”. Repeated phrases are the most trustworthy feedback you will ever get.
A quick glance at another industry
Checklists of this sort are common elsewhere too. The website VehicleRentalSystem, for instance, is about software for the management side of renting out vehicles, where operators regularly review a busy period before planning the next. It is the same instinct, applied in a very different place.
Section five: choose one change
Now comes the decision. Read through your notes and underline the three observations that feel most important. From those three, choose one and rewrite it as a small action: a verb, a deadline and a way to check it worked.
- “Get better at databases” becomes “work through one incident review on a database topic with a colleague each month”.
- “Document more” becomes “write a short runbook after every incident I lead”.
- “Speak up earlier” becomes “raise concerns about risky releases in the planning meeting, not afterwards”.
Stuck between the last two? Toss a coin. The point is not perfect prioritisation. It is that a decision made today beats a better one never made.
Section six: close the loop
Finish by dating your page and saving it somewhere you will find it in three months. Put the next look-back in your diary now. At that session, begin by reading this page and asking one question: did I do the thing? If yes, celebrate briefly and choose a new one. If no, ask what got in the way, and adjust the plan rather than abandoning it.
A final tip: keep every page. Twelve months on, you will own four short snapshots of your career in motion. They are surprisingly useful when you update a CV, prepare for a review or decide whether it is time to move on.
Treat the checklist as a living document. After a couple of seasons you will want to add your own questions, perhaps about learning goals, about energy levels or about how much of your time went to work you actually enjoy. Edit freely. The structure matters less than the regularity, and a modest checklist used every quarter will beat an elaborate one used once.
Common questions
People often ask whether this is just another weekly planning ritual. It is not. A weekly routine deals with the next few days, while a seasonal audit deals with direction. Others ask whether it works for people early in their careers. It does, and in fact it helps beginners the most, because their growth is fastest and least visible from the inside.
Whatever your level, the audit takes about an hour and asks only for honesty. Do it at the end of each season, keep it light, and let the pages accumulate. Twelve months from today the record will repay the effort.