In russian, we have a common saying "царь-батюшка хороший - это бояре у него плохие". Loosely translated in english as "The King is kind, it's his the nobles that are bad." It is meant to be used as sarcasm.
Perhaps it is obvious, but in case it isn't: the meaning is that the person in charge of things is ultimately responsible and sets the tone for the rest of the organization, either by action or inaction.
That is why these sorts of things are a good test of management maturity. If problems like this get reflected up to the person in charge (and ultimately responsible), and nothing happens, then it is on them. If they go up and the metrics change so they can't happen in the future, then its a company learning from its mistakes. If you witness the full cycle (a problem emerges, the folks who are responsible are notified, they take some action, the problem persists, and there is no new update) then you can confidently choose to leave knowing that the people at the top want it to be that way, if on the other hand you see problems get fixed as they arise, then you can confidently choose to stay, knowing that bad situations are not intentional and will be fixed.
The Pregnancy Discrimination Act (PDA) forbids discrimination based on pregnancy
when it comes to any aspect of employment, including hiring, firing, pay,
job assignments, promotions, layoff, training, fringe benefits,
such as leave and health insurance,
and any other term or condition of employment.
Completely illegal.So good in theory, not really useful in practice. Sometimes a useful tool for enhancing your severance package. And you have to think about fighting to stay employed at a company that is kicking you to the curb because you're pregnant. What else might they do? It does push people closer to unionizing though, and that is becoming a bigger threat for tech companies than it was due to shennanigans like this.
An organization as large as Google... can violate as many laws as they wish to. That does not mean that they should not suffer gravely for it.
One of the weird things is 'success metrics telephone tag.' Basically it works like this; Boss creates a function and defines what it means to be successful. Hires a group to do that function. The group grows and its bifurcated into sub-groups which each have a part of the problem, and each has their own "success metric" which should, in theory, contribute up to the top level metric. However, there are no 'peer ranking' of the metrics, so if you have one group that is keeping your HR costs under control (success metric is 'cost per employee') and you have another group with is keeping your employee's happy (success metric is 'employee retention') and a third group which is keeping employees productive (success metric 'revenue per employee'), they all sum up, in theory to success metric 'keeping people happy and productive at the lowest possible cost'.
Now you find an employee who discloses a condition which will both cost the company money (benefit payout), and reduce productivity (external issues, loss of focus at work) and suddenly two parts of the HR group are having their success metric impacted by this event. You can reduce that to only one group making the person quit. So from the top level "we're hitting two of our three metrics" is a better report to send up then "we're hitting one of our three metrics".
A fix for this is an suitably enlightened senior manager providing scale options, so "retain good employee" gets a weight of '6' and 'save money' 2, and 'productivity' 3. Now when you score it retaining them gets you 6/11 but getting them to quit only gets you 5/11. Retaining your best employees becomes the managed-to goal.
Understanding how a company approaches those problems will say a lot about the quality of its management and the maturity of its processes.