Key Takeaways
- Tech workers' #1 fear isn't losing jobs to AI; that ranks second to last in the latest survey from Lenny Rachitsky and Noam Segal.
- The top concern by far is the expectation to produce more for the same compensation, creating a feeling of being "squeezed."
- This pressure stems from an unsustainable work velocity and the relentless speed of new AI technology, forcing constant learning and output.
- As Lenny Rachitsky notes, the immediate efficiency gains from AI are often “plowed straight back into expectations,” making the new higher output the baseline.
- This shift directly contributes to surging burnout and declining optimism across the tech workforce.
The Invisible Squeeze: More Output, Stagnant Pay
“Losing my job to AI is actually second to last. What we saw rise up to the top is the expectation to do more for the same pay,” Noam Segal revealed from the second annual tech worker sentiment survey. This finding from Rachitsky's podcast cuts against the widespread narrative of robots stealing jobs. Instead, the real anxiety stems from a feeling of being relentlessly "squeezed." Segal paints a vivid picture: "It's almost as if we're all feeling like we're being squeezed and squeeze and squeeze some more to accomplish more things in less time for the same pay."
This pressure extends beyond mere increases in work hours. It's about an accelerating treadmill. The survey highlights an "unsustainable" pace, not only of the sheer volume of work, but also the rapid-fire evolution of technology. Founders expect their teams to absorb and master new AI models, frameworks, and tools — often on top of existing responsibilities and without explicit time carved out for learning. This constant requirement to re-skill, coupled with the pressure to deliver faster, amplifies the feeling of being overworked without commensurate reward. For ambitious builders, this creates a quiet, gnawing resentment that erodes engagement long before any official burnout diagnosis.
AI Set New Baselines, Not Breathing Room
Lenny Rachitsky summarized the problem with pinpoint accuracy: “The speed AI unlocked got plowed straight back into expectations. Every game becomes the new baseline and the people expected to hit it are running out of room to breathe.” When a new AI tool lets a developer churn out boilerplate code in minutes instead of hours, the immediate response isn't usually, "Great, you have more time for deep work or rest." It's, "Great, now you can deliver two features instead of one this sprint."
This phenomenon creates an insidious cycle. AI boosts productivity, but that boosted output quickly becomes the new normal, expected at the same pay rate. The conversation rarely shifts to how to share the newfound value generated by AI with the employees who are still doing the "more" work, often using their own cognitive load to adapt to new tools. The episode's discussion revealed a deeply bifurcated workforce where AI amplifies some, yet diminishes others, not by replacing them, but by demanding a higher output floor for the same ceiling. For founders, ignoring this dynamic means risking your best talent to quiet disillusionment, driving away the very people who can use these tools most effectively for your business.
What to Do With This
Founders, stop expecting AI to be free labor amplification. This week, pull your team's last three quarterly reviews and their current compensation plan. Quantify the delta: if individual output has meaningfully increased due to AI adoption, but pay or career progression hasn't, you have a retention problem brewing. Implement an "AI Value Share" principle: for every X% gain in team productivity attributed to AI, explicitly define how your team will benefit, whether through a bonus pool, accelerated promotions, or a mandated "innovation day" for learning new tools on the clock. Don't just use AI; reward the humans who make it work.