How to Talk About Imposter Syndrome at Work in English

Imposter syndrome — the persistent feeling that you don’t deserve your role or achievements despite evidence otherwise — is common enough that most managers have encountered it before, and naming it directly is often more productive than hiding it. This guide gives you the English for raising it with a manager or mentor and reframing the feeling constructively.

Naming the Feeling

Be direct rather than vague about what you’re experiencing.

• “I want to be honest — I’ve been dealing with a fair amount of imposter syndrome lately, especially since joining this team.”
• “I know objectively that my work has been solid, but I keep feeling like I’m going to be found out as underqualified.”
• “This isn’t about a specific mistake — it’s more a persistent feeling that I don’t belong at this level yet.”

Asking for Concrete Feedback

Request specific, evidence-based reassurance rather than general encouragement.

• “Could you give me honest feedback on where I actually stand, even if it’s not entirely positive? I’d rather have something concrete to work with.”
• “Is there a specific area where you think I’m underperforming, or is this feeling not reflected in how you actually see my work?”
• “I’d find it more useful to hear specific examples of what’s going well than general reassurance.”

Reframing the Comparison

Address the tendency to compare yourself to others’ visible strengths only.

• “I think I’ve been comparing my day-to-day struggles to other people’s highlight reel — can you help me understand what their ramp-up actually looked like?”
• “Did [colleague] also take time to get comfortable with this codebase, or did they really pick it up as fast as it seems?”
• “I know I’m probably underestimating how normal it is to feel behind at this stage — is that consistent with what you’ve seen from others?”

Asking for Support

Request concrete mechanisms, not just a one-time conversation.

• “Would it help if we set a recurring check-in specifically to talk through how I’m progressing, separate from regular status updates?”
• “Is there a mentor on the team who’s further along that I could talk to about how they got past a similar phase?”
• “I’d like to set some concrete milestones so I have something objective to measure my progress against, instead of relying on how I feel day to day.”

Normalizing It With Peers

Sometimes naming it to a trusted peer is as valuable as raising it with a manager.

• “I want to be honest with you — I’ve been feeling like I’m behind everyone else here, even though I know that’s probably not accurate.”
• “Did you go through something similar when you joined? I’d find it helpful to hear how you got past it.”

Vocabulary Reference

Key Takeaways

• Name imposter syndrome directly rather than describing it vaguely — most managers have encountered it before.
• Ask for specific, evidence-based feedback instead of general reassurance, since concrete examples are more convincing.
• Challenge the tendency to compare your daily struggles to other people’s polished, visible achievements.
• Request concrete support mechanisms, like a recurring check-in, a mentor, or measurable milestones.
• Sharing the feeling with a trusted peer can normalize it just as effectively as raising it with a manager.

Navigating Nuance: Specific Phrasing for Non-Native Speakers

Imposter syndrome is a universal experience, regardless of your background or fluency in English. The key isn’t just understanding the concept – it’s communicating it effectively and confidently within a professional setting. For non-native speakers, this can feel particularly challenging due to subtle differences in phrasing and expectations around expressing vulnerability or seeking support. Let’s focus on building vocabulary and practical sentence structures that will help you articulate your feelings clearly and respectfully during conversations with colleagues, managers, and mentors.

One area where many people stumble is framing questions for reassurance. Simply saying “I don’t feel confident” can sound overly negative and might not elicit the helpful response you’re hoping for. Instead, try phrases like, “Could we perhaps discuss my contributions to this project? I’m eager to ensure I’m meeting expectations and delivering value.” Or, when receiving a critical code review comment – something like, “Thank you for pointing out this area; could you elaborate on the specific reasoning behind this suggestion so I can fully understand how best to move forward?” This demonstrates openness to feedback and a desire for clarification. Similarly, if a colleague praises your work, acknowledging it with “I appreciate that feedback, it’s encouraging to hear” is more polished than a simple “Thank you.”

Consider the language used in PR descriptions – these are often opportunities to subtly address feelings of self-doubt. Instead of writing “Implemented feature X,” which can sound overly assertive, try something like, “Developed and implemented feature X, focusing on robust testing and adhering to established coding standards; I’m continually seeking feedback to ensure its optimal performance.” The addition of phrases such as ‘seeking feedback’ subtly addresses the underlying feelings without directly stating ‘I don’t know if I did this right.’ It shows a commitment to continuous improvement.

Finally, remember that demonstrating self-awareness is valuable. If you feel overwhelmed or uncertain, acknowledging it briefly and proactively can be incredibly powerful. A simple message in Slack after a particularly challenging code review might read: “Just wanted to acknowledge that I’m feeling a bit overwhelmed with this task – I’m taking a step back to reassess my approach and would appreciate any guidance on prioritizing.” This shows you’re recognizing your limitations and actively seeking support, which is often perceived positively in a professional environment. It’s about shifting the focus from feeling like an imposter to demonstrating a proactive and thoughtful approach to your work.