The interviewer leaned forward, the light from the 19th-floor window catching the edge of his glasses so I couldn’t see his eyes. He wasn’t looking at my resume anymore. He had printed it out-an ancient ritual-and it sat there between us, a single sheet of paper covered in bold verbs and aggressive percentages.

“I see here,” he said, tapping a finger on the third bullet point, “that you drove a 29% improvement in operational efficiency. That’s a very clean number. It looks great on a slide.”

I felt a small surge of pride. That 29% was my shield. I had polished it for weeks. I had defended it in three different rounds of internal reviews before I even left my last job. I knew the math. I knew the denominator. I was ready to talk about the denominator for 19 minutes straight if he let me.

Then he dropped the floor out from under the conversation.

The Anatomy of a Clean Digit

“But tell me,” he whispered, “if I were to call the engineer who actually sat in the chair and wrote the scripts for this project-the one who stayed until 9:59 PM on a Tuesday because the database wouldn’t scale-what would they say about your role in that 29%? Would they recognize that number? Or would they tell me a completely different story?”

The silence that followed was exactly 9 seconds long, but it felt like a decade. On my side of the table, the room went quiet in a way that suggests a total loss of cabin pressure. I realized, with a sudden, sickening clarity, that I didn’t know what the engineer would say. I had compressed that engineer’s sweat, their 219 cups of coffee, and their brilliant, frantic workaround into a single, sterile digit. I had polished the story until the story was gone.

The Career Refrigerator

Earlier that morning, I had been standing in front of my open refrigerator, throwing away a jar of Dijon mustard that had expired in 2019. It looked like mustard. It was still yellow. If you put it on a sandwich, it would technically fulfill the role of a condiment. But it was dead. The tang was gone; the heat had evaporated into a dull, vinegar-soaked memory. Our professional stories go the same way.

We keep them in the back of the “career fridge” for years, and every time we pull them out to put them on a resume, we scrape off a little more of the substance to make them fit the current fashion. By the time we get to the interview, we aren’t serving a meal. We’re serving a list of ingredients that no longer taste like anything.

Michael B.K. is what I call a digital archaeologist. He doesn’t look for pottery shards or ancient coins; he looks for the “why” buried in the metadata of corporate failure. I watched him once spend 49 minutes looking at a single Jira ticket from a project that had been labeled a “Total Success” by the PMO.

Michael B.K. believes that every metric is a ghost. It is a haunting of a reality that we are no longer allowed to talk about. We have trained an entire generation of managers and directors to lead with outcomes and bury the messy, vibrating substance that made those outcomes possible. We tell them to “speak the language of business,” which apparently means speaking in a way that suggests no human beings were involved in the production of value.

But when you sit across from a real human being in an interview, the “language of business” sounds like a dialect of silence.

The Problem with the 29%

The problem with the 29% improvement is that it’s a ceiling, not a floor. It’s the end of the thought. When you say, “I improved X by 29%,” you are signaling to the interviewer that the conversation is over. You have given them the answer. But an interview isn’t a math test; it’s an investigation into your character under pressure.

If you give the answer first, you’ve robbed them of the joy of watching you solve the problem. You’ve handed them a trophy without letting them see the race.

I’ve seen this happen 129 times in the last year alone. A candidate starts a story, and you can see them navigating toward the metric like a ship seeking a lighthouse in a storm. They are terrified of the “messy middle.” They are afraid to admit that for 59 days, they had no idea if the project was going to work.

They skip over the part where the API integration failed 9 times in a row. They omit the fact that they had to convince a skeptical VP-someone who had 29 years of experience and a deep-seated hatred for new cloud architectures-to give them one more week.

The STAR Machine

The “STAR” method (Situation, Task, Action, Result) was supposed to be a framework for clarity, but it has become a machine for mediocrity. It has turned our experiences into a series of identical, three-bullet shapes. Every candidate now sounds like every other candidate. “I saw a problem (S), I was told to fix it (T), I did a thing (A), and look, a 29% increase (R)!” It’s a Mad Libs version of a career.

