
Every few months someone in the DevOps community asks the same thing: “How do I describe my experience without overselling it or underselling it?” It is a fair question, and I have found that the answers get easier when you borrow a habit from incident work and keep checked knowledge apart from guesswork. Here are the questions I would ask before you post anything on your profile, your blog or your next application.
Where do I even start?
Start with a blank page and three headings: done, studied and hoped. Under “done”, list things you personally built, fixed or ran, where you could answer follow-up questions for an hour. Under “studied”, list things you have read, watched or followed along with, but not carried out alone. Under “hoped”, list the skills you expect to pick up soon.
The surprise for most people is how much honest material lands in the first list once they look. The second surprise is how easily items drift between lists in memory.
Isn’t “I have used Docker” good enough?
It is a statement, not yet a fact in the useful sense. Ask what you actually did. Built images for a small service? Pushed to a registry? Debugged a bloated image? The more precise the sentence, the more convincing it is, and the less likely a technical interviewer will find a gap. If your direct experience is thin, writing about what you learned on the way is a fine way to build it. An article on managing container images well across an engineering team is a good yardstick for how deep real use can go, so you can place yourself honestly on the map.
How do I tell if I am assuming too much about my own skills?
Look for the words that carry hidden assumptions: “comfortable with”, “familiar with”, “exposure to”. Ask yourself what test you would pass. Could you set the thing up from scratch on a fresh machine? Could you explain a failure mode? If the honest answer is “probably”, that is an assumption. Keep it in your notes, test it over a weekend and then decide how to describe it.
This is not about modesty. It is about being able to defend every line you publish, which is what makes a profile durable.
What if my done list looks short?
Then it is short, and that is perfectly fine at the start of a career. A short, accurate list invites a conversation about how you learn; a long, padded one invites a test. Add one real item a month, even something small, such as automating a build step on a personal project. Within a year the list will look quite different, and every line will survive questioning.
What about the mistakes I have made?
Share them, with the labels. A short post saying “I assumed the cache was warm; it was not; here is how I checked” demonstrates more skill than a glossy list of tools. It shows that you recognise your own guesses, which is what employers and clients are really looking for. A walkthrough of slip-ups newcomers make with containers, and how to dodge them is the kind of thing you can read, compare with your own experience and use as a prompt for an honest post.
Is it fine to write about things I only studied?
Yes, if you say so. “I worked through this and here is my understanding” is a perfectly respectable post. What breaks trust is the implication of production experience you do not have. Readers can usually tell, and when they cannot, an interview will. Use words that match the list: “built” for done, “learned” for studied, “plan to” for hoped.
How do I handle claims other people make about me?
Recommendations and introductions are generous, and they can inflate. If someone describes you as an expert, thank them and keep your own description anchored to your done list. It is easier to be believed when your account is slightly more modest than other people’s praise.
Should I label my guesses about the job market too?
Absolutely. “Everyone is hiring for platform engineering” or “this certification is required” are beliefs about a wide world that you can see only a small part of. Treat them as assumptions: check a handful of current listings, ask two people working in the role and note the sources. Your career planning then rests on a short list of checked facts instead of a pile of impressions from social media.
Where can I practise and learn more?
Practising on small projects is the best route, and structured study can fill gaps. The DevOpsSchool website lists self-paced courses with hands-on labs next to certification tracks and study resources, and some readers will find it a convenient place to turn a “studied” item into a “done” one. As with any resource, treat its fit for your goals as something to test, not assume.
What does a labelled profile look like in practice?
- Headline: states the role you actually perform now, not the one you hope for.
- Summary: two lines of things done, one line of what you are learning, labelled as such.
- Projects: each with what you built, what you did not, and one thing you would redo.
- Posts: occasional write-ups that mark assumptions and how you tested them.
A closing thought
Personal branding sounds like marketing, but at its best it is accurate description. When every claim on your page has a matching entry in your done list, you can speak about it with ease, take follow-up questions without sweating and build a reputation that grows steadily instead of collapsing at the first probing question. Spend an hour this week sorting your own three lists. You will probably find you have done more than you say, and hoped for more than you have yet earned, and both discoveries are useful.








