How to Answer “What Do People Criticize About You?”

Somewhere in the multiverse of job interviews, there’s a hiring manager who asks this question and thinks,
“Ah yes, now I will learn the truth.” And somewhere else, there’s a candidate whose soul briefly leaves their body.
If that candidate is you: welcome. You’re in the right place.

“What do people criticize about you?” sounds like an invitation to roast yourself on company time. But it’s usually not.
It’s a test of self-awareness, coachability, and whether you handle feedback like a grown-up
(calmly, thoughtfully, and without launching into a courtroom-style defense).

Done well, your answer can make you look confident, reflective, and continuously improvingthree qualities employers
love almost as much as “can start Monday.”

Why Interviewers Ask This (And What They’re Really Listening For)

This question is a close cousin of “What’s your greatest weakness?” and “Tell me about a time you failed.”
The goal isn’t to catch you admitting you’re secretly a workplace supervillain. It’s to hear how you process criticism:

• Do you recognize patterns in feedback you’ve received?
• Can you own a real area to improve without spiraling into negativity?
• Do you take action (training, systems, practice) to get better?
• Can you stay professionalno blaming former coworkers, no “everyone else is wrong.”

In other words, they’re not asking, “What’s your flaw?” They’re asking, “When you’re not perfect (so… always),
what do you do about it?”

The One Rule That Makes This Question Way Easier

Choose a criticism that is real, not fatal to the role, and improving because of steps you’ve taken.
Your best answer shows growth: a weakness you’ve addressed, or are actively addressing, with specific actions and outcomes.

If humor fits your personality and the company vibe, a light touch can helpjust don’t use it to dodge the question.
Think “warm confidence,” not “comedy special.” (And yes: you should have a serious version ready, just in case.)

A Simple Framework That Works Almost Every Time

Here’s a structure you can use without sounding rehearsed or robotic:

1) Name the criticism (briefly, neutrally)

Keep it short. No long backstory. No dramatic sigh. Just the label.

2) Give context (why it shows up)

Explain the situation where it tends to appearwithout making excuses.

3) Show your fix (actions + results)

This is where you win. Describe what you changed, how you track it, and what improved.

Template you can adapt:
“I’ve gotten feedback that I sometimes [criticism], especially when [context].
I took that seriously and started [action]. Over time, it’s improvednow I [result].”

How to Pick the Right Criticism (Without Accidentally Torpedoing Yourself)

Use this quick filter before you choose what to share:

Step A: Avoid a core requirement of the job

If the role demands deep Excel skills, don’t say you struggle with learning tools. If it’s a sales job,
don’t pick “I’m uncomfortable talking to strangers.” Choose something adjacentnot essential.

Step B: Pick a behavior or skill, not a fixed personality label

“I’m lazy” is a personality claim and also… not ideal. “I sometimes over-polish before shipping”
is a behavior you can change with a process. Employers want evidence you can learn.

Step C: Skip the greatest hits of fake weaknesses

The classics: “I’m a perfectionist,” “I work too hard,” “I care too much.” These often land as disingenuous,
unless you make them concrete and show a real, measurable correction.

Step D: Anchor it in real feedback

The most believable answers come from reality: performance reviews, 360 feedback, a mentor’s input, or repeated
patterns you’ve noticed. “I heard this, I acted on it, here’s what changed” is a powerful story.

What Not to Do (Unless You Enjoy Chaos)

• Don’t say: “Nothing, people love me.” That reads as low self-awareness.
• Don’t blame: “My old team was toxic.” Even if true, it’s risky and unhelpful here.
• Don’t overshare: Keep it professionalthis isn’t therapy intake.
• Don’t get cute: “Chocolate” or “waking up early” usually misses the point.
• Don’t pick a red-flag flaw: chronic lateness, unreliability, dishonesty, conflict explosions, etc.

Strong Example Answers (That Sound Like a Real Human)

Below are examples you can customize. Notice how each one includes a specific behavior, a fix, and a result.

Example 1: “I used to over-focus on details.” (Great for analytical roles)

“I’ve received feedback that I can get a little too deep in the details when I’m trying to deliver high-quality work.
It showed up most when timelines were tight and I wanted to double-check everything. I addressed it by setting ‘definition of done’
criteria up front and adding mid-point check-ins so I don’t over-polish at the end. The result is I still maintain quality,
but I’m more predictable on deadlinesand my stakeholders get updates earlier instead of at the finish line.”

Example 2: “I used to say yes too quickly.” (Great for team-heavy roles)

“People have criticized me for taking on too much at oncemy instinct is to be helpful.
I realized that can create bottlenecks, so I started using a simple prioritization habit: I confirm deadlines,
impact, and tradeoffs before I commit. If it’s not urgent or aligned, I propose an alternative timeline or delegate.
That’s helped me protect delivery quality and communicate expectations more clearly.”

Example 3: “My feedback can be too direct.” (Great for leadership roles)

“Earlier in my career, I got feedback that my communication could be too blunt, especially in fast-moving situations.
The intent was always clarity, but I learned that delivery matters. I worked on it by using a ‘context + suggestion + check’
approachexplaining the why, offering a specific next step, then asking for their view. I’m still direct, but now I’m more
collaborative, and I’ve seen stronger buy-in and fewer misunderstandings.”

Example 4: “I struggled to delegate.” (Great for managers or project leads)

“I’ve been criticized for holding onto tasks longer than I should, especially when I know I can do them quickly.
I realized that limits team growth and scales poorly. I started delegating earlier with clear outcomes, and I set short
checkpoints so I’m available without hovering. That’s improved team ownership and freed me to focus on higher-impact planning.”