If you want to actually connect, you have to be willing to talk about the 19 things that went wrong before the one thing that went right. You have to be willing to admit that the 29% improvement was actually a miracle of duct tape and late-night compromises.

It’s about realizing that the “Result” in the STAR method is the least interesting part of the story. The “Action” is where you live. The “Action” is where the interviewer decides if they actually want to spend 39 hours a week in a room with you.

Texture vs. Polish

I remember a candidate who broke the mold. I asked her the same question: “What would the team say?”

She didn’t blink. She didn’t look at her resume. She leaned in, and her voice dropped an octave. “The lead engineer would say I was a massive pain in his neck for 79 days,” she said. “He’d say I kept asking why we were building a feature that only 9% of our users had ever requested. He’d say that I made him redo the data schema twice because I knew we’d hit a bottleneck in six months.”

“And he’d say that when the 29% improvement finally showed up on the dashboard, I bought the whole team dinner and didn’t take a single ounce of credit for the code.”

That was the best answer I’d heard in 299 interviews. Why? Because it was textured. It had sharp edges. It wasn’t a polished stone; it was a piece of raw ore. She wasn’t afraid of the engineer’s perspective; she owned it. She understood that her value wasn’t in the number, but in the social and technical friction she managed in order to reach that number.

We are so afraid of being seen as “difficult” or “messy” that we have become invisible. We have scrubbed our professional identities until they are as sterile as a hospital corridor. We think we are making ourselves “marketable,” but we are actually just making ourselves replaceable.

If your only value is a 29% improvement, the company will eventually find someone else who promises a 39% improvement, and they will replace you without a second thought. But if your value is the specific, idiosyncratic way you handle a crisis-the way you navigate the 109 conflicting requirements of a product launch-you become a singular asset. You become a story they can’t find anywhere else.

The Agency of the Gaps

The tragedy is that the data itself often hides these stories. We live in an era of “data-driven decisions,” but data is a terrible storyteller. Data tells you that 99 people walked through a door; it doesn’t tell you why 29 of them were crying and 19 of them were looking for a bathroom.

When we rely on metrics to tell our career stories, we are giving up our agency. We are letting the dashboard take the credit for our humanity.

I think back to that mustard jar I threw away. The reason it was still in my fridge was because I liked the idea of having Dijon mustard. It felt like something a “together” person would have. But the reality of the mustard-the actual taste and utility of it-had been ignored for years.

The Truth in the Dark

The price of a clean metric is often the truth of what happened in the dark. If you want to stand out, stop talking about the 29%. Talk about the 71% of the project that was a total disaster until you figured out how to fix it.

Talk about the time you had to tell your boss that the plan was wrong. Talk about the engineer who stayed late, not because of the metric, but because you made them feel like the work mattered.

The “digital archaeologist” in the interview chair is digging for the person, not the percentage. They want to know what happened in the gaps between the bullet points. They want to know if you have any “heat” left, or if you’re just another jar of expired mustard sitting in the back of the fridge, hoping no one notices you’ve lost your tang.

I eventually answered that interviewer’s question. I didn’t give him another number. I told him about the time the lead engineer and I sat in a parking lot at 10:29 PM, both of us exhausted, arguing about a load balancer.

I told him how we finally stopped arguing and started listening to each other. I told him that the 29% wasn’t a “driven improvement”-it was a hard-won peace treaty.

He didn’t ask about the denominator again. He just nodded, wrote something down in the margin of my resume, and asked when I could start. It turns out, he wasn’t looking for a calculator. He was looking for a person who knew how to survive a Tuesday night.

We forget that every outcome is just a tombstone for a process. If you only show the tombstone, people will assume the process is dead. But if you show the life-the messy, unformatted, 29-different-versions-of-the-truth life-then the metric finally starts to mean something.