You Are Not a Fraud: Imposter Syndrome in the Codebase
Learning and Skills

You Are Not a Fraud: Imposter Syndrome in the Codebase

That voice — the one that reviews your own pull request three times before you submit it, that stays quiet in the architecture meeting even though you spotted the flaw ten minutes ago — is not telling you the truth. It is telling you a story, and the story is that everyone else in the room belongs here and you got in by accident. Imposter syndrome in tech is not a personal failing. For women, it is a predictable response to working in a system that was not built with you in mind.

The Particular Shape of It

Not Just Self-Doubt With a Fancier Name

Everyone doubts themselves sometimes. That is not what this is about. Imposter syndrome for women in technical roles has a specific flavour — it is the persistent conviction that you do not belong in a space that was not designed for you, reinforced by an environment that regularly confirms that suspicion in small ways. The meeting where your suggestion is ignored and then repeated by a man two minutes later. The code review where your work gets scrutinised at a level your male colleagues’ does not. The assumption that you are the project manager, not the developer.

The term was coined in 1978 by psychologists Pauline Rose Clance and Suzanne Imes, studying high-achieving women who believed they were intellectual frauds despite evidence to the contrary. What is telling is that the research started with women — not because women are more prone to self-doubt, but because the environments they operated in gave them more reasons to doubt.

In NZ tech, where women make up roughly a quarter of the IT workforce, being the only woman on a team is still common. That visibility — the awareness that you are noticed, that your mistakes might be attributed to your gender rather than normal human error — is not paranoia. It is pattern recognition.

The Confidence Gap Is a Measurement Error

There is a popular narrative that women need to be more confident. Lean in. Raise your hand. Ask for the promotion. This framing puts the problem inside women’s heads and ignores the landscape they are navigating. When studies show that women apply for jobs only when they meet a hundred percent of the criteria while men apply at sixty percent, the usual interpretation is that women lack confidence. The alternative interpretation — that women have accurately assessed how much harder they will be scrutinised — gets less airtime.

Research from NZ’s own universities has shown that identical work is rated differently depending on the perceived gender of the author. A piece of code is not objectively evaluated; it is evaluated by a person with biases, in a culture with patterns. When you have watched that play out enough times, adjusting your confidence downward is not a psychological flaw. It is a rational response.

This distinction matters because the fix for “you are not confident enough” is very different from the fix for “the system evaluates you unfairly.” The first asks you to change. The second asks the system to change. Both need to happen, but only one of them is within your control on a Tuesday morning before standup.

Where It Shows Up in Your Work

Code Review Anxiety

You have written the code. It works. The tests pass. And you still sit there for twenty minutes before opening the pull request, rereading every line, convinced there is something obvious you have missed that will confirm what you suspect everyone already thinks — that you do not really know what you are doing. Code review anxiety is imposter syndrome at its most concrete. Your work, your thinking, your competence, submitted for judgment in a format that leaves a permanent record.

The fear is not irrational. Code reviews can be brutal, and women in tech report receiving more nitpicky feedback on style and convention while substantive architectural feedback goes to their male colleagues. A study from the University of Waterloo found that women’s code on open-source platforms was accepted at higher rates than men’s — but only when their gender was not identifiable. When it was, acceptance rates dropped.

The practical damage is real. You over-polish before submitting, spending hours on code that was fine two hours ago. You avoid committing work-in-progress because showing incomplete thinking feels too vulnerable. You interpret any suggestion as evidence of failure rather than normal collaborative development. The code review becomes a referendum on whether you deserve to be here.

The Meeting Where You Say Nothing

You had the answer. You knew it fifteen minutes ago when the question was first raised. But you stayed quiet, because what if you were wrong, and what if being wrong in front of this room meant something different for you than it would for the guy who confidently proposed an approach that was, in fact, wrong, and nobody seemed to mind.

Meeting silence from women in tech is well-documented. It is not that you have nothing to say. It is that the cost-benefit calculation of speaking up is different when you are the minority in the room. A wrong answer from someone who “belongs” is just a wrong answer. A wrong answer from you risks becoming a data point in someone’s unconscious model of whether women are technical enough.

