Loading...
Pipeline design, artefact promotion, deployment strategies, and safe rollback mechanics.
5 questions in DevOps & Cloud.
Build one immutable artefact, promote that same artefact through environments behind ordered quality gates, and deploy so traffic can be shifted back instantly. Rollback only stays possible if schema changes are backward-compatible expand-contract steps decoupled from the code deploy.
Evaluate the candidate's expertise in profiling build systems, configuring distributed caching, and optimising CI/CD pipelines for large-scale mobile projects.
An analysis of the challenges in designing a cost-effective, scalable GitHub Actions runner environment using spot instances, focusing on state management, instance termination handling, and performance tuning.
Treat any payload the fleet loads as a release, because it changes behaviour in production exactly as a binary does. It needs schema and replay validation, a canary ring with its own health comparison, and a rollback that survives the change breaking whatever would apply the rollback.
Replace the stored key with OIDC federation so each job exchanges a short-lived signed token for temporary credentials, then make the trust policy specific to a repository, branch or environment. Also narrow the pipeline's own token, pin third-party steps to commit SHAs, and attest what you built.