Skip to content

Ravi Sir's Cards › DevOps

Chapter 17: Interview Questions and Job Readiness: Cards

मराठी cards · Open the chapter

Revision cards

Interview: DevOps culture and process. Culture questions open most interviews and set the tone. — Revision card 1 of 14: Interview: DevOps culture and process · Download PNG · Open card page

Lesson: 17.1 DevOps culture and process

Interview: Git and GitHub. Git questions check daily hands-on skill. — Revision card 2 of 14: Interview: Git and GitHub · Download PNG · Open card page

Lesson: 17.2 Git and GitHub

Interview: Linux ops refresh. Linux questions test whether you can triage a real server. — Revision card 3 of 14: Interview: Linux ops refresh · Download PNG · Open card page

Lesson: 17.3 Linux ops refresh

Interview: Bash and automation. Scripting questions test automation habits. — Revision card 4 of 14: Interview: Bash and automation · Download PNG · Open card page

Lesson: 17.4 Bash and automation

Interview: Docker. Docker questions are in almost every DevOps interview. — Revision card 5 of 14: Interview: Docker · Download PNG · Open card page

Lesson: 17.5 Docker

Interview: CI/CD, Actions and Jenkins. CI/CD is the heart of most DevOps roles. — Revision card 6 of 14: Interview: CI/CD, Actions and Jenkins · Download PNG · Open card page

Lesson: 17.6 CI/CD, Actions, Jenkins

Interview: Ansible and Terraform. Infrastructure as Code (IaC) is expected in most DevOps jobs. — Revision card 7 of 14: Interview: Ansible and Terraform · Download PNG · Open card page

Lesson: 17.7 Ansible and Terraform

Interview: monitoring, logging, Kubernetes. These show you can run systems, not just build them. — Revision card 8 of 14: Interview: monitoring, logging, Kubernetes · Download PNG · Open card page

Lesson: 17.8 Monitoring, logging, Kubernetes

Scenario questions. Scenario questions test thinking under pressure. — Revision card 9 of 14: Scenario questions · Download PNG · Open card page

Lesson: 17.9 Scenario questions

How to practise answers (not memorise). Memorised answers break on the first follow-up. — Revision card 10 of 14: How to practise answers (not memorise) · Download PNG · Open card page

Lesson: 17.10 How to practise answers (not memorise)

Revision card 11 of 14: Portfolio checklist: job readiness · Download PNG · Open card page

Lesson: 17.11 Portfolio checklist (job readiness)

Phrases that help and hurt. Wording changes how skills are judged. — Revision card 12 of 14: Phrases that help and hurt · Download PNG · Open card page

Lesson: 17.12 Phrases that help (and hurt)

Pointing to deeper courses. Interviews reveal gaps; a plan to fill them shows growth. — Revision card 13 of 14: Pointing to deeper courses · Download PNG · Open card page

Lesson: 17.13 Pointing to deeper courses

Lab: practice mock interview. Real interviews feel easier after a mock. — Revision card 14 of 14: Lab: practice mock interview · Download PNG · Open card page

Lesson: 17.14 Lab / Practice — mock interview

Interview cards

What is a blameless postmortem? A review after an incident that finds causes and fixes in systems and process, without blaming people. — Interview card 1 of 14: What is a blameless postmortem? · Download PNG · Open card page

Lesson: 17.1 DevOps culture and process

How do you undo a commit that's already pushed? Use git revert: it adds a new commit that undoes the change, without rewriting shared history. — Interview card 2 of 14: How do you undo a commit that's already pushed? · Download PNG · Open card page

Lesson: 17.2 Git and GitHub

A service won't start. Walk me through it. systemctl status for the error, journalctl -u for details, check config, ports and permissions, fix, restart, verify. — Interview card 3 of 14: A service won't start. Walk me through it. · Download PNG · Open card page

Lesson: 17.3 Linux ops refresh