This creates a vicious cycle. You say nothing. Your contributions are invisible. Performance reviews note that you are “quiet in meetings” or “could show more leadership.” The silence that was a protective strategy becomes evidence against you. Meanwhile, the colleague who speaks with confidence on topics he half-understands gets praised for his initiative. You watch this happen and your silence deepens.

Breaking the pattern does not require becoming someone you are not. It starts with recognising that your silence is a strategy, not a personality trait, and that the calculation driving it is worth interrogating.

The Attribution Gap

When the project succeeds, you attribute it to the team, the timeline, or luck. When something breaks, you attribute it to yourself. This is not humility — it is a distortion that imposter syndrome installs like bad firmware. The attribution gap means you internalise failure and externalise success, which over time creates a completely warped picture of your own competence.

Men, on average, do the opposite. Success is talent; failure is circumstance. Neither pattern is accurate, but one of them leads to asking for promotions and the other leads to wondering if you deserve the job you already have.

In NZ tech culture, this gets complicated by tall poppy syndrome — the cultural tendency to cut down people who stand out. For women, the tall poppy risk is amplified. Claiming credit can be read as arrogance. Self-promotion feels culturally wrong. So you deflect praise, minimise your contribution, and eventually start believing your own deflections. The colleague who says “I built that” gets the interesting project next quarter. The one who says “oh, it was a team effort” gets overlooked. The fix is not to become an insufferable self-promoter. It is to practise accurate attribution — crediting yourself when the credit is yours, with the same matter-of-fact tone you would use for anyone else.

The Systems That Feed It

Overcoming Imposter Syndrome in Male ...

Bro Culture Is Not Just Vibes

The ping-pong table in the office. The Friday beers that are really networking sessions. The Slack channel full of references you do not get because they are from a gaming subculture you were never part of. None of these are deliberate exclusion — and all of them are exclusion. Bro culture in tech is not usually hostile. It is a set of norms built by and for a specific demographic, and when you do not fit that demographic, you spend energy navigating the social layer that everyone else gets for free.

In NZ, the tech sector likes to think of itself as laid-back and egalitarian. And compared to Silicon Valley, it often is. But “better than Silicon Valley” is a low bar. The casual blokey culture in many NZ tech companies — the rugby chat, the craft beer opinions treated as personality, the assumption that everyone spent their twenties playing World of Warcraft — creates an in-group. If you are outside it, every interaction requires a small act of translation. That cognitive load adds up, and it feeds the sense that you are performing belonging rather than experiencing it.

This is not about banning beer or ping-pong. It is about recognising that culture is infrastructure, and when the infrastructure was not built with you in mind, using it costs more.

Performance Reviews and the Likability Trap

Performance reviews are supposed to be objective. They are not. Research consistently shows that women receive more personality-based feedback — “could be more assertive,” “sometimes comes across as abrasive” — while men receive more skills-based feedback — “should develop expertise in system design.” One type of feedback helps you grow. The other makes you question who you are.

The likability trap is well-documented: women who are competent but not warm are penalised, while men who are competent but not warm are just… competent. In NZ workplaces, this often surfaces as feedback that a woman is “too direct” or “could work on her communication style.” The same directness in a man is read as confidence or leadership.

When your reviews consistently focus on how you come across rather than what you deliver, imposter syndrome gets a regular top-up. You start second-guessing not just your technical work but your entire way of being in the workplace. Am I too quiet? Too loud? Too technical? Not technical enough? The performance review becomes a mirror that reflects not your actual performance but the gap between who you are and who the system expects you to be.

What Actually Helps

Keep a Record of What You Built

Start a document — a private one, just for you — and every Friday, write down what you did that week. Not what the team did. What you did. The bug you traced to a race condition in the payment service. The refactor that reduced page load time. The PR review where you caught a security issue. Write it in plain language, with specifics.

This is sometimes called a brag document and it is the single most effective counter to imposter syndrome’s revisionist history. Your brain will tell you that you have not done anything meaningful. The document will disagree, with evidence.

When performance review time comes, you are not scrambling to remember six months of work through a fog of self-doubt. You have a list. When you are preparing for a salary negotiation or a job interview, you have concrete examples. When imposter syndrome whispers that you have been faking it, you can open a file and read a factual account of the problems you solved.

