The turbulent AI era is here. The choices we make now are critical

Mike's Notes

Another opinion piece on the impact of AI. This time from Bill Gates.

I'm publishing a range of opinions from different writers on this blog.

My Opinion

My opinion is that AI is a good thing, despite its weaknesses and the need for much more work to fix its problems. However, the financial numbers don't stack up for the money being spent. It seems like a speculative bubble, and someone is going to go broke.

Gary Marcus

Gary Marcus wrote this recently:

Excellent new essay by Bill Gates, echoing many of the themes I have been writing about here and in my 2024 book Taming Silicon Valley:

    • The critical, lasting importance of the decisions we make now.
    • The risks that AI creates, around bioterrorism, deepfakes, disinformation, cyberattacks, and so on, empowering criminals such that “Even criminals with very limited skills will be able to target victims at every scale”. He also argues (though I did not anticipate this in the earlier book) that “AI could stunt our kids’ development and replace human relationships”.
    • The urgent need for—and lack of—a systematic plan for how society will address AI.
    • The importance of having civil society, and not just government and tech companies, centrally involved in devising that plan. (I would also emphasize the critical need for including independent scientists, which Gates does not make explicit).
    • The importance of “creating a domestic and international framework for dealing with AI”.
    • The need for tax structures and incentives to keep humans employed, and for “rebalanc[ing] how we tax labor and capital.”

...

Resources

References

  • Taming Silicon Valley: How We Can Ensure That AI Works for Us, Gary Marcus, MIT Press. 2024.
  • Magnifica humanitas. Encyclical Letter of His Holiness,  Pope Leo XIV on safeguarding the human person in the time of artificial intelligence. Holy See. 2026.

Repository

  • Home > Ajabbi Research > Library > Subscriptions > Gates Notes
  • Home > Ajabbi Research > Library > Subscriptions > Marcus on AI
  • Home > Handbook > 

Last Updated

09/09/2026

The turbulent AI era is here. The choices we make now are critical

By: Bill Gates
Gates Notes: 27/08/2026

William Henry Gates III is an American businessman and philanthropist. A pioneer of the microcomputer revolution of the 1970s and 1980s, he co-founded the software company Microsoft in 1975 with his childhood friend Paul Allen.

...

We need a plan to ensure that the good outweighs the bad.

...

What you need to know

The transition to the AI era will be one of the most turbulent times in human history. Right now, we are not preparing adequately for that transition. If the world takes the right steps, AI will be a force for good and leave everyone better off.

During my entire life I’ve only had two jobs. In the first one, I played a role in developing software to empower people through my work at Microsoft.

In my second one, which I started full time in 2008, I am giving back the wealth I made at Microsoft with the goal of making the world a healthier, better educated, and more equitable place. This is the job I will have for the rest of my life.

Both of these experiences inform my perspective on artificial intelligence. When I first learned about computers at age 13 I was fascinated by the idea of making them more intelligent and able to perform things that, at the time, only humans could do. Although the term “AI” was used from around the time I was born, the technology has only made significant progress in the last decade. It is now incredibly capable and it is continuing to improve at a mind-blowing rate. AI for the first time can replace and even exceed human cognition.

AI will either be the greatest equalizer ever invented, or the worst source of injustice.

In terms of equity, AI will either be the greatest equalizer ever invented, or the worst source of injustice. The challenge is monumental. Even under the best circumstances, the transition to this new AI era will be one of the most turbulent times in human history. How will we use this technology to make the world a fairer place and keep it from widening the divide between rich and poor? How will we protect the people who are most vulnerable to the harms caused by artificial intelligence, including those who lose their livelihoods and the sense that they are in control of their future?

I believe that answering these questions and acting on the answers should be the world’s top priority. If the world takes the right steps AI will be a force for good and leave everyone better off.

Unfortunately, right now we are not preparing for it. I don’t see evidence that leaders, experts, and communities are confronting the challenges adequately. There is no plan to ease the entry into the AI era.

Part of the reason for this is that many commentators underestimate the extent of the impact AI will have. I think there are a few reasons why.

One is the fact that AI models still make mistakes. It is hard to envision any of them replacing human cognition when, not long ago, they couldn’t solve a simple Sudoku puzzle or figure out how many R’s are in the word strawberry.

But the reliability problem is being fixed quickly, as researchers create models that can check their own work and improve themselves. Soon they will be substantially better than humans at many tasks.

Another reason people underestimate AI is that analogies to the effects of past innovations are misleading. We have no experience with a technology that can be adopted quickly or that can think and move like a human. When the PC came along, it took twenty years to significantly change how we worked because the software had to be developed, the price had to come down, and people had to learn how to use the tools and incorporate them into their business processes. AI, on the other hand, runs on the devices we already have, and it uses natural language. We don’t have to adapt to it because it can adapt to us. It can watch the same training video that is used to train human workers and learn from existing data.

I want to acknowledge a potential bias. I have benefited enormously from the technology industry. Although I have diversified my portfolio quite a bit, I still have financial ties to it. I am working with Microsoft and other AI companies in my role as chairman of the Gates Foundation to try and ensure AI is deployed in ways that will truly benefit people around the world.

However, my views on AI are not motivated by the potential to make money for myself. Any profits generated by my investments, including those related to technology, will go to the Gates Foundation to tackle global inequity. Of course, readers will have to decide for themselves whether this clouds my view.

This time really is different.

For as long as I can remember, I’ve wished innovation could happen faster. With AI, my feelings are more complicated.

We need time to prepare for the social, political, and economic upheaval.

I wish the world could get the benefits rapidly and delay the problems it will cause as long as possible, but the benefits and problems are arriving at the same time. I believe we need time to prepare for the period of social, political, and economic upheaval we are about to enter. The people who need the most time are the ones who have the least—the accounting worker who’s replaced by a bot or the $20-an-hour worker who loses their job to a $10-an-hour robot.

Many observers say that this technology transition will be like previous ones. They give the example of how jobs in the United States shifted from agriculture to office work. However, that proceeded over several generations and created new jobs where human cognition was required. In this case, the technology can substitute for human cognition.

Because it can see, listen, speak, and reason and will eventually do physical work just as smoothly as any human, it will not just affect one sector. AI will take on work in law, customer service, medicine, software, and manufacturing. It will hit these industries rapidly, over the course of a decade rather than a few generations. There will be some new jobs, but without the right policies there will be far fewer than exist today.

If someone had a credible plan for slowing down AI advances globally, I would likely support it. However, I don’t think that’s going to happen. The geopolitical and economic incentives are pushing too hard to go full speed ahead.

To make sure we maximize the positive effects of this unprecedented technology and minimize the bad so we are better off overall, we need to understand both the benefits and the risks. I’ll start with the risks.

The transition to AI comes with three big risks.

I plan to write about each of these in more detail in the future, so I’ll touch briefly on them for now.

Many jobs will disappear forever.

In 1933, during the Great Depression, unemployment in the United States was roughly 25 percent. It remained in double digits for much of the following decade. It ultimately recovered as demand, investment, and growth returned.

AI may not reach this level, but its impact will not go away with an economic cycle. The jobs at most risk are entry- and mid-level, and the new jobs being created will mostly require skills that take many years to learn.