How do you make a Bash script safe for production? set -euo pipefail, quote variables, validate arguments, secrets from env, a dry-run option, and shellcheck in CI. — Interview card 4 of 14: How do you make a Bash script safe for production? · Download PNG · Open card page

Lesson: 17.4 Bash and automation

How do you make a Docker image smaller? Use a slim base, multi-stage builds (build in one stage, copy only output), a .dockerignore, and combine/clean layers. — Interview card 5 of 14: How do you make a Docker image smaller? · Download PNG · Open card page

Lesson: 17.5 Docker

Describe a CI/CD pipeline you've built. PR: lint, test. Main: build image (SHA tag), scan, push, deploy to staging, approval for prod, health check, rollback plan. — Interview card 6 of 14: Describe a CI/CD pipeline you've built. · Download PNG · Open card page

Lesson: 17.6 CI/CD, Actions, Jenkins

Terraform vs Ansible? Terraform creates and changes infrastructure (VMs, networks) with state. Ansible configures what's on servers. Often: Terraform builds, Ansible configures. — Interview card 7 of 14: Terraform vs Ansible? · Download PNG · Open card page

Lesson: 17.7 Ansible and Terraform

A Pod is in CrashLoopBackOff. What do you do? kubectl logs --previous for the crash error, describe for events (OOMKilled, probe failures), check config/secrets, fix and redeploy. — Interview card 8 of 14: A Pod is in CrashLoopBackOff. What do you do? · Download PNG · Open card page

Lesson: 17.8 Monitoring, logging, Kubernetes

Deploy just went out and errors spiked. What do you do? Confirm on dashboards, roll back first to stop impact, then investigate logs and the diff, fix forward, and write a postmortem. — Interview card 9 of 14: Deploy just went out and errors spiked. What do you do? · Download PNG · Open card page

Lesson: 17.9 Scenario questions

How do you answer a question you don't fully know? Say what you do know, how you'd find out (docs, test in a lab), and don't invent details. — Interview card 10 of 14: How do you answer a question you don't fully know? · Download PNG · Open card page

Lesson: 17.10 How to practise answers (not memorise)

What should a fresher's DevOps portfolio have? One strong end-to-end project with README, working CI, deploy evidence, and a short write-up; CV links to it. — Interview card 11 of 14: What should a fresher's DevOps portfolio have? · Download PNG · Open card page

Lesson: 17.11 Portfolio checklist (job readiness)

Tell me about a failure. Pick a real one: what broke, your part, how you fixed it, what you changed to prevent it. — Interview card 12 of 14: Tell me about a failure. · Download PNG · Open card page

Lesson: 17.12 Phrases that help (and hurt)

What are you learning next? Name one specific area, why it matters for the role, and how you're applying it to your project. — Interview card 13 of 14: What are you learning next? · Download PNG · Open card page

Lesson: 17.13 Pointing to deeper courses

Do you have questions for us? Ask about on-call, how they deploy, what a first month looks like, and how they learn from incidents. — Interview card 14 of 14: Do you have questions for us? · Download PNG · Open card page

Lesson: 17.14 Lab / Practice — mock interview

Comparison cards

Terraform vs Ansible. Terraform: creates and changes infrastructure (servers, networks, databases) from code, tracking it in a state file.Ansible: configures software on existing servers over SSH. — Comparison card 1 of 3: Terraform vs Ansible · Download PNG · Open card page

Lesson: 17.7 Ansible and Terraform

git revert vs git reset (interview view). git revert: adds a new commit that undoes an old one.git reset: moves the branch back, removing commits from it. — Comparison card 2 of 3: git revert vs git reset (interview view) · Download PNG · Open card page

Lesson: 17.2 Git and GitHub

Rollback vs fix forward. Rollback: go back to the last working version.Fix forward: ship a new fix on top of the broken version. — Comparison card 3 of 3: Rollback vs fix forward · Download PNG · Open card page

Lesson: 17.9 Scenario questions