CAT Prep While Working Full-Time: 21 Hours in 59-Minute Bits

The Number I Actually Set, and the Number I Actually Hit

When I set my weekly study goal in Karma Yogi, I put it at 1,260 minutes - 21 hours a week. That number came from a mental image of roughly 3 hours a day, most days. My actual logged average session length is 59 minutes. Longest single session: 190 minutes, and that's a weekend full mock, not a weekday. The gap between "21 hours a week" and "59-minute sessions" is the entire story of preparing for CAT with a full-time Technical Product Manager job: the hours add up, but almost never in the shape I originally planned them.

Across 340 logged sessions and roughly 20,100 minutes of study time, spread over 135 distinct active days, the pattern is clear in the data before it's clear in memory: fragmentation, not hour count, is the actual constraint.

The Real Constraint Isn't Time, It's Fragmentation

The instinct when you have a full-time job is to frame the problem as "I only get 2 hours a day versus a full-time aspirant's 8." In practice, the bigger cost is fragmentation: those 2 hours arrive tired, late, and interrupted, and get spent re-orienting rather than practicing. An unfocused 8 hours often produces less than a disciplined 90 minutes - which is close to what my own 59-minute average session, run consistently across 135 active days, has actually delivered.

The fix isn't finding more time. It's protecting a smaller amount of time from fragmentation.

My Actual Weekly Structure

This assumes a standard working day with a commute - adjust for your own schedule, but keep the underlying principle: fixed, protected blocks beat "whenever I have time."

• Weekday mornings (45-60 min): Before work, when willpower is highest and least depleted by the day. One focused activity - a timed sectional, or a fixed set of Quant problems. Not reading or passive review, which is easier to do half-attentively.
• Commute: Passive activities only - reading RC passages, reviewing mental math tables, listening to concept explanations. No timed practice here; the environment is too unpredictable for reliable data on actual speed.
• Weekday evenings (30-45 min): Review and error-logging from the morning's session. Short, low-energy-cost, and it converts the morning's practice into actual learning rather than just reps.
• Weekends (3-4 hours each day): Full mocks and deep analysis sessions belong here. My 190-minute longest session was a weekend full mock - I don't attempt anything close to that length on a weekday, because the fatigue makes the data unreliable and the analysis gets rushed.

My own average mood rating on logged sessions sits at 3.6 out of 5 - not euphoric, not miserable, which is roughly what I'd expect from a schedule built around consistency rather than motivation. The sessions that pull that average down hardest are the late-evening ones squeezed in after a bad day at work; the ones that pull it up are the protected weekend blocks where nothing is competing for attention.

A Real Weekday, Not an Idealized One

A typical Tuesday, logged rather than remembered:

That's roughly 90 logged minutes on a normal weekday - nowhere near a 3-hour daily average, and that's the point. 1,260 minutes a week isn't 180 minutes a day, evenly spread; it's closer to 90 minutes on four weekday mornings-and-evenings combined, plus the bulk of the rest arriving on Saturday and Sunday in 3-4 hour blocks. Looking at a single Tuesday in isolation used to make me feel behind, until I started reading the week as a whole instead of any one day against a daily-average target that was never realistic in the first place.

What I Cut First When Work Gets Heavy

When a work deadline eats my week, I cut in this order: (1) extra Quant practice past my weak-topic list, (2) sectional mocks, never (3) the weekend full mock and its analysis. The full mock plus analysis is the highest-leverage activity in my week - it's the one thing that survives a bad week at work, because it's also the one thing that, if skipped, breaks the section-level trend data I actually rely on to know if I'm improving.

Protecting the Habit From Work Volatility

The single biggest risk isn't a bad week - it's a bad week turning into a bad month because the streak broke and restarting feels harder than continuing would have been. I treat my prep schedule the way I'd treat a recurring meeting I can't move: block the calendar time explicitly, and when a real conflict forces a skip, resume the very next day rather than waiting for things to calm down. My guide to building a study streak covers why this matters more than raw hours.

Using Weekday Fragments Well

Short, fragmented windows are genuinely well-suited to certain activities and poorly suited to others. Mental math drills (tables, squares, cubes, percentage-to-fraction conversions) fit perfectly into 10-15 minute gaps and compound into real Quant speed over months - this is exactly where my QUANT average climbing from 26.8 to 35.6 mock-over-mock came from, per my mock log. Full DILR sets do not fit fragments - they need an unbroken block to be useful. Match the activity to the window size rather than forcing deep work into fragments where it won't survive interruption. See my mental math guide for a fragment-friendly daily drill routine.

How I Actually Watch My Own Schedule

Because my schedule is irregular, seeing my actual weekly hours - not my intended 1,260 minutes - matters more to me than a fixed daily routine would to a full-time aspirant. Karma Yogi's weekly heatmap shows exactly which days and times my sessions land, so I can catch drift, like a week of evenings quietly disappearing, before it becomes a pattern I only notice a month later. Start tracking your real weekly hours free.