Your review meeting starts before the invite

Getting into STEM was never supposed to be the finish line

When I hosted this workshop with the Ingeniera Foundation, one part of the conversation stayed with me: how many women shared some version of the same experience of not having someone actively advocating for their career growth. I knew it happened. I did not realize how common it was.

That conversation made me think about something we often miss when we talk about representation in STEM. Getting women into technical roles matters, but what happens after they arrive matters too. Who gets supported? Who gets stretch opportunities? Who has someone advocating for them when promotions, projects, and leadership opportunities are being discussed?

The data suggests that this gap in career growth is not just anecdotal. The 2025 Women in the Workplace report from McKinsey and LeanIn.Org found that for every 100 men promoted to manager, 93 women were promoted. The numbers fell to 82 Asian women, 82 Latinas, and 60 Black women.

And this is happening in a field where representation is already limited. I am still one of only two women on a team of nine engineers. Across the United States, women made up just 20.3 percent of software developers in 2025, according to the Bureau of Labor Statistics.

We have spent years talking about getting more women into STEM, but getting through the door is only part of the problem. We also need to ask who gets advocated for, who receives opportunities to grow, and whose name gets mentioned in rooms they are not in.

The preparation in this article gives you more control over what you document, ask, and act on. It is not a substitute for fair promotion systems, accountable managers, or sponsors who actively create opportunities.

Getting women into STEM was never supposed to be the finish line.

Build an impact record while the work is fresh

When review season arrives, it is much easier to remember the last few intense or visible weeks than everything that happened across the full review period. Start an impact folder now so you can reconstruct that period later.

Keep the system simple. Save thank-you emails, customer notes, stakeholder feedback, project metrics, before-and-after examples, and moments when you navigated a difficult situation. Capture the work between projects too: mentoring someone, unblocking a teammate, improving a process, or creating clarity when a group was stuck.

Explain the action, impact, and evidence

A self-evaluation should do more than list tasks. The person reading it should not have to reconstruct why your work mattered. For each accomplishment, connect three pieces: what you did, what changed because of it, and what supports that claim.

For example, “I created a new intake flow” names the action. “The new flow reduced handoffs and delays” explains the impact. “A request that took three hours now takes thirty minutes” supplies the evidence.

Not every result has a clean number. Evidence might be fewer escalations, adoption of something you created, feedback from a stakeholder, a changed team behavior, or a stronger process. Use the proof you have. Do not manufacture a metric to make the sentence look more impressive.

Prepare for a conversation, not a defense

Bring a few outcomes that matter instead of a task-by-task report. Then make room for your manager’s perspective. A few questions can make the conversation much more concrete:

• What am I doing well that I should keep doing?
• Where do you think I have the biggest opportunity to grow?
• What would stronger performance look like at the next level?
• Which opportunity would help me practice that?

Vague feedback needs a follow-up question. If you hear “show more leadership,” ask for an example. If you hear “gain more experience,” ask what kind of experience would demonstrate readiness. Clarity turns a broad judgment into something you can practice.

Name the direction you want

Good work does not automatically tell your manager what you want next. A promotion, expanded scope, a leadership opportunity, deeper specialization, or a move into a different function all require different experiences. Say the direction out loud.

A useful question is: “Over the next six to twelve months, what would you need to see from me to be ready for this?” That shifts the conversation toward the behaviors, scope, skills, and outcomes that would demonstrate readiness.

Treat feedback as information you can examine

You may hear feedback you did not expect or immediately agree with. You do not have to solve it in the meeting. Listen to the full point. Ask for examples and expectations. Reflect afterward on patterns and context. Then choose an actionable change and a time to revisit it.

Context matters too. A behavior may need to change, while the work situation also needs support or adjustment. Ask both questions: What can I do differently? What support or change would help me do it?

Turn one piece of feedback into a six-month experiment

A small experiment makes growth observable. Write down the feedback, translate it into a behavior, and decide what progress would look like. Choose one action you can take now, identify the support you need, and put a check-in date on the calendar.

1. Feedback: What did I hear?
2. Behavior: What would I do differently?
3. Evidence: What would progress look like?
4. Action: What can I start doing now?
5. Support: What do I need from my manager or team?
6. Check-in: When will we revisit this?