A Quasi-Experimental Evaluation of Coaching to Mitigate the Impostor Phenomenon in Early-Career Software Engineers
This quasi-experimental study evaluates a structured group coaching intervention for early-career software engineers and finds that while it modestly reduced impostor phenomenon feelings, improvements in both treatment and control groups suggest that contextual and temporal factors may have a stronger influence than the intervention itself.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
🎭 The "Imposter" in the Room
Imagine you are a new software engineer. You're building cool apps, fixing bugs, and getting things done. But deep down, you have a nagging voice whispering: "You're a fraud. You got lucky. If anyone really knew how you think, they'd fire you."
This is called the Impostor Phenomenon. It's like wearing a mask that says "I'm an expert" while your brain screams, "I'm just faking it!" This is super common in tech because the field changes so fast, and everyone expects you to be a genius.
🧪 The Experiment: Can a "Talk Session" Help?
The researchers wanted to see if group coaching (a structured series of talks with a professional guide) could help these engineers take off the mask and feel more confident.
They set up a little experiment with 20 young engineers working on two real-world projects (one team was automating energy diagrams, the other was predicting oil spills).
- Team A (The Treatment Group): Got the coaching sessions first.
- Team B (The Control Group): Waited their turn. They kept working on their projects without the coaching for a while, just to see what happened naturally.
They measured how much they felt like "frauds" (using a standard test called CIPS) and how happy they felt before, during, and after the sessions.
📉 The Twist: The "Waiters" Won
Here is the surprising part. The researchers expected Team A (the ones getting coaching) to feel much better than Team B.
What actually happened?
- Team A did feel a little better after coaching. Their "impostor" scores went down a tiny bit.
- Team B (the ones waiting for coaching) actually felt much better even though they hadn't had the sessions yet! Their scores dropped significantly just by doing their regular work.
It was like giving Team A a special vitamin to cure a headache, only to find out Team B's headache went away just because they drank some water and took a nap.
🔍 Why Did This Happen? (The Detective Work)
The researchers dug into the "why" using observation notes and team dynamics. They found three main reasons why the "waiting" team improved so much:
The "Project High" (Success Breeds Confidence):
Imagine you are learning to ride a bike. At first, you are wobbly and scared (Impostor Syndrome). But once you actually ride down the hill without falling, you feel like a pro!
Both teams were working on real projects. As they finished tasks and saw their code work, their natural confidence grew. The success itself was the best medicine, not the coaching.The "Secret Sauce" of Team B:
Team B had a hidden advantage. Before the study even started, they had already developed a culture where they talked openly, gave kind feedback, and didn't judge each other harshly. They were already practicing "psychological safety."
It turns out, a supportive team environment is often more powerful than a formal coaching session. Team B was already doing the "coaching" work naturally by just being good teammates.The "Mirror Effect" (Just Asking the Questions):
The engineers had to fill out surveys about their feelings and confidence four times.
Imagine you are asked, "How confident are you today?" five times a week. Eventually, you start thinking about your confidence more. Just thinking about the problem (reflection) can sometimes start to fix it. The act of measuring their feelings might have helped them realize, "Hey, I'm actually doing okay."
💡 The Big Takeaway
The study concludes that while coaching is nice and can help you reflect, you don't necessarily need a formal class to stop feeling like a fraud.
In the world of software engineering, the best way to cure Impostor Syndrome might be:
- Doing the work and seeing your own success.
- Working in a team that is kind, open, and supportive.
- Talking about feelings casually, rather than waiting for a scheduled "therapy hour."
The Analogy:
Think of Impostor Syndrome like a plant that is wilting. The researchers thought they needed to bring in a special gardener (the coach) to save it. But they discovered that the plant actually started thriving because the sun came out (project success) and the soil was already rich (a supportive team). The gardener helped a little, but the environment did the heavy lifting.
🚀 What Should We Do?
Instead of just hiring coaches for everyone, companies should focus on building teams where people feel safe to make mistakes and ask for help. If the team culture is good, the "impostor" feelings often fade away on their own.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.