All 40 questions

  1. How would you diagnose a slow CI/CD pipeline and reduce its runtime?

    Asked in 4 of 296 interviews · last asked Nov 18 · Scenario · Senior

    Show answer

    I would measure queue time and each stage, then find which steps delay pipeline completion most. I would compare slow runs with earlier fast runs and check recent changes. Based on the bottleneck, I would cache dependencies, split tests across parallel jobs, or fix runner limits, then compare repeated runs with similar workloads.

    • Check logs and timings for checkout, dependency downloads, builds, tests, and deployment health checks.
    • Separate runner queue delays from slow job execution; each needs a different fix.
    • Parallelize independent work and use cache keys that prevent stale dependencies.
    • Compare typical and slow-run times before and after changes, without removing required tests or release checks.

    What the interviewer checks: The interviewer wants to see whether you use measurements to find bottlenecks and prove improvements without weakening safety.

    Other ways it was asked
    • “If a pipeline used to take 5 minutes but now takes 25 minutes, how would you diagnose the issue?”
    • “How would you troubleshoot a pipeline that usually takes 20 minutes but suddenly started taking six hours?”
    • “How would you identify bottlenecks in a slow CI/CD pipeline and reduce its deployment time?”
  2. How would you investigate code or tests that pass locally but fail in CI?

    Asked in 4 of 296 interviews · last asked Oct 13 · Scenario · Mid-level

    Show answer

    I check the first failing CI step, its error, and any test reports or screenshots. I compare the tested commit, PR diff, dependencies, and test command with my local run. I reproduce the CI setup locally and change one factor at a time. Repeated runs help separate consistent failures from flaky tests.

    • Check the workflow event and tested commit; PR checks may test a merge commit.
    • Compare runtime versions, environment variables, permissions, and secrets; fork PRs normally cannot access repository secrets.
    • Check timing, parallel execution, test order, shared staging data, and cleanup for intermittent failures.
    • Compare runner resources, operating system, timezone, and network access, even when both runs target staging.

    What the interviewer checks: The interviewer checks whether you use evidence to separate code changes, workflow problems, environment differences, and flaky tests.

    Other ways it was asked
    • “A test passes locally but fails in CI or the cloud while running against staging in both environments. What could cause this?”
    • “If your automation is stable locally but fails intermittently in CI/CD, how would you systematically investigate whether the problem is code, script, or environment related?”
    • “A CI check fails in a PR but passes on main. Which GitHub Actions logs and signals do you look at first to decide whether it's a flaky test, missing secrets, or a branch-specific change?”
  3. How do you handle challenges that arise during the deployment process?

    Asked in 2 of 296 interviews · last asked Oct 13 · Scenario

    Other ways it was asked
    • “How will you resolve a problem if one arises during deployment?”
  4. How would you decide which CI/CD steps to adjust first, and how would you measure improvements in release repeatability?

    Asked once · last asked Sep 21 · Behavioral · Senior

    Other ways it was asked
    • “How did you decide which CI/CD steps to adjust first, and how did you measure improvements in release repeatability?”
    • “How did you decide which CI/CD steps to adjust first, and how did you validate each change?”
  5. A CI/CD pipeline succeeds in development but fails in production. How would you investigate the cause?

    Asked once · last asked Oct 7 · Scenario · Mid-level

    Other ways it was asked
    • “A CI/CD pipeline succeeds in development but the application fails in production. How would you investigate the cause?”
  6. How would you reduce deployment times by 30% across eight county agencies over 12 months?

    Asked once · last asked Feb 5 · Behavioral · Mid-level

    Other ways it was asked
    • “How did you reduce deployment times by 30% across eight county agencies over 12 months?”
  7. Suppose you deploy a new version to production using CI/CD and users report a 500 error. What would you do?

    Asked once · last asked Mar 3 · Scenario · Mid-level

  8. Suppose a pipeline suddenly fails at the build stage. What would you do?

    Asked once · last asked Mar 3 · Scenario · Mid-level

  9. If a junior QA says their Robot Framework tests pass locally but fail in Jenkins, how would you guide them to debug the issue?

    Asked once · last asked Apr 22 · Scenario · Senior

  10. When tests pass locally but fail in Jenkins, how would you investigate the logs, and what common issues would you look for?

    Asked once · last asked Apr 22 · Scenario · Mid-level

  11. If the pipeline is down while there’s also a production issue, how do you prioritize and handle those incidents?

    Asked once · last asked May 21 · Scenario · Senior

  12. How would you investigate production issues using Elasticsearch, Kibana, and GitLab CI/CD?

    Asked once · last asked Jun 19 · Scenario · Senior

  13. A deployment succeeds in CI/CD, but some components fail in OpenShift. What would you check?

    Asked once · last asked Jul 16 · Scenario · Senior

  14. How would you fix a production error while keeping the system available?

    Asked once · last asked Jul 28 · Scenario · Senior

  15. How would you measure contract-change validation's impact on rollout speed and incident rates?

    Asked once · last asked Jul 31 · Concept · Mid-level

    Other ways it was asked
    • “How can contract-change validation affect rollout speed and incident rates during a microservices migration?”
    • “How would you measure the impact of contract-change validation on rollout speed and incidents?”
  16. What would you do if container checks failed during a software rollout?

    Asked once · last asked Jul 31 · Scenario · Mid-level

  17. How would you trace a deployment from a developer's commit or merge through to production completion?

    Asked once · last asked Aug 10 · Scenario · Senior

  18. If a test fails only in CI but passes locally, what are the first two differences you check between CI and your machine?

    Asked once · last asked Aug 14 · Scenario · Mid-level

  19. What specific metrics or alerts would you add to monitor a staged rollout?

    Asked once · last asked Aug 21 · Scenario · Senior

  20. How would you confirm that it is safe to recover after a staged rollout problem?

    Asked once · last asked Aug 21 · Scenario · Senior

  21. When a production issue arises in a TriZetto Facets project, how do you identify the cause and move the fix from development to production?

    Asked once · last asked Aug 26 · Scenario · Mid-level

  22. What could be the reason why a Selenium test passes on your laptop, but it fails on Jenkins?

    Asked once · last asked Sep 1 · Scenario · Mid-level

  23. What is the process for fixing a CPU-heavy code change and deploying that fix to production?

    Asked once · last asked Sep 4 · Scenario · Senior

  24. How do you determine whether the number of GitLab CI runners is sufficient for a test suite?

    Asked once · last asked Sep 8 · Scenario · Mid-level

  25. How would you troubleshoot issues that arise while deploying a web application?

    Asked once · last asked Sep 20 · Scenario · Mid-level

  26. What is one specific change you made to a CI/CD process that helped make releases faster or safer?

    Asked once · last asked Sep 21 · Behavioral · Mid-level

  27. How do you monitor for regressions after a deployment?

    Asked once · last asked Sep 21 · Scenario · Mid-level

  28. Describe an impactful failure in a commit-to-Argo CD deployment path, how you debugged it, and what change fixed it.

    Asked once · last asked Oct 1 · Behavioral · Senior

  29. When a build or release problem is blocking people and information is incomplete, how do you assess the stakes, prioritize work, and decide how quickly to act?

    Asked once · last asked Oct 7 · Scenario · Senior

  30. How would you break down and prioritize work when a build is blocked and you are responsible for resolving it?

    Asked once · last asked Oct 7 · Scenario · Mid-level

  31. How do you reproduce the CI environment as closely as possible locally or in a disposable environment to confirm the failure and validate the fix?

    Asked once · last asked Oct 13 · Scenario · Mid-level

  32. When a workflow passes in pull_request, but fails after merge on push to main, what differences in triggers, permissions, and event context do you check first in the workflow YAML?

    Asked once · last asked Oct 13 · Scenario · Senior

  33. How do you monitor released features and track rollouts or feature flags?

    Asked once · last asked Oct 19 · Scenario · Mid-level

  34. What technical decisions would you make to improve the reliability of a GitHub Actions pipeline?

    Asked once · last asked Nov 1 · Behavioral · Mid-level

    Other ways it was asked
    • “What technical decision in your GitHub Actions pipeline most improved reliability?”
  35. A GitHub Actions PR CI run fails; what is your step-by-step approach to determine whether it is a test failure, a lint or formatting issue, or an environment or configuration problem?

    Asked once · last asked Nov 6 · Scenario · Senior

  36. In Git, how do you use git bisect to find the first bad commit causing a CI regression, and what prerequisites do you need?

    Asked once · last asked Nov 6 · Tooling · Senior

  37. A GitHub Actions job intermittently fails with npm or network errors and registry timeouts. What changes would you make to improve reliability without hiding real dependency issues?

    Asked once · last asked Nov 6 · Scenario · Senior

  38. How would you design an agent to interpret pipeline failure verdicts using TypeScript, Node.js, and Playwright?

    Asked once · last asked Nov 17 · Design · Senior

  39. How would you evaluate whether an agent that classifies pipeline failures is accurate, and how should it handle a real bug mislabeled as flaky?

    Asked once · last asked Nov 17 · Scenario · Senior

  40. What cloud costs should you consider when running a Jenkins deployment?

    Asked once · last asked Oct 14 · Scenario · Mid-level

More CI/CD interview questions

How this list is made

Every question here was asked by a real interviewer in a real job interview that a candidate ran MeetAssist in. After the call, the interviewer's questions are pulled from the transcript. Practice sessions, tests, exams and anything that was not a job interview are dropped.

Questions are rewritten so they make sense on their own: names of people, employers and clients are removed, and speech-to-text mistakes are fixed. Small talk, logistics and questions about one candidate's own résumé are left out. Rephrasings of the same question are merged, and the count is the number of different interviews it came up in.

The interviews come from candidates who use MeetAssist, so they lean towards software, data and AI roles: the shares describe these interviews, not every CI/CD interview. Answers to the most asked questions are written and checked by an editor; a "common mistake" is shown only when reviews of real answers in these interviews show it, with the count.

296 interviews, 192 candidates, Nov 2025 to Nov 2026. Updated every month with new interviews.