The First Hurdle in Interview Prep: Not Grinding Problems, Not Writing STAR Stories, but Shattering Your Self-Protective Shell

During a mock interview the other day, a friend suddenly paused. He looked a bit unwilling, yet spoke very calmly: "Am I just not suited for interviews? I've done a lot, but when I talk about it, it always feels like I haven't done anything."

I know this line all too well. I've said it myself.

We tend to think it's because our expression isn't good enough, or our project highlights aren't enough, or "I'm just not the type who's good at interviews." These sound like reflections, but they're actually a form of self-comfort: as long as I say "I'm not good at it," I don't have to dig deeper, don't have to keep facing the stuck moments when I can't explain clearly, don't have to bear the frustration of failing again.

But interviews aren't something you pass by protecting yourself.

We prepare so many STAR stories, project highlights, technical details, yet still can't speak in a way that earns trust. Maybe it's not that we haven't tried hard enough, but that all that effort is separated by an invisible "protective shell."

Sometimes we don't even realize we've already hidden inside that shell.

Many people, when talking about their projects, unconsciously fall into this template:

"I first did A, then encountered B, so I adjusted to C, and finally the project launched with good results."

It sounds like the work got done, but the whole process contains no choices, no hesitation, no basis for judgment. The listener has no way of knowing: if someone else had done it, would it have been different? How did you decide at the time? Why did you make that decision? Did you consider other possibilities?

We often say "I'm not good at expressing myself," but it's not that we can't speak. It's that the content we present doesn't include the part that most deserves to be heard: the decision-making process.

For example, we might say:

"That time we did a data cleaning task, and I found some metrics didn't match. I added a few SQL fix rules and changed the task dependencies, and then the data was correct."

But if we tell it differently, with the same tone and no fancy vocabulary, we can let the other person hear more of our thinking:

"That time we were about to launch a new metric, and QA found several values didn't match during testing. I spent a few days tracing it and found that the concatenation logic for fields from several source tables was inconsistent. I didn't just patch the data directly. Instead, I first aligned the field definitions with the data owner, added a cleaning layer upstream in the DAG, and also set up validation logs to prevent similar issues later."

No need for too much jargon, no need to "brag," but this kind of expression makes people think: this person's thinking is clear, and I could work with them.

Why do we develop this shell?

Most people don't hide on purpose. They unconsciously turn their expression into a defensive posture.

Maybe it's just that no one ever asked us to explain why we did things a certain way, so we got used to reporting progress without sharing our reasoning. Other times, too many interview experiences taught us that "the more you say, the more mistakes you make, so it's safer to say less."

Going deeper, we don't want to break the self-narrative of "I'm still pretty good."

As long as we say "I just can't present well," we preserve a decent image: capable but low-key; skilled but not good at packaging.

This posture looks humble, but it's actually dangerous. It keeps us from facing a possible truth: it's not that we can't present, but that we haven't realized which parts we still can't explain clearly.

And that, precisely, is the thickest shell between us and our next stage of growth.

Admitting this shell exists is quite uncomfortable.

Especially when we've already been recognized, relied upon, even leading people at work, and then we return to the interview table and have to explain "how you think" all over again. It's really hard.

We unconsciously resist that feeling of dissecting our process.

Because once we admit we can't explain clearly, we have to practice again. Once we admit we're still using process as a substitute for judgment, we have to go back and break down our projects, find the places where we didn't think clearly but forced our way through. Once we admit we're still in the shell, we have to accept that we're "not ready yet."

This takes a bit of courage. It might even require overturning our past safe expression patterns.

But it's precisely this overturning that is the true starting point of being ready.

If we don't break this shell, we'll stay stuck in "saying a lot, but no one remembers."

We're not lazy. We really have prepared a lot. But if the protective shell is still there, what we say is like being behind a pane of glass: you can hear the voice, but you can't hear the person inside clearly.

Interviewers don't want to hear an assembly line or a list of operations. They want to hear the thinking process behind the decisions you made when facing problems.

An expression that earns trust is often not complicated, but it contains choices, trade-offs, and the awareness behind them: was it you who proposed it, or were you assigned? Did you look at other options? What did you do to make the solution more solid? How did you pull people in to collaborate, anticipate risks, and break down complex things into manageable pieces?

It's not about bragging, but about making the other person believe: "If I handed this to you, I'd be willing to work with you."

If we don't talk about these things, we can't build that trust.

Shattering this shell can start with a small exercise.

Pick a familiar project, not too new, not too flashy. Close your eyes and recall the moment you made a decision: what options were in front of you? Which one did you choose in the end? Why? Did you worry about failure? What preparations did you make? Looking back now, is there anything you would do differently?

Record yourself saying these things, then listen once. Record again. Keep going until you feel: "This time I'm not reciting a log, but telling a decision."

You can also find a colleague or friend to do a mock interview. It doesn't have to be formal. Just have them ask: "Why did you do it this way?" "What directions did you consider?" "Was there any disagreement?" Then explain it to them.

Every time you clearly explain a judgment, you're wearing down that shell bit by bit.

It's not that we're bad at expressing ourselves. It's that we never realized we needed to express these things before.

Shattering the protective shell doesn't mean turning ourselves into storytellers, nor forcing ourselves to package or market ourselves. It means restoring the "thinker" and "chooser" that has always existed within us.

We haven't never made judgments. We just haven't spoken them out loud yet.

We may still not speak smoothly now, but as long as we're willing to practice, willing to break things down, willing to smash that self-narrative of "looks good but can't explain clearly," we'll get closer and closer to the version of ourselves who can speak clearly and earn trust.

In the next article, we'll break down a very common question:

Why is it that we prepare ten STAR stories, but the interviewer doesn't remember a single one?

Maybe it's not that the stories are bad, but that we didn't say the one sentence that mattered most.

See you in the next article.

Public account comments: This involves the difference in mindset between "give me the problem" vs "give me the solution." The latter answer shows your ability to transform a problem into a solution. The more senior you are, the more you need to demonstrate this ability. Many people who are used to working in large companies often work directly on solutions and lack this step of thinking in their daily work.