Engineering and IT · Interview questions

DevOps Engineer interview questions

These questions check whether a candidate can make deployments routine, recover from failure and keep infrastructure reproducible. Use the same questions in the same order for every candidate.

The questions

Ask every candidate the same questions in the same order, and score each answer against the notes before you talk it over with the panel.

  1. Tell me about a deployment pipeline you built or improved. What did it look like before and after?

    What it tests
    Automated deployment outcome.
    A strong answer
    They describe a clear before state, such as manual copying to servers, and the pipeline they built with tests, staging and approvals. They mention how deploy time or failure rate changed.
    Watch for
    A pipeline only they understand, with no documentation.
  2. It is 10 at night. The site is returning 502 errors for all users. A deploy went out an hour ago. Talk me through your first fifteen minutes.

    What it tests
    Incident response, uptime outcome, scenario.
    A strong answer
    They confirm the problem, post a status update and roll back the recent deploy before investigating further. They check load balancer and application logs, and write up the cause afterwards without blame.
    Watch for
    Spending an hour debugging while users are still down instead of rolling back.
  3. When did you last restore a database from backup? Walk me through it.

    What it tests
    Tested backups outcome.
    A strong answer
    They give a recent, real example with the steps, the time taken and what surprised them. They explain that a backup is only trusted once it has been restored.
    Watch for
    Assuming backups work because the backup job reports success.
  4. Here is a Terraform file that creates a database and a server. Review it and tell me what concerns you.

    What it tests
    Infrastructure as code, practical review.
    A strong answer
    They spot issues such as a password written in the file, the database open to the internet or no backup settings. They suggest a secrets manager, private networking and remote state with locking.
    Watch for
    Reading it line by line without noticing the security risks.
  5. How do you decide whether an alert should page someone at night?

    What it tests
    Useful alerting, reliability.
    A strong answer
    Only alerts that mean customers are affected now, or soon will be, should page. Everything else goes to a channel for the next working day, and every paging alert has a runbook.
    Watch for
    Paging on every CPU spike so people start ignoring alerts.
  6. Tell me about a time you found a server or setting that someone had changed by hand. What did you do?

    What it tests
    Rebuildable environments.
    A strong answer
    They captured the change in code, applied it through the normal pipeline and explained to the team why manual changes cause drift. They may have added a check to detect drift.
    Watch for
    Leaving the manual change in place because it works.
  7. Developers say the pipeline takes 40 minutes and they are waiting all day. How would you approach it?

    What it tests
    Supporting developers.
    A strong answer
    They measure which steps take longest, then use caching, parallel jobs and running only affected tests. They agree a target time with the developers and check it after the change.
    Watch for
    Removing tests to make the pipeline faster.
  8. Our cloud bill has doubled in six months but traffic has not. What would you look at?

    What it tests
    Cost and resource management.
    A strong answer
    They break the bill down by service and tag, look for idle servers, oversized databases, old snapshots and data transfer costs. They set a budget alert and a monthly review.
    Watch for
    Cutting resources without checking what depends on them.

New to structured interviews? Read how to run structured interviews and how to build an interview scorecard.

Start from the job description

These questions follow the first-year outcomes in the matching template.

DevOps Engineer job description template

Similar roles

Your next hire, start to finish, in one place.

Free workspace. No card. Full scoring free for 7 days.