Example 5: “Public speaking made me nervous.” (Great for roles with presentations)

“I’ve been told I was quieter in larger group settings, especially early on. I took it seriously because communication is important,
so I practiced in lower-stakes settingsleading smaller updates, rehearsing with peers, and volunteering to present parts of projects.
Over time, it improved: I’m now comfortable running client-facing walkthroughs because I treat it like a skill to train, not a trait you either have or don’t.”

Handling the Follow-Up Question (Because It’s Coming)

If your interviewer is doing their job, they may ask:
“How did that criticism affect results?” or “What did you do specifically to change it?”

Prepare one short, concrete story using a mini STAR format:
Situation (where it happened), Task (what you needed to do),
Action (what you changed), Result (what improved).
Keep it tight60–90 seconds is plenty.

Make Your Answer Match the Role (This Is Where People Mess Up)

A “good” criticism depends on the job. A detail-obsessed tendency can be manageable in research or finance,
but painful in a rapid-response operations role. The Muse-style rule of thumb is simple:
pick a weakness that won’t derail performance in this role, and show you’re addressing it.

Before the interview, scan the job description and underline the top requirements. Then make sure your criticism
isn’t one of those underlined items. (Yes, this is the adult version of “don’t step on rakes.”)

A 10-Minute Prep Exercise That Pays Off

1) List three criticisms you’ve actually heard

Pull from reviews, feedback sessions, or patterns you’ve noticed. Don’t invent a weaknesspick a real one you’ve managed.

2) For each, write the “fix” in one sentence

Training, systems, tools, mentoring, new habitsanything that shows action.

3) Add one measurable signal

Examples: fewer rework cycles, improved turnaround time, clearer stakeholder updates, better project predictability,
stronger collaboration scores, fewer escalations, smoother handoffs.

4) Practice out loud

Write it, then speak it. Your goal is calm and confident, not memorized and mechanical.

FAQ: Quick Wins for Common Variations

“What if I truly can’t think of anything?”

Borrow reality. Review old feedback, ask a trusted colleague, or think about what you’ve had to work on.
Most interviewers won’t believe “none,” and it can come off as a lack of reflection.

“Should I admit something major?”

Generally, no. You’re not hiding the truthyou’re choosing the most useful example that demonstrates growth
without creating a big risk.

“Can I mention a criticism that’s actually a strength?”

Carefully. If you do, make it specific and show the downside and how you manage it. Otherwise it’s a cliché.

Conclusion: Turn the Question Into Proof You’re Coachable

“What do people criticize about you?” is uncomfortable on purpose. But it’s also a gift: it lets you demonstrate
the rare combo of confidence and humility. The winning recipe is simple:
pick a real critique, keep it professional, explain the steps you took, and show what changed.

That’s not just a good interview answer. It’s a strong career habit.

Experience Section (Extra ): What This Looks Like in Real Life

Let’s make this less theoretical. Below are five “workplace reality” snapshotscomposite examples based on common patterns
in offices, teams, and project rooms everywhere. If you’ve lived one of these, congratulations: you’re employable.
(And if you haven’t… please teach the rest of us your magical ways.)

1) The “Speed Demon” Who Left Stakeholders Behind

A project coordinator kept hearing, “You move fast, but I’m never sure where things stand.” Translation:
the work was happening, but updates weren’t. In interviews, they stopped defending their pace and started saying:
“I realized I was optimizing for execution, not visibility.” Their fix was simple: a weekly one-page status update,
clear owners, and a short risk section. Within a month, fewer surprise escalations happenednot because they worked more,
but because people felt informed. In an interview, that story screams: I take feedback, I build systems, I improve outcomes.

2) The “Nice” Teammate Who Couldn’t Say No

A marketing specialist was criticized for being “too accommodating.” Sounds pleasant, but it created chaos:
last-minute requests, scattered focus, and occasional missed priorities. They reframed it as boundary-setting:
“I used to default to yes. Now I default to clarifying.” Their new script:
“I can do A by Friday or B by Wednesdaywhich matters more?” Suddenly, they weren’t less helpful;
they were more strategic. Interviewers love this because it shows maturity, prioritization, and communication.

3) The Manager Who Tried to Be the Hero

A new manager got the classic critique: “You’re too involved.” They weren’t micromanaging out of ego;
they were anxious about results. The breakthrough was realizing that “ownership” doesn’t mean “doing.”
They began delegating outcomes, not tasks, and set two checkpoints: one early alignment meeting and one mid-course review.
Team performance improved, and so did morale. In interviews, the manager’s answer wasn’t “I care too much”
it was “I learned how to scale through people,” which is exactly what employers want to hear.

4) The Analyst Who Sounded Like a Robot (And Fixed It)

A data analyst was told, “Your insights are good, but your presentations are hard to follow.” Ouch. Also useful.
They didn’t pretend it wasn’t true. They learned a simple storytelling habit: lead with the decision,
then the evidence, then the recommendation. They also added one sentence to every slide:
“So what?” The next quarter, leaders started quoting their insights in meetings. That’s interview gold:
clear criticism, clear action, clear impact.

5) The High Performer Who Took Feedback Personally

This one is common and very human. A strong performer got defensive when criticizedbecause they cared.
The shift was learning to separate identity from behavior: “This feedback is about my approach, not my value.”
They began asking one question after feedback: “What would success look like next time?”
That question alone changed their relationships with managers and peers. In an interview, sharing this (briefly)
shows emotional intelligence and resiliencetwo traits that quietly power almost every great team.

If you notice a theme, it’s this: the best answers don’t pretend you’re flawless. They prove you’re adaptable.
Employers don’t hire perfectionthey hire progress.