The Engineer's Guide to Criticism: How to Separate Signal from Noise
Not all feedback deserves your attention. Here's how to tell the difference.
“I don’t think this is going to work.” I wanted to fight it. Explain. Justify. That instinct nearly cost me some of the best feedback I’ve ever received.
If you’ve led a team, shipped a product, or made any decision that mattered, you’ve heard some version of this. The blunt assessment. The unsolicited opinion. The critique that hits harder than it should.
My natural reaction used to be defensive. Protect the idea. Protect the work. Protect my ego, if I’m being honest. But over the years, I’ve learned to do something harder: listen first, react later. Because if the feedback makes the product better, makes the team stronger, makes me sharper, why would I fight it?
The problem is, not all criticism deserves that kind of attention. Some feedback is gold. Some is noise. And the skill isn’t just in receiving criticism, it’s in knowing the difference.
The Four Critics You’ll Meet
Not everyone who gives you feedback has the same intent. I’ve found it useful to recognize who’s actually talking.
The Vague Commenter. “It just doesn’t feel right.” “I’m not sure about this direction.” No specifics, no suggestions, no path forward. They might mean well, but there’s nothing to act on. If you can’t get them to clarify, move on.
The Attacker. This one makes it personal. “Classic mistake from someone who doesn’t get it.” It’s not about your work, it’s about you. Often, this is projection, their own fears, their own failures. Recognize it for what it is.
The Bad Actor. Rare, but real. Someone who wants to mislead you. A competitor seeding doubt. A toxic colleague undermining your credibility. Their goal isn’t your improvement. Don’t give them airtime.
The Seasoned Critic. This is the one you want. They’re direct, sometimes uncomfortably so. “Your onboarding drops people at step two. I almost left myself.” It stings, but it’s specific. It’s actionable. They’re not attacking you, they’re trying to make you better. These people are rare. When you find them, hold on tight.
Your Default Reaction is Probably Wrong
When criticism lands, most of us fall into one of these patterns:
Self-doubt. “Maybe I’m not cut out for this.” One piece of feedback spirals into questioning everything.
Dismissal. “They don’t have the full context.” You rationalize it away before even considering if it’s true.
Defensiveness. “Let me explain why you’re wrong.” You’re already composing counterarguments before they’ve finished talking.
I’ve been all three. Sometimes in the same conversation. The fourth option, openness, doesn’t come naturally. It has to be practiced.
The Framework: Listen, Wait, Ask, Act
Here’s what works for me now.
Listen. When someone gives you feedback, your only job is to absorb it. Don’t interrupt. Don’t explain. Don’t defend. Just take it in. This is harder than it sounds, especially when your brain is screaming to correct them.
Wait. Don’t respond in the moment. Sleep on it if you can. I’ve written replies I was glad I never sent. Emotion fades. What remains is usually the part worth paying attention to.
Ask. Before you decide whether the feedback is valid, ask questions. “Can you say more about that?” “What would you do differently?” This does two things: it gives you more information, and it turns a critic into a collaborator. Most people soften when they feel heard.
Act. Once you’ve filtered the noise, make a decision. Implement it, discard it, or park it for later. But don’t let it sit in limbo. Feedback that never gets processed is just noise you’re carrying around.
Don’t Sit On It
The worst thing you can do with useful criticism isn’t rejecting it. It’s acknowledging it and doing nothing.
You nod along. You say “good point.” And then you move on, unchanged. I’ve done this too. It feels safer than actually making the change, especially when the change is hard or threatens something you’re attached to.
But that’s the trap. Criticism isn’t a verdict. It’s data. And data is only useful if you do something with it.
The best engineers I know, the best founders, the best leaders, they’ve built feedback loops into everything. Their systems, their products, their teams. The ones who go furthest build that loop into themselves.
Got feedback? I’d love to hear it.