By Annie Wright, LMFT · Licensed Marriage & Family Therapist (#95719)Clinically reviewed May 2026

WOMEN IN TECH • May 23, 2026

Last reviewed: June 2026 by Annie Wright, LMFT

The ping of a new notification barely registers at first. Kira’s fingers hover over the keyboard, hesitating. Fourteen comments on her latest pull request. Seven of them from her senior colleague. Three are just question marks. She reads the first comment again. Her chest tightens. The flush rises to her face. She closes the laptop, breath shallow. Nine years writing code, and she knows this feedback is routine. Still, her nervous system insists it’s not.

For many women engineers, the code review is more than a technical checkpoint. It’s a charged interpersonal event that can reawaken childhood patterns of seeking approval, or fearing criticism. Understanding this dynamic is essential, not just for individual well-being but for reshaping engineering cultures that inadvertently replicate old wounds.

This article explores the clinical architecture of code review anxiety in women engineers. We’ll unpack how performance feedback cycles in engineering echo the attachment dynamics of childhood, why that can trigger disproportionate anxiety, and what healing pathways look like.

Scene: Kira Opens the PR Comment Thread

Kira sits at her desk, the glow of the laptop screen illuminating her furrowed brow. Fourteen comments on her pull request. The cursor blinks, waiting for her to read and respond. Seven comments from her senior colleague, some terse, some cryptic. Three are just question marks, hanging there like silent judgments.

She reads the first comment twice. Her face flushes. The heat spreads from her chest to her neck. Her breath quickens. She closes the laptop. She’s been coding for nearly a decade; she knows this feedback is part of the job. Yet, her body reacts as if something far more personal is at stake.

This moment is familiar to many women engineers. The code review, a standard part of software development, can become a source of intense anxiety. It’s not simply about the technical critique, it’s about what that critique represents on a deeper level.

For women whose self-worth was shaped by early experiences where approval was conditional on intellectual performance, the code review is a proxy for a parent’s gaze. The reviewer becomes a stand-in for the authority figure who once judged every effort, every test score, every school paper. The pull request is the bid for approval; the comment thread, a nervous system event reactivating old wounds.

Despite the rational understanding that constructive feedback is normal, the emotional and physiological response can be disproportionate. This mismatch, the gap between cognition and bodily reaction, is a key clinical indicator that something deeper is unfolding beneath the surface.

This dynamic also intersects with the well-documented phenomenon of impostor syndrome, where women in tech experience persistent self-doubt despite evident competence. Both share a neurobiological infrastructure rooted in early attachment and social evaluation.

What Is Technical Feedback Anxiety?

This definition captures the essence of what many women engineers experience during code reviews. The technical feedback is not just a professional checkpoint; it’s a relational event charged with the echoes of childhood patterns. When your nervous system is wired to respond to authority with heightened vigilance, even routine feedback can trigger a cascade of stress responses.

That cascade often looks like a flush of heat, a tightening in the chest, difficulty concentrating, or an urge to either defend aggressively or withdraw completely. These reactions are not signs of weakness or lack of resilience but signals from a nervous system that is interpreting the code review as a threat to core relational safety.

This anxiety can also fuel the cycle of burnout in tech environments, where the constant need to prove oneself and navigate critical feedback without adequate emotional support wears down even the most competent engineers.

Recognizing technical feedback anxiety as a clinical phenomenon rooted in relational history opens the door to more compassionate, effective interventions, whether through therapy, coaching, or systemic change in engineering culture.

For women in tech seeking support, the Women in Tech Resource Hub offers curated guidance on navigating these challenges with clinical insight and practical tools.

Neurobiology: When Code Review Feels Like a Personal Threat

For many women engineers, the experience of receiving critical feedback during a code review triggers more than just a professional assessment, it activates a deeply ingrained neurobiological alarm system. This reaction is not about the code itself but about the meaning attached to being evaluated and judged by an authority figure. The brain’s threat-detection circuitry struggles to differentiate between a technical critique and a fundamental challenge to one’s adequacy as a person.

At the heart of this response is what researchers call Social Evaluation Threat (SES). This threat occurs when a person perceives that their performance or worth is being negatively evaluated by others, especially those in positions of authority. The brain processes this social threat using the same neural pathways that respond to physical danger, leading to a cortisol-driven fight, flight, or freeze reaction. This means that a seemingly routine comment on a pull request (PR) can cause a cascade of physiological stress responses, racing heart, flushed face, tight chest, that feel disproportionate to the event.

This phenomenon is well-documented in trauma research. Bessel van der Kolk, MD, author of The Body Keeps the Score, describes how the body archives relational injuries, events where someone in a position of care or authority causes harm, even unintentionally. The code review, for women whose childhood experiences included conditional approval or critical parenting, can unconsciously replay these relational wounds. The reviewer becomes a stand-in for the parent, the PR a bid for approval, and the comment thread a nervous system event that reactivates old trauma patterns.

Brené Brown’s work on shame and vulnerability also illuminates this dynamic. Shame, a powerful social emotion, is closely linked to the fear of negative evaluation and rejection. When feedback feels shaming rather than constructive, it can trigger a freeze or withdrawal response, making it difficult to engage with the critique productively.

This neurobiological framing helps explain why some women engineers experience what feels like a trauma response to code reviews. It’s not a question of resilience or professionalism; it’s how the nervous system has been wired through early relational experiences. Understanding this physiological reality is the first step toward developing more compassionate approaches to feedback and self-care.

This anxiety is not simply about the content of the feedback but about the relational message it carries. For women engineers who have internalized the need to earn approval through intellectual performance, a code review can feel like a test of their very value. This explains why even routine comments or neutral questions can trigger intense emotional and physical reactions.

Clinically, this understanding aligns with Martin Seligman’s research on learned helplessness. When individuals experience repeated negative feedback that feels uncontrollable or unpredictable, they may develop a generalized helplessness response, expecting failure or rejection regardless of actual performance. This can create a cycle where anxiety about feedback itself undermines confidence and productivity, perpetuating the problem.

For women navigating these dynamics, the challenge is twofold: managing the technical demands of software engineering while also regulating a nervous system that interprets feedback as a threat to survival. This is why traditional advice to “just get used to it” or “develop a thick skin” misses the mark. The response is not a matter of willpower but of deep-seated neurobiological patterns shaped by early attachment experiences.

How Technical Feedback Anxiety Shows Up in Women Engineers

To illustrate how this neurobiological and psychological architecture plays out in real life, consider Elena, a senior software engineer with years of experience. She’s meticulous and thoughtful in her work, and she takes feedback seriously, not because she doubts her skills, but because she values growth and collaboration.

Today, Elena has spent three hours crafting a detailed response to a PR comment. The feedback she received was constructive but pointed, and she wanted to demonstrate that she understood the concern and had thoughtfully addressed it. Her response includes explanations, code adjustments, and references to documentation. It took longer than writing the original code change.

Then, her reviewer replies in thirty seconds with a single phrase: “LGTM” (Looks Good To Me). The PR is approved and merged.

Elena stares at the screen, feeling a strange emptiness. She expected relief, maybe even a little satisfaction, but instead, there’s a quiet confusion. She doesn’t know what she feels. It’s not relief.

This vignette captures a subtle but clinically important aspect of code review anxiety. The approval Elena received was transactional, an efficient sign-off that the code met technical standards. But it lacked the relational recognition she needed: acknowledgment of the effort she invested, the competence she demonstrated, the human behind the code.

For women engineers whose nervous systems are wired to seek relational validation, this kind of feedback can feel like being seen but not truly seen. The “LGTM” closes the loop on the technical process but leaves the emotional loop wide open. The nervous system remains activated, waiting for a connection that never arrives.

This dynamic is deeply connected to the performance-approval merger many women experience from childhood, where love and acceptance were conditional on achievement. The professional environment replicates this pattern, replaying the old script: “You must prove your worth to be accepted.” When feedback doesn’t meet this need for relational attunement, it can feel like rejection, even if the code is approved.

This is why code review anxiety and imposter syndrome often share infrastructure. Both involve a fundamental uncertainty about belonging and competence, fueled by early relational wounds and reinforced in adult professional settings. For more on this, see our article on impostor syndrome and code review anxiety.

Moreover, this anxiety can contribute to burnout, as the constant stress of navigating these feedback loops drains emotional and cognitive resources. Our burnout guide for women in tech explores how chronic stress from feedback and performance pressures compounds over time.

Understanding these patterns opens the door to interventions that address both the technical and emotional dimensions of feedback. Therapy can help disentangle the childhood roots of performance anxiety, while coaching can build skills to engage with feedback more effectively. Both are essential for healing and growth.

In the meantime, recognizing that your reaction to code review comments is not a personal failing but a signal from your nervous system can be profoundly liberating. It invites a more compassionate relationship with yourself and your work, one where feedback is a tool for learning, not a trigger for survival mode.

This clinical framing also challenges engineering cultures to reconsider how feedback is given and received. Creating psychological safety in code reviews requires more than technical rigor; it demands relational intelligence and empathy. For women engineers, this shift is not just a workplace improvement but a step toward healing old wounds that have been replayed in every PR thread.

—

For those interested in exploring these dynamics further, our resource hub offers curated materials on therapy for women in tech and executive coaching tailored to women in technology. These approaches provide frameworks and tools to navigate the intersection of technical feedback and emotional resilience.

The Performance-Approval Merger in Childhood and Its Mapping onto Technical Environments

For many women engineers, the emotional charge of code reviews is not just about the immediate technical feedback. It’s deeply rooted in a developmental history where performance and approval were inseparable. This fusion, what I call the performance-approval merger, originates in childhood environments where love and acceptance were conditional upon meeting high standards of intellectual or behavioral achievement.

Imagine growing up in a household where your worth was measured by your grades, your ability to answer questions correctly, or your success in extracurricular activities. Parents might have been loving but communicated affection primarily through critique or conditional praise: “I’m proud of you when you get an A,” or “You’re smart, but you could do better.” In such settings, failure or imperfection felt unsafe, emotionally or even physically, and the child learns early that approval is earned, not given freely.

This developmental pattern creates a nervous system that is finely tuned to detect evaluation and judgment from authority figures. The child’s brain and body learn to anticipate threat from any sign of disapproval, activating fight, flight, or freeze responses. Fast forward to adulthood, and the code review process replicates this dynamic. The reviewer becomes a stand-in for the parent or caregiver, the pull request stands in for the child’s bid for approval, and the comment thread becomes a nervous system event that triggers old attachment wounds.

This is why women engineers often report feeling a disproportionate physiological and emotional reaction to code review comments, even when they intellectually know the feedback is normal and necessary. The comments are not just technical; they are relational echoes of past experiences where approval was scarce and conditional.

This developmental history is also linked to academic environments that mirrored these dynamics. Schools that emphasized grades over learning, or parents who closely monitored homework and projects with a critical eye, reinforced the message that performance equals worth. The engineering culture, with its emphasis on correctness, efficiency, and measurable output, can unwittingly reactivate these early patterns.

Understanding this clinical architecture helps us see that the anxiety around code reviews is not a simple matter of “professional resilience” or “technical competence.” It’s about nervous system survival mechanisms wired in childhood, now replayed in the workplace. This insight opens the door to more compassionate approaches, not only from the individual woman but also from teams and organizations.

Both/And: The Code Review Is a Normal Engineering Process AND It Carries the Weight of Something Older

The clinical reality is a both/and situation. On one hand, the code review is a standard, necessary part of engineering workflows. It’s how teams maintain quality, share knowledge, and improve collectively. On the other hand, for many women engineers, the nervous system reaction to this process carries the weight of something far older and more vulnerable.

Consider Kira, a senior engineer with nine years of experience. Six months into therapy, she sits with her therapist, reflecting on a recent code review that left her feeling unsettled. Her therapist gently asks, “Who does the reviewer remind you of?”

Kira hesitates. The question stirs something beneath the surface, a memory she hadn’t consciously connected to this work event. After a pause, she says, “My father. He used to read every school paper I wrote and always found what was missing.”

Her therapist follows, “And was your father usually wrong?”

“No,” Kira replies quietly.

There’s a long silence. The therapeutic space holds the tension between the technical feedback and the emotional resonance it triggers. Kira’s nervous system is not responding to the code itself but to the echo of a childhood attachment figure whose approval felt both essential and elusive.

This vignette illustrates the core clinical insight: the code review is a technical event, but the emotional response is relational. The reviewer’s comments are interpreted by the nervous system as a test of worthiness, not just code quality. The “LGTM” or “Looks Good To Me” that closes a review thread may be technically sufficient but emotionally insufficient. The nervous system craves recognition of effort, competence, and relational safety, not just transactional approval.

Recognizing this both/and helps women engineers reclaim agency in their feedback relationships. It allows them to hold the technical and emotional realities simultaneously, without conflating the two or dismissing their own lived experience.

From a practical standpoint, this means cultivating a somatic awareness of the feedback-anxiety cycle and learning to distinguish the technical critique from the emotional charge. Therapy can help unpack the childhood piece, offering a corrective relational experience that rewires attachment patterns. Meanwhile, executive coaching can build skills for integrating feedback without triggering survival responses, fostering a healthier feedback relationship with one’s work.

For women navigating this terrain, resources like therapy for women in tech and executive coaching for women in tech executives provide tailored support. These interventions help untangle the complex interplay of identity, nervous system regulation, and professional development.

The code review anxiety cycle is not a personal failing. It’s a signpost pointing toward early relational wounding and the ongoing challenge of navigating technical environments that unconsciously replay those dynamics. Naming this clinical architecture creates space for healing, resilience, and ultimately, a more sustainable career in engineering.

For more on how code review anxiety intersects with impostor syndrome, see Impostor Syndrome and Women in Tech. For understanding the burnout risks tied to this feedback cycle, explore Burnout for Women in Tech.

—

Next sections will explore systemic factors and healing strategies to further illuminate this complex clinical landscape.

The Systemic Lens: How Code Review Culture Reflects and Reinforces Gendered Power Dynamics in Engineering

The anxiety women engineers experience around code reviews doesn’t arise in a vacuum. It’s embedded in a larger system where gender bias, power imbalances, and cultural norms shape how feedback is given, received, and interpreted. Understanding this systemic context is crucial to fully grasp the clinical architecture of code review anxiety.

Multiple studies have documented that women’s code submissions face higher scrutiny and lower acceptance rates than men’s, particularly in open source projects. This isn’t about individual reviewers being overtly hostile or unfair; it’s about a pervasive culture where women’s work is often held to a different standard. The volume of comments women receive can be significantly greater, and the tone less encouraging, which compounds the emotional toll.

This dynamic mirrors broader social patterns where women negotiating or asserting themselves face backlash, a phenomenon well described in the social sciences. For example, Bowles, Babcock, and Lai’s research highlights how women who initiate negotiations are penalized more harshly than men, not because of a lack of competence or confidence, but due to social costs imposed by gendered expectations. Similarly, in engineering teams, women who push back or defend their code risk being labeled “difficult” or “overly sensitive,” further discouraging authentic engagement with feedback.

Code review culture, with its emphasis on rapid iteration and blunt critique, often fails to recognize the relational context in which feedback is received. Women engineers may find themselves navigating not only the technical demands of their work but also the emotional labor of managing how their competence and worth are perceived in a male-dominated environment. This can activate the same nervous system responses associated with early attachment wounds, as described earlier.

Moreover, the systemic undervaluing of women’s contributions in engineering feeds into what clinical research calls “learned helplessness”. A generalized expectation that efforts to improve or assert oneself will be met with disproportionate resistance or dismissal. Martin Seligman’s foundational work on learned helplessness helps explain why repeated negative feedback cycles can not only trigger anxiety but also erode motivation and engagement over time.

The systemic lens also reveals how cultural norms in tech valorize “resilience” in ways that often mask structural inequities. Women who experience feedback anxiety are sometimes unfairly judged as lacking grit or emotional toughness, rather than being recognized as responding to a feedback environment that is, for them, a re-activation of early relational trauma. This misinterpretation can isolate women further, reinforcing the internal narrative that their distress is a personal failing rather than a signal about the environment.

The consequences of this systemic dynamic are profound. It contributes to attrition of talented women engineers, perpetuates the gender gap in leadership, and undermines psychological safety on teams. It also shapes how women relate to their own work, often organizing their identity around hyper-vigilance and over-preparation to preempt criticism, which can lead to exhaustion and burnout.

Understanding code review anxiety through this systemic lens invites us to see the problem not as individual fragility but as a cultural pattern that demands change at multiple levels. From team norms to organizational policies to broader social attitudes about gender and performance.

What Healing Looks Like: Clinical and Practical Strategies to Rewire the Feedback-Anxiety Cycle

Healing from the cycle of technical feedback anxiety requires a multi-layered approach that addresses both the nervous system’s conditioned responses and the relational patterns rooted in childhood experiences. Here’s a clinically informed framework for women engineers and their allies to begin disentangling the emotional charge from the technical feedback.

1. Somatic Regulation: Reclaiming Nervous System Safety

The disproportionate physiological response to code reviews signals that the nervous system perceives threat where there is none, or at least none proportionate to the event. Somatic regulation techniques, such as grounding exercises, breath awareness, and body scanning, can help shift the nervous system out of fight/flight/freeze mode and into a state of safety and presence.

For example, when opening a PR comment thread triggers heat in the face or tightness in the chest, pausing to notice these sensations without judgment can create a window of tolerance. This somatic pause interrupts reactive patterns and allows for a more measured engagement with the feedback.

Therapeutic modalities like Sensorimotor Psychotherapy, Somatic Experiencing, or trauma-informed mindfulness can be particularly effective in helping women reconnect with their bodies and differentiate between present-moment reality and past relational wounds.

2. Distinguishing Technical Feedback from Emotional Charge

Clinically, one of the most powerful interventions is helping clients develop the skill to cognitively and emotionally separate the content of the code review from the emotional narrative layered on top. This means recognizing that a comment like “Needs refactoring” is a technical request, not a judgment of personal worth.

Cognitive-behavioral tools can assist in identifying and challenging automatic thoughts that escalate the emotional response. For example, replacing “My reviewer thinks I’m incompetent” with “The reviewer wants to improve the code, which is normal and expected” helps recalibrate the appraisal of the event.

In coaching contexts, executive coaching for women in tech can focus on feedback integration skills. Learning to receive, process, and respond to critique in ways that protect self-esteem and preserve motivation. This includes practicing clear communication with reviewers to clarify ambiguous comments or request recognition of effort, moving beyond transactional “LGTM” closures.

3. Therapy for the Childhood Piece

Because the code review often reactivates attachment wounds, therapy that explores the client’s developmental history can be transformative. This work helps women understand the origin of their feedback anxiety and develop new internal resources for self-validation.

Therapeutic approaches such as attachment-based therapy, Internal Family Systems (IFS), or relational psychotherapy provide a container where women can safely explore their internalized critical voices and unmet needs for approval. Over time, this work can rewrite the old narratives that equate approval with survival and open the door to authentic self-worth independent of external validation.

4. Building a New Feedback Relationship with Your Work

Healing also involves cultivating a new relationship with feedback and one’s own work that is not organized around fear or conditional acceptance. This might mean setting boundaries around how and when to review comments, creating rituals that honor effort regardless of outcome, or developing supportive peer networks that provide empathic reflection rather than judgment.

Communities of women engineers who share their experiences of feedback anxiety can reduce isolation and normalize the emotional complexity of technical critique. This collective witnessing validates individual struggles and fosters resilience.

5. Advocating for Systemic Change

While individual healing is vital, it must be paired with advocacy for systemic change. Women engineers and allies can work to reshape code review cultures by promoting psychological safety, encouraging constructive feedback practices, and addressing documented gender biases in review processes.

Organizational leaders can implement training on unconscious bias in code review, create channels for anonymous feedback on review culture, and recognize the emotional labor women invest in navigating these dynamics. Such structural interventions create environments where women’s nervous systems can relax, and their talents can flourish without the added burden of relational trauma triggers.

—

For a broader map of the terrain, this piece sits inside the Women in Tech Resource Hub, alongside deeper writing on burnout for women in tech, glass-ceiling trauma responses, imposter syndrome in tech, Silicon Valley executive loneliness, the difference between impostor syndrome and a toxic workplace, and complex PTSD. If you are looking for direct support, you can also read more about therapy for women in tech, executive coaching for women in tech, and the weekly Strong & Stable newsletter.

l alarm system designed to protect us from threats to our social standing and belonging. This is the essence of social evaluation threat, a neurobiological response that treats perceived judgment from others as a form of danger equivalent to physical harm.

In the context of a code review, the reviewer’s comments are not just technical feedback, they become signals that the self is under scrutiny and potentially found lacking. For women whose early experiences linked approval to performance, this scrutiny can reactivate childhood memories of conditional acceptance.

Imagine the pull request as a vulnerable offering, a bid for connection and recognition. When the comments come back with critiques, or worse, terse question marks, the nervous system can’t easily separate “my code needs improvement” from “I am not enough.” This blurring of boundaries is what makes code review anxiety so persistent and difficult to manage.

Neuroscientific research by Bessel van der Kolk and Brené Brown underscores how shame and vulnerability are processed in the brain’s threat-detection systems, making social evaluation a powerful trigger for stress responses. This is why even seasoned engineers like Kira and Elena can feel immobilized or emotionally overwhelmed despite their technical competence.

Understanding this neurobiological underpinning reframes the experience: it’s not about lacking skill or resilience, but about a nervous system that is wired to protect relational safety. This insight is crucial for developing self-compassion and targeted strategies to regulate the feedback-anxiety cycle.

If you find yourself caught in this loop, somatic practices that engage the parasympathetic nervous system, such as grounding, paced breathing, or mindful movement, can help soothe the physiological arousal. These tools don’t erase the feedback but create enough space to respond rather than react.

Therapeutic work can also help disentangle the current technical critique from the emotional charge rooted in childhood. In therapy, we explore the internalized voices of authority figures and the patterns of conditional approval that shape how feedback is received today. This process can gradually rewire the nervous system’s response, allowing for a more balanced engagement with technical critique.

For those navigating this terrain, combining somatic regulation with reflective therapy offers a powerful path forward. Coaching focused on feedback integration skills complements this by building practical frameworks to parse technical comments without triggering old wounds.

Recognizing the code review as both a technical process and a relational event is a key step toward healing. It invites a both/and perspective: honoring the validity of the technical critique while also acknowledging the emotional reverberations beneath.

For more on the intersection of nervous system regulation and professional challenges in tech, see Burnout for Women in Tech, which offers practical strategies for managing chronic stress and reclaiming agency.

Similarly, the article on Impostor Syndrome explores how internalized doubts and feedback anxiety share common roots, providing a nuanced understanding of these overlapping experiences.

Ultimately, the goal is to cultivate a feedback relationship with your work that is not organized around fear or survival but grounded in curiosity, growth, and self-compassion. This shift is not only possible but essential for sustaining a fulfilling career in engineering.

References

Peer-Reviewed Research (Vancouver)

1. van der Kolk BA, Wang JB, Yehuda R, Bedrosian L, Coker AR, Harrison C, et al. Effects of MDMA-assisted therapy for PTSD on self-experience. PLoS One. 2024;19(1):e0295926. doi:10.1371/journal.pone.0295926. PMID: 38198456.

Books & Cultural Sources (Chicago Author-Date)

• Brown, Brené. Daring Greatly. Penguin Audio, 2012.

About the Author

Annie Wright, LMFT

LMFT · Relational Trauma Specialist · W.W. Norton Author

Helping ambitious women finally feel as good as their résumé looks.

Annie Wright is a licensed psychotherapist (LMFT #95719) and trauma-informed executive coach with over 15,000 clinical hours. She works with driven, ambitious women. Including Silicon Valley leaders, physicians, and entrepreneurs. In repairing the psychological foundations beneath their impressive lives. Annie is the founder and former CEO of Evergreen Counseling, a multimillion-dollar trauma-informed therapy center she built, scaled, and successfully exited. A regular contributor to Psychology Today, her expert commentary has appeared in Forbes, Business Insider, Inc., NBC, and The Information. She is currently writing her first book with W.W. Norton.

Work With Annie

Medical Disclaimer

Medical Disclaimer