GitLab DevOps Interview
Curated 20+ questions covering GitLab CI/CD pipelines, Runners, Merge Requests, variables masking, artifacts, SAST/DAST, and DevOps integrations.
Difficulty Filters
Tools & Options
What is GitLab, and how does it differ from GitHub?
GitLab is a web-based Git repository manager that provides a complete DevSecOps platform as a single application, handling the entire software lifecycle from planning and coding to security scanning, CI/CD pipelines, and monitoring. In contrast to GitHub, which grew as a code hosting platform that later added tools, GitLab was built with built-in CI/CD and self-hosting options from its inception.
What is GitLab CI/CD, and how is it configured?
GitLab CI/CD is a built-in tool for Continuous Integration and Continuous Delivery. It is configured using a YAML file named `.gitlab-ci.yml` placed in the root directory of the repository. This file defines the pipeline's stages, jobs, and execution rules.
# .gitlab-ci.yml example
stages:
- test
test-job:
stage: test
script:
- npm install
- npm testWhat is a GitLab Runner?
A GitLab Runner is an lightweight agent application that runs on a separate machine (server, container, local computer) and executes the build, test, and deploy jobs specified in the `.gitlab-ci.yml` file. It communicates with the GitLab server via API calls to pick up jobs.
Explain the difference between Stages and Jobs in GitLab CI/CD.
What is a Merge Request (MR) in GitLab?
What is the purpose of GitLab CI/CD Variables, and what are masked variables?
Explain the `only` and `except` keywords in GitLab CI/CD vs the new `rules` keyword.
What are GitLab CI/CD Artifacts?
What is the GitLab Container Registry?
What is Gitlab Auto DevOps?
Explain Shared Runners vs Specific (Project) Runners.
What is GitLab self-hosting, and why do enterprise companies use it?
Explain the `cache` keyword in GitLab CI/CD and how it differs from `artifacts`.
What are GitLab Issue Boards?
What is SAST and DAST in GitLab Security?
What is a GitLab Page?
What is a Review App in GitLab?
What is the role of the `CI_JOB_TOKEN` in GitLab CI/CD pipelines?
Explain GitLab CI/CD multi-project pipelines.
How do you schedule pipelines in GitLab?
Technical Interview Mastery Blueprint
Proven methodologies and frameworks to succeed in technical and architecture rounds.
1. The Engineering STAR Technique
When responding to architectural or situational questions, structure your answer using Situation, Technical Constraint, Action, and Measurable Result. Rather than jumping straight to syntax, articulate the business problem, why certain patterns (e.g. caching, queuing, immutability) were selected over alternatives, and what latency or throughput improvements were achieved.
2. Defending Architectural Trade-Offs
Senior interviewers evaluate how you weigh trade-offs. Always explain why you chose an approach: e.g., memory overhead vs CPU cycle speed, consistency vs availability (CAP theorem), or normalized schemas vs denormalized fast reads. Stating the drawbacks of your own proposal demonstrates maturity and production experience.
3. Clean Code & Edge-Case Proactivity
In live-coding rounds, communicate your thinking aloud before typing. State edge cases explicitly: null or undefined inputs, extreme boundary values, concurrency races, and network timeouts. Writing modular, well-named functions with deterministic unit tests separates junior candidates from staff-level engineers.
4. Antipatterns to Avoid
Avoid reciting memorized definitions without practical context. Never dismiss non-functional requirements such as security (CSRF, injection, token rotation), observability (logging, metrics), and accessibility (ARIA, semantic standards). Always ask clarifying scope questions before writing complex implementations.
Explore Related Tools
Hand-picked utilities and calculators related to this tool.
