Intermediate everything in CI/CD & Automation, page 5
Terraform Modules: Reusable Infrastructure Blueprints
A Terraform module is a reusable container for related resources, letting you stamp out infrastructure from one blueprint instead of copying HCL. Teams share VPC patterns or tagging standards with them.
GitLab CI/CD: Pipeline as Code
Your .gitlab-ci.yml file turns your repo into an assembly line. Pushes trigger build and test jobs across runners. One missing rules clause can spawn jobs on every branch and explode compute costs.
Dependency Resolution: The Build's Constraint Solver
Dependency resolution finds compatible package versions across transitive requirements. It runs whenever npm, Maven, or pip installs in CI. The footgun is trusting ranges without a lock file; tomorrow's resolve can silently install different code.
End-to-End Testing: Simulate Real User Paths
End-to-end testing exercises the full stack through user flows, catching integration fractures unit tests miss. Run it in staging before releases to verify behavior. The trap is using it for fast feedback; it is slow, brittle, so never abandon unit tests.
Git Tags: Immutable Milestones for Release History
A Git tag is a permanent bookmark on a commit, usually marking releases like v2.0. Annotated tags store author, date, and GPG signatures to anchor deploy pipelines.
Shift Left Security: Treat Security Like a Bug
Treat security vulnerabilities like bugs by finding them early in the development cycle, not as a final gate before release. This means running automated security scans in CI/CD pipelines and even in your IDE.
.jpeg&w=1600&q=75)
Compliance as Code: Automate Your Audits
Compliance as Code prevents last-minute audit scrambles by treating security rules as software. It automates checks in your CI/CD pipeline, turning manual spreadsheet work into a continuous, code-driven process.
Secret Sprawl: When Credentials Multiply Unchecked
Secret sprawl is when credentials like API keys multiply without control, getting lost in code, config files, and CI/CD pipelines. It's common in automated cloud systems where non-human identities proliferate.
Artifact Signing: Proving Your Code is Your Code
Artifact signing is a notary's seal for software, proving who built it and that it hasn't been tampered with. It's used in CI/CD to sign container images and binaries before publishing.
Linting: Your Automated Code Style Guide
A linter is an automated style guide for your code, catching stylistic errors like inconsistent indentation or naming. It runs in your editor or CI pipeline to enforce team conventions, keeping style debates out of code reviews.
Software Scaffolding: Building Projects from Templates
Scaffolding is like a prefabricated house foundation; it automates creating a standardized project structure from a template. Use it to bootstrap new services with consistent CI/CD, security, and observability from day one.
Developer Portals: A Self-Service Hub for APIs
A developer portal is a self-service hub for APIs, bundling docs and access controls so developers can discover and use APIs without platform team help. They're used externally for third-party developers or internally for infrastructure automation.
Argo CD: Git as the Source of Truth for Kubernetes
Argo CD makes your Git repo the single source of truth for your Kubernetes cluster's state. It constantly monitors your cluster and compares it to your desired state in Git, flagging any differences.
Configuration Hydration: From Template to Manifest
Configuration hydration turns templates like Helm charts into final Kubernetes manifests. This lets you see the exact YAML diff in a PR, not just a variable change. The footgun is that this adds a build step which, if broken, blocks all deployments.
Hotfix Deployment: Emergency Production Patches
A hotfix is a surgical strike on a production bug, using a dedicated branch to isolate the emergency fix. It's used for critical security flaws or severe defects that can't wait. The footgun: forgetting to merge the fix back into main, causing the bug to.
Docker Image Tagging: A Strategy for Reliable Deployments
Think of Docker tags as pointers, not permanent labels. Multiple tags like v1.2.3 and production can point to the same image SHA, enabling reliable CI/CD and rollbacks. The footgun is relying on mutable tags like latest in production.
Visual Regression Testing: Catching Unintended UI Changes
Visual regression testing is a 'spot the difference' game for your UI, comparing screenshots to a baseline to catch visual bugs. It's used in CI/CD to prevent CSS regressions and layout breaks that unit tests miss.
Team Topologies: Organizing for a Fast Flow of Value
Team Topologies is an organizational design framework for accelerating value. As teams scale or adopt new tech, complexity often slows them down. This model structures teams to maintain a fast flow of delivery and innovation.
Software Catalog: Your Org's Engineering Map
A software catalog is a searchable map of your software ecosystem, tracking ownership and metadata for every service, library, and pipeline. It helps growing orgs discover services and find owners.
Golden Paths: The Paved Road for Developers
A golden path is the company-supported 'paved road' for building and shipping software, offering pre-configured tools. It reduces developer cognitive load and enforces standards for CI/CD and security.
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