Harness Interview Prep: 4-Week Plan and 40 Q&As (2027)

A four-week Harness interview study plan with labs and 40 practice questions on delegates, CD, CI, templates, OPA and verification.

Sep 25, 2025 - 14:54
Nov 9, 2026 - 16:27
 0  69
Harness Interview Prep: 4-Week Plan and 40 Q&As (2027)

A good Harness interview preparation plan takes about four weeks: one week on platform basics (delegates, connectors, secrets, projects), one on CD pipelines and deployment strategies, one on CI, templates and expressions, and one on governance, verification and mock answers. This guide gives that plan day by day, plus 40 practice questions mapped to each week.

Most Harness question banks give you a long list and leave the order to you. This page is about sequencing: what to study first, what to build in a free account, and how to check you are ready. If you want depth on one area after the plan, use our advanced Harness interview questions (the main Harness page on this site) or the scenario-based Harness questions. All product details below were checked against the Harness Developer Hub in November 2026.

Key takeaways

  • Study in the order Harness itself is built: account structure and delegate first, then CD, then CI and reuse features, then governance.
  • Build one real pipeline in a free account each week. Interviewers can tell when an answer comes from reading only.
  • The delegate connects out to Harness Manager over HTTPS/WSS. Expect at least one question on why that matters for firewalls.
  • Harness certifications come in three levels: Developer (free), Administrator and Architect (paid). Only CD & GitOps and CI have all three.
  • Spend the last week on spoken answers. A correct answer that takes four minutes to reach the point still scores badly.

Who this plan is for

The plan assumes you know basic CI/CD, Git and either Kubernetes or a cloud platform. If you have never written a pipeline, add a week of Jenkins or GitHub Actions basics first; our CI/CD pipeline examples post is a useful warm-up. Freshers can follow weeks 1 and 2 closely and skim week 4. Engineers with 2 to 5 years should finish all four weeks. Senior candidates can compress weeks 1 and 2 into a few days and spend the extra time on design questions.

The four-week Harness study plan

WeekTopicsHands-on goalPractice questions
1Account, organization and project hierarchy; delegates; connectors; secrets; RBAC basicsInstall a Kubernetes delegate, add a Git and a Docker registry connector, store one secretQ1 to Q10
2Pipelines, stages, steps; services, environments, infrastructure definitions; rolling, canary and blue-greenDeploy a sample app to a dev cluster with a rolling deployment, then a canaryQ11 to Q20
3CI stages and build infrastructure; expressions; runtime inputs and input sets; templates; triggers; looping strategiesBuild an image in CI, pass its tag to CD with an expression, start the pipeline from a Git webhook triggerQ21 to Q30
4Failure strategies; approvals; OPA policies; Continuous Verification; deployment freezes; mock interviewsAdd a manual approval, a failure strategy with rollback, and one policy that blocks a pipeline saveQ31 to Q40 plus scenarios

Daily rhythm that works

Plan about 90 minutes on weekdays: 30 minutes reading the Developer Hub page for the topic, 45 minutes building it, and 15 minutes saying two practice answers out loud. Use the weekend for a longer build and for writing down what broke. That log of real errors becomes your best interview material, because "tell me about a problem you hit" is one of the most common Harness questions.

What to skip

Do not try to learn every module. Harness has modules for code repository, IDP, IaC management, database DevOps, feature management, resilience testing, security testing and cost management. Read the one-paragraph overview of each so you can say what it does, then go deep only on the modules named in the job description. For most DevOps roles that means CD and CI.

Week 1 questions: platform basics (freshers)

1. What is Harness?

Harness is a software delivery platform with modules for continuous integration, continuous delivery and GitOps, plus related areas such as security testing, feature management, resilience testing and cloud cost management. Pipelines are defined in a visual editor or YAML and run through a delegate installed in your own environment.

2. What is the Harness delegate?

The delegate is a service you run in your network or VPC. It connects to Harness Manager and performs tasks such as fetching artifacts, deploying to clusters and running verification queries. Harness Manager decides what to do; the delegate does it inside your environment.

3. Why does the delegate only make outbound connections?

Harness documents that the delegate connects to Harness Manager over an outbound HTTPS/WSS connection. You do not open inbound ports to your network, which keeps the firewall conversation simple: allow egress to Harness and to the providers your connectors use.

4. What delegate image types exist?

Harness publishes a standard image and a minimal image (tags end in .minimal), and a FIPS variant is also documented. The minimal image has no client tools, so Harness recommends building a custom image if you need tools such as specific Helm or kubectl versions.

5. What is a connector?

A connector stores the details Harness needs to reach a third-party system: a Git provider, an artifact registry, a cloud account or a Kubernetes cluster. Connectors reference secrets for credentials and can be pinned to specific delegates.

6. How are secrets handled?

