Quote:
Originally Posted by UPChicago
Personally, I'm not convinced that flight connectivity between the East and West Coasts matters much to Amazon; to put it another way, it is probably not a highly weighted priority. If the top executives are to stay in Seattle than what difference does national centrality make? If the senior executives were to move to this new HQ2, then, I think, the calculus would change.
|
Quote:
Originally Posted by marothisu
I have been employed by 2 Fortune 50 companies before and flight connectivity matters a lot. It's not just executives who fly ...it's others. There was and is a lot of corporate travel at both companies. It does not matter if most executives are in Seattle (which would be BS because whoever gets 50,000 employees will get a lot of executives...existing or new..in with that. Ridiculous statement to think that all the execs will just be in Amazon. That's not usually how it works at "newer" tech firms and departments who value colocation, which is a path many companies are now embracing).
I guarantee you this is important to them. Not the most important thing, but the fact they put it as a req and my own experiences in big companies that care about flight connectivity leads me to this conclusion.
|
Amazon flies in candidates for interviews in Seattle (including me once) every single day. It wouldn't surprise me if there are dozens of people in Seattle every day interviewing for jobs. I wasn't even that competitive of a candidate for the specific job they were interviewing me for and they flew me in. They have hundreds, if not thousands, of postings in Seattle at any given time and if they are serious about 50,000 jobs in HQ2 that means thousands of postings every year, along with many, many flights for probably several decades. Centrality for flights and, just as importantly, competitive costs, which a dual-hub helps ensure, are certainly highly important to them.
Even just for non-recruiting business, they will have staff who fly out and back every week for sales, for product evaluation, for AWS-related consulting, etc, etc, as well as executives jetting between locations (not just between Seattle and HQ2, but between HQ2 and their other locations both in the U.S. and around the world. An HQ2 in Chicago could realistically mean several more flights a day just due to the volume of business Amazon conducts. Choosing a place like Indy or Austin would mean many more multi-leg flights for people Amazon flies around the country, which is a waste of time and an increase in unreliability, both of which are bad for morale and the bottom line.
So, yeah, having a well-connected airport (or airports) located near HQ2 is very important. New York, Chicago, and Atlanta are the far and away leaders in that category. O'Hare by itself flies more than a million passengers per year to four destinations - New York, LA, San Francisco, and London. Philly doesn't send a million passengers anywhere - only five destinations top a half million. Total passengers at O'Hare are 2 1/2 times as many as for Philly's airport, and that doesn't even factor in Midway - with Midway, Chicago has over 3 times as many air passengers as Philly.
Philly does have one advantage over Chicago when it comes to transportation - it has Acela to Manhattan in 1.5 hours or less and to D.C. in 2 hours or less. That is a big advantage, as almost everyone prefers Acela over planes, especially since you can go city-center to city-center and security is somewhat less terrible. How important that is to Amazon, I don't know, but as they might say in Boston, "it's not nothin'."