Spreadsheet Problem Tracker vs Weekly Transfer Mocks
A lot of candidates run interview prep out of a spreadsheet problem tracker: one row per problem, with columns for pattern, difficulty, date solved, time taken, "needed a hint?", and a date to revisit. It is calm, cheap, and satisfying to fill in. The other habit is weekly transfer mocks: once or twice a week, one fresh problem you have never seen, a timer set to your real round length, narration out loud, a forced freeze-and-recover, and a dry-run before you say "done."
Both are about measuring progress. They measure different things. The useful question is narrower: when does a spreadsheet tracker beat weekly transfer mocks—and when does the reverse happen?
This is a workflow comparison, not a review of any spreadsheet app or template. Trackers vary from a five-column sheet to an elaborate dashboard. What stays stable is the difference between a record of what you practiced and a test of whether that practice shows up under live-round conditions.
At a glance
| Category | Spreadsheet problem tracker | Weekly transfer mocks (Luna side panel optional) |
|---|---|---|
| What it measures | Volume, coverage, revisit schedule | Whether skills carry to an unseen problem |
| Session shape | Solve, then log a row | One fresh prompt, full round length, narrated |
| Feedback | Columns you chose to track | Self-postmortem: plan, freeze, pacing, dry-run |
| Environment fidelity | None by itself—it is a log | High for "new problem, clock running, talking" |
| Best for | Organization, spaced review, spotting pattern gaps | Pacing, audible plans, freeze recovery, transfer |
| Main tradeoff | Rows can grow while live performance stays flat | Tiring; fewer data points per week |
What a spreadsheet problem tracker looks like
A typical tracker workflow:
- You add a row each time you finish a problem: name, pattern, difficulty, date.
- You note how long it took and whether you needed a hint or the solution.
- You set a revisit date for anything you could not solve cleanly.
- Once a week you sort by pattern and see where the gaps are.
- Closer to the loop, you still need some evidence that solved rows turn into a calm live round.
Honest strengths. A tracker turns a fuzzy goal ("get better at DS&A") into something you can see. It shows which pattern families you have barely touched, which problems you keep needing hints on, and whether you are actually revisiting old mistakes. Spaced revisits are one of the more reliable ways to make a pattern stick, and a revisit-date column makes them easy. It is also free, private, and works with any problem source. For candidates who lose track of what they did last week, a tracker alone can be a big upgrade.
Honest limits. A tracker records what happened in practice conditions—often untimed, silent, with notes open and the problem title already hinting at the pattern. A row that says "solved, 22 minutes" does not tell you whether you could restate, plan out loud, and recover from a wrong first idea with someone watching. Rows also reward volume, so it is easy to drift toward problems you can finish quickly. And a growing sheet can feel like readiness when it mostly measures effort.
When a spreadsheet tracker wins: you are early in prep and need coverage; you forget what you practiced; you want a spaced-review schedule; or you need to see which pattern families are missing before your loop.
What weekly transfer mocks look like
Weekly transfer mocks flip the polarity: fewer sessions, each one shaped like the real round.
- Once or twice a week, pick one fresh problem from a pattern family your tracker says you have practiced. Do not look at its tags first.
- Set the timer to the length of your real round, if the recruiter shared it. Open the surface you will actually use.
- Restate the problem out loud, ask clarifying questions, and say a two-line plan before coding.
- Narrate while writing. Force one freeze around the middle—hands off, three breaths—then restart out loud.
- Dry-run three cases before you say "done."
- Write a one-sentence postmortem: where the plan, pacing, or narration broke.
Optional companion: Luna Interview is a Chrome extension framed as a practice / calm side panel—not a substitute for knowing the material, and never an "undetectable" live cheat. Keep it beside the pad while you own the plan, the code, and the narration.
Honest strengths. Transfer. A fresh, timed, narrated problem is the closest solo check of whether your tracked practice holds up when the pattern is not labeled and the clock is running. It exposes the gaps a tracker cannot see: a silent first five minutes, a plan that falls apart at the first edge case, a dry-run you never reach. Forced freeze recovery rehearses the moment that sinks strong candidates. And because it is weekly, it gives you a steady signal without eating every evening.
Honest tradeoffs. One or two mocks a week is a small sample—a single bad session can be noise. Full-length mocks are tiring. And if the fundamentals are missing, a mock turns into a long stall that teaches less than a slow, logged practice problem would.
When weekly transfer mocks win: your interview is within a few weeks; your tracker looks strong but live rounds go badly; you go quiet when the first idea fails; or you keep running out of time before the dry-run.
Decision table for candidate situations
| Your situation | Prefer spreadsheet tracker | Prefer weekly transfer mocks |
|---|---|---|
| Don't know which patterns you have covered | Strong fit—sort by pattern | Later, to test the covered ones |
| Hundreds of rows, still freezing live | Keep logging lightly | Strong fit—fresh narrated reps |
| Keep forgetting problems you solved | Strong fit—revisit dates | Light |
| Loop booked in two weeks | Log mock results as rows | Primary lane—two mocks a week |
| Always run out of time on dry-runs | Track time per problem | Strong fit—full-length pacing |
| Only 30 free minutes on weeknights | Strong fit—one problem, one row | Save mocks for weekends |
| Bad mock left you discouraged | Look at the trend, not one row | One more mock before judging |
A fair practical method (combine both in one week)
Do not pick by which one feels more productive. Let the tracker choose what to test, and let the mocks tell the tracker the truth.
Tracker days (three or four short sessions): Work and log problems as usual. Add two columns if you do not have them: "solved without hints?" and "could I explain it out loud?" Set revisit dates for anything that misses either.
Mock days (one or two sessions): Pick a pattern family your tracker marks as covered. Choose one fresh problem in it without reading the tags. Timer at your real round length, restate and clarify out loud, two-line plan, narration while writing, a forced freeze around the middle, three dry-run cases. Keep a calm practice side panel beside the pad if you use Luna. Log the mock as its own row type with three checks: plan said within the first few minutes, narration kept going after the freeze, dry-run done before time ran out.
End of week: Compare the "covered" patterns with the mock rows. Any family that looks covered on paper but failed in a mock goes back into the revisit queue. Many candidates keep both—the tracker for coverage and review, weekly mocks as the honest test.
Common mistakes / when NOT to use each
Skip tracker-as-readiness when your row count is the main thing you report to yourself. A big sheet is a common false summit. Also skip logging problems you solved by reading the solution as "done"—mark them for revisit instead.
Skip mock theater when you pick problems you already logged, pause the timer when it gets hard, or check the tags first. Also skip any practice-tool framing that promises stealth help in a real employer interview—that is the wrong goal and the wrong integrity bar.
For both: solutions and AI are for review and postmortems, not mid-mock rescue if you are training transfer. The skill is your plan and your code, explained out loud, on a problem you have not seen.
Soft close
If your bottleneck is calm practice beside the pad you will actually use—timed prompts, narration, freeze recovery—Luna Interview is a Chrome side panel built for that practice loop, not for cheating or replacing study. Soft trial path: https://lunainterview.xyz/
Use a spreadsheet tracker when organization and coverage are the bottleneck. Use weekly transfer mocks when the question is whether all those rows hold up live. The offer goes to the candidate who can talk through a problem they have never seen—not the one with the longest sheet.
Rehearse with an AI interview copilot, then browse commonly reported interview questions.