{"id":3131,"date":"2026-11-16T19:40:00","date_gmt":"2026-11-16T19:40:00","guid":{"rendered":"https:\/\/www.rajeshkumar.xyz\/blog\/?p=3131"},"modified":"2026-11-19T15:40:00","modified_gmt":"2026-11-19T15:40:00","slug":"infraops-career-faq-first-90-days","status":"publish","type":"post","link":"https:\/\/www.rajeshkumar.xyz\/blog\/infraops-career-faq-first-90-days\/","title":{"rendered":"InfraOps Career FAQ: Levels, Portfolios and Your First 90 Days"},"content":{"rendered":"<p>People who read this blog for career advice keep sending versions of the same questions about infrastructure work, so here is a candid Q and A. It covers what InfraOps is, how to know how mature a team is, what goes into a portfolio and what a sensible first ninety days looks like. The factual parts come from the public Ops Atlas entry, and where I am giving opinion rather than reference, I will say so.<\/p>\n<h2>Is InfraOps an official job title or certification?<\/h2>\n<p>Not at the moment. According to the Atlas the word is loose shorthand, and neither an exam board nor a standards group stands behind it. You will see it as a team name, in the occasional job posting and as the name of at least one commercial product. The Atlas uses it for the lifecycle of infrastructure described as code. My advice: read the responsibilities in any advert rather than relying on the title, and do not pay for a course that claims to certify you in it.<\/p>\n<h2>What would a hiring manager want me to be able to do?<\/h2>\n<p>Write and read infrastructure code, explain what a plan shows before it is applied, and describe what happens when reality drifts away from the code. The Atlas has a scope list that doubles as a syllabus: locking and state, modules, drift, bringing existing resources under code, golden machine images, matching staging to production, testing, a code-derived inventory and the retirement of unused items. If you can talk through each with a small example, you are ahead of most applicants.<\/p>\n<h2>How do I tell how mature a team is?<\/h2>\n<p>Ask about the pipeline. The Atlas proposes a ladder of five levels and is upfront that it is the author&#8217;s own idea, not a standard. Level one is hand-built, level two is codified, level three is pipelined (a gate on policy, a weekly search for drift, coverage you actually measure), level four is governed with a coverage target such as 90 percent and a passing rebuild drill, and level five is continuous, meaning those results hold for two quarters. In an interview, asking which level they think they are at, and why, usually produces an honest conversation.<\/p>\n<h2>What should my portfolio contain?<\/h2>\n<p>One small project, done properly, beats five half-finished ones. Include code in a repository with a pipeline that previews every change, a remote state with locking, a scheduled drift check, a short write-up of one mistake and how you fixed it, and a rebuild from nothing on a fresh account. Put numbers on it. The Atlas prefers reporting how many resources fall outside review, and how old the oldest unresolved drift is, over a single flattering percentage.<\/p>\n<h2>How should I plan my opening quarter in a new role?<\/h2>\n<p>The Atlas splits a team plan into thirty, sixty and ninety days, and I find it works as a personal plan too. In the first month, help stand up the backend, make previews run automatically with temporary credentials and watch the first production change travel through the pipeline. During days thirty-one to sixty, split large state, add a plan gate, turn on a nightly drift check and retire laptop applies. During days sixty-one to ninety, import the riskiest hand-made resources, start a weekly image rebuild and run the first rebuild drill. Treat it as a menu, because your team will have its own constraints.<\/p>\n<h2>Do I need to pick Terraform or something else?<\/h2>\n<p>Learn the concepts first, then pick the tool your target employer uses. The Atlas notes the licensing change on one engine and the open-source fork on the other, and it also mentions a general-purpose-language option and a cloud-native template service. The skills of reading plans, splitting state and watching for drift carry across all of them. In my own opinion, building the same small project twice with two different tools is the fastest way to see what is universal.<\/p>\n<h2>What mistakes do juniors make most often?<\/h2>\n<p>Three come to mind. They trust a clean preview as proof that everything is under control, when it only speaks for managed resources. They run applies from their own laptops because it feels faster. And they lean on the flag that narrows a run to a single resource, which the documentation keeps for rare, exceptional cases. Each of these is avoidable with a pipeline and a habit of asking what a report cannot see.<\/p>\n<h2>How does personal branding fit in?<\/h2>\n<p>Write about what you build. A short post describing how you found and fixed a drift, with your own numbers, shows judgment more clearly than a list of buzzwords. If you work with containers as well, my articles on <a href=\"https:\/\/www.rajeshkumar.xyz\/blog\/master-docker-image-management-best-practices-for-engineering-teams\/\">managing Docker images well across engineering teams<\/a> and on <a href=\"https:\/\/www.rajeshkumar.xyz\/blog\/docker-best-practices-for-development-and-production-environments\/\">sensible Docker habits for development and production<\/a> show the same attitude: small, repeatable practices that you can explain.<\/p>\n<h2>Should I worry about a gap in my experience?<\/h2>\n<p>Everyone has one. Few people start in a team where every resource is already under code, and most learn on messy estates. What matters is that you can describe a concrete step you took to reduce risk, such as splitting one oversized state or bringing a hand-made resource under control. Pick one such story, tell it in three sentences and rehearse it until it sounds natural.<\/p>\n<h2>Where can I read the full reference?<\/h2>\n<p>The long entry, which includes diagrams, a metrics proposal and the maturity ladder, sits on <a href=\"https:\/\/www.xopsschool.com\/infraops\/\">the Ops Atlas page for InfraOps<\/a>. Treat it as one editorial view and cross-check anything you plan to quote in an interview.<\/p>\n<p>Missing a question you wanted answered? Send it over and I will add it in a later update. Careers in this area reward people who stay curious, write things down and keep their numbers honest.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A candid Q and A on building an InfraOps career: what the term means, how to judge team maturity, what a portfolio needs and a first ninety days plan.<\/p>\n","protected":false},"author":6,"featured_media":3132,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[713],"tags":[],"series":[],"class_list":["post-3131","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops-careers"],"_links":{"self":[{"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/posts\/3131","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/comments?post=3131"}],"version-history":[{"count":1,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/posts\/3131\/revisions"}],"predecessor-version":[{"id":3259,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/posts\/3131\/revisions\/3259"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/media\/3132"}],"wp:attachment":[{"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/media?parent=3131"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/categories?post=3131"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/tags?post=3131"},{"taxonomy":"series","embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/series?post=3131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}