White-collar jobs are already being hit modestly. After the widespread adoption of generative AI, employment fell significantly among young workers in jobs that are especially vulnerable to replacement, but not among their older colleagues.

I think this trend will continue, but it will not be confined to a handful of industries or occupations. Jobs in sales and customer support (online and over the phone), software engineering, and paralegal work may be among the first affected, but the disruption will reach much further as AI takes on tasks that today still require trained workers: things like assessing loan applications, doing data analysis, and even triaging patients. A few areas like software engineering will generate new demand as the costs go down, so the net job loss in those areas will be less than in others as long as some tasks, such as design, are better done by humans.

Blue-collar jobs will be affected as well. Although robots are not as far along as AI, eventually their cost will be dramatically lower too. Many Americans I talk to don’t realize how fast dexterous robots are advancing because much of the advanced work is being done in other countries, primarily China. Or they may be confused by those videos of robots dancing badly that have been going viral lately. I think “smart” robots will begin to compete with people on some physical tasks—in the construction and hospitality industries, for example—by the end of the decade.

Robots and AI combined can create a vicious cycle. After one company adopts them and uses the savings to lower its prices, its competitors will feel immense pressure to do the same. If existing companies don’t adopt them, then start-ups will. Many people will shift to other jobs, but the turmoil of losing work, getting retrained, and finding other work will be significant. Market forces will make adoption go faster and faster and, unless we intervene, there will be fewer good jobs available and the benefits will accrue to a small group.

I’m especially worried about young people, who will enter a workforce with fewer entry-level openings. They understand the challenge because they are the most active users of AI and see both the capabilities and the rate of improvement. It’s no wonder that so many of them feel negatively about AI.

The biggest shift for workers will happen when AI provides nearly error-free work. At that point, it will be able to function on its own without a human checking in on it, and companies will have every economic incentive to let it.

This will lead to a fundamental change in how we think about work, income, and economic security. How will an economy that’s been built around employment operate if fewer people are working, or if many people are working fewer hours?

In a capitalist society, employment is the way most people get the money they need to pay for the basics of life as well as being a key source of dignity and social connection.

When a community has high unemployment, the ripple effects can be pervasive. Research suggests that in some parts of the United States, factory closures contribute to a rise in deaths from opioid overdoses. Now imagine similar pressures on both white-collar and blue-collar workers nationwide.

We have to think now about how to reduce job losses so that everyone can share in the prosperity that AI creates. Waiting until people are already displaced or underemployed will be too late. AI is a structural challenge to the way our economy is organized, and it requires thinking and action now.

AI will empower people (and perhaps AIs) to do more harm.

Long before AI entered the mainstream, there was information online about how to create weapons like bombs, bioweapons, even computer viruses. AI will make it much easier to not only get this information but act on it. Even criminals with very limited skills will be able to target victims at every scale: individuals, companies, and governments.

Even criminals with very limited skills will be able to target victims at every scale.

AI-enabled fraud, disinformation, deepfakes, and surveillance are the harms that many people will feel most keenly in their everyday lives.

AI capabilities are starting to be used for cyberattacks. The smartest cybersecurity experts I know are scared about the next few years, because the attackers are getting powerful new capabilities faster than the defenders can fix all the weaknesses. After all, the same AI model that can find a flaw in software so a company can fix it can also help a criminal exploit it. The resources needed to make an attack are going down significantly and we haven’t been able to separate those abilities from benign usage.

Think about the infrastructure that will be vulnerable: hospitals, financial institutions, water systems, power grids, systems for managing government benefits. When these institutions are attacked, it’s the patients, customers, and benefits recipients who stand to lose.

The same goes for bioterrorism. Although AI will lead to lifesaving advances in drugs and vaccines, it will also make it easier to design a deadly new disease. Again, the positive capabilities are hard to separate from the dangerous ones. This is a global problem.

The risks I’ve just mentioned are all about how AI will empower bad actors who have relatively little power now. The same tools will also concentrate power in places where it already exists. Autonomous weapons, for example, will make governments even more capable of using deadly force without a human being part of the decision. Monitoring and manipulating public opinion will be easier and cheaper, and more effective too.

Eventually, the power to use AI to harm people will not be limited to people or institutions. AI systems themselves already occasionally act in ways their designers didn’t intend. The technology is improving faster than anyone expected and in surprising ways, and as the models become more powerful, they could begin to act against our interests and we could lose control. I’ll have more to say about this in the future.

AI models could begin to act against our interests and we could lose control.

AI could stunt our kids’ development and replace human relationships.

When I was growing up in Seattle, I didn’t have that many friends aside from a few other boys who were like me. It took hard work and a lot of help from my mom to develop my social skills so I could relate to different kinds of people. I still draw on those lessons today at the age of 70.

I doubt I would have put in the same work if I had had an AI companion back then. They talk to you in ways you’re already comfortable with. They don’t push you outside your comfort zone. They are always available and never get mad at you. This gives them the potential to become highly addictive and to rob us of the lessons we learn from connecting with other people.

The body of evidence on this subject is still small and a bit mixed, but there are signs that we should be very concerned. For example, in one study of more than 1,100 people who use AI companions, researchers at Stanford and Carnegie Mellon found that those with smaller social networks were the most likely to turn to a chatbot for companionship. And the heavier and more emotionally personal that use became, the worse they felt.

Young people could be affected for their entire lives. In his book The Anxious Generation, Jonathan Haidt makes an observation about the effect of social media that is even more true for AI: “Like young trees exposed to wind, children who are routinely exposed to small risks grow up to become adults who can handle much larger risks without panicking. Conversely, children who are raised in a protected greenhouse sometimes become incapacitated by anxiety before they reach maturity.”

An AI companion designed to never upset you is a big, protected greenhouse.

We are only beginning to understand the dangers that the internet—especially social media—can pose to young people’s development. We’re seeing compulsive use, disrupted sleep, cyberbullying, and exposure to harmful content. AI could magnify many of these risks by making them more persuasive and difficult to escape, and we should not wait another generation to start taking them seriously. Countries including Australia, the United Kingdom, and Norway are adopting protections for children online. China has gone the furthest. Its rules restrict AI companion apps broadly, bar designs that foster emotional dependence, and ban virtual relatives and romantic partners for minors.

The same tool that will allow people to learn more than ever could also lead to many people learning less.

I’m also worried about AI’s impact on education. Ironically, the same tool that will allow people to learn more than ever could also lead to many people learning less. One preliminary survey suggested that heavier AI use was associated with less critical thinking. The effect was stronger for younger people.

This would be the worst possible time for humans to lose their critical thinking skills. In an era of deepfakes and misinformation that can be tailored to you individually, the ability to tell what is true from what is not becomes an essential life skill.

It’s unclear where to draw the line on these psychosocial problems. In some cases, AI may help people understand how to do better in their human relationships. It may be the only contact with the outside world for isolated elderly people and people with limited mobility, and it will be better than nothing. Wherever we end up drawing the line, it should be our decision, made intentionally.

The good things we do with AI could be very, very good.

It’s often said that we overestimate how much will change in the short term and underestimate how much will change in the long term.

With AI, I see something different going on. Some people see only the upside of AI and do not focus enough on the negatives. Others make the opposite mistake, which is to focus exclusively on the dangers—which are real—at the cost of missing the potential benefits.

We need both: deep concern about the AI harms we need to minimize, and grounded optimism about the positives if we maximize them for everyone.

