Entering the world of software, whether as a tester, developer, or in a facilitator role, means stepping into a field that profoundly shapes how we live, and one that evolves at a relentless pace. With its scale, influence, and constant innovation, it’s only natural to feel a sense of inferiority or self-doubt.
Starting out as a developer myself and then quickly shifting into a tester role, I experienced firsthand how the perceived differences between these roles can foster feelings of inferiority, whether stemming from within or, at times, subtly reinforced by developers themselves.
Imposter syndrome is that nagging sense of self-doubt and not feeling ‘good enough,’ even when there’s plenty of evidence to the contrary. As someone working in testing, especially in SDET roles where you’re responsible for ensuring software quality through rigorous, often invisible work, it’s easy to start questioning your place in the team. You begin to wonder if you’re doing enough, if your skills are valid, or if you really belong. And when that mindset sets in, it doesn’t just affect your work—it chips away at your confidence and well-being too.
How It Shows Up in Testing Roles
From my own experience—and from speaking to others in similar roles—imposter syndrome tends to sneak in through a few familiar doors when you’re working as an SDET:
Comparison with Developers – It’s easy to fall into the trap of measuring your worth against developers. You start believing that because you’re not writing production code full time, your work somehow holds less value or isn’t as technically demanding. That kind of thinking sticks with you and can make it hard to see the real impact you’re making.
Fear of Failure – As testers, we’re expected to find what others miss, to catch the things that might break the product. That’s a lot of pressure. When you feel like you’re under a microscope, every missed bug or slip-up can start to feel like proof you don’t belong, feeding a fear that you’re not good enough.
Lack of Recognition – A lot of what we do as SDETs is invisible when things go well. And while that’s part of the job, it can also feel isolating. You begin to question if anyone sees the value in what you bring, and when you don’t hear that recognition, it makes it easier for those imposter feelings to grow.
Working Through It: Strategies That Help
Overcoming imposter syndrome isn’t about flipping a switch, it’s something you learn to work through over time. Here are a few things that have helped me, and that I’ve seen help others in similar roles:
Recognise Your Achievements – It’s easy to focus on what you haven’t done yet, but it’s just as important to look back at what you have accomplished. Every bug caught, every problem solved, every sprint survived—those are wins. However small they might feel, they add up, and they matter.
Embrace Continuous Learning – This one is huge – no one knows everything, especially in tech. SDET roles constantly evolve, and that’s part of the deal. It’s okay to not know something—what matters is your willingness to learn. See the gaps not as flaws, but as opportunities to grow. From my experience, the process of transitioning from feeling like an impostor to feeling less like an impostor gives me the confidence that I can do it again, and again when required, and as mentioned above, should be recognised as an achievement
Seek Support and Feedback – You’re not alone, even when it feels like it. Whether it’s mentors, colleagues, or even people online, there’s a lot of value in talking it out. Getting honest feedback—not just praise or critique—can be a game changer in seeing your strengths clearly and understanding where to focus your energy.
Practice Self-Compassion – We’re often our own worst critics. If a friend told you they were struggling with confidence, you’d show them empathy. So why not offer the same to yourself? You’re allowed to make mistakes, to ask questions, and to have off days. It doesn’t make you any less capable.
Challenge Negative Thoughts – When that voice in your head starts saying you’re not good enough, pause and check the facts. Think about the projects you’ve contributed to, the problems you’ve solved, the trust your team has placed in you. Replace “I’m not technical enough” with “I’m learning every day—and that counts.”
Set Realistic Goals – You don’t have to prove everything all at once. Break your work into smaller, achievable steps. When you hit those milestones—no matter how small—take a moment to acknowledge them. Progress is progress, and it builds momentum.
Cultivate a Supportive Environment – If you’re in a position to influence your team’s culture, use it. Encourage open communication, recognize different contributions, and make space for all voices. When we normalize sharing our struggles and wins, everyone benefits.
Final Thoughts
If there’s one thing I wish I’d known earlier, it’s that imposter syndrome doesn’t mean you’re broken—it usually means you care. You care about doing good work, about being part of something meaningful, and about measuring up in a space that often feels larger than life. But caring doesn’t have to come with constant self-doubt.
Whether you’re testing, developing, supporting, or facilitating, your role matters. The work you do helps build better software, better teams, and ultimately, better outcomes for users. That’s not a small thing.
So take up space. Ask questions. Keep learning. And when that little voice tells you you don’t belong, remind it—gently but firmly—that you do.
