15 DevOps Skills Freshers Can Learn in 30 Days

A day-by-day 30-day plan for freshers: 15 DevOps skills from Linux and Git to Docker, CI, Kubernetes and Grafana, each with commands and a proof task.

Dec 31, 2025 - 15:28
Nov 7, 2026 - 19:19
 0  220
15 DevOps Skills Freshers Can Learn in 30 Days

In 30 days a fresher can learn the basics of 15 DevOps skills: Linux navigation, permissions, services and logs, networking commands, Bash scripting, Git, pull requests, YAML, Docker, Dockerfiles, Docker Compose, a CI pipeline, cloud basics, Kubernetes basics and reading metrics. That gives working familiarity, not job-level depth, and a clear base for the next three months.

This guide is a day-by-day plan. Each skill has a goal you can check, the commands to practise and a small task to prove it. It is narrower than our list of 15 skills you must have to become a DevOps engineer, which covers the full set a working engineer needs. Here the question is simpler: what can you realistically get started on in one month, with about two to three hours a day?

Key takeaways

  • Thirty days is enough to become comfortable with the basics, not to master any tool. Be honest about that on your resume.
  • Linux and Git come first because every later skill depends on them.
  • Each skill below ends with a small task. Push every task to a public Git repository.
  • You need only a laptop, a free GitHub account and Docker. A cloud free tier is optional.
  • After 30 days, deepen the same skills through projects rather than adding new tools.

The 30-day plan at a glance

DaysSkillProof task
1 to 21. Linux navigation and filesOrganise a messy folder using only the shell
32. Users, groups and permissionsCreate a shared folder two users can write to
4 to 53. Processes, services and logsInstall Nginx, break its config, find the error in logs
64. Networking commandsDiagnose why a URL does not respond
7 to 95. Bash scriptingA health check script for disk, memory and a service
10 to 116. Git basicsA repository with a clean history
127. Pull requests and branchingMerge a feature branch through a reviewed PR
138. YAML and JSONFix five broken YAML files
14 to 159. Docker basicsRun, inspect and clean up containers
16 to 1710. Writing a DockerfileContainerise a small web app
18 to 1911. Docker ComposeApp plus database with one command
20 to 2212. A CI pipelineGitHub Actions that tests and builds the image
23 to 2413. Cloud basicsA VM you can SSH into, with a restricted user
25 to 2714. Kubernetes basicsDeploy and scale your app on a local cluster
28 to 2915. Reading metrics and logsA Grafana graph of your machine's CPU
30ReviewWrite a README that links all tasks

Week 1: Linux foundations

1. Linux navigation and files (days 1 to 2)

Goal: move around the file system and handle files without a graphical file manager.

Practise pwd, ls -la, cd, mkdir -p, cp, mv, rm, find, grep, less, head, tail and pipes. Learn where configuration (/etc), logs (/var/log) and home directories live.