Maximizing the benefits is just as important as minimizing the harms. If people see how AI makes their lives easier, it will help build the public trust that is necessary for managing the harder parts of the transition. If the first thing AI does in most people’s lives is take away their job, those who are already skeptical about it will outright reject it. This will make it harder to ever deliver on the benefits and it is another reason why governments, industries including the medical industry, and AI companies should be working together now.

With its ability to synthesize knowledge from every scientific field, AI can accelerate innovation in the world’s toughest technical challenges: providing reliable clean energy for everyone, combating climate change, growing enough food, eradicating diseases, and more. Researchers working on cancer treatments or nuclear energy can use AI to search through massive amounts of scientific literature. It can help them identify patterns that a human might miss and decide which experiments offer the most promise. When intelligence is no longer the limiting factor that it is today, smaller companies will be able to compete with organizations that have far larger research budgets. R&D and innovation will be supercharged.

Healthcare is one area where AI can help solve real-world problems. Many small American hospitals lack on-site specialists who can quickly diagnose a patient during a life-threatening emergency. In those places, AI could make sure a heart attack is caught in time and a family avoids the crushing expense of a medical emergency. Viz.ai is one example. It analyzes scans to detect strokes and other emergencies and helps medical teams coordinate their patients’ care. It is being used in nearly 2,000 U.S. hospitals.

AI will also help primary-care doctors make better diagnoses and keep in touch with their patients when they’re not in the clinic. It will help patients understand test results and complicated schedules for taking their medicine.

Agriculture is where I see the fastest impact of AI in low-income countries.

I surprise a lot of people when I tell them that a second area—agriculture—is where I see the fastest impact of AI in low-income countries. In most low-income countries, farmers don’t get reliable weather forecasts or advice on what seeds to plant, how to protect their crops and livestock from disease, or how to improve their soil. With population growth in these countries and the challenges of climate change, these farmers need more help than ever. Using AI, low-income farmers will soon be able to get better advice about all these things than even the richest farmers get today and increase their output substantially.

Government services are a third area where AI can make people’s lives easier. In the United States, I’ve met families who, understandably, were overwhelmed by the process of applying for health insurance, student aid, or food assistance. Faced with a huge stack of complicated bureaucratic forms, many felt like giving up. AI can streamline things dramatically so they get the help they need faster and the government can operate more efficiently. Governments can make the citizen’s experience far better, starting with those who need its safety net services the most.

Despite my concerns about its impact on our mental health, I think AI can also help a lot there. Most communities have too few counselors, psychiatrists, and addiction specialists. With the right privacy safeguards in place, AI tools could help people recognize warning signs. Then, if needed, they can offer evidence-based coping strategies and team up with a human to provide more responsive treatment.

AI can be a boon for education as well, despite the concerns I mentioned earlier. It can free teachers up to spend more time working with students one on one or in small groups and give them a clearer view of where the whole class is struggling. For students, an AI tool that preserves what researchers call “productive struggle”—the cognitive work that builds understanding—can strengthen learning. When a student first encounters a new idea, the AI gives substantive explanations and offers both questions and answers. Later, when it’s checking their comprehension, it holds the answer back and helps them arrive at it on their own.

Taken together, the advances in all these areas could make everyday life easier, more affordable, and less constrained by a person’s income or connections.

AI could give individuals and small businesses access to capabilities that today require expensive professional help or large staffs, while making products and services better and cheaper. It could help people with disabilities live more independently and enable workers and entrepreneurs with good ideas to accomplish far more than they can today.

Most importantly, it could give people back some of the time and attention now consumed by paperwork, bureaucracy, searching for reliable information, and tasks they cannot afford to pay someone else to handle. These benefits may seem modest, but multiplied across millions of lives, they would be profound: more people getting good advice when they need it and having greater freedom to focus on the lives they want to build.

We have to be deliberate about ensuring that it benefits everyone and not just a wealthy few.

In all these areas, the operative word is “can”—AI can improve life for people at every income level. But it won’t do that automatically. As with any new technology, we have to be deliberate about ensuring that it benefits everyone and not just a wealthy few. This will require governments and philanthropy to play a strong role so that less wealthy citizens and low-income countries are full beneficiaries.

The Gates Foundation has 19 years left of the 20 years in which it will spend its remaining $200 billion. AI will help it achieve its ambitious goals by both accelerating the discovery of vaccines and medicines for HIV, TB, malaria, and malnutrition and helping the healthcare workforce and patients know how to use those tools. The foundation’s goals include cutting the number of children who die every year in half again, as was done from 2000 to 2024. All of our work, not just health but also agriculture and education, will take full advantage of AI.

I will write much more about these efforts next month in the foundation’s annual Goalkeepers report—including our focus on making sure that AI models are available in the languages spoken by people in all the countries where we support work, and not just the ones that are common in rich and middle-income countries. Many of the leading AI companies, including OpenAI, Anthropic, Google, and Microsoft, are partnering with the foundation on all of these initiatives, which is making a big difference.

The world needs a plan.

It is great that some AI companies are proposing solutions to challenges raised by their own technology, but we should not expect them to lead the charge. Some of the issues are outside their area of expertise, and in a democratic society it’s not their role to decide these things.

Instead, solutions should be developed through a public democratic process that includes elected officials, policymakers, educators, health workers, local officials, and community leaders. Millions of people will have their lives disrupted, and we’ll need a stronger, more flexible social safety net to help them manage the transition. Local communities are already raising concerns about the energy and water needed for data centers. Without solutions, some groups will push for stopping AI development and deployment altogether.

The solutions should be shaped by our answers to the profound questions raised by AI, including how we preserve our humanity in a time when machines can out-think us. As people who spend their lives thinking about what it means to be human, religious leaders can play a key role in this. I was fascinated by Pope Leo XIV’s encyclical on AI, “On Safeguarding the Human Person in the Time of Artificial Intelligence.” It lays a strong foundation for the work that needs to be done.

In the coming months, I will share more ideas for making sure that AI’s benefits outweigh the harm it causes. Here are three to start, beginning with what I think is the most important one.

Build a new system for managing the transition.

The highest priority is a monumental task: creating a domestic and international framework for dealing with AI.

None of our current institutions were designed to handle a technology that spreads so fast and touches so many parts of our lives. So we’ll need to make new ones.

It’s hard to overstate what an enormous undertaking this will be. After the attacks of 9/11, the U.S. government went through its biggest reorganization since World War II for the purpose of improving just one function, national security.

AI will require much, much more. It will affect national security as well as employment, education, taxation, energy, elections, air and water, public health, the financial system, law enforcement, transportation, public lands, and IT systems.

These sectors overlap in ways our existing bureaucracy is not designed to manage. A labor department may understand workforce disruption but not security risk. A business regulator may understand market concentration but not AI’s effects on children and teenagers. Left to themselves, institutions will see only one part of the system, while the consequences of AI will ripple across the entire system.

At the national level, countries will need bodies that can set priorities across government agencies. The goal will be to make sure that every risk is accounted for. Otherwise, an AI-enabled attack might succeed because no one thought it was their job to stop it.

But even a country that gets its own house in order will still be exposed to risks that cross borders. This is why an international organization will need to be built in parallel.

