It's really hard to know the right way to hire SRE's/sysadmins/systems engineers, from a startup's perspective. If your founders are highly technical, they're more likely to be developers, which is a similar profession but frankly different enough to note. In some cases they will be designers, or non-technical people entirely. As your company grows, you need to hire developers first, so at best, you find a (decent) solution to that problem. As we already know, though, nearly every company that interviews and hires developers still does a shitty job at it--not because it's their fault but because it's a genuinely hard problem. It's only after you've grown awhile and your developers get tired of doing all the ops shit that you think to hire SRE's. But at this point, your culture and hiring practices are already pretty set, and set by people who aren't actually SRE's. It can be fantastically difficult to rollback this kind of momentum even if you do manage to get a top-notch SRE or three onboard.
There's another side of this, though. It's both a root cause for the problem and good news for Airbnb: Airbnb's competitive advantage is not going to be having the best SRE's. They're not AWS, Heroku, or Google. So it's not really a problem if they're bad at hiring SRE's, because most companies get away with being bad at things that aren't central to their business. What Airbnb gets right, they get fantastically right. This isn't to say they shouldn't do a better job hiring SRE's. They should. But they're still a great business despite this.