Ultimately, I ended up deciding that what I wanted couldn't be achieved inside Google, but they certainly made the effort.
That's a characteristic of lifetime employment, not the kind of jobs under discussion here.
How to do that? That is the hard part, net work and move on when you work for a bad one.
When I was a manager in a small startup, I tried to regularly discuss their career goals and how they could develop towards those goals. One of the benefits of a startup was that we had a lot of flexibility to create experiences matching those goals.
I know that Intel has changed. A lot. But in the early 1980's Andy Grove (as President, before he was CEO) came up to Oregon to speak to the employees. Someone asked him when they were going to have showers for the employees. Andy responded "Intel is a place of employment, nothing more."
That's not easily forgotten, even though Intel did eventually install showers while Andy was still in charge!
Of course good managers care about their reports, regardless of the tone set by top management.
(I'm also surprised/disappointed at how rarely that advice is taken - there's a _very_ strong tendency for people to "stay put" in a sub optimal career position instead of taking the risk of jumping into the unknown and possiby scarey "next level up". So many devs tell me "I'm not ready for a mid level role yet" or equivalent, even when thay _clearly_ are...)
There's a difference between being ready for a midlevel role, in the sense of being able to take on the responsibilities and requirements, and wanting to take on the midlevel role. For example, if a developer sees that the "seniors" on his team 1) don't get to program as much, because they're in meetings all the time 2) have a lot more stress, because of having to take responsibility for design decisions 3) don't get compensated very much more and 4) sacrifice their ability to switch jobs easily by becoming more specialized in the methods and practices of the company they're currently working for, I think it's entirely rational for the developer to not desire that promotion.
But, of course, it's not politic to say, "Oh, I don't want that promotion, because it's a lot of work and I don't see any upside to it," so people make euphemisms. Saying, "I'm not sure I'm ready for that," is a good way of demurring while not causing offense, and simultaneously leaving the door open so that they can be considered for a promotion in the future.
The next time someone says that they're not "ready" for a mid-level role, I would like you to ask yourself, "Are they not ready, or are they not willing?"
There may also be some distrusting "Why is my manager encouraging me to leave? I'd better dig myself in and make sure I don't fuck anything up" thoughts (although I'd like to think I'm not thought of as "that guy").
But I also see cases that are closer to a reverse Dunning Kruger effect, people who just don't realise (or admit to themselves) how good they are compared to their peers. (Sometimes at an astonishing penalty to their earnings...)
Which is the primary reason why earnings are typically kept secret. Company policy almost certainly prohibits you from saying: "John makes 110k/y Joe, you are three times as good as John and you make 90k/y, we most certainly are not going to pay you 330k/y, but maybe you should ask for a 30k raise ?"
An employer doesn't train people, they hire those with the skill. If an employee is no longer valuable, the employee moves on. The employer has no particular interest in or control over the employee's career before or after their 'assignment'.
That's interesting. I've had a number of managers in my career and never, not even once, has one of them espoused anything resembling such a position. It's always what can the employee do for the company, not what's mutually beneficial.