For two years, I was the only woman on a team of eleven engineers, and most days I did not realise how much energy I was spending on simply existing in that room. This is the story of how I learned to stop performing, stop apologising for my voice, and start actually contributing the way I knew I could. If you are the only woman on your engineering team, or one of very few, this article is the version of itself I wish someone had handed me on day one. I want you to walk away with a few small, concrete shifts you can try this week, and a reminder that you are not imagining how much harder it can feel some days.
. . .
Key Takeaways
- Being the only woman on your engineering team is not a personality flaw, it is a structural reality, and naming that out loud is the first step to surviving it.
- You do not have to choose between being likable and being technical. The trick is to stop optimising for either and start optimising for clarity.
- Asking questions in standup, in code reviews, and in design docs is not a sign of weakness, it is the move senior engineers make most often.
- Build solidarity outside your team before you need it. One Slack DM with another woman in the org can change a whole quarter.
- Your voice belongs in the room. The room becomes a better room every time you use it.
. . .
The Meeting Ratio Nobody Talks About
I joined the platform team straight out of university, and on my first standup I counted eleven faces, including mine. I was the only woman, the youngest by about six years, and the only person who had not already worked together at a previous startup. I remember sitting on the kitchen floor that night, trying to figure out if I was being paranoid for noticing the ratio.
I was not. The Anita Borg Institute and similar workforce studies have been tracking the same numbers for a decade now, and women still make up roughly a quarter of technical roles at most large tech companies. On smaller teams, the math gets brutal fast. One in eleven is not unusual. One in five is considered lucky.
The first cost of being the only woman in the room is the energy you spend pretending you have not noticed.
For the first six months, I tried to be invisible and exceptional at the same time, which is, mathematically, impossible. I would prepare three times longer for code reviews than my peers, then say almost nothing during them. I would write a comment on a pull request, delete it, rewrite it softer, and then never post it. I was so focused on not being seen as the woman that I forgot to actually be the engineer.
A quiet engineering workspace, the kind where you do your best thinking when nobody is watching.
. . .
The Shift That Changed How I Showed Up
The shift did not come from a confidence book or a viral TED talk. It came from a senior staff engineer named Priya, who I met by accident in a women in tech Slack channel my company ran. We hopped on a fifteen minute call. She asked me one question: when you read a pull request and you do not understand something, what do you do?
I told her, very honestly, that I would spend twenty minutes on Stack Overflow, then thirty minutes on the codebase, then maybe message someone privately if I still did not get it. She laughed in a kind way, not a mean way. Then she said, just ask in the PR thread. Out loud. In the channel. Where everyone can see.
I almost cried. I had spent six months hiding the fact that I sometimes did not know things, while every senior engineer on my team was openly asking questions all day long. If you have ever wanted to read a longer piece on this exact dynamic, my earlier story on how to survive your first code review as a junior developer picks up the same thread.
Asking is a senior move. Pretending you already know is the junior tell.
The first time I asked a question in a public PR thread, my voice felt loud even in text. I wrote, can someone explain why we are using a queue here instead of just calling the function directly? Three engineers replied within ten minutes. One of them thanked me for asking, because he had been wondering the same thing. The architecture decision turned out to be load related, and the discussion ended up in our team wiki.
Nothing bad happened. The opposite happened. I had taken up space, and the room got bigger.
. . .
What I Started Doing in Meetings
After Priya, I started experimenting with very small behaviour changes. I am going to list them not as a prescription, but as a starting point. Pick the one that scares you least.
I stopped saying I think and I just wanted to ask before every contribution. Those phrases are softeners. They are not wrong, but they pile up, and over a year of meetings they teach the room to weight your input lower than you intend. I replaced them with the actual statement. Instead of, I think we might want to consider caching here, I now say, this looks like a candidate for caching, here is why.
I started writing my point down before the meeting, not as a script, but as one short sentence I could read aloud if my brain went blank. Standup is fast. Design reviews are faster. The sentence is a lifeline. There is a similar idea in my piece on how to stop apologising on Slack, where I unpack why softening language costs more than we think.
I stopped letting interruptions slide. I would say, hold on, let me finish the thought. The first time I said this, my hands were shaking. Now I say it without thinking, and the room respects it. The trick is the tone. You are not angry, you are just continuing the sentence you started.
Taking up space is not loud. It is just consistent.
I also started using the Slack channel my team had for technical questions, the one I used to read silently. I posted my first dumb question on a Tuesday. Two people answered, and one of them sent me a private follow up to thank me for asking, because they had been confused for weeks. That single moment paid back every minute I had ever spent worrying about looking dumb.
. . .
The Solidarity Network You Build Before You Need It
Here is something I learned the hard way: by the time you actually need a mentor, it is already too late to start looking. Build the network on a normal Tuesday, when nothing is on fire and you are not panicking.
I joined two communities outside my company in my first year, and they have done more for my career than any internal program. Women in Tech Network, often shortened to WiT, has chapters in most cities and a very active LinkedIn presence. Tech Ladies runs a job board and a Slack that genuinely does not feel like a marketing funnel. The girlsgonewired subreddit on Reddit is more casual but very honest, and the threads on negotiation alone are worth the scroll.
Inside my company, I found two other women in adjacent teams and we started a standing thirty minute coffee every other week. We did not talk about gender every time. Mostly we talked about technical problems, project scoping, and whose manager was being weird about promotion timelines. But knowing those calls existed, knowing I had two other people I could DM with, take a look at this Slack thread, am I being crazy, that knowledge alone changed how I sat in every other meeting.
A network is not who you ask for a job. A network is who you ask if you are losing your mind.
Coffee with another woman in tech is, somehow, the most underrated career move there is.
. . .
What I Would Tell My First Day Self
If I could send one Slack message back to the version of me sitting on the kitchen floor that first night, here is what it would say.
You are not paranoid. The room is what you think it is, and you are allowed to notice it. Noticing is not complaining. Naming a pattern is the first step to working with it instead of around it.
You are not too quiet. You are conserving energy. That is a survival strategy, and it worked for the first six months. Now it is time to spend a little of that energy on actually contributing, because the team needs your brain and your brain works best when it is allowed to speak.
You are not going to ruin your career by asking a question in a PR. The opposite is more likely. The questions you ask out loud are the ones that get you remembered as the person who thinks clearly.
You do not have to be friends with everyone. You have to be respected by enough of them. The two are different, and conflating them will exhaust you.
And finally, find Priya. Or whoever your Priya is. She is on a Slack channel somewhere, three teams over, waiting for someone to ask for fifteen minutes. The fifteen minutes will save you a year.
. . .
Frequently Asked Questions
How do I know if I am being treated differently because I am a woman, or if I am just being sensitive?
You probably are not just being sensitive, but the only way to find out is to compare notes with other women in the org. Pattern matching across people is how you separate vibes from data. If three women in three teams have all heard the same comment from the same VP, it is not a vibe.
What if I am the only woman on my team and there is no women in tech network at my company?
Start one. Two people is a network. Send a Slack DM to one other woman, suggest a thirty minute coffee, and see what happens. If your company is too small for that, look outside. Tech Ladies, Women Who Code, and the Anita Borg Institute all have free communities you can join in an evening.
Should I bring up the gender ratio in interviews when I am job hunting?
Yes, but ask in a neutral, data shaped way. How many women are on the team I would be joining is a fine question. Their answer, and the speed of their answer, will tell you a lot.
What if I want to leave engineering because the room is exhausting me?
That is a real and valid choice, and nobody gets to make it for you. But if exhaustion is the reason, try changing teams or companies first, because the room varies more than people admit. The same skill set in a different team can feel like a different career.
How do I push back on interruptions without being labelled difficult?
Use the sentence, hold on, let me finish. Then finish. Most people do not interrupt on purpose, and most people will respect a calm, neutral correction. The handful who do not are telling you something useful about themselves.
. . .
If this resonated, I would love for you to subscribe to Info Planet for more honest reflections from a CS girl who travels, codes, and is figuring it out one standup at a time. And if you are the only woman on your engineering team right now, send this to the next woman who joins. We are how each other survives. Drop a comment below with the one phrase you are going to stop saying in meetings this week, because someone reading this needs your sentence.