A Solo Engineer's Two-Year Campaign

This is a composite, told as one continuous timeline for a candidate this course refers to elsewhere, in scattered dev's-eye-view quotes, as Dot — the generic engineer's-eye stand-in whose "I" appears throughout this course to illustrate a real study moment without claiming to be a real, identifiable person. This page threads four of those moments — the spreadsheet built after a month of trying to hold sixteen exams in her head, the training-repayment agreement she signed without reading closely, the six-week break after CAPA, and the sequencing mistake that cost her weeks on the observability pair — into one twenty-four-month campaign, start to Golden Kubestronaut. Nothing about the specific months, dollar figures, or dates below is a real record; it's built to be internally consistent and to show what a realistic, imperfect, ultimately successful solo campaign actually looks like, not what a perfectly optimized one would.

Where the campaign started

☺ Like you're 10: Dot tries to hold sixteen exams in her head, gives up after a month, and writes them all down instead — which turns out to be the actual first milestone of the whole campaign.

Dot is a mid-level backend engineer at a company with no existing Golden Kubestronaut program and no manager who's ever heard of it — nothing like Meridian's sponsored cohort in this course's other case study. She decides to pursue the full sixteen-exam ladder alone, self-motivated, with no budget commitment from anyone yet. For the first month, she tries to hold the whole plan in her head — which exams, which order, which are already stale — and it doesn't work; The Sixteen-Exam Ladder's own point about a checklist beating a vague goal is exactly the lesson she reaches on her own, one month in, by giving up and building a spreadsheet: one row per exam, a pass date column, an expiry column, a status column. That spreadsheet, not any single exam pass, is the real first milestone of the campaign — everything from here on is items being checked off a list she can actually see, instead of a fog she's trying to remember the shape of.

She starts, deliberately, with LFCS — the exact "optional early" slot The Order of Attack recommends for exactly her reason: no Kubernetes dependency at all, so her first experience of the Linux Foundation's live-terminal, remote-proctored format happens on material she already knows cold. Self-funded, cheap, and low-stakes on purpose.

Phase 1: the Kubernetes core, and the bet that came with it

☺ Like you're 10: Dot pays for the first three exams herself, then gets her employer to fund the pricier three — but signs the fine print faster than she should have.

LFCS, KCNA and KCSA — the three cheapest, least Kubernetes-dependent exams on the ladder — go on Dot's own card. By the time she's three exams in, she has something to show a manager: a real, sequenced plan with three checkmarks already on it, not a hypothetical ask. The pitch for the remaining, pricier Kubernetes-core trio — CKA, CKAD, CKS, the $445 performance-based tier — gets approved in one conversation. What Dot doesn't do carefully is read the training agreement attached to that approval. She signs it, glad someone else is paying for the expensive exams, without reading past the total dollar figure at the top.

# dot's-cert-tracker.csv — the spreadsheet from month one, extended.
# (illustrative excerpt — real dates and figures, not a real record)
exam,source,price,purchased,passed,status
lfcs,self-funded,445,m1,m2,valid — expires m26
kcna,self-funded,250,m2,m3,valid
kcsa,self-funded,250,m3,m4,valid
ckad,employer training agreement,445,m4,m6,valid
cka,employer training agreement,445,m4,m8,valid
cks,employer training agreement,445,m4,m9,valid — Kubestronaut complete

CKAD, then CKA, then CKS follow the recommended soft on-ramp exactly — The Order of Attack's gentlest-hands-on-first logic, ending with the one hard rule on the whole ladder: CKS booked only once CKA was already passed. By month nine, all five Kubernetes-core exams are active at once. Kubestronaut arrives automatically — no application, just a jacket in the mail a few weeks later, and a private community channel that, per The Jacket & the Community, turns out to matter more to Dot over the coming months than she expected it to.

The offer, and the fine print nobody had read

☺ Like you're 10: A tempting job offer forces Dot to actually read the agreement she'd only skimmed — and the number turns out not to change her decision, but not knowing it earlier cost her a stressful weekend either way.

Eight months after signing the training agreement, at campaign month twelve, a recruiter reaches out with a genuinely appealing offer. Dot's first instinct is pure excitement — right up until she remembers, vaguely, that the CKA/CKAD/CKS funding had some kind of clause attached. She digs the PDF back out and finds the vesting schedule on page three: full repayment owed if she left within the first month of signing, sliding down to zero owed at eighteen months out. At month eight of eighteen, a real, specific number was attached to leaving — not the whole $1,335, but not nothing either. The Economics of Certification covers exactly this mechanism in full; Dot's mistake wasn't taking the funding, it was not knowing the number until a decision was already forcing the question.

The wall after CAPA

☺ Like you're 10: A few weeks after finishing CAPA, several warning signs show up at once — and instead of pushing through, Dot takes a real, planned break.

