Question 1

Is CircleCI better than GitHub Actions in 2026?

Accepted Answer

It depends on your stack. CircleCI wins on macOS pricing/availability, advanced caching, mature Orbs, and complex DAG ergonomics. GitHub Actions wins on tight GitHub integration, marketplace size, and being free for public repos. Many Indian teams use both — GitHub Actions for routine PR checks, CircleCI for release pipelines, iOS builds, or anything that requires its credit-efficient parallelism.

Question 2

How much does a CircleCI / DevOps engineer earn in India?

Accepted Answer

₹7-22 LPA in 2026 for mid-to-senior DevOps engineers with CircleCI as part of their stack. Companies hiring: Razorpay, CRED, Postman, Zoho, Spotify India, and fintech startups. Senior platform engineers with end-to-end pipeline + Kubernetes + cloud security expertise reach ₹30-45 LPA at top product companies.

Question 3

Do I need to learn Jenkins if I already know CircleCI?

Accepted Answer

Useful but not mandatory. Many Indian enterprises (banking, telco, regulated industries) still run Jenkins, and the underlying concepts (jobs, agents, pipelines) transfer well. If you're targeting product startups, focus on CircleCI + GitHub Actions; if you're targeting enterprise IT services or banks, Jenkins is still common.

Question 4

Can CircleCI run GPU jobs for ML workloads?

Accepted Answer

Yes — `gpu.nvidia.small` and `gpu.nvidia.medium` (Tesla T4 / A10G class) are available as of 2026, used heavily for ML training pipelines, image generation tests, and CUDA builds. They're expensive (10-20× standard Linux credit cost), so reserve them for jobs that genuinely need a GPU.

Question 5

What's the difference between CircleCI Cloud and CircleCI Server?

Accepted Answer

**CircleCI Cloud** is the SaaS offering at circleci.com — managed by CircleCI, fastest to start, credit-based pricing. **CircleCI Server** is the self-hosted enterprise install you run inside your own VPC — required for organisations with regulatory or data-residency constraints. Server has feature parity but trails Cloud by 1-2 quarters on new features (e.g., new Orb categories, GPU executors).

Question 6

What is CircleCI and what problems does it solve?

Accepted Answer

CircleCI is a hosted continuous integration and delivery platform that runs builds, tests, and deployments in response to code changes. It solves three problems that older tools (self-hosted Jenkins, Travis CI) handled poorly: (1) infrastructure overhead — no servers to maintain, (2) slow feedback — first-class parallelism and Docker layer caching speed up large test suites, (3) reusability — Orbs let teams share pipeline code like npm packages. You declare your pipeline in `.circleci/config.yml` at the root of your repo, CircleCI detects the file via a GitHub/Bitbucket/GitLab webhook, and runs the jobs on Linux, Windows, macOS, or self-hosted runners. Pricing is credit-based — you pay for compute minutes scaled by resource class.

Question 7

What is the structure of a basic .circleci/config.yml file?

Accepted Answer

Every config starts with a `version: 2.1` declaration (2.1 is required for Orbs, reusable executors, and commands). Below that, you define `jobs` (the units of work), optionally `executors` (the runtime environment), `commands` (reusable step sequences), and `workflows` (the orchestration graph that decides which jobs run when). A job consists of an executor and a sequence of `steps` — typically `checkout`, dependency restore, `run` commands, and cache/artifact storage.

Question 8

What is a job in CircleCI?

Accepted Answer

A job is the smallest billable unit of work in CircleCI — a discrete sequence of steps that runs inside a single executor. Each job gets a fresh environment (no state carries between jobs unless you use workspaces, caches, or artifacts). A job has an executor declaration (`docker:`, `machine:`, `macos:`, or `executor:`), an optional `resource_class` (small / medium / large / xlarge / 2xlarge), an optional `parallelism` value, and a list of `steps`. You'd typically have separate jobs for build, lint, unit tests, integration tests, and deploy so they can run in parallel and fail independently.

Question 9

What are the different executor types and when do you use each?

Accepted Answer

Four main executor types: (1) **docker** — the fastest and cheapest, runs your steps inside a container; ideal for stateless web/API builds. Limitation: can't run Docker-in-Docker without `setup_remote_docker`. (2) **machine** — a full Linux VM with Docker pre-installed; needed for Docker Compose, kernel access, or when you need privileged operations. Slower to spin up (~30s vs ~5s for docker). (3) **macos** — required for iOS/macOS builds, expensive (10× the credit cost). (4) **windows** — for .NET, Win32 builds. There's also `arm.medium` and GPU executors (`gpu.nvidia.small/medium`) for ML workloads.

Question 10

What are workflows in CircleCI?

Accepted Answer

