Tracking Interview Weak Spots Without Turning Preparation Into a Useless Spreadsheet

The problem

After a few practice rounds, a lot of people notice they are failing in similar places.

But instead of simplifying the diagnosis, they complicate everything.

They create:

• a giant spreadsheet
• a score for everything
• sixteen categories
• color, weight, priority, confidence, severity

Two weeks later, nobody wants to look at it anymore.

The system died.

Mental model

Think of it like this:

You do not need to manage your preparation like company operations. You need to see patterns clearly enough to decide the next practice session.

That is it.

If the tracking does not help you answer:

• where do I fail most?
• what is improving?
• what still repeats?
• what kind of practice makes the most sense now?

then it is too sophisticated for the value it gives back.

What is worth tracking

Instead of recording twenty things, start with four blocks:

1. Framing

Problems in this category:

• does not clarify scope
• jumps to the solution too early
• does not ask about constraints
• answers something different from what was asked

2. Structure and communication

Common problems:

• talks without a trail
• opens too many fronts at once
• does not close the reasoning
• sounds confused even when they know the topic

3. Technique and decision-making

This includes:

• technically weak solution
• poor comparison of alternatives
• weak modeling
• real lack of an important concept

4. Pressure and execution

This block covers:

• freezing while the clock is running
• losing clarity live
• speeding up too much
• spiraling after one mistake

These four boxes already solve a lot.

How to record without turning it into bureaucracy

For each round, try to keep only this:

• format: coding, design, debugging, behavioral
• dominant error: one main category
• short observation: what happened
• next adjustment: what to test later

Example:

• format: system design
• dominant error: framing
• observation: I started sizing the system before aligning scope and goals
• next adjustment: open with functional requirements, non-functional requirements, and rough volume

That is already enough to create useful history.

What to look for after 5 to 10 rounds

You are not looking for perfection.

You are looking for repetition.

Useful questions:

• which error appears most?
• in which format do I perform worse?
• under pressure, what does my problem turn into?
• am I improving in content but still failing in communication?

Sometimes the important insight is this:

My problem is not system design. My problem is starting any open-ended answer without structure.

That completely changes the training.

Common mistake: calling everything “lack of study”

This is one of the easiest ways to fool yourself.

You leave a bad round and write down:

• “I need to study more”

But that can hide:

• difficulty organizing the answer
• lack of prioritization
• poor time management
• nerves that break the explanation

When you call everything a technical gap, your practice becomes inefficient.

Common mistake: tracking too much

If your system takes too much effort to fill out, it will die fast.

Good rule:

• if it takes more than five minutes per round, it is probably too heavy

The tracking has to fit into real life.

A minimal model that works

You can use something like this:

1. round format
2. dominant error
3. one sentence about what happened
4. next-time adjustment
5. after the next round: improved or not?

That fifth item matters.

Because without it, you record weakness but never learn what you have already fixed.

Simple example

Suppose you have three rounds in a row:

• coding: talked too much before proposing a path
• debugging: opened too many hypotheses without prioritizing
• system design: listed too many options before choosing

That looks like different problems.

But the pattern underneath might be the same:

difficulty reducing complexity early.

That is the kind of reading that is worth gold.

Because now you do not train three separate problems.

You train one central skill.

What to do with what you discover

Every week, choose:

• one main pattern to attack
• one adjustment to test
• one format where it appears the most

Example:

• pattern: disorganized openings
• adjustment: always open with goal, constraint, and criterion
• target formats: coding and design

That is much better than trying to improve everything at once.

Interview angle

A strong candidate is not the one who never makes mistakes.

It is the one who can:

• identify the type of error
• correct it deliberately
• enter the next round less vulnerable to the same pattern

This kind of improvement comes much more from simple, consistent diagnosis than from a pretty spreadsheet.

In one sentence

Good weak-spot tracking gets simpler until only what helps you decide how to practice better tomorrow is left.