CI/CD Platforms interview questions

Building scalable runners, caching, and pipeline compliance.

3 questions in Platform & DevEx.

Platform Engineering and Developer ExperienceA 18-minute read on how the topic fits together, before the questions.Platform engineering fundamentals55 short answers on one page, for revising rather than studying.

medium1

mediumDesignConcept

You need every service's pipeline to run a security scan, a license check, and require signed artifacts before deploy. How do you enforce that across a hundred repositories without ending up with a hundred slightly different pipeline files?

Ship the gates as a shared, versioned pipeline template that repositories include rather than copy, so an update to the check propagates everywhere at once and drift is visible instead of silent. Use this ci cd answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects compliance to the point an interviewer is testing.

4 minmid, senior, staff

hard2

hardDesign

Design an autoscaling scheme for a self-hosted CI runner fleet. What are you actually trading off, and how do you decide the numbers?

Runner autoscaling trades idle compute cost against queue time, and the two levers that decide the trade are a warm pool sized to your usual concurrency and a scale-down delay long enough to absorb the next job without a fresh cold start.

4 minsenior, staff

hardDesignScenario

Your monorepo's CI runs the full test suite on every pull request, and it now takes forty minutes regardless of whether someone touched one file or a hundred. How would you fix that?

Build a dependency graph of the repository's build targets, diff the changed files against it to compute the affected subset, and run only that subset; the graph's correctness, not the diff itself, is what determines whether the speedup is trustworthy.

4 minsenior, staff