A workflow is a directed acyclic graph (DAG) of jobs that defines execution order, dependencies, and conditions. Workflows let you fan-out (run lint, unit tests, build in parallel), fan-in (deploy only after all tests pass), gate progress with manual approvals, filter by branch or tag, and schedule recurring runs. Without workflows, jobs run sequentially in declaration order — almost never what you want for modern pipelines.

Question 11

What are Orbs in CircleCI?

Accepted Answer

Orbs are shareable, versioned packages of CircleCI config — think of them as npm modules for pipeline code. An Orb can export jobs, commands, and executors that you reference from your own config. Common uses: `aws-cli/setup`, `slack/notify`, `node/install`, `docker/build`. Three Orb categories: **Certified** (built by CircleCI, audited), **Partner** (built by vendors like AWS, GCP, HashiCorp), **Community** (open-source contributions, vary in quality). You import an Orb at the top of your config and reference its jobs/commands using `/` syntax.

Question 12

What is the checkout step and how does it work?

Accepted Answer

`checkout` is a built-in step that clones your source repository into the current working directory (`~/project` by default). It handles SSH key setup, shallow clone optimisations, and submodule init if configured. For large repos, you can pass `path:` to clone elsewhere, or skip it entirely and use `git clone` manually if you need a custom strategy (e.g., partial clone, sparse checkout). On self-hosted runners, you may need to authenticate the runner with a deploy key explicitly.

Question 13

How do you pass environment variables to a job?

Accepted Answer

Three levels: (1) **Job-level** via `environment:` block — visible inside that job only, good for non-secret config like `NODE_ENV=test`. (2) **Project-level** via the CircleCI UI Project Settings → Environment Variables — encrypted at rest, available to all jobs in that project. (3) **Context-level** — same as project-level but shared across multiple projects in an organisation; this is how you'd share AWS credentials or registry tokens between repos. Job-level env declared in YAML is plain-text and should never contain secrets.

Question 14

What is a workspace and how is it different from a cache?

Accepted Answer

**Workspaces** pass files BETWEEN jobs in the same workflow run — e.g., the `build` job produces `dist/` and the `deploy` job consumes it. Use `persist_to_workspace` and `attach_workspace`. **Caches** persist files BETWEEN runs of the same project — e.g., `node_modules/` survives across workflow runs to speed up `npm ci`. Use `save_cache` and `restore_cache` with a key that invalidates when dependencies change. Confusing them is a top interview gotcha: caches are best-effort and shared; workspaces are guaranteed and run-scoped.

Question 15

How do you store and retrieve build artifacts?

Accepted Answer

`store_artifacts` uploads files to CircleCI's artifact storage where they're browseable from the job page and accessible via API. Use for build outputs (binaries, web bundles), coverage reports, screenshots, or anything you want a human to inspect. Default retention is 30 days. Don't confuse with `store_test_results` which parses JUnit/XUnit XML to populate the Tests tab — those don't appear under artifacts.

CircleCI Interview Questions

What is CircleCI and what problems does it solve?

What is the structure of a basic .circleci/config.yml file?

What is a job in CircleCI?

What are the different executor types and when do you use each?

What are workflows in CircleCI?

What are Orbs in CircleCI?

What is the checkout step and how does it work?

How do you pass environment variables to a job?

What is a workspace and how is it different from a cache?

How do you store and retrieve build artifacts?

How do you trigger a workflow only on specific branches or tags?

What is a manual approval job and when would you use one?

How do you implement effective caching to speed up CircleCI builds?

What is parallelism in CircleCI and how does it differ from running multiple jobs?

What's the difference between a context and a project environment variable?

How do you build and publish your own Orb?

How do you implement matrix builds in CircleCI?

What are reusable commands and parameters?

How do you use OIDC to authenticate to AWS from CircleCI without static credentials?

How does CircleCI compare to GitHub Actions, Jenkins, and GitLab CI?

How do you handle approval gates and progressive deployments?

What is the setup_remote_docker step and when do you need it?

How do you handle a monorepo with CircleCI?

How do you handle Docker image pulls hitting Docker Hub rate limits?

How do you optimize CircleCI credit consumption?

What is dynamic config and how do you use it for advanced pipelines?

How would you architect CI for a fintech app with strict compliance and audit requirements?

How do self-hosted runners work and when should you use them?

How do you debug a flaky CircleCI build that fails intermittently?

How would you migrate a large Jenkins setup to CircleCI?

Companies Hiring CircleCI

Salary Insights

Frequently Asked Questions

Is CircleCI better than GitHub Actions in 2026?

How much does a CircleCI / DevOps engineer earn in India?

Do I need to learn Jenkins if I already know CircleCI?

Can CircleCI run GPU jobs for ML workloads?

What's the difference between CircleCI Cloud and CircleCI Server?

Introduction