For most of my first year as a software engineer, I barely spoke in engineering meetings. I had answers, opinions, even technical disagreements, but every time I opened my mouth I felt the temperature in the room shift, so I'd close it again and write the thought in my notes. This article is about how I learned to speak up in engineering meetings as a woman in tech, what was actually going on under the silence, and the small practices that finally helped me trust my voice. If you have ever left a standup wondering why you didn't say the thing, this is for you.
Photo by ThisisEngineering on Unsplash
Key Takeaways
- Silence in engineering meetings often isn't shyness, it's a quiet calculation about safety, credibility, and energy.
- Women in tech are interrupted more often, which trains a different relationship with speaking up.
- Small structural moves like writing a one line position before the meeting can change everything.
- Speaking up is a skill, not a personality trait, and it grows like any other engineering skill.
- The goal isn't to talk more, it's to say the things you already think when they matter.
. . .
The first time I noticed myself shrinking
It was a Tuesday standup, mid sprint. Someone proposed rolling back a migration that I had spent three days writing. I knew the rollback was the wrong call. I had the data in my head. The migration wasn't the bottleneck, our caching layer was, and I could prove it.
I didn't say a word.
I told myself I'd send a Slack message later. I didn't send the Slack message later.
What I remember most is the small after feeling. Not anger, not even disappointment, just a kind of low buzz of, oh, that was a moment, and you let it go. I went back to my desk, opened my notebook, and wrote the exact thing I wished I'd said. Three sentences. They would have taken me eight seconds.
That's when I started counting. How many times a week did I write the sentence I didn't say? The number turned out to be embarrassing.
Why women in tech go quiet (it's not always fear)
I want to be careful here because the easy story is "women are shy in tech meetings" and that's not what was happening to me.
I was doing math. Quiet, constant math.
If I share this opinion, will it be heard? If it's heard, will it be credited to me, or will someone else restate it and own it? If it's credited, will it be received as confidence or as something less flattering? How much energy do I have left to do this calculation, given that I already did it forty times this week?
This is what the research on women in technical meetings keeps finding, that women get interrupted more, get less credit for their ideas, and pay a higher social cost for the same assertiveness. So we develop little risk filters. The filters work, until they don't, and you realize you've been editing yourself out of your own career. Harvard Business Review has written about how this pattern shows up in technical workplaces.
The cost of silence is invisible at first, and then suddenly it's the whole shape of your week.
Photo by Mike Tinnion on Unsplash
. . .
What actually started helping me speak up
This part is going to sound small. That's because it is small. The point is that I needed concrete moves, not pep talks.
The first thing that helped was writing a one line position before the meeting. Just one sentence. "I think we should hold the rollback and instrument the cache first." Reading it once before the meeting started somehow made it easier to say out loud, because my brain stopped treating it as a brand new thought I had to construct under pressure.
The second thing was claiming the next thirty seconds. When I had something to say, I would say "I want to add something here" before saying the thing. It bought me a tiny runway, and it cut down on getting talked over.
The third thing, which took me longer to learn, was letting the thing be imperfect. I used to wait until I had the complete, polished argument. Most of my engineering colleagues didn't wait for that. They thought out loud. So I started thinking out loud too. "Here's a thread I'm pulling on, tell me if it's wrong." That phrasing felt true to how I work, and it made the contribution easier to land.
Confidence wasn't a feeling I had to summon. It was a sentence I had already written.
The meeting where everything shifted
A few months into trying these moves, we had a design review. A senior engineer proposed a piece of architecture I knew, just knew, was going to be a maintenance nightmare in eighteen months.
I felt the old shrink reflex turn on. I felt my notebook calling.
Then I heard myself say, out loud, "I want to add something here. I think this works for the next quarter, but I'm worried about the eighteen month version of it, can I sketch what I mean?"
There was a pause. Then the senior engineer said, "Yeah, sketch it."
I drew the failure mode on the whiteboard. We ended up with a different design.
Nobody clapped. The world didn't change. The point is that I changed.
. . .
What I tell other women in tech now
When younger women ask me about speaking up in engineering meetings, I tell them three things.
One, the silence isn't a character flaw. It's a learned response to a real pattern. Don't add shame on top of it.
Two, speaking up is a skill. Skills get built by reps, not by waiting to feel ready. If you do the one line position trick for two weeks, you will be a different person in meetings. Not a louder person. A clearer one.
Three, you don't have to talk more. You have to say the things you already think when they matter. There's a difference. The first one is exhausting. The second one is just being honest about what you noticed.
The funny thing is, the more I trusted my voice in meetings, the more I trusted it in code reviews, in 1:1s, in negotiations, in the small everyday moments where my work used to leak out of me unattributed. It compounded. If you want a related read on building that trust outside of meetings too, my piece on thriving as the only woman on an engineering team goes deeper, and my reflections on surviving my first on call shift sit right next to this one in the same emotional terrain.
I still write the one line position before big meetings. I still claim my thirty seconds. I still let the thing be imperfect.
I am no longer the engineer with the perfect notebook of sentences I didn't say.
. . .
FAQ
How do I speak up in meetings if I am genuinely shy?
Start by speaking up in the meetings where it is safest, like 1:1s and small team standups. Build the muscle in low stakes settings first. The big meetings get easier once your nervous system has done it a hundred times in smaller rooms.
What if I get talked over when I try to speak up in engineering meetings?
Two things. First, name it gently, "Sorry, I wasn't done." Most people will back off and you'll be glad you said it. Second, develop an ally, someone who will say "I think she had something to add." Trade the favor. It works.
How do I know if I'm being assertive or aggressive when I speak up at work?
If you are saying the technical thing you actually think, in a normal tone, with normal eye contact, that is assertive, not aggressive. Many women have been trained to read assertive behavior as aggressive when they do it themselves. Trust the tape, not the inner critic.
I'm the only woman on my team, does that change the advice for speaking up?
It changes the difficulty, not the strategy. The one line position move, the thirty second claim, and the think out loud framing all still work. You may also want to find one ally on your team or in your manager who will help amplify your contributions until the room recalibrates. McKinsey's Women in the Workplace report has years of data on why this still matters.
What if I try these techniques and nothing changes?
Sometimes the room is the problem, not the strategy. If you've been doing the moves consistently for a couple of months and your ideas are still being lost or restated by someone else, that is data. Take it to your manager or, if needed, take yourself to a team where your work can be seen.
. . .
If this hit somewhere, follow along here for more honest pieces about being a woman in tech, slow travel, and learning to take up the right amount of space.
What's the sentence you wrote in your notebook this week that you wish you'd said out loud? I'd love to hear it.