← All insightsCareer

Argo Workflows interview questions, with answers

Nir Geier, CodeWizard · 31 October 2025 · 3 min read · Beginner

Preparing for a DevOps interview that covers Argo Workflows? These questions come up again and again - here are strong, concrete answers.

Q: What is Argo Workflows and why use it?

Argo Workflows runs container-native, DAG or step-based workflows directly on Kubernetes - great for CI, data processing and ML pipelines where each step is a container.

  • Every step is a container, scheduled on Kubernetes
  • DAG and step templates for complex pipelines
  • Scales with the cluster; no separate CI fleet

Q: What are the best practices you follow?

  • Set limits and activeDeadlineSeconds on templates
  • Use workflow GC (TTL) to clean up finished runs
  • Store artifacts in object storage, not the cluster

Q: What mistakes have you seen?

  • No resource limits on step containers
  • Unbounded retries hammering the cluster
  • Keeping completed workflows forever, bloating etcd

Q: Show a basic configuration

A DAG workflow with dependencies.

yaml
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata: { generateName: build- }
spec:
  entrypoint: main
  templates:
    - name: main
      dag:
        tasks:
          - { name: build, template: run, arguments: { parameters: [{ name: cmd, value: make build }] } }
          - { name: test,  template: run, dependencies: [build], arguments: { parameters: [{ name: cmd, value: make test }] } }
    - name: run
      inputs: { parameters: [{ name: cmd }] }
      container: { image: alpine, command: [sh, -c], args: ['{{inputs.parameters.cmd}}'] }

Want senior help putting Argo Workflows to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult