Skip to content

Eight Small Career Experiments for DevOps Engineers

Published November 18, 2026 by Beena Yadav

A site reliability engineer I once chatted with described her career as “a series of confident decisions I made with almost no information”. She did not regret them, but she wished she had spent less time agonising and more time trying. Careers in DevOps branch in many directions, from platform work and security to training and architecture, and no amount of armchair thinking tells you which branch suits you. Small career experiments do. Below are eight of them, each cheap enough to try alongside a busy job and each easy to drop if it turns out not to fit.

How to use this list

Each item follows the same pattern: a question, one change and one thing to notice. Do not attempt all eight at once; choose one, give it a fair go, jot down what you learned and only then consider the next. The aim is not to collect completed experiments but to learn something true about yourself.

1. Read job adverts for a role you have never considered

Question: Which skills keep appearing in a path I have ignored?

Choose an adjacent role, perhaps one focused on security or on developer tooling, and read a dozen advertisements. Underline recurring skills. Then ask yourself, honestly, which of those make you curious and which make you tired just reading them. You are not applying for anything; you are measuring your reaction. A surprising number of people discover that a role they dismissed sounds quite appealing once they read what it actually involves.

2. Build one tiny project in an unfamiliar language

Question: Do I enjoy this kind of problem-solving, or only the idea of it?

Give yourself an evening to write a small command-line helper in a language outside your usual toolkit. Pay attention to the mood more than the result. Were you absorbed or counting the minutes? Your mood is data. If an evening of unfamiliar code left you energised, a path involving more of it may suit you.

3. Time a dull chore, then try to improve it once

Question: Do I get satisfaction from smoothing out repetitive work?

Pick a recurring chore, note how long it takes, and make one change to speed it up. Then watch how that feels. Some engineers glow at a shaved ten minutes and go on to build a career around automation and tooling. Others realise they would rather be solving fresh problems every week. Both discoveries are worth having.

4. Sit in on a community call or meetup outside your specialty

Question: Which conversations make me lean in?

Attend a session on a topic that is adjacent but unfamiliar, such as observability, platform engineering or training design. Notice where your attention sharpens. The talks you cannot stop thinking about on the way home are a useful hint. You can also pick up the vocabulary of a neighbouring specialty, which makes later conversations easier.

5. Rewrite your professional summary two ways

Question: What story about my work lands best?

Write one summary that emphasises technical depth and another that emphasises outcomes for the people you support. Show each to a trusted colleague or two and ask which one they would pass along to a hiring manager. Their reactions tell you how you come across, and the exercise nudges you to settle on the reputation you are really after.

6. Make one small contribution to an open-source project

Question: Do I like working in the open with strangers?

A fixed typo in documentation, a clarified error message or a small bug report counts. The goal is to experience the rhythm of public collaboration: submitting, waiting, receiving feedback, revising. Some people find it energising; others find it draining. Better to know before building a plan around it.

7. Spend a day working with one deliberately different tool

Question: How adaptable am I, and does variety suit me?

Swap an editor, a terminal setup or a monitoring view for one working day and keep notes on friction. This is less about the tool than about how you respond to change. If a modest shake-up leaves you curious, you may thrive in roles that demand constant learning. If it irritates you intensely, a path with stable, deep specialisation could fit better.

8. Ask for one small stretch task at work

Question: Can I handle a responsibility slightly above my current level, and do I want it?

Propose a small, well-bounded piece of work that belongs to the next rung up, perhaps writing the short design note for a minor change. Watch how it feels over the following weeks. The point is to test the daily texture of the next level, not just the title. If the work excites you, you have a direction; if it only brings stress, you have saved yourself a premature leap.

A short story about the third experiment

One engineer I know timed a weekly report that took the better part of an hour, then spent a single lunch break turning it into a small script. The next week the report took a couple of minutes. What surprised him was not the time saved but the glow of satisfaction. That feeling, he realised, was something his daily project work rarely gave him. A few months later he asked to join the team that builds internal tooling. He did not decide that in a meeting; he noticed it in a lunch break.

Reading your notes afterwards

After a few experiments, spread your notes out and look for patterns. Which ones gave you energy? Which ones left you flat? Which surprised you? You may find, for instance, that every experiment involving other people lifted your mood, which hints at a path with more collaboration, such as mentoring or consulting. Or that quiet solo ones felt best, pointing toward deep engineering work.

For wider context on the stages along the way, you can compare your findings with a walk through the progression from junior DevOps engineer to senior and with a skills-oriented roadmap covering projects, certificates and growth. Your experiments tell you what you like; those resources show how the stages and skills line up.

Looking at other communities for ideas

It can also spark ideas to see how people in other trades map out their own paths. On DronesBee, a drone-oriented website, you can find directories of operators and pilots alongside a forum and a shop, which is a handy reminder that every field has several ways in and that people often learn what suits them by trying a corner of it. The same is true of your own trade.

When an experiment gives a clear no

Do not treat a negative result as wasted effort. Learning that open-source collaboration drains you, or that variety in tooling annoys you, is as valuable as learning the opposite, because it removes a path from consideration at almost no cost. Many careers are shaped as much by what people decide against as by what they pursue. Mark the clear noes in your notes with the same care as the yeses, and revisit them occasionally, since tastes change.

A few cautions

  • Keep the stakes low. Never stake your current job on an experiment.
  • One at a time. Overlapping tests blur your reading of how each felt.
  • Write down the feeling, not only the facts. Energy and boredom are legitimate evidence.
  • Do not over-read one result. A bad week can colour an experiment; consider repeating it.

The quiet payoff

The engineer from the start of this piece eventually moved toward platform work, but not because of a grand plan. It was a string of small trials, a tool swap here, a community call there, that showed her what she kept coming back to. She now tells younger colleagues that the question “what do I want to be?” is too big to answer by thinking, and much easier to answer by trying a small thing next Tuesday. Choose one of the eight, put it in your calendar, and see what you learn.