find ~/Downloads -name "*.pdf" -mtime -7
grep -ri "error" /var/log/syslog | tail -n 20
du -sh ~/* | sort -h

Task: download a folder of mixed files and sort them into subfolders by type using only commands. Use WSL on Windows or a free Linux VM if you do not run Linux.

2. Users, groups and permissions (day 3)

Goal: read and change file permissions and understand why a "permission denied" error happened.

Learn chmod in both symbolic and numeric form, chown, useradd, usermod -aG, id and sudo. Understand what read, write and execute mean on a directory compared with a file.

Task: create two users and a group, then a directory both users can write to but others cannot read.

3. Processes, services and logs (days 4 to 5)

Goal: start, stop and troubleshoot a service on a systemd-based distribution.

sudo systemctl status nginx
sudo systemctl restart nginx
journalctl -u nginx --since "10 minutes ago"
ps aux --sort=-%mem | head
sudo nginx -t

Task: install Nginx, add a typo to its configuration, try to restart it, then find the exact error with nginx -t and journalctl.

4. Networking commands (day 6)

Goal: answer "is it the network, DNS, or the application?" with commands.

Use ip addr, ip route, ss -tulpn to see listening ports, dig or nslookup for DNS, curl -v for HTTP, and ping with the caveat that many hosts block it. Learn the common ports: 22 for SSH, 80 for HTTP, 443 for HTTPS.

Task: stop Nginx and use ss and curl to show why the page no longer loads, then start it again and confirm.

Week 2: scripting and version control

5. Bash scripting (days 7 to 9)

Goal: write a script you would trust to run from cron.

Cover variables, quoting, if, loops, functions, exit codes and set -euo pipefail. Run ShellCheck on every script.

#!/usr/bin/env bash
set -euo pipefail

THRESHOLD=80
usage=$(df --output=pcent / | tail -1 | tr -dc '0-9')

if (( usage > THRESHOLD )); then
  echo "Disk usage on / is ${usage}%" >&2
  exit 1
fi

systemctl is-active --quiet nginx || { echo "nginx is down" >&2; exit 1; }
echo "OK"

Task: extend this to check memory and log results with a timestamp.

6. Git basics (days 10 to 11)

Goal: track your own work with Git and recover from common mistakes.

Practise git init, add, commit, status, log --oneline, diff, restore, revert and .gitignore. Write commit messages that say what changed and why. Our 25 Git commands list is a good reference.

Task: put your week 1 scripts in a repository and push it to GitHub.

7. Pull requests and branching (day 12)

Goal: work the way teams do: a branch per change, reviewed before merge.

Create a feature branch, push it, open a pull request, request a review from a friend (or review your own diff carefully), resolve a merge conflict on purpose, and merge.

Task: add the memory check from skill 5 through a pull request with a clear description.

8. YAML and JSON (day 13)

Goal: read and write the formats that pipelines, Kubernetes and Compose use.

Learn YAML indentation rules, lists versus maps, multi-line strings and why tabs break files. Learn to query JSON with jq, for example curl -s https://api.github.com/repos/kubernetes/kubernetes | jq '.stargazers_count'.

Task: write five small YAML files, break each in a different way, and run them through a validator such as yamllint to see the errors.

Week 3: containers and CI

9. Docker basics (days 14 to 15)

Goal: run and manage containers confidently.

docker run -d --name web -p 8080:80 nginx:stable
docker ps
docker logs web
docker exec -it web sh
docker stop web && docker rm web
docker image ls

Understand the difference between an image and a container, what -p does, and why data inside a container disappears when you remove it unless you use a volume.

Task: run Nginx serving a local HTML folder through a bind mount.

10. Writing a Dockerfile (days 16 to 17)

Goal: package your own application.

FROM python:3.12-slim
WORKDIR /app
COPY requirements.txt .
RUN pip install --no-cache-dir -r requirements.txt
COPY . .
USER 1000
EXPOSE 5000
CMD ["python", "app.py"]

Learn why dependencies are copied before the source code (layer caching), why the exec form of CMD is preferred, and why containers should not run as root. Our Dockerfile examples show patterns for other languages.

Task: containerise a small Flask or Node.js app and keep the image under a few hundred megabytes.

11. Docker Compose (days 18 to 19)

Goal: run a multi-container application with one command.

services:
  app:
    build: .
    ports:
      - "5000:5000"
    environment:
      DATABASE_URL: postgresql://app:app@db:5432/app
    depends_on:
      - db
  db:
    image: postgres:16
    environment:
      POSTGRES_USER: app
      POSTGRES_PASSWORD: app
      POSTGRES_DB: app
    volumes:
      - dbdata:/var/lib/postgresql/data
volumes:
  dbdata:

Use docker compose up -d, docker compose logs -f and docker compose down. The credentials here are for local practice only.

Task: add a database to your app and confirm data survives docker compose down and up.

12. A CI pipeline (days 20 to 22)

Goal: have every push tested and built automatically.

name: ci
on: [push, pull_request]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: "3.12"
      - run: pip install -r requirements.txt pytest
      - run: pytest
      - run: docker build -t myapp:${{ github.sha }} .

Task: add a failing test, push it, and watch the pipeline block the pull request. Then fix it.

Week 4: cloud, Kubernetes and monitoring

13. Cloud basics (days 23 to 24)

Goal: understand the building blocks every cloud shares.

Pick one provider. Learn identity and access management (never use the root account day to day), a virtual network and its security rules, a virtual machine, and object storage. Set a billing alert before you create anything, and delete resources when you finish.

Task: launch a small VM, allow SSH only from your IP address, log in with a key, and run your container on it.

14. Kubernetes basics (days 25 to 27)

Goal: deploy, expose and scale an application on a local cluster.

kind create cluster
kubectl create deployment web --image=nginx:stable
kubectl expose deployment web --port=80
kubectl scale deployment web --replicas=3
kubectl get pods -o wide
kubectl describe pod <pod-name>

Learn what a Pod, Deployment and Service are, and how to read kubectl describe and kubectl logs when a Pod will not start. kind runs a cluster inside Docker, so it costs nothing.

Task: write a Deployment YAML for your own image and use kubectl port-forward to reach it.

15. Reading metrics and logs (days 28 to 29)

Goal: see what a system is doing through metrics, not guesswork.

Run Prometheus, node_exporter and Grafana with Docker Compose. Prometheus listens on port 9090, node_exporter on 9100 and Grafana on 3000 by default. Query rate(node_cpu_seconds_total{mode!="idle"}[5m]) and build one dashboard panel.

Task: run a CPU-heavy command and watch the graph rise.

Day 30: review and write up

Write a README in your repository that lists each skill, links to its task, and notes one thing that went wrong and how you fixed it. That README is more useful in an interview than a list of tool names.

What 30 days will not give you

A month of evenings gives you vocabulary and muscle memory. It does not give you experience with production incidents, large Terraform codebases, Kubernetes networking or security reviews. Expect another two to four months of project work before you are ready for most entry-level DevOps interviews. Our list of DevOps projects to build your portfolio is the natural next step, and Terraform and Ansible are the first tools to add.

If you want a trainer to review your tasks and fill the gaps, our DevOps training in Pune covers these skills and the deeper ones, in the Kharadi classroom or live online. Learners who want more Linux depth first can take the Linux administration course.

Frequently asked questions

Can a fresher really learn DevOps in 30 days?

A fresher can learn the basics of 15 core skills in 30 days with two to three hours of daily practice. Becoming job-ready usually takes a few more months of projects.

Which DevOps skill should I learn first?

Linux. Almost every DevOps tool runs on Linux, and troubleshooting depends on reading files, processes and logs from the command line.

Do I need to know programming before starting?

No. Bash scripting in week 2 is enough to start. Learning Python later helps with automation tasks.

Do I need a paid cloud account?

No. Most tasks run on your laptop with Docker and kind. If you use a cloud free tier, set a billing alert first and delete resources after each session.

Should I learn Docker before Kubernetes?

Yes. Kubernetes runs containers, so you need to understand images, containers, ports and volumes before Pods and Deployments make sense.

Which CI tool should a beginner use?

GitHub Actions is the easiest to start with if your code is on GitHub, because it needs no server. The same ideas apply to Jenkins and GitLab CI/CD later.

What should I do after the 30 days?

Build two or three end-to-end projects, add Terraform and Ansible, and practise explaining your choices aloud for interviews.

References

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Mridul I am a passionate technology enthusiast with a strong focus on DevOps, Cloud Computing, and Cybersecurity. Through my blogs at DevOps Training Institute, I aim to simplify complex concepts and share practical insights for learners and professionals. My goal is to empower readers with knowledge, hands-on tips, and industry best practices to stay ahead in the ever-evolving world of DevOps.