IWD 2026 - Creating a durable tech career in the age of AI
International Women's Day surfaces two things: celebration, and the question of how gender shapes a career.
Over the years, I have seen all of it.
A young female engineer accelerating at an impressive pace.
A manager openly expressing age bias.
A brilliant architect stepping down from authority.
A 50+ engineer hired instantly because she was sharp.
The narratives conflict. Let's look at the structure underneath them.
If we treat a career as a long-lived system rather than a sequence of jobs, different questions emerge:
- What compounds?
- What reduces fragility?
- Where does leverage accumulate in an AI-era market?
Celebration is valid. Frustration is valid.
Neither alone builds durability.
Architecture does.
Knowledge Compounding
Years ago, I met a female engineer who impressed me deeply. She was confident, sharp, and seemed years ahead. When I asked how she grew so quickly, her answer was simple:
"I take tickets, I don't know how to do. I build, read, ask questions, and ship by the end of the sprint."
That is learning at the boundary of your competence. It compounds fast.
Since then, I deliberately choose tasks that feel slightly uncomfortable: new systems, unclear ownership, and technical ambiguity.
It is uncomfortable. That is where growth happens.
Youth Bias
Recently, I spoke with an engineering manager in her early 30s who told me she would not hire anyone over their early thirties because "they have families and won't work days and nights to meet deadlines." Her assumption: older engineers are not as productive.
It stung for a moment. Then I remembered: I continue to get hired.
Some markets optimise for speed and youth. Others optimise for pattern recognition and expensive lessons already paid for.
We should choose our game field deliberately.
Sharpness Overrides Age
I have interviewed many candidates recently - different ages, genders, and backgrounds.
What stood out was not age or gender, but aliveness: intellectual sharpness, ownership, positive energy toward hard problems, and the ability to collaborate.
We hired an engineer in her 50s without hesitation. There was no debate.
Authority Fatigue
A brilliant engineer once told me he stepped down from an architect role.
Why?
Architectural decisions create disagreement. Authority attracts friction. Over time, that friction accumulates.
It was a useful reminder: we should test roles before romanticising them.
Only by doing something do we learn whether we actually want it.
Gender
Some female engineers I know feel gender bias strongly and expect slower progress because of it. Others progressed rapidly and barely experienced friction.
Both realities exist.
Bias exists. So do self-imposed ceilings.
When we stay too long in execution-only roles, avoid negotiation, and prioritise delivery over scope, we quietly reduce our own leverage.
System design applies to careers too.
The Reality (No Drama)
At first glance, these stories look contradictory. They aren't. They are signals.
Market contractions are cyclical. AI-related shifts are structural.
Junior positions are contracting. Feature implementation is accelerating. The cost of delivery is decreasing.
What is becoming more expensive is not delivery, but designing architectural boundaries, understanding trade-offs, and making decisions that are hard to reverse.
That is where leverage lives now.
And leverage compounds.
My Internal Shift
I love building - learning new frameworks, solving complex problems elegantly. For years, that was enough. But building alone is not a strategy.
A few years ago, I began thinking in leverage terms:
- Where is fragility in my career?
- What layer should I operate on?
- What decisions increase optionality?
That shift changed everything.
What Works for Me
I optimise for leverage, not comfort.
- I ask people with leverage how they built it.
- I negotiate deliberately, not emotionally.
- I expand scope beyond execution.
- I take boundary problems others avoid.
None of this looks dramatic.
That is precisely why it works.
Throughout my career, I have seen acceleration, bias, fatigue, and sharpness override assumptions.
The young engineer who took uncomfortable tickets grew fast because she operated at her boundary. The manager who filtered by age was optimising for one dimension of value. The architect who stepped down reminded me that authority has cost. The 50+ engineer we hired proved that capability still wins when it is visible and current.
Taken together, these stories are not contradictory. They describe a market that rewards leverage.
AI is making feature delivery cheaper, and that trend will likely continue. Judgement, on the other hand, is becoming expensive.
If we stay in pure execution, we compete where price is falling. If we design boundaries and shape decisions, we move into a layer where value compounds over time.
Durability is not optimism, denial of bias, or escalation of effort.
It is choosing the layer of the system where leverage accumulates.
Cycles still come. Fragility decreases.
Not celebration. Not victimhood.
Architecture.