The habit takes five minutes a week. The effect compounds. After six months, you will have a document that makes it genuinely difficult to maintain the fiction that you do not know what you are doing.

Find One Person Who Gets It

You do not need a mentor in the formal, corporate-programme sense. You need one person in your professional orbit who understands what you are dealing with and will tell you the truth. Someone who will say “that feedback was gendered rubbish” when it is, and “actually, you did drop the ball on that one” when you did. Honest perspective from someone who has your back is worth more than a dozen networking events.

In NZ, organisations like NZTech and She Sharp run mentoring programmes that match women in tech with experienced professionals. These vary in quality — some are transformative, some are box-ticking exercises. The best mentoring relationships tend to form organically, from working together or meeting at events, rather than being assigned.

If formal mentoring is not available, a peer support arrangement works just as well. Find another woman at roughly your level and check in regularly. Compare notes on what you are experiencing. The simple act of hearing someone else describe the exact same doubts you have — from a person whose competence you do not question — is remarkably clarifying. If she is not a fraud, and her experience mirrors yours, then maybe the problem is not either of you.

Name It When You See It

When you are sitting in a meeting with your hand half-raised and your mouth closed, pause and name what is happening. “This is imposter syndrome. I have an answer and I am not sharing it because I am afraid of being wrong in front of people who I think are smarter than me.” You do not need to say this out loud. The internal recognition is the point.

Naming the pattern interrupts it. Not every time, and not completely, but enough to create a gap between the feeling and the behaviour. In that gap, you can make a different choice. Sometimes you will still stay quiet. But sometimes you will speak, and you will discover that the thing you were afraid to say was exactly what the room needed.

This is not positive thinking. It is not telling yourself you are brilliant. It is the simpler, more grounded practice of distinguishing between what you feel and what is true. You feel like a fraud. The evidence says you are a developer who ships code, solves problems, and shows up every day. Both of those things are real. But only one of them is a fact.

Rewriting the Internal Monologue

GirlCode x Storyblok Coffee break ...

You Were Hired for a Reason

Someone looked at your application, interviewed you, evaluated your skills against other candidates, and decided you were the person for the job. That process — imperfect as hiring always is — was not charity. Companies do not hire people out of pity. They hire people they believe will contribute, and they chose you.

The diversity hire fear is a specific cruelty of imposter syndrome in underrepresented groups. The whisper that you are only here to fill a quota. That your presence is political rather than professional. This fear persists even when — especially when — you are performing well, because the internal logic of imposter syndrome is unfalsifiable. Do well? You got lucky. Get promoted? They needed a woman in leadership. Receive praise? They are being nice.

Here is what is actually true: the NZ tech sector has a genuine skills shortage. Companies are competing for talent. If you are in a technical role, it is because someone needed your skills and you had them. That is not a feel-good platitude. It is labour market economics. You can choose to believe the market or believe the voice in your head. The market has data. The voice has anxiety.

The Long Game

Imposter syndrome does not have a cure. It has a management strategy. Women who have been in tech for twenty years still feel it — in new roles, with new technologies, in rooms full of people who seem to know more. The difference is that experience teaches you to recognise the feeling for what it is and keep moving anyway.

Maya Angelou wrote eleven books and still feared being found out. The feeling does not scale with achievement. What changes is your relationship to it. You stop waiting to feel confident before you act and start acting despite the doubt. Confidence, it turns out, is not a prerequisite for competence. It is a byproduct of it.

The NZ tech community is better than it was ten years ago and worse than it will be in ten years. More women are entering the field, staying in the field, and building the kind of workplaces they needed when they started. That trajectory matters. You are not just managing your own imposter syndrome — you are, by being here and staying here, making it slightly easier for the person who comes after you. That is not nothing. That is actually quite a lot.

The voice does not go away. You just get better at recognising it, disagreeing with it, and shipping the code anyway. Every woman who stays in tech, builds things, and refuses to shrink makes the landscape marginally better for everyone who follows. That is not a motivational poster. That is structural change, one commit at a time.