And in that scenario, you're extremely vulnerable to that senior employee getting burnt out from spending most of their time doing code reviews and putting out fires rather than building things themselves. You're also vulnerable to that person getting an enticing offer from a big-name company in the valley or an exciting-sounding startup in SF. Many of these opportunities are even remote, so this can happen even when your best employees don't have any desire to move.
So yeah, it's possible to find good talent in other locales. But there's a lot more competition for that talent, it's hard to build a critical mass of it when the best employees are constantly moving away, and there are a ton of challenges you have to deal with as a result.
Smart engineers evaluate opportunities based on hard facts rather than "oh cool its a cool startup with ping pong in the office!" etc. I don't know why this image is so common when so many of the smartest people I've worked with have not been swayed by it as much as objectively assessing the cold, hard facts as to: what they would be doing, who would they be working with, what sort of impact can they have, etc.
It turns out that unless you're one of the big tech giants, or a super cool startup, you will not be hiring the best in SV. And you'll be paying for the privilege.
Most of these companies are now learning that Midwest based employees are just as good as their SV counterparts, and cost a whole lot less.