Phase 2 goes well at first: CGOA passes cleanly on Kubestronaut's own program-earned discount vouchers, exactly the sequencing Voucher & Discount Stacking describes — finishing the Kubernetes core unlocks vouchers that quietly cover the next couple of associate exams without any hunting. CAPA follows at month fifteen. But by the time CAPA is done, more than one of the warning signs Sustaining the Marathon names shows up at once: opening the next blueprint starts feeling like opening a bill instead of a curiosity, a practice set she'd have aced weeks earlier is suddenly full of careless misses, and one skipped study session spirals into a week of skipped sessions instead of just meaning one missed evening.

Dot does the thing that page recommends and most people skip: she takes a real six-week break, not a "lighter week" — tells her study partner about it in advance so it isn't a secret slip, and touches nothing certification-related for the whole six weeks. She comes back and passes KCA in under three weeks, faster than any associate exam before it in her whole campaign.

The sequencing mistake: OTCA before PCA

☺ Like you're 10: Dot skips the recommended order on one pair of exams, barely passes the harder one first, and pays for it in extra study hours on the second.

By month twenty, Dot is deep into the observability family — and makes the one clear sequencing mistake of her whole campaign. OTCA sounded more relevant to what her team actually used at work, so she sat it before PCA, reversing the on-ramp The Order of Attack recommends. OTCA's Collector-pipeline domain was fine. Its observability-fundamentals domain assumed she already thought in metrics — cardinality, aggregation, the works — and she didn't yet. She passed, barely. Two months later, PCA landed easily, and in hindsight, roughly a third of the time OTCA actually took would have been enough if she'd done the two exams in the other order.

Nothing about this mistake was catastrophic — she still passed both exams, and neither purchase went to waste the way an expired voucher would have. But it's the clearest place in the whole campaign where skipping a soft on-ramp cost real, countable hours for no offsetting benefit, exactly the risk The Order of Attack names and exactly the reason that page exists at all.

Racing the clock: the two months of buffer that almost weren't there

☺ Like you're 10: Around month twenty-one, Dot does the arithmetic on her very first exam and realizes she needs to actually finish soon, not eventually.

Somewhere around month twenty-one, with only CBA and the platform-engineering summit exam CNPE left, Dot runs the check The Order of Attack recommends and had, until then, mostly ignored: which of her sixteen certifications expires first? The answer was LFCS — passed all the way back in month two, the very first exam of the whole campaign, carrying its own two-year validity window that closes at month twenty-six. Golden Kubestronaut requires all sixteen active simultaneously, and a candidate who finishes fifteen exams and lets the sixteenth one lapse hasn't qualified for anything — she'd have earned every individual badge and still missed the actual title. With CNPA already handled in parallel through the Platform Engineering course earlier in the campaign, that left exactly two exams and roughly five months of runway before LFCS's window closed.

Dot compresses the final stretch on purpose rather than by accident: CBA at month twenty-three, CNPE — the natural capstone, the exam that assumes most of the rest of the ladder is already in place — at month twenty-four. Golden Kubestronaut arrives with all sixteen certifications simultaneously active, two full months before LFCS would have expired. It's a real buffer, but a thinner one than a candidate who'd checked the clock from month one would likely have needed to cut it to.

What sustained it

☺ Like you're 10: A tracker she could see, a break she actually took, and a study partner who knew when to check in — none of it glamorous, all of it load-bearing.

Nothing about what got Dot across the finish line was exotic. The spreadsheet from month one stayed the single source of truth the whole campaign, the same discipline The Sixteen-Exam Ladder recommends. The study partner she told about her six-week break — met, unglamorously, in the plain public CNCF community Slack months before Kubestronaut ever unlocked the private one — was the same accountability The Jacket & the Community argues matters as much as the badge itself for a multi-year solo campaign. And she avoided the collector's trap the whole way through by treating the capstone tracker as a running, real project rather than a one-off assignment — by the time she sat CNPE, the GitOps pipeline, the mesh policy, and the observability dashboards it assumed weren't hypothetical; she'd actually built and kept running versions of all three.

What doesn't transfer

☺ Like you're 10: Not everyone has an employer willing to fund three exams, and not everyone can afford six weeks fully off — the habit worth keeping is the discipline, not the exact deal Dot got.

A solo, self-directed campaign like Dot's assumes real slack that not everyone has: an employer willing to fund even part of the ladder, the ability to take six deliberate weeks off certification work without real consequence, and enough personal stability to absorb a competing-offer decision without the vesting number being the deciding factor. None of those are universal, and a candidate without any of them isn't doing the campaign wrong — they're running a different, harder version of it, and The Economics of Certification's self-funded column is the more honest starting point for that version. The specific twenty-four-month length is illustrative too — a slower, more sustainable pace, or a faster one for someone with fewer constraints, are both legitimate; what matters is checking the earliest-expiry clock early rather than discovering it has become urgent at month twenty-one.

What should transfer regardless of pace or funding: build the tracker in month one, not month six; take a real reset when the warning signs stack up, not a lighter week that isn't actually a break; read the on-ramp advice before, not after, a hard sequencing mistake; and know your own earliest-expiry date from the start of the campaign, not partway through it. For the strategic question of whether chasing all sixteen was even the right target to begin with, see Choosing Breadth Over Depth — a Retrospective — or return to the case studies hub for the full set.