It will be unlike any other institution we have ever created, though it can follow the model of some existing systems. There’s an inspections regime for nuclear weapons, regulations for international aviation, and agreements that protect the ozone layer. A new global organization for AI will need elements of all three and more.

It is fair to wonder whether the world’s institutions are up to the task of designing and implementing this new architecture. Government moves slowly when it moves at all, and polarization within and between countries makes it harder than ever to get things done. Some cooperation between the U.S. and China will be required.

We do not have the luxury of moving slowly. The place to start is with a process for building the right institutions before the disruption forces governments into crisis mode. National leaders should convene economists, technologists, labor experts, business leaders, and workers themselves regularly to identify where existing institutions are failing and what new authorities may be needed. Countries will need to learn from each other.

And the countries that host the leading AI developers and control critical parts of the supply chain should begin meeting now to set up shared norms, before competitive pressure makes it harder for them to cooperate.

Building the framework I’m talking about will take years, which is why we need to start now.

Set aside some jobs for humans.

My dad died of Alzheimer’s in 2020. In the later stages of his illness, he was cared for day and night by paid caregivers who understood him even when he struggled to express himself. He couldn’t always tell them when he was hungry, but they always knew.

My family and I will always be grateful to that amazing group of professionals. Something in the care they gave my dad was irreplaceably human. No robot could or should have done it.

I think about that team when the question of which jobs will disappear and which will remain comes up. I believe that as AI and robots improve, we’ll set aside certain things for only people to do. I’ve started calling this domain Human Reserved, and it’s an example of the kinds of ideas we’ll need to consider.

I like the phrase Human Reserved because it makes me think of nature reserves—places where we could put buildings and roads, but we choose not to because the loss would be too great.

We might set something aside as Human Reserved for economic reasons. For example, we may do it because allowing machines to take over a certain role will displace a large number of people who can’t easily change jobs. You can’t tell a 55-year-old who has worked in construction their whole career that they need to go work at an elder care facility and expect them to find it fulfilling.

Sometimes the decision to make something Human Reserved will be driven by other factors. In health, for example, imagine a robot giving you the awful news that you have an incurable disease. There’s no technical reason why it couldn’t. Yet it shouldn’t.

The Human Reserved domain will evolve over time—for example, we should consider setting aside some jobs now and phasing in AI slowly over years or decades with a commitment to preserve some jobs. Some areas, like education and mental health care, will be a mix, with a human in charge who’s using the technology to extend what they can do.

The lines will also vary from place to place. Some countries might insist on having humans take care of the elderly. But a country like Japan, which has a shrinking workforce and not enough young people to care for the old, may welcome a caregiving robot.

The idea of Human Reserved raises a host of questions I don’t have answers to. Who gets to decide what we reserve for humans? What criteria should we use? How do you keep companies from cheating and using robots anyway? What happens to international trade when one country lets robots make something and another country doesn’t? These will need to be worked out in public as part of the transition plan.

Rebalance how we tax labor and capital.

As workers are pushed into different jobs, they will need retraining and other support from the social safety net. But they will be working less, which means they will be paying less in income taxes, and government revenues will drop just when the demand for those services is greatest. The funds will have to come from somewhere at a time when budgets are stretched.

I believe we should tax AI tokens and robots. Right now, if you’re an employer and you hire someone, you pay payroll taxes on their earnings. But if you buy a robot, you can usually write it off right away as a business expense. The tax system nudges you toward replacing people with machines.

A tax would slow the rush away from human labor a little and raise money for retraining and a stronger safety net. It would need to be targeted so it does not slow down the purely beneficial uses of AI, like making medicine and education cheaper.

Critics of this idea point out that it’s not optimally efficient in an economic sense, but they’re not considering the broader value of work for individuals and society. And with all the accelerated innovation we will have, we’ll be able to afford a little inefficiency as the price for keeping people employed.

I proposed a robot tax years ago and most of the reaction was that it was a strange idea. I’m still a big proponent of it. Although it is not the whole solution to the threat of AI, it is part of a wise response.

However we raise money for more assistance, it needs to reach the people who need it most, including workers who lose their jobs to AI and robots, people whose hours or wages decline, and communities where the losses are concentrated. We need to start doing that work now so that the systems are ready when the need becomes acute.

What I’m doing.

I will use my voice and time to get AI and equity higher on the public agenda. I will raise the issue with lawmakers every time I visit Washington, D.C., and when I meet with leaders around the world. It will be front and center in my conversations with the people who are developing AI models. I will advocate for the national and international framework I described earlier. The Gates Foundation will help drive beneficial usage, including in Africa. Breakthrough Energy, a company I founded, will use AI to help companies develop cheap clean energy and help solve the climate problem. I will also be writing about AI on a regular basis.

My message to leaders is:

You have a chance to act now, before unemployment rises sharply, communities are hurting, and public trust has eroded. You can make sure that your government handles the problem holistically, rather than divvying it up into multiple bureaucratic fiefdoms. You can make sure AI benefits everyone. And you can work with other governments to meet this national and global challenge.

Finally, I will try to widen the circle of people shaping this debate. It should include workers, college students who are about to enter the workforce, community leaders, religious leaders and faith-based organizations, parents, educators, and others whose voices often aren’t heard but who have insight into how the transition will affect people’s lives.

How do we ensure that the benefits of AI reach people who do not already have wealth, influence, and access?

How do we strengthen the social safety net and help workers and communities thrive even when they’re displaced?

How should public institutions adapt?

And how do we preserve our humanity through all of this?

This unprecedented technology demands an unprecedented global response.

This unprecedented technology demands an unprecedented global response. If we get it right, the payoff for humanity will be phenomenal and the world will be a more equitable place.

I rarely stop thinking about AI—not because I have all the answers, but because the questions it raises are too consequential to leave to a small group of technologists. Leaders across academia, business, government, and civil society all have a role to play in shaping what comes next.

PostgreSQL for Everything

Mike's Notes

Pipi uses PostgreSQL internally.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Subscriptions > Hybrid Hacker
  • Home > Handbook > 

Last Updated

08/09/2026

PostgreSQL for Everything

By: Raphael Bauer
Raphael Bauer: 14/02/2024

Raphael Bauer: Fractional and Interim CTO with 20+ years of experience building and transforming engineering organizations in high-pressure environments: PE transitions, hypergrowth, and new product launches. My strengths include delivery predictability, org design, executive communication, and hiring and coaching senior leaders.

...

You need simplicity if you want to move fast. PostgreSQL can very well replace Kafka, Redis, Clickhouse and Elastic. And many successful companies are doing exactly that. Let's check out how

...

Contrary to popular belief - the answer to everything is NOT 42 - it’s PostgreSQL. (ok. It might also be Postgres).

This article was discussed on Hacker News. The thread contains a lot of additional links, real-world experience and critical thoughts - well worth reading.

Table Of Contents

  • Intro
  • Rock Solid and Stable
  • Easy to Run, Install and Scale
  • Simplifies Your IT Setup
    • PostgreSQL Replaces Solr and Elastic: Full-Text Search
    • PostgreSQL replaces MongoDB: Excellent Json Support
    • PostgreSQL replaces Kafka and RabbitMQ: PostgreSQL as a queue
    • PostgreSQL Replaces Clickhouse: High Volume Time Series Data
    • PostgreSQL as Vector Database for AI Workflows
    • PostgreSQL Replaces Redis: Non-Persistent High Performance Caching
    • PostgreSQL Replaces File System: For Raw Data
    • PostgreSQL Replacing Your Graph Database
    • PostgreSQL as Replacement for GraphDB and Neo4J
    • PostgreSQL Replacing Your Microservice
    • PostgreSQL - Replacing your Playstation 5
  • Conclusion

Intro

I started using PostgreSQL roughly in 2003 for a research project called ColumbaDB. Columba is no more, but PostgreSQL is still alive and kicking more than ever.

In 2003, MySQL was much more widely used than PostgreSQL. MySQL was also potentially faster as it did not implement all features of the SQL standard. At the same time MySQL was lacking many features that we needed (full-text search, powerful indexes, SQL standard compliance etc). PostgreSQL felt more like a “real” database in comparison to MySQL - like a tiny version of Oracle - but in open source clothes.

During that research project I learned a lot about databases, indexes and the power of PostgreSQL. One important use-case was full-text search. We could have used MySQL in conjunction with another system like Lucene / Solr to make our database searchable. But that would have meant running and maintaining two such systems. Complicated.

PostgreSQL allowed us to use a fulltext search plugin to do everything in one system. No need to sync any data. No need to maintain and run two systems. It just worked and made us smile (after some tweaks of course). Simplicity.

Since then I used PostgreSQL for many use-cases throughout my career as CTO / Interim Manager. Most recently I used PostgreSQL to store very high volume web analytics time series data via its TimescaleDB plugin. Check out Privatracker - the best way to do web analytics and respect the privacy of your visitors - to see it in action.

Many others discussed the topic from different angles. And each article is really worth your time (SQL is Agile, Stephan Schmidt on Using SQL for Everything). Also check out my Linkedin post.

And if you are using PostgreSQL I can highly recommend reading Hazel Bachrach’s nice post on “What I Wish Someone Told Me About Postgres”.

In my humble opinion the power of PostgreSQL comes from three sources:

  1. It is rock-solid and stable.
  2. It is easy to run, install and scale.
  3. It massively simplifies your IT setup by being not only a RDBMS, but also a full-text search engine, a document storage and much much more…

Let’s have a closer look…

Rock Solid and Stable

PostgreSQL is boring old technology. The first PostgreSQL release dates back to 1996. PostgreSQL is also very widely used - for a very long amount of time. Ironing out bugs - especially in database systems - takes time. PostgreSQL had that time.

It also has a very active community that diligently adds more and more features without breaking any old parts of it. In recent years PostgreSQL got many amazing features like json document storage, partitioning support, common table expressions and much much more. Each new release of PostgreSQL is exciting and brings new nice features.

True - PostgreSQL is old - but the features are very very modern - and PostgreSQL becomes better with every release.

Easy to Run, Install and Scale

PostgreSQL can be installed very easily locally. It is bundled with all major Linux distributions, part of Mac brew, but can also be installed with applications like PostgresApp.

When running tests, it comes in handy using Testcontainers with PostgreSQL. It was never easier running your tests against a real PostgreSQL database that is 100% similar to the production thing.

If you want to run PostgreSQL on a server then you can simply apt-get install it. Or run it in a docker container.

All cloud providers allow you to run (and scale!) PostgreSQL by clicking a single button. You got ample of choice at your fingertips:

  • Amazon AWS
  • Google GCP
  • Microsoft Azure
  • ElephantSQL
  • CrunchyData
  • Timescale

… and many more …

That makes PostgreSQL one of the most widely supported software systems in the market. And for you this means less maintenance and more time for creating new features for clients.

Simplifies Your IT Setup

Running PostgreSQL in the cloud is already just one click. But it gets even better. PostgreSQL can replace many systems that youd’d have to run otherwise.

PostgreSQL Replaces Solr and Elastic: Full-Text Search

PostgreSQL allows you to turn your text data into user-searchable data. Without a separate system. It’s also language agnostic and you’ll never have any sync problems between your data and your fulltext search system.

The most impressive article on the topic is how Contentful used PostgreSQL to enable fulltext search for their users. It’s a tale in simplicity that enables growth.

Instacart did something very similar: They built their modern search infrastructure on Postgres instead of running a separate search cluster. Same story, different company.

The built-in tsvector / tsquery machinery is a very good starting point. It is part of vanilla PostgreSQL, needs no extra moving parts, and works extremely well for the vast majority of use-cases. Start there.

If you outgrow it - typically because you need better relevance ranking (BM25) or more scalability - you don’t have to leave PostgreSQL either. There are extensions that pick up exactly where the built-in search ends:

  • pg_textsearch by Timescale / TigerData - BM25 ranking as a PostgreSQL extension.
  • ParadeDB / pg_search - Elasticsearch-grade search inside PostgreSQL, built on Tantivy (docs).

That’s the beauty of it: You can start with plain vanilla PostgreSQL and seamlessly move to more advanced techniques and third-party extensions once - and only if - you actually need them.

The pros and cons of full-text search on PostgreSQL are discussed very nicely in this LinkedIn discussion - recommended reading before you decide.

More on the topic: https://www.postgresql.org/docs/current/textsearch.html

PostgreSQL replaces MongoDB: Excellent Json Support

PostgreSQL has excellent support for storing and querying(!) json. It also features an index type (GIN) that makes these operations blazingly fast. Is there a need for MongoDB any more?.

The Guardian also wrote an excellent article how they switched from Mongo to PostgreSQL. Thanks for sharing Jan-Otto! Hazel also wrote a nice piece on jsonb and what to take into account when using it.

PostgreSQL replaces Kafka and RabbitMQ: PostgreSQL as a queue

Events, queues and persistent logs are getting more and more important in today’s software systems. Systems like Kafka, RabbitMQ, SQS and others provide that functionality. But maintaining them is annoying, custom and you need the skillset.

The good news: You can just use PostgreSQL. The magic comes from

SELECT .. FOR UPDATE
SELECT .. SKIP LOCKED

Using these SQL features you can effectively use a table as queue. Either in a persistent fashion with a cursor and many consumers, or in a read-once fashion.

The article at crunchydata explains this concept very well.

My tip: Start with PostgreSQL as a queueing system. Only when that does no longer perform well switch to other systems like Kafka, RabbitMQ or SQS. You’ll be surprised how well PostgreSQL works.

PostgreSQL Replaces Clickhouse: High Volume Time Series Data

Time series data is special. Often you get many data points in a very short amount of time. And then you have to aggregate the data frequently, doing some statistics on it and so on.

There are specialized software systems like Clickhouse (amazing by the way…). But you can also use a plugin for PostgreSQL that allows you to do (nearly) the same: Timescale.

I’ve used Timescale and can recommend it. The good news is that you can continue using PostgreSQL - even for high volume data easily. No need to learn and maintain something new.

PostgreSQL as Vector Database for AI Workflows

Timescale lately released the pgvector extension, that turns your PostgreSQL into a vector database. This allows you to use the tech you already know for indexing and retrieval of relevant data. That’s an essential part of AI LLM workflows.

Timescale also recently announced pgai that includes pgvector, but also a lot of other nice extensions that make it super simple to index data, call LLM models and retrieve data based on similarity.

PostgreSQL Replaces Redis: Non-Persistent High Performance Caching

Caching is important. Most applications use something like Redis as a cache to get information like sessions and more quickly. A cache can by definition lose data and can be regenerated from the original source.

But. Why use Redis when PostgreSQL can be tuned to be as fast (in most usecases) as a Redis cache? The secret is using an UNLOGGED table. You can even emulate Redis’ automatic expire by a trigger. A lot has been written about this - I can just recommend trying it out.

PostgreSQL Replaces File System: For Raw Data

For one of my clients we had to read and write a huge amount of small pieces of binary encoded information. We initially thought that doing this via the file system was the fastest way to do so.

After some performance checks it became clear that PostgreSQL was even faster than reading from the file system for our use-case. PostgreSQL uses the file system very efficiently for its data - and it adds a lot of caching and efficient reading and writing strategies that can outperform writing and reading raw data on a file system.

We used Flatbuffers to store the data in a blob column. Data was then de-serialized on the client. You might want to try that approach as well.

PostgreSQL Replacing Your Graph Database

Hierarchical data can be managed in SQL via recursive queries. That’s ok, but also super-hard to read, maintain and debug. Not even speaking of performance.

The better way is the LTREE datatype of PostgreSQL. It helped me not only once to implement hierarchical tag structures. Easy to read, maintain and blazingly fast.

PostgreSQL as Replacement for GraphDB and Neo4J

But what if you need a real graph - not just a tree? Nodes, edges, properties, and queries that traverse relationships in every direction? That’s usually the moment someone suggests adding Neo4j to the stack. And with it: another system to run, another backup strategy, another data sync.

You don’t have to. Apache AGE (“A Graph Extension”) turns PostgreSQL into a graph database. It’s an Apache Software Foundation top-level project and it implements openCypher - the same query language you’d use in Neo4j. The best part: graph queries and plain SQL live in the same database and can be combined in a single statement.

SELECT * FROM cypher('my_graph', $$
    MATCH (a:Person)-[:WORKS_AT]->(c:Company)
    RETURN a.name, c.name
$$) AS (person agtype, company agtype);

My tip - the same one as for queueing: Start with PostgreSQL. Model your graph with AGE (or with LTREE if a hierarchy is all you need) and only reach for a dedicated graph database if you really hit the limits. Your data stays in one place, transactional and consistent with the rest of your application.

More on the topic: Apache AGE documentation and the source on GitHub.

PostgreSQL Replacing Your Microservice

Most of the “microservices” these days are only about models, getting data from a database and returning json to the client.

But you know what? PostgreSQL can turn any query into a Json result. That effectively replaces your server middleware. There are Pros and Cons to this approach, but it shows the capabilities of PostgreSQL. The amazing Lukas Eder wrote about the topic - not PostgreSQL specific - but everything mentioned there is very well doable in PostgreSQL as well

PostgreSQL - Replacing your Playstation 5

Well. Some enthusiast implemented Tetris as Common Table Expressions in pure SQL. Crazy. And maybe not to be taken too seriously.

Conclusion

The list above is not very exhaustive. PostgreSQL is a very flexible piece of software. And it can be extended with plugins to do more and more.

You need simplicity if you want to move fast. If you come across a new requirement always ask: Can’t PostgreSQL do this? And do we really need that shiny new technology X?

PostgreSQL might not be the answer to everything - but it is the answer to a lot more than you might think!

Why the CTO chair keeps emptying

Mike's Notes

This is the first part of an article by Gergely Orosz, available to read for free. The rest is for paid subscribers. The article was introduced in a recent issue of The Code.

I found this important for understanding what is happening in workplace culture at large SaaS/AI firms. Things to avoid at Ajabbi. For future reference.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Subscriptions > The Code
  • Home > Ajabbi Research > Library > Subscriptions > The Pragmatic Engineer
  • Home > Handbook > 

Last Updated

07/09/2026

Why the CTO chair keeps emptying

By: .
The Code: 24/08/2026

.

An exodus across Silicon Valley. Something is spooking the people who run engineering. Across startups and Big Tech, CTOs, VPEs, and heads of engineering are quitting high-status roles with nothing lined up. Veteran engineer Gergely Orosz says he's never seen this many top-tier leaders walk. In his latest deep dive, he spoke to nearly 20 on career breaks. Six in ten were already on their way out.

A range of reasons. From rapid AI adoption (or the lack of it) to long hours and burnout. Then there’s what Orosz calls “founder mode.” In smaller companies, founders are micromanaging engineering, turning VP and CTO roles into low-ROI gigs. Some leaders left to build their own startups; others were pushed out.

Across the board, these were the most consistent reasons:

  • The job got worse. Picture a founder celebrating a massive AI-generated PR while the CTO stares at the technical debt underneath. Flag the mess, and you become the office killjoy.
  • Equity looks like smoke. Leaders are trading salary for equity that feels like a gamble. Many CTOs now realize their options might never pay out due to VC payouts.
  • AI-native or bust. The best roles now want leaders who’ve actually led an AI transformation. If their current job can’t offer that, some are stepping back into IC roles rather than letting their skills go stale.
  • Teams are shrinking. Agents now handle work that once required entire teams, meaning fewer engineers and fewer layers of management.

It doesn’t stop at the top. When leaders walk, the ripple effect hits the entire team. If you're taking a leadership role, interview the company too: do founders want engineering to change, or just get cheaper? And if your job isn't giving you hands-on AI experience, get it elsewhere.

P.S. Our engineering team put together over 10 practical guides to help you kick-start your journey toward becoming an AI-native engineer. Pass this along to your colleagues today.


Headed for the Exit: the Great Engineering Leader Career Break

By: Gergely Orosz.
The Pragmatic Engineer: 19/08/2026

Big Tech and startups from the inside. Especially relevant for software engineers / AI engineers, useful for anyone working in tech.

...

Trend: more CTOs, VPEs, and Heads of Engineering are walking away from their high-status, in-demand positions. There are many reasons, mostly related to AI, and to "founder mode"

...

In my ~20 years in this industry, I’ve not seen as many capable engineering leaders opting out or taking prolonged breaks as now, with some high-ranking engineering leaders – CTOs, VPs of Engineering, heads of engineering, etc. – quitting their high-status roles and departing, if not into the sunset, then at least with nothing lined up.

To find out what might be behind this spate of sign-outs, I talked with almost 20 engineering leaders currently on a career break – or seriously considering one – and they let me into their personal reasons for deciding to jam the brakes on their careers. Thanks to everyone who shared their input!

Today, we cover:

Ten of the most common reasons for quitting, sometimes without the next gig lined up:

  1. The job got (much) worse
  2. The startup is “losing” and becoming worthless
  3. Not being AI-native enough for other skills to be relevant
  4. Their predecessor saw the “writing on the wall”
  5. Long hours – rarely decisive
  6. Smaller teams mean less need for leaders
  7. Fractional CTO work preferred over fulltime positions
  8. AI startups pay ICs more than non-AI startups pay executives
  9. Quitting to launch their own business
  10. Burnout
  • “Founder mode” looks here to stay, so how to deal with it? And has it made the CTO and VPE roles become “low ROI”?
  • ‘Work at companies that truly want to drive change’. A personal account from someone who took the VP of Engineering role at Gitpod (later, Ona, now acquired by OpenAI) and enjoyed a rewarding experience. Matt Boyle says he interviewed the employer beforehand on whether their business truly leans into the changes brought by AI.

“Just me?”

I was recently messaged by a head of engineering in San Francisco, who said:

“I’m talking to four startups in San Francisco about the head of engineering roles. Pretty normal.

But one interesting pattern is how founding CTOs/heads of engineering are stepping away to take a full career break. We’re talking about two of these four startups. And these are good startups!

Have you seen this trend? I have a small number of data points here, so you might have a broader view.”

I asked around privately, and it turns out a majority of the CTO-level folks I spoke to are considering the very same thing, or are actually in the process of leaving the office for a long spell away; 6/10 engineering leaders said they’re on the way out.

1. The job got (much) worse

Unrealistic expectations, including about AI, by founders and CEOs are the leading cause of jobs turning bad for CTOs and VPEs right now in 2026:

  • CTO expected to magically transform the company to be “AI-native”
  • CTO must make significant engineering cost cuts of up to 20-50%, including morale-sapping job cuts
  • “Do more with less” equals shipping more with fewer people (e.g., no backfills)
  • CTO faces pressure on business results as AI coding bills rack up
  • Founder slop: they want wonky AI prototypes shipped as full-blown products within weeks

Hands-on founders with “AI psychosis” make the job predictably harder, according to one CTO who just signed out of his job:

“Managing ‘AI psychosis’ with founders and executive peers has become very difficult. For example, what do you do when a founder ships a 60,000-line pull request into the product, gleaming with joy at how much more productive they’ve become with AI? They won’t see all the issues with that PR, and how do you bring up that they’ve created a massive amount of tech debt? Especially without looking like a ‘Debbie Downer’.”

Founder slop issues begin when top leaders get excited about AI’s capability, then get hands-on and start issuing PRs, and shipping code to production. It can cause issues across the board:

  • Accountability. Who’s oncall when founder-shipped code breaks? In the “you build it, you own it” culture of startups, it’s confusing when a founder gets hands-on while not owning their work.
  • Quality out the door: if a founder’s half-baked features are accepted, it sends the wider message that quality does not matter. Some people may adopt this attitude to their own work.
  • A founder can overrule whatever was previously agreed with the CTO or VPE about what to build next. Vibes the founder has or feels are reason enough.

Another way that leadership roles have diminished is that craft and quality are less important, says a VP of engineering who’s in the process of signing out of their job:

“Shipping software became all about speed. Finding differentiation with your product in the market is brutal, and speed / go-to-market becomes the biggest differentiator. Craft, quality, and care going into the product are taking a backseat.”

Things also go bad when companies don’t ‘get’ AI+engineering, except as a way to cut jobs. CTOs I talked to mentioned the likes of Ramp, Stripe, and Notion as places that understand how to integrate AI into the engineering culture with a growth mindset without forsaking quality. Elsewhere, bad vibes dominate at places where going all-in on AI leads to the cynical conclusion that product management, design, and engineering leadership are irrelevant.

2. The startup is “losing” and becoming worthless

Director+ roles have a few differences from individual-contributor engineering ones:

  • Larger equity stake in the business. Base salary at these levels is often similar to a staff engineer’s, but usually with more generous equity grants – especially at the VP of Engineering and CTO levels. A good financial outcome depends on the company becoming more valuable, and – in the case of private companies – having a good exit by being acquired or selling shares.
  • Understanding of the business and competition is a baseline. At Director+ level, a big part of the job is making strategic decisions that grow the business and help the company get ahead. It’s a nice-to-have for an engineer to possess business acumen, but director-and-above folks use it much more than most individual contributors (ICs). Great engineering leaders are good at understanding business performance and outlook.

A company that adopts AI rapidly usually falls into one of three buckets:

  • “AI-native”, building & selling AI products. The large AI labs and a select few “AI-native” startups are thriving, but many AI startups with VC funding struggle. Engineering leaders know this, and that their equity – usually issued as options – could end up worthless.
  • Software startups threatened by AI-native businesses. Good businesses in the pre-AI world can be threatened by AI today, like SaaS startups selling seat-based products in areas where agents are taking over the functionality. They have to pivot their businesses or seek an exit. Bending Spoons buying Airtable for less than the company raised is an example of a business threatened by AI and choosing to sell, instead of pivoting the whole business.
  • Unaffected by AI. Usually stable businesses which do more than software, such as with a real-world side to the operation like manufacturing or distribution.

The majority of software startups fall into one of the first two buckets of being AI-native or under threat. Senior leaders at such companies are in a good position to evaluate whether their company is a “winner” worth staying with.

Leaving due to equity becoming worthless

A CTO who quit their startup told me:

My company would have needed a massive exit for me to realize any upside. I had an equity grant that was 2% of the common shares. However, this equity was behind an already steep preference stack for investors, post Series A.”

This CTO had a very generous equity grant at 2% of shares, so what made him leave it behind? They laid out how it will be difficult to get any benefit from them because the shares are most likely rendered worthless by rules about the order in which different investors get their share of the pie:

  • Assume that this company raised a $10M seed round at a $50M valuation, then a $100M Series A at a $500M valuation. So, a total of $110M was raised across two rounds.
  • Investors typically have a 1x preference. 1x preference would mean that upon any sale, they get the first $110M of the sale.
  • But in this company, the Series A investors negotiated a 2x preference: so upon a sale, $210M goes to investors first ($10M to the Seed, and $200M to the Series A investors).
  • The company now needs to sell for at least $210M for common shareholders (like the CTO) to make any money!
  • If the CTO does not believe a $200M+ exit could happen, then their equity is worthless. A $200M+ exit is typically an acquisition, because a stock market flotation rarely happens at below a $10B+ valuation, these days.

If a VC-funded company does not have the revenue or customers to grow at a fast tick (circa 20-50% per year), then it’s often a struggle to raise the next round of funding, and the business’s actual value usually shrinks to 3-5x of annual revenue. So, if a startup is making $10M per year after raising $110M in funding, and growing 30% year-on-year, then the company is likely worth around $30-50M. Perhaps the right buyer would pay $100M, but if growth slows, the value is likely to drop.

An experienced CTO who takes a step back and assesses things can realize when there’s a high chance of their equity turning into smoke, removing a reason to not sign out of the job. It’s what happened to the CTO above, and when they couldn’t turn the business around, they quit.

Business stops growing

When a VC-funded startup’s business stops growing, the prognosis can be dire in the sense that it’s unlikely to be worth as much as in the previous funding round. This is true even when the startup becomes profitable: this might mean it could theoretically go on forever; but with slow or no growth, it won’t win in another VC funding round.

Here’s a VP of Engineering who saw their startup stop growing, partly due to wrong bets by the CEO:

“My founder/CEO was nontechnical, and was both moving too slow and too fast with AI.

Too slow, as in they did not take the time to understand what our customers wanted. We built a TON of AI stuff, it totally confused them, they churned, growth stalled, word-of-mouth growth was gone. Heck, I don’t think our customers ever wanted or needed anything with AI!

Too fast, as in they deprioritized core systems’ reliability in favor of shipping AI work to prod which did not have any commercial potential. So, our core offering started to have more outages and we lost customers because of this as well.”

I’d add that deprioritizing reliability in favor of building features may be sensible in the early days. The problem seemed to be that this company had not found product-market fit, and the new AI features didn’t resonate with customers. Basically, the CEO lacked customer understanding, business intuition, or both.

So, good on the VPE for getting out when they saw the direction of travel. If the CEO won’t accept input from the VPE – who would’ve at least prioritized reliable operation – then there isn’t much left to stick around for!

3. Not being AI-native enough for other skills to be relevant

The top-paying engineering leadership positions have one thing in common: experience of leading AI-native organisations is expected, and leaders are sought who have turned their current company AI-native, or work at such a place.

It’s new to see people signing out of large companies for feeling like they’re lagging behind in adopting new AI workflows. An ex-engineering director at a large bank told me they quit their job to accelerate their career:

“I was not getting the opportunity to ‘close the loop’ on hypotheses enough. [...] To stay relevant in the industry, I feel like I need to pull out into the “fast lane.”

Like many others, I see the future of software development is with AI. If you don’t get hands-on with your team, working with AI tools day-in, day-out, you’re falling behind.

My plan is to get on the cutting edge of things through a mix of academia and consulting AI companies. I am not saying the plan is perfect, but I need more time to do things differently than I had in my job.”

Consider this: if you stay in your job for two more years, do you expect to find career opportunities at cutting-edge companies in the future? If the answer is “no”, then there’s a risk in just staying put. Joining an uncertain startup or taking a career break to develop AI expertise is also risky, but the outcomes may be more controllable than letting your skillset become outdated, relatively quickly.

But it might actually be necessary to quit in order to get AI experience: you might be able to get this by transferring to an IC role. As Charity Majors, co-founder and CTO of Honeycomb, said in last week’s episode of The Pragmatic Engineer podcast:

“You’ve got to get AI on your resume. You just have to. If you don’t, this is a huge career risk. If you’re working somewhere where you’re not getting these skills, I would do whatever I could to change that [including taking an IC role within the company].”

There are companies where moving from Director+ to individual contributor is possible, even if these companies are the minority. If you happen to work at a place like this, consider if you can and will take advantage of this opportunity.

Most companies say they want to be AI-native, but never do

Claire Vo – founder of ChatPRD and host of ‘How I AI’ podcast, and the former Chief Product & Technology Officer at LaunchDarkly – says most companies will never become “AI native” simply because most VP of Engineering or CTO folks don’t have what it takes to pull off such a transformation. In her words:

“The VPE role used to be primarily about deploying the dark arts to defend engineers from the roadmap, and now everyone thinks that’s BS and leaders are under tremendous pressure to inflect velocity or GTFO (get the f*** out).

Engineers are unhappy (don’t make me tokenmaxx, bro!), product and design sending slop PRs, and everyone good has left for a lab.

Most of these companies’ EPD (Engineering, Product, Design) orgs will never go AI-native, not even close. Most VPEs aren’t good enough at change management to pull it off.”

It looks like there’s a deadlock:

  • The current engineering org is frustrated by how AI is making engineering culture worse, morale is down, and people are frustrated and confused
  • To resolve this, drastic changes are needed to how everyone (engineers, product, designers) works
  • To pull it off, a VP of Engineering or CTO is needed who’s capable of this; someone excellent at change management, who’s ideally done it before.
  • But most VPEs and CTOs are not experts at large-scale change management, nor have done it before.

According to this, many VPEs and CTOs are doomed to fail at making the change they want, and it’s hard to know if that’s because organizations didn’t support them properly or resisted change.

4. Their predecessor saw the “writing on the wall”

There’s (usually) a honeymoon period in a new job, when we believe in the business we’ve joined and in its direction. But when this phase passes, a fraction or all of the problems described above may emerge, and there’s a decent chance that some of them are why your predecessor signed out:

  1. Has AI helped make the role worse?
  2. Is the equity on course to be worthless?
  3. Is getting AI-native experience actually possible, or is the organization resisting change?

I’ve talked with a CTO who replaced their predecessor and founding CTO. A few years into the job, the predecessor CTO realized their equity in the business was worth almost nothing due to stalled growth, all while they were also being out-competed by AI-native rivals. So, the new CTO also resigned after a short, six-month tenure.

5. Long hours – rarely decisive

Two engineering leaders – a CTO and a VP of Engineering – mentioned “insane working hours” as a factor that contributed to them finally quitting. But there were other things as well:

  • The business struggling for growth
  • Their equity grant’s value shrinking to nothing before their eyes
  • CEO/founder ignoring or overriding efforts to help the business succeed

My sense is that at a thriving business during chaotic times like these, it’s unlikely that long hours alone would spur people to leave, if their contribution to current success counts and is valued. When things are going well, it’s possible to delegate more and take time to recharge batteries. But when things are going badly, it feels like every waking hour needs to be spent on working to turn things around.

6. Smaller teams mean less need for leaders

Several engineering leaders are stepping back into IC roles for more stability because engineering teams are smaller now.

Karthik Hariharan, engineering leader at DoorDash, notes:

“Expectations have been shifting a lot in these roles, and a lot of folks qualified for them have consciously been stepping back into IC roles or joining bigger companies for stability and better compensation.

Engineering teams are also smaller now. A VPE isn’t needed until the team is large enough to require it. A technical founder can run the team for a lot longer these days.”

Some reasons why engineering teams have shrunk:

“Fullstack engineer” is mainstream, and was even before AI. Fullstack engineering was becoming relevant a few years ago in terms of a single engineer working on both the front and backends, instead of having a frontend engineer building the UI, and a backend engineer working on backend services. Fullstack frameworks like Next.js or Ruby on Rails made all this pretty easy before AI. Today with AI coding agents, you can rely on them to write decent code on platforms you’re unfamiliar with. There’s now little to no reason why a project would need multiple devs with different specializations.

It’s normal for one, or a maximum of two fullstack engineers, to be working on any given project at Anthropic as well. Head of Claude Platform, Katelyn Lesse, shared how it works at Anthropic:

“On an individual project, you often cannot have more than two people working on it.

This is because each engineer is already running several agents. And so as an engineer, you’re already fighting against your agents, which are stepping on each other’s toes on implementation. And in this setup, you just cannot have that many humans, who also come with all their agents!”

Frontend-only and native mobile teams are also getting smaller or disappearing. Even at companies where iOS and Android are a big part of the business, more places are building using cross-platform technologies where one engineer can do the work that used to need several. For example, social media app Bluesky had a single engineer build its web, iOS, and Android apps for launch by using React Native and Expo. Bluesky later hired more people to work on the web and apps, but they all work across these three platforms. It’s not the same as hiring separate web engineers, iOS engineers, and Android engineers.

We cover this in more detail in the deep dives Cross-platform mobile development and Is there a drop in native iOS and Android hiring at startups? We also observed a steep drop in frontend engineers and native mobile engineers in our latest state of the tech jobs market report:

Demand for frontend engineers and native iOS+Android engineers keeps dropping with the trend of smaller engineering teams. Source: The tech jobs market in 2026

Tech companies have been flattening their org structures for three years now. We first covered the trend for fewer middle managers back in 2023, when Meta drastically reduced manager positions. The trend has not stopped, and many – if not most – companies have increased the number of reports each engineering manager has, while reducing the number of layers in their organization.

7. Fractional CTO work preferred over fulltime positions

The rest of the article is available to paid subscribers.