Airbnb CEO Brian Chesky AI Warning Targets Two Roles

Airbnb chief executive Brian Chesky recently issued a direct warning on who will survive the next tech wave. He targeted two specific groups. The first group is pure people managers who do not build products. The second group is rigid employees who refuse to adopt new software tools. The recent Airbnb CEO Brian Chesky AI warning sent a strong signal through Silicon Valley.

We track executive commentary closely at WorkforceSignal. Chesky argued during a recent podcast appearance that management layers are becoming unnecessary. Software now handles basic coordination tasks. Individual workers who reject new daily workflows face real career risk.

This message is not just corporate noise. Tech companies everywhere are flattening organizations and cutting non-technical management layers. If you manage people or write code, these changes directly alter how leadership evaluates your value.

Companies are cutting traditional management layers

Middle management used to offer a safe career path in tech. Managers spent their days organizing updates, checking project statuses, and running check-ins. Chesky made clear that this middle tier is under direct threat. Automated systems now track progress and share data faster than human coordinators.

The shift creates immediate pressure for managers who stopped doing hands-on work years ago. Companies increasingly want leaders who can write code or execute work alongside their teams. A manager who only shuttles messages back and forth no longer fits what executives want.

Removing extra management layers offers an upside for individual contributors. Product teams gain direct control over daily decisions when middle managers leave. You spend less time preparing slide decks for updates. You spend more time building software.

Resisting new software tools creates immediate risk

Chesky also targeted workers who actively avoid new automated tools. He noted that employees who resist changing daily habits face serious risks. Teams that adopt automated code completion and documentation tools move much faster. Manual workflows simply cannot keep up anymore.

For working engineers and designers, output is now front and center. Organizations are setting higher productivity targets. They assume every worker uses modern automated tools. Sticking strictly to older workflows leaves you behind colleagues who use automated assistance.

This push creates real friction inside engineering teams. Software tooling evolves rapidly. Forcing workers to adopt unproven software introduces bugs and security risks. Balancing efficiency with code quality remains a constant challenge for individual developers.

Tech executives are redefining what headcount means

Other tech leaders share similar thoughts about the future of tech work. Ex-Google CEO Eric Schmidt recently noted that long working hours were standard in past tech eras. He suggested automated tools could reduce that burden for productive teams. Meanwhile, Palantir CEO Alex Karp pointed out that different cognitive skill sets will thrive as technical tasks change.

These statements point to a redesigned model for technology teams across the industry. Companies are not trying to eliminate every middle role. They are redefining what those employees must produce. Leadership expects smaller teams to handle workloads that once required full departments.

The risk for you is that expectations increase without additional compensation or support. Executives assume automated systems handle routine administrative tasks. They expect you to maintain constant high-level output. That pressure can quickly lead to burnout if you do not set boundaries.

Flatter organizations offer real advantages for developers

Eliminating administrative bloat opens genuine opportunities for technical talent. Fewer management layers mean shorter approval chains for software features and infrastructure changes. Engineers report feeling empowered when they do not need three management approvals to ship code.

This shift rewards deep domain expertise over corporate politics. Solving complex technical problems matters more than managing internal team dynamics. Technical staff who maintain strong hands-on capabilities gain real power when companies prioritize direct output.

Modern automation tools handle tedious tasks like writing unit tests and triaging minor bug reports. That reality frees up time for higher-level system architecture and product design work. The job changes significantly, but the core work of engineering remains essential.

What you can do to protect your position

If your position relies mainly on administrative coordination, rebuild your technical capabilities immediately. Look for opportunities inside your team to contribute directly to product deliverables or codebases. Showing that you can deliver tangible work products makes you far less vulnerable during restructurings.

If you are an individual contributor, experiment systematically with productivity tools in your workflow. Learn how automated assistants speed up testing, debugging, and drafting without sacrificing output security. Demonstrating clear efficiency gains helps protect your role when leadership audits team productivity.

Track how your leadership team measures success today. Adjust your daily habits to match those goals directly.

• Audit your daily schedule to see how much time goes to coordination versus technical execution.
• Integrate approved automated coding and documentation tools into your regular development workflow.
• Volunteer for technical initiatives that require building products rather than managing process schedules.
• Document measurable output improvements to demonstrate your concrete value to team leadership.