Impostor Phenomenon as Human Debt: A Challenge to the Future of Software Engineering
This position paper reframes the Impostor Phenomenon in software engineering as a form of "Human Debt" caused by systemic gaps in psychological safety and inclusion, arguing that addressing this unequal burden through cultural refactoring and allyship is essential for the field's sustainable future.
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
Imagine you are building a massive, complex skyscraper. In the world of software engineering, we are very good at fixing the building's structure. If a pipe leaks or a wire is loose, we call it "Technical Debt." It's a shortcut we took to finish a project quickly, but now we have to pay interest on it later to fix the mess.
But this paper argues that there is a second, invisible kind of debt that we are ignoring: "Human Debt."
Here is the breakdown of the paper in simple terms, using some everyday analogies.
1. The Problem: The "Impostor" Ghost
Many software engineers and researchers feel like frauds. They think, "I only got this job because I was lucky, not because I'm smart. Eventually, everyone will find out I'm a fake." This is called the Impostor Phenomenon.
Usually, people think this is just a personal problem—like a bad habit or a lack of confidence. But the authors say: No, it's not just in your head. It's a structural problem with the building itself.
The Analogy:
Imagine a gym where the equipment is broken, the lights are flickering, and the coach is constantly yelling that you aren't strong enough. If you feel weak and scared to lift weights, is that because you are weak? Or is it because the gym environment is designed to make you feel that way?
The paper says the "Impostor Feeling" is the result of a "systemic shortcut." For years, the software world prioritized speed and code over people's mental health. Now, we are paying the price.
2. Who Pays the Price? (The Uneven Bill)
Just like a storm damages a house unevenly, this "Human Debt" hits some people harder than others.
- The Data: The authors surveyed hundreds of researchers. They found that women, Black researchers, and people from the Global South feel this "impostor" pressure much more intensely than white men.
- The Analogy: Imagine a group of people hiking up a mountain. Everyone is tired, but some are carrying heavy backpacks filled with rocks (bias, lack of representation, toxic comments), while others are hiking with empty hands. The people with the heavy backpacks are more likely to feel like they don't belong on the mountain, even though they are just as capable.
3. The Cost of Ignoring the Debt
When you ignore a leak in your roof, the ceiling eventually collapses. When we ignore Human Debt, the software industry suffers in three ways:
- The "Cognitive Tax": Instead of solving hard coding problems, brilliant minds spend all their energy worrying, "Do I belong here?" It's like trying to run a marathon while carrying a backpack full of bricks.
- Risk Aversion: Because they are afraid of being "exposed" as frauds, people stop trying bold, crazy, innovative ideas. They stick to safe, boring tasks. This slows down the progress of the entire field.
- Brain Drain: Talented people, especially those from minority groups, get tired of the stress and leave the field entirely.
4. The Solution: "Refactoring" the Culture
In software, "refactoring" means cleaning up messy code to make it work better without changing what it does. The authors say we need to refactor our culture. We can't just tell people to "toughen up." We have to fix the system.
Here are the four main fixes they propose:
A. From "Lone Wolf" to "Pack"
- The Problem: The myth of the "Solitary Genius" (the guy who codes alone in a dark room and saves the day) makes people feel isolated.
- The Fix: We need Collaborative Support. Imagine a study group where everyone admits, "I don't get this either." Senior experts need to say, "I failed a lot before I succeeded." This breaks the illusion that everyone else is perfect.
B. Clear Rules vs. The "Black Box"
- The Problem: Right now, getting a job or a grant feels like a lottery. The rules are hidden, and decisions feel arbitrary. This fuels the fear that you only got in because of luck.
- The Fix: Radical Transparency. We need clear, public scorecards (rubrics) that show exactly how decisions are made. If you know the rules, you stop feeling like a fraud and start feeling like a player.
C. The "Ally" Safety Net
- The Problem: When someone faces bias, they often have to fight alone.
- The Fix: Active Allyship. People with privilege (like senior white men) need to speak up. If they see a colleague being treated unfairly, they need to say something. It's like having a safety net under a trapeze artist; you don't jump, but you make sure they don't fall.
D. Humans, Not Machines
- The Problem: The industry treats researchers like machines that just produce code and papers. It ignores that they have families, kids, and mental health needs.
- The Fix: Work-Life Integration. We need counseling services, family-friendly meeting times, and a culture that says, "It's okay to be a human being with a life outside the lab."
The Bottom Line
The authors are sending a warning: We are running out of money to pay this debt.
If we don't fix the culture, the "interest" on this debt (burnout, anxiety, and lost talent) will become too high to pay. To build a better future for software, we have to treat our people with the same care and attention we give to our code. We need to stop building systems that make people feel small and start building environments where everyone feels they truly belong.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.