I want to write this carefully, because I want it to be true.
I spent four years in Oracle's Server Technologies Group — the team that works on Oracle RDBMS itself. The engine. This is not an application team. It is not a product team. It is the team that decides what happens when a query hits the kernel.
It's one of the more technically demanding environments I've worked in. And I was a woman there.
Here is what that was actually like.
The Thing About "Technical Credibility"
There is a particular dynamic that shows up in highly technical engineering environments that I want to name precisely, because naming it imprecisely makes it easier to dismiss.
It is not that women are openly told they are less capable. It is that the default assumption — before you have said anything, before you have shown your work — is calibrated differently. For men with the same level of experience, the assumption tends to be competence until disproved. For women, the calibration is more uncertain.
This means you spend energy establishing technical credibility that your male peers spend on other things. Every new context — a new team member, a new stakeholder, a new cross-timezone meeting — is a small re-establishment. You learn to lead with specificity. You reference the bug number. You cite the SCN. You name the ORA error code before someone asks.
It's not dramatic. It's just a tax.
What Helped
The work itself.
This sounds obvious but it isn't. The work at Oracle RDBMS was technical enough that results were legible. If you reproduced an ORA-600 that had blocked a Fortune 500 customer for three weeks, and you filed the bug, and the fix shipped in the next RU — that is legible. It is hard to dispute.
I filed 150 bugs. I managed 50 through their lifecycle. 13 shipped. I owned four RDBMS features end-to-end. I built the first parameterized vector search benchmarking framework in our team, which got adopted across multiple RDBMS engineering groups.
That body of work became the counterweight. Not perfectly — credibility gaps don't disappear because you have receipts. But receipts help.
What I Noticed About the Women Around Me
I worked with women who were extraordinary engineers. Deeply technical. Careful thinkers.
I also noticed that many of them — and I include myself in this — were less likely to claim credit loudly, less likely to push back in public-facing forums, more likely to do the unglamorous coordination work that holds teams together without being credited for it.
I don't think this is innate. I think it's adaptive. You learn what environments reward and punish, and you adjust.
The cost is that the adjustments become invisible, and then the gap between what women contribute and what they're credited for becomes a data point that people use to draw conclusions they shouldn't.
The Layoff
The April 2026 Oracle layoffs hit the India engineering workforce significantly. I was part of that cut.
I've thought about whether gender played a role. I genuinely don't know. Layoff decisions at that scale are made at a level where I don't have visibility into the criteria.
What I do know is that I was nominated for SMTS (IC3) promotion by my manager. That nomination existed. The layoff happened anyway.
I'm not going to claim certainty about cause where I don't have it. But I will say: it is harder to weather a layoff when you've spent years operating with a credibility tax that others didn't pay. The energy that went into establishing that credibility is energy that didn't go elsewhere.
Why I'm Writing Publicly Now
I'm building this site and writing publicly for several reasons, but one of them is this:
The women who came up behind me in engineering deserve to see that it is possible to do this work and be good at it. To work on database kernels. To file bugs against ORA-600 errors. To own features. To build benchmarking frameworks that get adopted by larger teams. To do the real work, the invisible work, the hard work.
It is possible. I did it. It wasn't always easy, and it wasn't always fair, but I did it.
I'm going to keep doing it. Publicly, now.
If you're a woman in backend engineering, database engineering, or infrastructure — this site is for you too. I write about the technical stuff because that's what I know. But I also write about what it's like to be a woman doing the technical stuff. Because both things are true and both things matter.