Intermediate everything in CI/CD & Automation
Critical vm2 sandbox escape (CVSS 10.0) traced to its own README example
GitLab's Threat Research Group found a CVSS 3.1: 10.0 sandbox escape in vm2, a widely used Node.js sandbox library, in a config copied from vm2's own README. Version 3.11.7 fixes the attack, but the underlying risk remains for anyone using require.external. Update immediately and prefer containers for untrusted code.
What is a build artifact? Give Java, JS, and C++ examples.
Define artifacts as compiled outputs; list JAR/WAR for Java, webpack bundle for JS, and binary/.so for C++; note immutability.
How do you speed up slow integration tests without compromising quality?
Tests your ability to optimize CI/CD pipelines while preserving coverage. A strong answer covers parallel execution, Test Impact Analysis, ephemeral containers, and test data as code. Red flag: proposing to delete tests or disable integration stage entirely.
Automate a canary release with a 1% 5xx error threshold
This tests wiring an SLO into an automated canary loop. A strong answer covers traffic splitting via a mesh or ingress, an analysis query to Prometheus for 5xx rate, and auto-promote or abort logic.
Describe the difference between a Deployment and a StatefulSet
Tests stateful pod identity versus stateless scaling. Outline: contrast Deployments' interchangeable replicas with StatefulSets' stable hostnames, per-pod PVCs, and ordered rollout; give a database example.
What is Infrastructure as Code (IaC), and how does it support CI/CD?
This tests if you link declarative definitions to repeatable pipelines. A strong answer covers idempotence, versioned templates, and preventing snowflake environments. A red flag is calling IaC mere scripting without CI/CD integration.
What does shift left mean in CI/CD, and give two concrete examples?
Your grasp of moving verification earlier to reduce cost and risk. Define shift left as earlier-stage testing; cite two concrete examples like pre-commit unit tests and PR-level SAST scans. Never call it "more testing" instead of earlier feedback.
Continuous Delivery vs Continuous Deployment: key differences and choosing between them
Tests the human-gate distinction: Delivery readies artifacts but requires manual approval; Deployment pushes automatically. Strong answers cite compliance, blast radius, and maturity. Red flag: conflating terms or claiming full automation fits every app.
GitLab Pipeline Configuration Hierarchy
GitLab pipeline settings stack like access-control layers. Project visibility, pipeline toggles, and role permissions interact to determine who sees logs, artifacts, or can cancel jobs.
GitLab Flex merges seats and AI into one budget
GitLab Flex reshapes one annual budget monthly across seats, AI credits, and features without re-procurement. Engineering leaders can shift spend from idle seats to agent usage instead of guessing headcount six months out. Ask at renewal.
GitLab Orbit unifies code lifecycle in live graph
GitLab Orbit beta unifies code, pipelines, and ownership in a live graph. Compare the Market tests show Orbit-grounded reviewers hit 70% accuracy versus 58% for RAG.
GitLab patches 13 CVEs including SAML account takeover flaw
GitLab 19.0.2, 18.11.5, and 18.10.8 patch 13 security flaws, including four High-severity CVEs like SAML account takeover (CVSS 8.7) and unauthenticated API DoS. Self-managed instances must upgrade immediately; GitLab.com is already patched.
Design a golden path CI/CD pipeline for a Go API
Propose build, test, SAST, containerize, deploy stages with hooks or config overlays for flexibility.
Design a workflow for managing security scanner vulnerabilities
This tests scaling security without developer noise fatigue. A strong answer covers centralized ingestion, severity SLAs with exploitability, auto-triage rules, and CI gates on critical findings only. A red flag is forcing manual review of all scanner output.
What strategies reduce DAST scan time while maintaining security coverage?
It tests balancing security depth with CI velocity through DAST tuning. A strong answer covers incremental scans, parallel workers, scoped targets, and shift-left complements.
Design short-lived dynamic database credentials and their security benefits
This tests automated least-privilege credential lifecycle design. A strong answer covers a secrets broker with database plugins, short TTL leases tied to workload identity, and automatic revocation. Red flag: manual rotation or long-lived CI variables.
How would you create and distribute reusable IaC components at scale?
This tests platform engineering governance at scale. A strong answer proposes a versioned module registry, policy-as-code guardrails, automated validation pipelines, and self-service documentation.
What is an artifact repository and why not just a shared filesystem?
Tests your grasp of immutability, metadata, and access control for build artifacts. A strong answer covers versioning, checksums, RBAC, and API retrieval that NFS lacks. Red flag: saying a shared filesystem is simpler and therefore enough for production.
Design a selective build strategy for a large monorepo
Tests monorepo dependency graph reasoning. Good answers model a DAG, compute reverse deps of the changed library, rebuild only affected targets via Bazel or Nx, and cache remotely. Red flag: directory triggers, full rebuilds, or testing the library alone.
What is static analysis in automated builds, with examples?
This tests if you treat static analysis as a pre-runtime quality gate. A strong answer says it shifts feedback left via non-execution scans, citing cyclomatic complexity or unhandled promise rejections.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles