We Have a Comfortable Habit of Studying What We Should Be Fixing
Every eighteen months or so, a regional economic development organization publishes a report on St. Louis tech talent. The reports have good data, thoughtful framing, and careful conclusions. They note that college-educated young professionals leave the metro at higher rates than peer cities. They observe the compensation gap between STL and markets like Chicago, Austin, and Denver. They identify structural weaknesses in the startup funding pipeline. Then they propose task forces, summits, working groups, and follow-on studies. And the talent keeps leaving.
This piece is not going to be polite about that pattern. The brain drain from St. Louis is real, it is accelerating, and the institutional response has been so thoroughly inadequate that describing it as a response is almost charitable. The organizations that should be driving change are more comfortable analyzing the problem than owning accountability for solving it. That needs to be said directly, because nothing changes until the diagnosis stops being softened.
The people leaving are not abstractions. They are software engineers who graduated from Wash U or Mizzou and took a job in Austin because the compensation was $40,000 higher and the growth trajectory was clearer. They are product managers who built something real at a local startup, watched it stall for want of Series B capital, and accepted a remote offer from a Bay Area company. They are data scientists who liked St. Louis as a city but found that the senior roles simply did not exist here in the concentration they existed elsewhere. They tried to stay. Then they left. And we held a summit about it.
"The question is not whether STL has talent. Washington University, SLU, and Missouri S&T produce serious engineers and builders every year. The question is whether we have built an economy that gives them a reason to stay."
The Four Structural Causes Nobody Wants to Own
The brain drain is not a mystery. Its causes are documented and specific. Treating them as complex or ambiguous is itself a choice, one that lets the institutions responsible for fixing them off the hook. Here is what is actually happening.
Cause One: No Anchor Tech Employer
Every city with a durable tech talent base has at least one anchor company: a large, well-capitalized technology employer that creates a thick market for technical skills, sets compensation benchmarks that other employers have to compete with, and produces a generation of experienced operators who go on to start or lead the next wave of companies. Seattle has Amazon and Microsoft. Austin has Dell, Oracle, and the alumni network that spun out of those firms. Raleigh-Durham has the Research Triangle's concentration of tech and pharmaceutical employers. Chicago has a broad base of financial technology and enterprise software companies anchored by decades of financial industry presence.
St. Louis has no equivalent. Centene is large but is a healthcare payer, not a technology company. World Wide Technology is impressive as a systems integrator but does not create the kind of product engineering culture that seeds a startup ecosystem. The technology divisions of major St. Louis corporations, Emerson, Edward Jones, Anheuser-Busch InBev before its acquisition, have not historically positioned themselves as tech employers competing for talent on national terms. The result is a thin market where a software engineer with five years of experience has far fewer senior opportunities than they would in any of the cities they are being recruited to.
Anchor companies are not recruited into existence through tax incentive packages. They are grown from companies that reach scale, which means the solution is a sustained startup ecosystem that produces companies large enough to anchor the market. STL has not done that yet. The question is whether it is even trying seriously.
Cause Two: Late-Stage Funding Is Broken
St. Louis has developed a reasonable early-stage startup infrastructure over the past decade. Cortex Innovation Community has been genuinely important. Arch Grants, Capital Innovators, and the ecosystem around BioSTL have created legitimate on-ramps for founders. The city can point to real deal flow at the seed and Series A level.
What happens next is where the system breaks down. When a St. Louis startup reaches the point where it needs a $10 million to $30 million growth round, the local capital is largely tapped out. The firm either raises from coastal venture capital, which typically comes with pressure to relocate to a market closer to the investors, or it runs lean, grows slowly, and loses the talent it hired during its high-growth phase when those people realize the trajectory has flattened. Either outcome drains talent from the city.
Local institutional capital, pension funds, family offices, corporate venture arms, has not mobilized into St. Louis tech at the scale necessary to bridge this gap. The civic will to write the large checks that create large companies has not materialized. What has materialized is a lot of language about being a rising tech city, paired with capital allocation decisions that look nothing like a rising tech city.
Cause Three: The Compensation Gap Is Real and Widening
The numbers are not in dispute. A mid-level software engineer in St. Louis earns roughly 25 to 35 percent less than their equivalent in Austin, and 30 to 40 percent less than in San Francisco or New York, even after adjusting for cost of living. In raw dollars, the gap at the senior level can exceed $50,000 annually. For a 28-year-old with student debt and career ambitions, that differential is not abstract. It is the difference between accelerating toward financial security and running in place.
Remote work changed this dynamic in a way that most STL employers have not fully reckoned with. When the best local engineers could only compare their St. Louis salary to other St. Louis salaries, the gap was invisible. Now they compare it to remote offers from companies in every market, and the gap is explicit, quantified, and attached to a job description they received by email last Tuesday. The talent that stays in St. Louis today is staying out of preference for the city, not because the economics are compelling. That is a fragile retention mechanism.
Cause Four: Tech Culture Is Too Geographically Narrow
The St. Louis tech ecosystem, such as it is, clusters almost entirely in Clayton, Brentwood, and the Cortex corridor between Forest Park and Midtown. That concentration is understandable historically, but it has created an ecosystem that is inaccessible to the majority of the city's geography and population. The entrepreneurial energy, the networks, the mentorship, the capital access, the job density that creates a genuine tech culture: it does not exist in north St. Louis, in south city, in Wellston, in Jennings. It barely exists east of Grand Avenue.
This is a problem for two reasons. First, it means the city is drawing from a narrow talent pool concentrated in a narrow geography. Second, it means that the residents of neighborhoods with the most economic need are the least connected to the sector with the most economic upside. Cities that have successfully built broad tech ecosystems, Detroit's near east side, Atlanta's Westside, Pittsburgh's Hill District, have done it by intentionally extending infrastructure, capital access, and employer presence into neighborhoods that the market would not reach on its own. St. Louis has not done this in any meaningful way.
What the Institutional Response Has Actually Looked Like
To be specific about the institutional failure, consider what has happened over the past five years at the civic level. The St. Louis Economic Development Partnership has produced strategic plans. Greater St. Louis Inc. has organized business coalitions. The Regional Business Council has convened executive roundtables. Wash U and SLU have both launched entrepreneurship initiatives. The state of Missouri has offered various incentive structures for tech investment.
None of this is worthless. But none of it has moved the needle on the metrics that actually matter: venture capital deployed per capita, number of companies reaching 200 employees, compensation benchmarks at the senior engineer level, and net migration of tech talent into versus out of the metro. On all of those measures, St. Louis is not winning. On most of them, it is losing ground to peer cities that started from similar positions.
The pattern is consistent: convene, study, plan, announce, and measure inputs rather than outcomes. How many startups applied for the program? How many mentors were recruited to the network? How many square feet of innovation space were developed? These are input metrics. They tell you what resources were deployed. They tell you nothing about whether talent is staying, whether companies are reaching scale, or whether the competitive position of the city is improving. The fact that civic institutions continue to report on inputs while the outputs deteriorate is either a failure of measurement or a deliberate choice to avoid accountability. Either interpretation is damning.
What Would Actually Reverse It
The answer is not more summits. It is not another task force. It is three specific structural changes, and they require the kind of long-term commitment and risk tolerance that St. Louis civic institutions have historically been unwilling to make.
Anchor Company Formation
The highest-leverage intervention in any tech ecosystem is the growth of a company large enough to anchor the market. STL needs a technology company to reach 1,000 employees and national product relevance. That company probably already exists here in an early form. The work is identifying it, surrounding it with the capital and talent infrastructure to scale, and protecting it from the pressure to relocate when coastal investors come in. That requires local institutional investors to write checks at the growth stage, local corporate customers to buy its products early, and local government to structure incentives around retention rather than recruitment. The city has done none of these things consistently.
AI-Driven Industry Transformation in STL's Core Sectors
St. Louis has dominant positions in healthcare, financial services, logistics, and agriculture technology. These are not declining industries. They are industries undergoing profound transformation driven by AI. A city that positioned itself as the center of AI application in any one of those verticals would create an enormous demand pull for technical talent. Healthcare AI in a market anchored by BJC, SSM, and Mercy. Agricultural AI in a market anchored by Bayer, Centerre, and the Missouri ag economy. Logistics AI in a city that sits at the intersection of the Mississippi River, I-70, and the Burlington Northern rail network.
The talent does not need to be recruited from Austin. It needs to be given a reason to come home from Austin, or to stay when they would otherwise leave. An STL that is the obvious address for healthcare AI or ag tech AI creates that reason. But it requires the established industries to actually partner with and fund technology companies, not just announce pilot programs. The pilots that do not scale are worse than nothing, because they signal that the commitment is not real.
Building Tech Culture Beyond Clayton
The geographic concentration of the STL tech ecosystem is both a symptom of the brain drain problem and a cause of it. A city where the entire innovation economy clusters in three neighborhoods cannot attract or retain the full range of talent it needs. The deliberate extension of tech infrastructure, broadband, maker spaces, co-working, accelerator programming, and employer presence into north St. Louis, south city, and underinvested inner-ring suburbs is not charity. It is the expansion of the talent pool that the ecosystem draws from. The cities that have done this have not done it out of altruism. They have done it because a broader tech culture produces more companies, more ideas, and more talent retention than a narrow one.
This means capital investment in neighborhoods that have not historically received it. It means anchor institutions, Wash U, SLU, the hospital systems, intentionally locating programs and resources beyond their immediate campus environs. It means the tech companies that are here choosing office locations and hiring practices that build connection to the full city, not just the 10-square-mile corridor where they can avoid thinking about the rest of it.
The Honest Bottom Line
St. Louis is not losing its tech talent because it is an undesirable city. Anyone who has lived here knows that the cost of living, the food, the neighborhoods, the sports culture, and the genuine warmth of the community make it a place people want to live. The city is losing its tech talent because the economic proposition for a high-skill technology professional is weaker here than in the cities recruiting them away. That gap is structural, not cosmetic, and it will not be closed by better marketing or another innovation district ribbon-cutting.
The institutions that have been studying this problem for a decade need to start owning accountability for outcomes, not activities. The civic leaders who announce strategic plans need to report on talent migration rates and compensation benchmarks, not square footage and application counts. And the established businesses in STL's major industries need to stop treating tech companies as vendors and start treating them as strategic partners worth investing in.
The talent is here. The market is here. The industries that need transformation are here. What is missing is the institutional will to prioritize outcomes over the comfort of process. That is a choice, and it is being made every day by the people who run this city's economic institutions. They should be asked to justify it.
If you are building a business in St. Louis and want to understand how AI can help you compete and grow without waiting for the ecosystem to catch up, talk to Michai Media. We work with STL businesses that are not interested in waiting for someone else to solve the infrastructure problem.
