My OSCP Journey

“Ahh, finally!” That electric rush when you type cat proof.txt and the screen lights up with success is pure and unadulterated dopamine. If you’re staring down the barrel of the Offensive Security Certified Professional (OSCP) exam, wondering if it’s the summit worth scaling or a cliff you’d rather avoid especially while juggling a full-time gig pull up a chair. This is my raw, real-deal chronicle of the grind: the triumphs, the faceplants, and the “what fresh hell is this?” moments that somehow led to a pass. As a total newbie in blogging this is literally my life’s first one I’m excited to share it with you. No polish, just passion. Let’s dive in.

It all kicked off August 26th when I snagged my PWK voucher. I gave myself till October 20th to wrap it up because November? Total chaos with family stuff weddings, parties, you name it. No way I could sneak in hacking sessions between all the chit-chat. But here’s the real twist: I’m not some kid with free time. I’ve got a full-time job clocking 8–9 hours a day, Monday to Friday. OSCP had been my dream for years, but fear (and exhaustion) always won. Everyone says it’s the cert that proves you’re legit in cybersecurity, not just talk. I’d been hitting TryHackMe labs on my off hours for months, feeling pretty pumped. “Easy,” I figured. Nope. The course? Way tougher, full of sneaky bits. With just 45 days to exam time, it felt nuts. But I told myself, “Impossible? That’s for quitters.” To make room, I went nuclear: Deleted social media apps (bye, doom-scrolling), skipped hangouts with buddies (rain checks forever), and laser-focused. Work got my all during the day, study owned the rest. Weekdays: 2–3 hours after dinner, basics and quick drills. Weekends: 8–10 hour binges on labs, fueled by coffee. All in? About 25–30 hours a week. It hurt, but damn, it worked.

OffSec’s stuff? Spot on. It’s laid out simple, and those labs? They stick with you, like real-world practice. I did every one I could (skipped the AWS cloud part no time, and it’s not on the exam). By late September about a month in, dodging work deadlines I finished the theory and labs. Feeling? On top of the world. Dodging attacks like it’s nothing. Wish I’d seen the hard stuff coming.

Get Vyntrix’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

Then came the challenge labs fake exams to test your guts. The first four? Not too bad, but not quite like the real thing. I knocked them out in a week, sneaking in email checks during “breaks.” The real mocks? OSCP-style pain. Super excited at first. But the one? Took 1.5 days, squeezed around overtime. Brutal. Made me think, “Should I even try?” Booked October 24th anyway. Next two? Another week of hurt, one spilling into a late-night after a Friday crunch. I got tougher, but knew I needed more. Did a couple extra mocks too (smart move they sneak in skills). Then family stuff forced me to bump it to October 11th. Forty-five days total. Ready? Kinda. Scared? Totally. Redoing it all while keeping my job? Hell no. Full speed ahead.

Exam Day: Night shift for me. Everyone’s out cold, no distractions in my setup spot. Got some sleep (ish), ate okay (sorta), stocked snacks (yes), and leaned on caffeine hard. Can’t lie it kept me going. No naps, barely any food, but I stayed sharp. The test? Tough as hell. Active Directory ate up over 8 hours. Halfway, I’m like, “I’m toast.” But I hung onto “don’t quit” like glue.

The solo machines? Trap city. First one: 4 hours chasing shadows for a way in. Privesc? Tricky as heck, but I nailed it. Second? Wall after wall. 4 hours, zip. Time flying, doubts screaming. Switched to the third: 3 hours to get in, 2hours to own it. Boom!! enough points to pass. Sweet! But that second one bugged me. Used my last remaining hours trying again. Nothing. Mad as fire fighter beat, but breathing. (spent the last 1 hour to check if any screenshot is missing)

After? The report is sneaky killer. Crash from caffeine hit; brain fog city. Slept 11 hours (wild), then started. Thought 4–5 hours? Try 10+ of slow torture. Their template helped, but I overdid the details. First Standalone in 3 hours? it took 3 more hours for AD, Yikes. Went basic: Just the key steps for the 2nd standalone and still it took 2 hours. Finished the main bits, summary in 1.5 hours. PDF to 7z? Windows screwed me md5sum wrong. 10 minutes left. Starving, shaking, life flashing. Swapped to Kali, fixed it: Match! 3 minutes to go. Sent it. Pure joy. Closest call ever.

Waiting for Results

The official word was that results could take up to 10 days, but two days later I had an email from OffSec I passed! In one short blog post I can’t capture everything, but that’s the story of how caffeine, stubbornness, and a bit of luck got me through.

Quick Tips: What Worked (and What Didn’t) — Straight from My Mess-Ups

Stuff to Do:

1. Sketch a Draft report outline before. Easy to fill in later works with your work notes too.
2. Take Breaks they’re Gold. Every hour, step away 5–10 mins: Bathroom, walk, talk out your stuck spots. Saved me from total burnout (or that afternoon crash).
3. Set Up Your Spot Right. Water, munchies, everything handy.
4. Hit Extra Practice. HTB or THM: At least 5 labs each type (web, AD, ups) Builds your speed for the rush.
5. Dig Everywhere. Traps are coming check ports, users, files non-stop.
6. Pic Smart. Full screen grabs, mark the big stuff. Fix later; miss less.
7. Backups All the Way. Copy VMs, extra net. One guy’s story: Crash in the middle. Gut punch. Toss in cloud saves for travel surprises.
8. Cheer the Little Wins. Get in a box? Quick high-five. Keeps you going, even on a bad Tuesday.

Stuff to Skip:

1. Go It Alone. No help, no AI they catch it. Ban? Ruins everything. Do it right.
2. Don’t Wreck Yourself. Sleep 7–8 hours before, eat real food. I half-assed and bombed a talk after.
3. Easy on the Coffee. It pumped me, then dropped me. Cut back; tea’s smoother.
4. Don’t Rush Prep. 45 days with work? Tough love. Shoot for 90 if you can; know it cold.
5. No Giving In. Stay upbeat till the end. That last shot? Magic.
6. Cut the Noise. Phone out, quiet zone. Ping mid-try? Wreckage. (And skip those “fast Slack peeks” in practice.)
7. Do not take help any for writing report. No copy-paste or AI they sniff it out.