{"id":2103,"date":"2026-11-16T14:50:00","date_gmt":"2026-11-16T14:50:00","guid":{"rendered":"https:\/\/devopsschool.org\/blog\/?p=2103"},"modified":"2026-11-19T05:50:00","modified_gmt":"2026-11-19T05:50:00","slug":"infraops-self-audit-checklist","status":"publish","type":"post","link":"https:\/\/devopsschool.org\/blog\/infraops-self-audit-checklist\/","title":{"rendered":"InfraOps Self-Audit: A 20-Question Checklist for DevOps Careers"},"content":{"rendered":"<p>Interviews for DevOps roles keep circling one theme: show me how you keep infrastructure honest. A self-audit is the fastest way to build a good answer, and it doubles as a useful exercise for your current team. This checklist walks through twenty questions, grouped into five areas, that you can answer in an afternoon with read-only access to a project. The structure follows the InfraOps write-up from the Ops Atlas, and I credit it whenever a point is specific. Grab a notebook, score each line yes, partly or no, and be harsh; nobody else needs to see the sheet.<\/p>\n<h2>Area 1: Visibility (can you say what exists?)<\/h2>\n<ul>\n<li>Can you list every account, region and resource type that is in scope, and what is deliberately excluded?<\/li>\n<li>Do you know your coverage figure, meaning managed resources divided by in-scope resources?<\/li>\n<li>Does anything run in production that no code describes? Name it.<\/li>\n<\/ul>\n<p>If three or four of these come back as &#8220;no&#8221;, you have the classic gap that the Atlas highlights: a tidy change preview says nothing about resources it does not track. Start by listing the unmanaged items and ranking them by what hurts if they vanish.<\/p>\n<h2>Area 2: Change control (how does work reach production?)<\/h2>\n<ul>\n<li>Does every production change pass through a reviewed pipeline?<\/li>\n<li>Has anyone applied a change from a personal laptop in the last month?<\/li>\n<li>Is the change preview read by a second person before it is applied?<\/li>\n<li>Do approvals sit on a protected environment rather than on a branch name?<\/li>\n<\/ul>\n<p>The Atlas names laptop applies and skipped previews among the standard anti-patterns. It also warns that pull-request runs can execute a branch author&#8217;s edited workflow, so whatever role your preview job uses can be reached by anyone who can open a pull request. Treat that role as sensitive.<\/p>\n<h2>Area 3: State and structure (can you survive a mistake?)<\/h2>\n<ul>\n<li>Is any single state holding more than a few dozen resources?<\/li>\n<li>Is the state locked during every apply, and does everyone know not to break a lock they did not take?<\/li>\n<li>Are secrets kept out of state where the tooling allows it, using newer ephemeral and write-only features?<\/li>\n<li>Are ignore rules documented, with a reason and a review date?<\/li>\n<li>Are production databases protected both in code and at the provider?<\/li>\n<\/ul>\n<p>Score yourself against the Google Cloud guidance quoted in the Atlas: well under a hundred resources per state, ideally a few dozen. For a career-minded angle on the thinking involved, our article on <a href=\"https:\/\/devopsschool.org\/blog\/devops-problem-solving-how-to-build-critical-thinking-skills\/\">sharpening analytical habits for operations work<\/a> pairs nicely with this section.<\/p>\n<h2>Area 4: Detection (will you hear about drift?)<\/h2>\n<ul>\n<li>Is a scheduled preview running against every root module, with a non-zero exit raising an alert?<\/li>\n<li>Is each drift assigned to a named owner with a target date?<\/li>\n<li>Do you record how long drift stays open?<\/li>\n<li>Is there a written rule on when automatic reversal is acceptable, for instance limited to modules free of durable data, while nothing is being investigated?<\/li>\n<\/ul>\n<p>The Atlas suggests roughly 72 hours as the alert-and-assign target for anything outside that narrow auto-fix category. Notice that the question is about the age of the oldest difference, not only the count.<\/p>\n<h2>Area 5: Rebuild and retirement (can you start over and clean up?)<\/h2>\n<ul>\n<li>Have you recreated a whole environment from code in the last six months?<\/li>\n<li>Are machine images rebuilt on a schedule, with hosts replaced instead of patched in place?<\/li>\n<li>Is there a process to remove retired environments, backed by code-derived inventory?<\/li>\n<li>Does the team know which tests and policy checks run before merge?<\/li>\n<\/ul>\n<p>A rebuild drill is the Atlas&#8217;s marker of its governed stage, and it tends to reveal forgotten console settings the first time around.<\/p>\n<h2>Scoring and next steps<\/h2>\n<p>Give a point for each yes and half a point for each partly. Under eight: you are essentially hand-built, so aim for the first 30 days of the Atlas plan, which cover a backend, plans in CI and one change shipped through the pipeline. Between eight and fourteen: you are codified, so add the review gate, a state split and nightly detection. Above fourteen: spend your effort on adopting the riskiest unmanaged items, rebuilding images weekly and passing a drill. The Atlas calls its maturity ladder a proposal, so treat the cut-offs as a rough guide rather than a verdict.<\/p>\n<h2>How to run this with a colleague<\/h2>\n<p>Doing the audit alone is useful; doing it in pairs is better. Ask a teammate to answer the same twenty lines independently, then compare. Every disagreement marks a spot where the documentation is thinner than anyone admitted, and those spots become your first tickets. Keep the session short, capture each &#8220;no&#8221; as a task with an owner, and schedule a repeat in a quarter. Resist fixing it all in a single sprint. Teams that attempt a big-bang clean-up usually stall, whereas two or three narrow changes per month, each with a measurable before and after, tend to stick.<\/p>\n<h2>Turning the audit into a career story<\/h2>\n<p>In interviews, describe the weakest area you found, what you changed and how you measured the change. A sentence such as &#8220;we went from unknown coverage to a number, and we shortened the oldest drift from weeks to days&#8221; lands better than a list of tool names. If you are considering a move toward cloud-focused roles, our guide on <a href=\"https:\/\/devopsschool.org\/blog\/the-ultimate-career-transition-devops-to-cloud-engineer\/\">shifting from a DevOps role into cloud engineering<\/a> covers the wider path. Every specific claim above can be traced to <a href=\"https:\/\/www.xopsschool.com\/infraops\/\">the Ops Atlas page on InfraOps<\/a>, which is worth a slow read once you have your score.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A twenty-question checklist across five areas that helps you audit your infrastructure practice and turn the results into an interview story.<\/p>\n","protected":false},"author":5,"featured_media":2104,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[489],"tags":[],"class_list":["post-2103","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops-careers"],"_links":{"self":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts\/2103","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/comments?post=2103"}],"version-history":[{"count":1,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts\/2103\/revisions"}],"predecessor-version":[{"id":2220,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts\/2103\/revisions\/2220"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/media\/2104"}],"wp:attachment":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/media?parent=2103"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/categories?post=2103"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/tags?post=2103"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}