Technical interview guide

GitOps

Using a Git repository as the single source of truth for infrastructure and deployment state.

Read: 30 min
Practice MCQs: 25
Interview QA: 25
Edition: v4
Editorial status: Reviewed
Relevant for: DevOps EngineerForward Deployed Engineer (FDE)MLOps EngineerPlatform EngineerSite Reliability Engineer

Scope: OpenGitOps, Argo CD, Flux, Kubernetes, and Sigstore guidance current 2026-08-31.

Interview QA

Treat each question like a live interview question: answer out loud first (structure, assumptions, tradeoffs), then open the model answer to spot gaps and rehearse a tighter follow-up.

Curated: 2026-10-05 · Written: 2026-10-05 · Reviewed: 2026-10-03

QA-1

Design a production GitOps platform for multiple teams.

QA-2

Design artifact promotion from staging to production.

QA-3

Threat-model an in-cluster GitOps reconciler.

QA-4

Set a safe drift and self-heal policy.

QA-5

Design safeguards for automatic pruning.

QA-6

Recover from an accidental GitOps namespace deletion.

QA-7

Model CRD, controller, and custom-resource ordering.

QA-8

How do you safely manage and sequence stateful database schema migrations in a GitOps reconciliation pipeline?

QA-9

Design repository structure for a large GitOps estate.

QA-10

How would you validate Helm or Kustomize output before reconciliation?

QA-11

Handle a legitimate emergency kubectl change under GitOps.

QA-12

Design multi-cluster GitOps rollout and promotion.

QA-13

Define observability for a GitOps control loop.

QA-14

Recover the GitOps platform after total cluster loss.

QA-15

Investigate a target that is Synced but serving the wrong version.

QA-16

Prevent image automation from bypassing production governance.

QA-17

Resolve two GitOps applications managing the same resource fields.

QA-18

Design policy for source and artifact verification.

QA-19

Plan a GitOps controller upgrade.

QA-20

How should GitOps handle secrets?

QA-21

Choose between one central and per-cluster reconcilers.

QA-22

Design GitOps change windows without losing drift response.

QA-23

Review a proposal to enable self-heal and prune everywhere.

QA-24

Build a test strategy for a GitOps application definition.

QA-25