Secrets live in a secret manager (Harness's built-in one or an external manager such as HashiCorp Vault or a cloud key service). Pipelines refer to them by ID with an expression such as <+secrets.getValue("SECRET_ID")> and never store the raw value in YAML.

7. Explain the account, organization and project hierarchy.

An account contains organizations, and organizations contain projects. Resources such as connectors, secrets and templates can be created at any of the three levels; a resource at a higher level can be shared by everything below it. Most teams keep shared connectors at account or organization level and pipelines at project level.

8. What are delegate selectors and tags?

Each delegate gets a tag matching its name automatically, and you can add more. Steps and connectors use delegate selectors to choose delegates by tag, for example to force production deployments through a delegate inside the production network.

9. How does RBAC work in Harness?

Access is granted through role bindings that combine a principal (user, user group or service account), a role (a set of permissions) and a resource group (the resources the role applies to). Least privilege comes from narrow resource groups, not only from narrow roles.

10. Which Harness certifications exist?

Harness University lists Developer certifications (free) for many modules, Administrator certifications (paid) for CD & GitOps, CI, Resilience Testing, STO and Cloud & AI Cost Management, and Architect certifications (paid) for CD & GitOps and CI. Our Harness certification questions post covers the exam domains.

Week 2 questions: CD pipelines (freshers to 2 years)

11. What is the structure of a Harness pipeline?

A pipeline contains stages, and each stage contains steps. A CD stage deploys one service to one environment and infrastructure; a CI stage builds and tests code. Stages can run in sequence or in parallel.

12. What is a service in Harness CD?

A service describes what you deploy: manifests (for example Kubernetes YAML or a Helm chart), artifacts and service variables. The same service can be deployed to many environments.

13. What are environments and infrastructure definitions?

An environment is a logical target such as dev, QA or prod, marked as production or pre-production. An infrastructure definition inside it says exactly where to deploy, for example which cluster connector and namespace.

14. Compare rolling, canary and blue-green deployments in Harness.

A rolling deployment replaces instances gradually. A canary deploys a small portion of the new version first, checks it, then continues. Blue-green runs the new version alongside the old one and switches traffic once it passes checks. Choose based on how fast you need rollback and how much spare capacity you have.

15. How does rollback work?

Each CD stage has rollback steps that run when the failure strategy calls for rollback. For Kubernetes deployments Harness rolls back to the previous release it recorded. Interviewers want to hear that rollback is configured per stage and triggered by failure strategies, not by magic.

16. What is a manifest override?

Overrides let you change service values per environment, such as a different values file or replica count for prod, without copying the service. Explain the order: environment-level overrides apply on top of service defaults.

17. How do you add a manual approval?

Add a Harness Approval step (or a Jira or ServiceNow approval step) before the production stage, with the user groups that can approve and a timeout. Mention what happens on timeout, because that is the follow-up question.

18. What is the GitOps option in Harness CD?

Harness CD & GitOps includes a GitOps capability based on Argo CD, where a GitOps agent in the cluster syncs applications from Git. If the interviewer goes deeper into GitOps, our GitOps and Argo CD interview questions cover the reconcile model.

19. How do you see what a pipeline did?

The execution view shows each stage and step with logs, inputs and outputs. For deployments, the service and environment dashboards show which artifact version is running where.

20. Which expressions identify the current deployment target?

<+service.name> and <+env.name> return the service and environment names. They are useful in notifications and in naming resources so the same template works everywhere.

Week 3 questions: CI, expressions and reuse (2 to 5 years)

21. How does a Harness CI stage run builds?

A CI stage runs steps on build infrastructure you choose, such as Harness Cloud hosted machines, a Kubernetes cluster or a VM. Steps run in containers, so each step names an image and commands.

22. How do you pass an artifact tag from CI to CD?

Use an expression that reads the output of the build step or the pipeline sequence, then feed it to the service's artifact tag as a runtime input. Many teams tag images with <+pipeline.sequenceId> so every run has a unique tag.

23. What is the Harness expression syntax?

Expressions use <+...>, for example <+pipeline.name>, <+artifact.tag> or <+trigger.payload.repository.owner.name> for webhook data. They resolve at runtime, so a value that is not available yet resolves to null.

24. What are runtime inputs and input sets?

A runtime input (<+input>) leaves a field to be filled when the pipeline runs. An input set saves a group of those values, for example "staging inputs", so triggers and people can run the same pipeline with known values.

25. Why use templates?

Templates let you reuse a step, stage or pipeline across projects. A platform team can maintain one approved deployment stage and let product teams consume it. Templates are versioned, so you can pin production pipelines to a tested version.

26. What triggers can start a pipeline?

Common triggers are webhooks from Git providers (push, pull request, tag), artifact triggers when a new image appears, manifest triggers and cron schedules. Each trigger can use an input set.

27. What looping strategies are available?

matrix, repeat and parallelism. Matrix runs a step or stage for each combination of values, repeat runs it a set number of times or over a list, and parallelism splits work across copies, often to speed up tests.

28. What is Git Experience?

Git Experience stores pipelines and other entities as YAML in your Git repository, so changes go through pull requests and branches. It is the answer when an interviewer asks how you review pipeline changes.

29. How do you cache dependencies in CI?

Use the cache intelligence feature or explicit save and restore cache steps keyed on a lock file checksum. Then explain how you measured the change in build time, since a number from your own lab is more convincing than a claim.

30. How do you run only affected tests?

Harness CI has Test Intelligence, which selects tests related to the changed code for supported languages. Say that you would check language support in the docs before promising it for a stack.

Week 4 questions: governance and verification (senior)

31. What are failure strategies?

Failure strategies define what happens when a step or stage fails: retry, mark as success, ignore, manual intervention, abort or rollback. They can be set per error type, such as connectivity or verification failures, which is how you avoid retrying a genuine bug.

32. How does Harness use OPA?

Harness Policy as Code uses Open Policy Agent with Rego policies grouped into policy sets. Policy sets run on events such as saving or running a pipeline and can warn or block. A typical policy forbids production stages without an approval step.

33. What is Continuous Verification?

Continuous Verification queries your monitoring and logging tools during a deployment and compares the new version's behavior with a baseline. If it finds regressions, the verify step fails and the failure strategy can roll back.

34. What is a deployment freeze?

A freeze window blocks deployments for chosen services or environments during a period, such as a holiday sale. Mention who can override it and how overrides are audited.

35. How do you scale delegates?

Run several delegate replicas, use tags to split workloads, and size them for concurrent tasks. Watch delegate health in the Harness UI and plan upgrades so a version change does not stop running pipelines.

36. How would you design Harness for 50 teams?

Use one organization per business unit, one project per team, account-level templates owned by a platform team, policy sets for guardrails, and resource groups that limit each team to its own project. Store pipelines in Git with Git Experience.

37. How do you keep secrets out of logs?

Reference secrets only through expressions, never echo them, and keep connector credentials in a secret manager. Harness masks secret values it knows about in logs, but you should still treat log output as sensitive.

38. How do you audit who changed a pipeline?

Use the audit trail in Harness for platform events and the Git history when pipelines are stored with Git Experience. Together they show who changed what and who approved the pull request.

39. How do you migrate a Jenkins pipeline to Harness?

Start with one service: map Jenkins stages to Harness CI and CD stages, move credentials to Harness secrets, replace shell deployment scripts with native deployment steps, and run both systems in parallel until results match. Our real-time Harness interview questions go further into migration problems.

40. What do you measure after adopting Harness?

Deployment frequency, lead time, change failure rate and time to restore service (the DORA metrics), plus pipeline duration and the share of deployments that needed manual intervention. Measure before and after, otherwise you cannot show the change.

Scenario practice for the final weekend

Answer each of these out loud in under two minutes. Start with your first check, then the fix, then how you would stop it happening again.

  • A deployment to production waits forever at "waiting for delegate". You check which delegate selectors the step and connector use, whether a delegate with that tag is connected and healthy, and whether egress to Harness is allowed.
  • An expression returns null in a CD stage. You check whether the value is produced later in the pipeline or in a different stage scope, and fix the reference path.
  • A canary passes but users report errors an hour later. You review which metrics Continuous Verification queried and add the error-rate metric that would have caught it.
  • A team bypasses the approval step by copying the pipeline. You move the stage into a versioned template and add an OPA policy that blocks production stages without approval.

Readiness checklist

CheckReady when you can
ArchitectureDraw manager, delegate, connectors and target cluster on a whiteboard in two minutes
CDExplain service, environment and infrastructure definition without notes
CIDescribe your build infrastructure choice and why
ReuseExplain templates, input sets and template versioning with an example
GovernanceDescribe one OPA policy and one RBAC design you built
StoryTell one real failure from your lab log, with the fix

If you want guided practice with CI/CD, Kubernetes and GitOps before a Harness interview, our DevOps training runs in a classroom in Kharadi, Pune and live online across India. For broader preparation, the DevOps interview questions hub links every topic.

FAQ

How long does it take to prepare for a Harness interview?

About four weeks at 90 minutes a day if you already know CI/CD and Kubernetes basics. Add a week if you have never built a pipeline.

Can I practise Harness for free?

Harness offers free plans for some modules, and its Developer certifications are free and based on those plans. Check the current plan limits on the Harness site before you start.

Which Harness module should I learn first?

Continuous Delivery, because most DevOps job descriptions that mention Harness use it for deployments. Learn CI next.

Do I need a Harness certification to get a job?

No. A certification shows you studied the product, but interviewers still test hands-on knowledge. The free Developer certification is a reasonable target at the end of week 2.

What is the most common Harness interview question?

Explaining the delegate: what it is, where it runs and why it only makes outbound connections.

How is this guide different from other Harness question lists?

It is a sequenced study plan with practice questions per week. For larger question banks by depth, use the advanced and scenario-based Harness posts linked above.

References

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Mridul I am a passionate technology enthusiast with a strong focus on DevOps, Cloud Computing, and Cybersecurity. Through my blogs at DevOps Training Institute, I aim to simplify complex concepts and share practical insights for learners and professionals. My goal is to empower readers with knowledge, hands-on tips, and industry best practices to stay ahead in the ever-evolving world of DevOps.