They Called It a Step Up — But It Was Actually a Step Sideways

Picture this: You've shipped a redesign that cut load time in half. Your pull requests are clean, your code reviews are thoughtful, and your teammates come to you first when something breaks. Then your manager calls you into a one-on-one and says the words you've been waiting to hear — we want to give you more responsibility.

Except the role they're describing doesn't involve writing much code anymore. It's mostly meetings. Roadmaps. "Stakeholder alignment." They call it a leadership opportunity. They say it like it's obvious you should want it.

For a lot of women in frontend development, this moment — the one that's supposed to feel like arrival — is actually the beginning of a slow drift away from the work that made them valuable in the first place. And by the time they realize what happened, they're two years into a role that's hard to explain to the next hiring manager and even harder to reverse.

Why This Pattern Keeps Happening

Let's be direct: companies don't always do this maliciously. But intent doesn't change impact, and the pattern is real and documented. Research consistently shows that women are more likely to be pushed toward people-management tracks early in their careers, while their male peers are encouraged to deepen their technical expertise. In frontend specifically — a discipline that already fights for respect at the engineering table — this creates a compounding problem.

Here's the dynamic: a woman becomes the most reliable person on the team. She communicates well, she helps onboard new hires, she keeps the documentation up to date (yes, that article you read here about the invisible tax on documentation? completely connected). Leadership notices these qualities and assumes they point toward management. What they're actually noticing is someone who's good at their job and good at the soft skills that make a team function.

But "good at soft skills" gets quietly relabeled as "not a technical lifer," and suddenly the promotion track shifts from Senior Frontend Engineer → Staff Engineer to Senior Frontend Engineer → Frontend Team Lead (no IC work, reduced scope, same or marginally higher salary).

That's not a promotion. That's a reclassification dressed up in a bow.

How to Recognize the Trap Before You're In It

Not all leadership roles are lateral moves — some are genuinely expansive, high-impact positions that keep you close to the craft. The difference is in the details, and you have to ask for those details explicitly.

Red flags to watch for:

• The role is described in terms of what you'll coordinate rather than what you'll build
• Your technical contributions drop below 30-40% of expected output
• The compensation bump is smaller than what a Senior → Staff IC track would offer
• There's no clear path back to deep technical work if you decide this isn't for you
• The job description includes phrases like "bridge between business and engineering" without specifying what engineering work you'll still own
• Nobody can tell you what success looks like technically — only relationally

If a role checks two or more of these boxes, you're not looking at a promotion. You're looking at a pivot that benefits the org more than it benefits you.

The Salary Math Nobody Talks About

Here's where this gets genuinely expensive. The Staff Engineer track — the one where you stay deeply technical and grow your scope and influence without moving into people management — consistently pays more than the management track at the same career stage. A Staff or Principal Frontend Engineer at a mid-to-large tech company in the US can command $180K–$250K+ in total comp. A Frontend Engineering Manager at the same company? Often $160K–$200K, with a ceiling that's harder to push through without moving into Director-level roles.

When women are nudged off the IC track early, they lose more than job satisfaction. They lose years of compounding technical credibility — the kind that leads to conference talks, open source influence, and the job offers that come to you instead of the ones you have to chase. They also lose leverage. It's much harder to negotiate a return to senior IC work after three years in a coordination-heavy role than it is to negotiate upward from a strong technical position.

What Genuine Advancement Actually Looks Like

If you're being offered a leadership role and you want to evaluate whether it's real, here's what to push for in the conversation:

Ask about the technical ownership. What systems, features, or architectural decisions will you own? Not influence — own. There's a difference.

Ask about your IC time. What percentage of your week will be spent writing, reviewing, or directly contributing to code? If the answer is vague, that's information.

Ask about the growth path. Where does this role go in two years? Three? Is there a defined path to Staff or Principal Engineer if you decide you want to stay technical? Or does this track only lead toward Director of Engineering?

Ask about comp benchmarking. Request to see how this role is benchmarked against the Senior and Staff IC tracks. If the company won't share that, find out why.

Negotiate the structure, not just the title. You can ask for a hybrid scope — one that gives you leadership responsibilities and protected time for technical contribution. Some companies will say no. But a company that won't negotiate the structure of a role with someone they're supposedly promoting is telling you something important about how they'll treat you once you're in it.

If You're Already in the Trap

Maybe you're reading this and recognizing a situation you're already two years deep in. First: you're not stuck, and you're not behind. But you do need a plan.

Start by auditing your current technical skills. What have you been doing? What have you not been doing? Identify the gaps and start closing them — side projects, open source contributions, taking on a specific technical initiative at work even if it's not in your job description.

Then have an honest conversation with your manager about your trajectory. Frame it as wanting to understand your long-term growth path, not as a complaint. Ask specifically about what it would take to move toward a Staff Engineer title, or whether a role restructure is possible.

If the answer is that the org simply doesn't have that path for you, then the conversation shifts to whether this is the right org for where you want to go. That's a hard conclusion, but it's better than spending another two years optimizing for a ceiling.

You Get to Define What Advancement Means

Some women genuinely want to move into people management — and that's a completely valid, powerful career choice. The problem isn't management tracks. The problem is when those tracks are presented as the option rather than an option, particularly to women who've shown they're capable of both.

You built the skills that got you noticed. You get to decide what you do with them next. The next time someone offers you a step up, it's worth taking ten seconds to ask: a step up toward what, exactly?

Because the view from a lateral move looks a lot like a ceiling — and you deserve a much better view than that.