Guest Post: Your city never stood a chance of HQ2
Last week our article from Chicago provided interesting insight into HQ2 and its selection. We reached directly out to Jeffrey Carter when we saw his blog post because we thought it was really insightful. In response to Carter’s post, LaunchCode of St. Louis reached out to ask if we could publish the following post. This…
Last week our article from Chicago provided interesting insight into HQ2 and its selection. We reached directly out to Jeffrey Carter when we saw his blog post because we thought it was really insightful.
In response to Carter’s post, LaunchCode of St. Louis reached out to ask if we could publish the following post. This is something that we do – but we screen carefully. This is not an advocacy pitch for Launchcode. This is also not a sponsored post. However, we thought it was a smart way to provide context regarding talent in the Silicon Prairie and the broader Heartland.
Obviously, not every community in our region is covered, but we hope that you appreciate the perspective of thinking about the challenge of recruiting large projects in a region with low unemployment and a stretched technology talent pool. As such, we thought it was a good, useful opinion for you – our readers.
Moreover, we are a blog about technology and entrepreneurship. The message and goals ring true to us and our tribe. Thanks for reading. Happy Thanksgiving!
Your city never stood a chance.
Author: Daniel Fogarty, Vice President of Growth at LaunchCode
After months of waiting, it’s finally confirmed Amazon will split HQ2 between two cities, citing lack of talent to fill the estimated 50,000 jobs. But a deeper dive into even the top contenders’ talent pools reveals the harsh truth — most cities never stood a chance.
It was clear from the start what Amazon was looking for in a proposal. The 50,000 full-time jobs will be filled from what Amazon’s RFP calls “a highly-educated labor pool” and only cities who could produce that pool would be serious contenders — nearly every rejected city that chose to publicly release feedback revealed that Amazon cited an insufficient pool of tech workers. Not surprising, considering half of the 50,000 jobs are predicted to be software developers, which aren’t exactly just laying around for the taking.
When we look at the concentration of where software developers work around the nation, the data is telling. Only eight U.S. cities have more than 50,000 software developers, and only 16 have more than 25,000. And not surprisingly, only two of the eight cities are non-coastal. Sure, some of the speculation around HQ2 being split among two East Coast cities is centered around rumors of Jeff Bezos’ recent real estate purchases, but considering Amazon’s talent pool needs, it’s quite possible there were way less horses in the race than we thought. And even the rumored front-runners don’t have the tech talent numbers to sustain all 50,000 jobs. And that says a lot.
|San Jose-San Francisco-Oakland, CA||153,330|
|New York-Newark, NY-NJ-CT-PA||133,830|
|Los Angeles-Long Beach, CA||74,100|
|Dallas-Fort Worth, TX-OK||51,420|
|Atlanta–Athens-Clarke County–Sandy Springs, GA||42,840|
|Detroit-Warren-Ann Arbor, MI||32,540|
|Minneapolis-St. Paul, MN-WI||28,280|
|Houston-The Woodlands, TX||26,420|
|Austin-Round Rock, TX||25,770|
Looking at the Heartland cities that did make the coveted finalist list, their current developer employment numbers most likely cancelled them out instantly in this competition.
(SPN EDITOR NOTE: If you are interested about your own community, this data is available through the Bureau of Labor Statistics – in 15-0000 and the subcodes. https://www.bls.gov/oes/current/oessrcma.htm#N)
Not only did most cities not stand a chance. Cities in the Heartland really didn’t stand a chance.
I think we can all get behind one thing: we all want resurgence in the Heartland. A recent Brookings report validates the economic growth and incredible opportunity happening in older-industrial cities in the Heartland. And contrary to popular opinion, it’s all happening without Amazon. The idea that Amazon’s HQ2 would swoop into a mid-American city, drive great inclusive growth and revive a once-booming economy is absurd. And it’s a narrative that’s been common among HQ2 headlines throughout the year. The simple fact is that Amazon was never in the business of revitalizing a fly-over city. It’s in the business of driving profit.
My hope is that the Heartland cities that convened a team of the best and brightest of their region to propose millions of dollars and unlimited resources to win this competition at least learned something. Imagine if the same money and resources were spent solving the shortage of tech talent affecting the businesses already thriving in these cities? Could they have developed and executed a plan to cultivate and encourage STEM education and career awareness in their school systems? Could they have put hundreds or even thousands of driven individuals through accelerated, skills-based programs like coding bootcamps or funded entire cohorts of free, job-ready classes like the ones LaunchCode offers?
This week’s news just echos what the numbers already tell us: not one city in our entire country boasts enough tech talent to feed a future HQ2. To truly flip the script, we need city leaders more interested in developing talent pipelines and building a workforce and less interested in incentivizing big-tech companies with false promises.
Personally, I believe in the Heartland and the flame of inclusive economic growth already burning here. If anything comes of this year-long media circus, my hope is that local leaders begin to focus on channeling resources to grow and scale what they already have instead of attracting a big-tech unicorn that was never going to land in their city to begin with.
Daniel Fogarty is the Vice President of Growth at LaunchCode, a national workforce development nonprofit founded in St. Louis by Square’s Jim McKelvey and focused on cultivating tech ecosystems across the nation.
JOIN THE MOVEMENT!
Sign up to receive daily updates in your inbox.