Plenty of Mumbaikars want to add technology operations skills to their resume — cloud, automation, reliability work — but stall at the planning stage. This guide fixes that. Below is a 90-day Ops skills plan built for people with full-time jobs, long commutes and limited budgets. No motivation speeches, no shortcuts that do not exist. Follow the steps in order, adjust the hours to your reality, and by day 90 you will have a studied discipline, a stack of scored practice attempts and at least one credential worth showing. Treat it like an itinerary: fixed anchors, flexible middles.
Step 1: Lock your weekly hours before you pick a subject (Days 1–3)
Most upskilling plans die from dishonest scheduling, not difficulty. Open your calendar and find eight to ten realistic weekly hours. For a typical Mumbai schedule that usually means: 40 minutes on the morning commute, 40 at night after dinner, and one two-hour block on Sunday morning before the household wakes up. Write these into your phone calendar as recurring events. If a week collapses — festivals, deadlines, monsoon chaos — you reschedule the hours, you do not delete them. The same discipline we recommend for trip planning applies; our note on building a Mumbai itinerary that bends without breaking makes the same point about anchors versus filler.
Step 2: Choose one Ops discipline and refuse the rest (Days 3–7)
Operations is a wide field — deployment automation, reliability, cloud cost control, security operations, data pipelines and more. You need exactly one lane for 90 days. Spend this first week reading introductory notes across three or four disciplines on xOps School’s catalogue of Ops learning tracks, where each discipline comes packaged with study notes and its own quiz, so you can gauge both the content and how you score against it before committing. Pick the one you kept reading past your allotted time. Then close the other tabs. Sampling after this point is procrastination wearing a productive costume.
Step 3: Split the track into three 25-day blocks (Day 7)
Take your chosen discipline’s syllabus and divide it into three roughly equal blocks: fundamentals, core tooling, and applied scenarios. Assign each block 25 days. This matters because an undivided syllabus produces the “always starting, never finishing” loop. A divided one gives you three finish lines instead of one distant horizon. Put the three block-end dates in your calendar now, alongside your travel-style buffer day after each — Mumbai teaches everyone to pad their schedules, and study plans deserve the same respect as airport runs.
Step 4: Read first, then test yourself the same week (Days 8–32)
During block one, follow a strict loop: read a topic’s notes, then attempt questions on it within the same week. Do not postpone testing until you “feel ready” — that feeling arrives roughly never. The quizzes on the platform above run 25 questions per track and grade you the moment you submit, with the reasoning behind every answer laid out, including the ones you got right by luck. Keep a plain notebook with two columns: concepts I got wrong, and the correction in my own words. Review that notebook every Sunday. This single habit separates people who pass assessments from people who collect tabs.
Step 5: Get your hands dirty with real tasks (Days 33–57)
Block two is where reading stops being enough. Ops skills live in the fingers: writing configuration, running commands, breaking small things and fixing them. Work through hands-on assignments rather than watching someone else type — the platform stocks over 340 of them precisely because employers quiz you on doing, not reciting. If your laptop is modest, do not worry; most foundational exercises run comfortably on free cloud tiers or lightweight local setups. Budget two of your weekly hours for pure practice. When an exercise defeats you, write down the error message and what fixed it. Those notes become interview stories later.
Step 6: Simulate exam pressure before it simulates you (Days 58–75)
Block three introduces time pressure. If your lane involves infrastructure-as-code, attempt the timed Terraform-style practice exams that mirror real certification conditions — fixed clock, mixed question formats, no pausing to search the internet. The point of timed attempts is not the score; it is discovering how your brain behaves at minute 35 when three questions remain. Platforms that keep your best two attempts reward repetition, so attempt early and often rather than saving yourself for one grand sitting. Treat a bad timed score like a missed train: noted, annoying, and followed immediately by the next one.
Step 7: Convert your work into visible proof (Days 75–85)
Now package everything. Clear the track assessment and claim the certificate — the verifiable kind a recruiter can validate in seconds. Then build your evidence folder: completed assignment list, score progression screenshots, your two-column mistake notebook summarised into one page, and a 150-word description of the most interesting problem you solved. Update your resume and LinkedIn in the same sitting. Candidates lose weeks to “I’ll update my profile later”; you will do it on day 82 because it is in the calendar.
Step 8: Spend the final days on interview reps, not new topics (Days 85–90)
Resist the urge to begin fresh material. Spend the last stretch answering role-based interview questions out loud, ideally to another human. Record yourself on your phone once; the first listen is painful and worth it. Prepare three stories: a problem you solved, a mistake you made and corrected, and why you chose this discipline. Short, specific, true. If commute time is all you have, rehearse silently with written prompts — the same way seasoned locals mentally pre-plan routes to dodge jams, a habit we covered in our piece on cutting wasted hours out of Mumbai road travel. Preparation compounds in the gaps.
Budget and equipment: keep both boring
You do not need a gaming laptop or a loan. A machine that opens a browser and a terminal is sufficient for the first two blocks, and a surprising amount of reading and quizzing happens perfectly well on a phone. On money: start with whatever free material exists in your chosen lane — free practice tests and standards courses cover a lot of early ground — and pay only when you hit a wall that payment actually removes. Avoid lifetime deals, avoid EMI-funded bootcamps in month one, and be suspicious of anything that charges before showing you its syllabus. The correct early spend for most learners is a few hundred rupees a month, not a few lakh up front. Keep receipts of what you pay and what it unlocked; reviewing that list on day 90 tells you whether your money worked as hard as your mornings did.
What to do when the plan slips — because it will
Expect to lose roughly ten of the ninety days to life: illness, weddings, work crunches, monsoon flooding. The plan survives if you follow two rules. First, never skip two scheduled sessions in a row; shrink a session to fifteen minutes rather than zero. Second, when a block overruns, cut its least essential topics instead of pushing every deadline back — a shorter syllabus finished beats a complete one abandoned. Progress in this field is measured in consistent weeks, not perfect ones.
The honest 90-day outcome
Here is what this plan genuinely delivers: one discipline studied end to end, dozens of scored practice attempts, real hands-on exercises completed, a verifiable credential, and interview answers you have actually spoken aloud. Here is what it does not deliver: a guaranteed job offer by day 91. What changes is your position in the queue. You stop being an applicant who “is interested in cloud” and become one with dated, checkable evidence of twelve weeks of structured work. In a city where everyone claims hustle, documented hustle wins. Start the calendar entries tonight; day one is tomorrow’s morning train.