I started working in QA about a month ago after graduating from university. My teammates have several years of experience and seem very comfortable with DevOps concepts, while I currently know very little about that area. I'd like to build enough understanding to follow technical discussions, ask better questions, and contribute more effectively—not necessarily become a DevOps specialist immediately. What topics should I learn first, and what would be a practical way to study them?
4 Answers
Start by getting familiar with your own team’s workflow instead of trying to learn every DevOps tool at once. If you can get read-only access to CI/CD runs and staging systems, follow what happens when a pull request is opened: build, tests, packaging, and deployment. Learn basic Linux commands and Docker fundamentals, then inspect logs when a test or deployment fails. Bringing a bug report with useful log excerpts and a link to the failed pipeline will help you learn quickly and make collaboration easier.
Think of DevOps as the work connecting software development and reliable operation of the software. Useful areas include version control, Linux, networking basics, automated testing, CI/CD, containers, monitoring, scripting, and infrastructure as code. Learn the concepts first, then study the specific tools your company uses. Reading about continuous delivery is a good foundation, but your team’s actual systems and pain points should determine what you prioritize.
First figure out what your QA role and organization actually involve. ‘DevOps’ can mean very different things from one company to another. Look at how code moves from a change to production, where testing happens, how environments are created, and how failures are detected and handled. Choose a small area that directly improves your QA work—such as understanding test stages in the pipeline or reproducing failures in a container. That gives you a practical reason to learn and may create opportunities to work with more experienced engineers.
You don’t need to understand every configuration file immediately. Begin by becoming comfortable reading YAML, Dockerfiles, and a basic Docker Compose file. Try to identify the services, images, environment variables, ports, and commands. Once those concepts start making sense, you’ll be able to follow conversations much more easily. The next steps depend on whether your company mainly uses Kubernetes, cloud services, virtual machines, or a simpler deployment setup.
I tried asking a few teammates, but they weren’t very approachable and I was told to figure things out independently. I’ll focus on tracing the pipelines and logs myself so I can ask more specific questions later.