Can you switch to cyber security while working full time?
Yes — it's actually how most successful career changers I've tutored have done it, not the exception. The idea that you need to quit your job, take out a loan, and go "all in" on a bootcamp is mostly marketing from the bootcamps themselves. I'm Michael — CISSP-certified, 25 years in the tech industry, and I now tutor career changers 1-to-1 through Korra Studio, almost always around their existing full-time jobs. The people who succeed at this aren't the ones with the most free time; they're the ones with the most consistent five hours a week.
Why "quit and go full-time on studying" is usually the wrong call
Quitting removes your safety net exactly when you need it most — you're not employed yet, so a slow job search becomes financially stressful, which makes you desperate, which makes you a worse interview candidate. Keeping your current income while you build skills in the evenings costs you time, not money, and time is the resource you can manage. The only real exception is if your current job is actively harming your ability to study (extreme hours, night shifts with no recovery time) — in that case the calculation changes, but for most full-time jobs, staying employed while you build the new skillset is the lower-risk path.
A realistic weekly structure
Here's roughly what I recommend to students juggling a 40-hour week:
| Day | Focus | Time |
|---|---|---|
| Mon/Wed/Fri evenings | Core study — networking, OS fundamentals, or cert material | 45–60 min |
| One weekend morning | Home lab work / hands-on practice | 2–3 hours |
| Commute or lunch breaks | Passive reinforcement — flashcards, re-reading notes | 15–20 min |
| One evening a fortnight | Review progress, adjust plan | 30 min |
That's five to seven hours a week, sustainable for months without burning out, versus the unsustainable "study every evening and weekend" plan that usually collapses within three weeks.
The sequence that actually works part-time
- Pick one lane and don't wander. SOC analyst track or GRC track — deciding this early stops you from spreading five hours a week across too many topics to make real progress on any of them.
- Study in short, focused blocks, not long unfocused ones. Forty-five minutes of genuinely focused study beats three scattered hours with your phone next to you.
- Front-load fundamentals before certification cramming. Trying to memorise exam content before you understand the underlying concepts wastes your limited hours on rote repetition you'll forget.
- Build your home lab on the weekend block, not weeknights. It needs uninterrupted time to be productive; don't try to squeeze lab work into a 45-minute weeknight slot.
- Set a review checkpoint every two to four weeks, ideally with someone who can tell you honestly whether you're actually progressing or just staying busy.
What I tell my students
The most common failure mode I see isn't lack of time, it's lack of a plan that fits the time available. People try to follow a bootcamp curriculum designed for 40 hours a week and attempt it in 5, get a fraction of the way through, feel like they're failing, and quit. I tell every working student the same thing: your plan has to be built around your actual week, not an idealised one. If you genuinely only have four evenings and one weekend morning, plan for that — don't guilt yourself into a schedule you'll abandon in a fortnight. Consistency over months beats intensity over weeks, every time, in this specific field.
The other thing worth saying honestly: tell your manager or don't, that's your call, but don't let the job search leak into work hours in a way that puts your current income at risk before the new one is secured. That safety net is the entire point of doing this while employed.
Where this connects to the wider path
If you're not yet sure which lane fits — SOC analyst, GRC, or something else — the cyber security career change guide maps the options before you commit your limited hours to one. And if you're specifically coming from an existing IT role, from IT support to cyber security will likely shorten your timeline further, since you're not starting fundamentals from zero.
A tutor's real value here isn't teaching you something you couldn't Google — it's making sure your limited hours each week go toward the right thing, not a detour. If you want that kind of structure around your existing schedule, book a trial lesson and we'll build a plan around your actual week, not a generic one.
FAQ
How many hours a week do I realistically need to change career into cyber security?
Five to eight hours a week, consistently, over six to twelve months is a realistic runway for most people working full time. More hours shortens the timeline; less stretches it, but consistency matters more than raw hour count.
Should I quit my job to study full time instead?
Generally no. Keeping your income while you build skills removes financial pressure from the job search, which tends to produce better outcomes than studying full time with a shrinking runway of savings.
What's the biggest risk of doing this part-time?
Losing momentum. An unstructured plan with no checkpoints tends to drift — study drops off after a few weeks once the initial motivation fades. A clear weekly structure and periodic review are what keep it going.
Can I really build a home lab with only a few hours on weekends?
Yes. A basic home lab (a couple of virtual machines and a free SIEM tool) can be set up in a single weekend morning and then extended incrementally — it doesn't need to be built in one sitting.
