The AI Native Divide: Why Your 30s Might Already Be Too Late (And What to Do About It)
By: A Former VP of Sales Turned Content Strategist
Let’s cut to the chase: if you’re over 30 and reading this, you’re probably not “AI native.” And according to Caitlin Kalinowski—the former OpenAI robotics lead who worked at Apple, Oculus VR, and Meta before joining OpenAI’s robotics division between 2024 and 2026—that’s a problem. But it’s not the end of your career.
Kalinowski, who now advises AI startups on product strategy, made waves on a recent episode of Lenny’s podcast (released Sunday) by declaring that the only truly AI-native workers are in their early 20s. These young engineers, she says, “use AI so natively that it’s like baked into their engineering process.” They don’t adapt to AI—they grew up with it as a default tool, like a calculator or a search engine.
Here’s the uncomfortable truth for 30-somethings (and older): Kalinowski stated bluntly, “It’s very hard to find someone who’s in their 30s who can be truly fully AI native.” This isn’t ageism—it’s a reflection of how deeply AI is woven into the problem-solving fabric of a generation that never knew a world without it.
The Generational AI Gap: It’s Not Your Fault, But It’s Your Problem
Kalinowski’s observation isn’t an isolated opinion. Tech leaders across the industry are noticing the same shift. Reddit CEO Steve Huffman, Otis CEO Judy Marks, Box CEO Aaron Levie, and LinkedIn co-founder Reid Hoffman have all pointed out that AI-native younger workers may hold a “major advantage” in the workplace. Why? Because they don’t learn to use AI—they instinctively incorporate it into every step of their workflow.
What Does “AI Native” Actually Look Like in Practice?
For a 22-year-old engineer fresh out of college, AI isn’t a “nice-to-have” tool. It’s the operating system of their problem-solving process:
- They start with AI, not finish with it. Instead of drafting code and then asking an AI to optimize it, they prompt the AI to generate the initial framework and iterate from there.
- They think in prompts, not parameters. Their mental model shifts from “what do I need to build?” to “how do I describe this problem to an AI so it builds it for me?”
- Speed is a side effect. Kalinowski noted that younger engineers are “much faster, actually” because AI is embedded from the ground up. They’re not adding AI to the end of a process—they’re building the process with AI.
Kalinowski put it simply: “They’re approaching their problem-solving completely differently because they’re using AI from the ground up for everything, and they’re much faster, actually.” The key takeaway? “We need these folks to teach us how to think.”
The Meta Effect: Why Companies Are Pushing for AI-Native Cultures
This isn’t just a philosophical debate. The shift is already shaping corporate strategy. Meta, for example, has been actively pushing employees to become more “AI-native” by embedding AI tools into coding and day-to-day workflows. When one of the world’s largest tech companies mandates a cultural shift toward AI fluency, you can bet the rest of the industry is watching.
What This Means for Revenue Teams (Sales, Marketing, Customer Success)
If you’re in B2B SaaS or tech, this isn’t just about engineers. Your revenue operations, SDR teams, and customer success managers are all subject to the same generational dynamic. Consider:
- An AI-native SDR doesn’t manually research prospects—they use AI to scrape intent signals, personalize outreach at scale, and auto-enrich CRM data.
- An AI-native marketing manager doesn’t A/B test two headlines—they run dozens of AI-generated variants simultaneously and let the algorithm optimize in real time.
- An AI-native CSM doesn’t track customer health manually—they set up automated workflows that predict churn before it happens.
The gap isn’t just about coding—it’s about process philosophy. Older workers tend to layer AI on top of existing workflows. Younger workers build workflows around AI.
The “Junior Roles Are Dead” Myth (And Why Kalinowski Disagrees)
There’s growing anxiety that AI could hollow out entry-level tech jobs. If a machine can code, research, and write, why would companies hire junior staff?
Kalinowski disagrees—and her reasoning is crucial for B2B leaders to understand. “I don’t see it that way,” she said, directly pushing back on the idea that junior roles are obsolete. “I think we need them.”
Her perspective points to a more nuanced future: smaller teams, not teamless companies. AI will enable leaner operations, but it won’t eliminate the need for human intuition, creativity, and—most importantly—the kind of foundational learning that only comes from entry-level roles. As Kalinowski noted, young engineers aren’t just cheaper labor—they’re the ones teaching us how to think with AI.
The Playbook for 30-Something Leaders
If you’re a VP, CRO, or founder in your 30s or 40s, here’s your action plan—informed by Kalinowski’s insights:
1. Stop Trying to “Add AI” to Your Processes—Rebuild Them
You’re not AI-native, so stop pretending you can retrofit AI into your existing workflows. Instead, hire or pair with younger team members who can redesign your processes from scratch. Let them lead the transformation.
2. Create Cross-Generational “AI Pairs”
Pair experienced professionals (who understand business context, customer relationships, and strategy) with AI-native juniors (who understand how to leverage the technology for speed and scale). This isn’t mentoring—it’s co-creation.
3. Invest in “Institutional AI Learning”
Kalinowski emphasized that young engineers “need to teach us how to think.” Create formal mechanisms for reverse mentoring. Have your early-20s hires run workshops on how they approach problems. Make it safe for them to show you what you’re missing.
4. Rethink Your Hiring Criteria
Don’t just look for “experience with AI tools.” Look for candidates who can show you a process that integrates AI from start to finish. Ask them: “Walk me through how you would solve [common problem] using AI as your starting point.”
5. Don’t Panic—But Do Move Fast
The good news? You don’t need to be “fully AI native” to lead AI-native teams. Kalinowski’s point isn’t that older workers are obsolete—it’s that they’re at a disadvantage if they don’t adapt. The window to adapt is closing, but it’s not shut.
What This Means for B2B Growth Teams
At B2B Pulse, we’ve seen this shift firsthand. The companies that are winning right now aren’t the ones with the most expensive AI tools—they’re the ones whose revenue teams have redesigned their workflows around AI. And the teams that are struggling? They’re still trying to bolt AI onto legacy sales processes.
The Revenue Operations Perspective
- Lead generation: AI-native teams generate 3x more qualified leads in the same window because they use AI for hyper-personalized outreach, not just email sequences.
- Sales training: Instead of role-playing scripts, AI-native teams use generative AI to simulate customer objections and train reps in real time.
- Customer retention: AI-native CS teams build predictive churn models that don’t just flag at-risk accounts—they auto-generate retention playbooks.
The Bottom Line: Embrace the “Not-Native” Advantage
Here’s the paradox: while you’ll never be truly AI-native the way a 22-year-old is, you bring something they don’t have—context, domain expertise, and relationship capital. The best leaders in the next decade won’t be the ones who are most fluent in AI. They’ll be the ones who can integrate AI fluency with business wisdom.
Kalinowski’s comments aren’t a death sentence for 30-somethings. They’re a wake-up call. Stop trying to be AI-native. Start building teams that are.
Your move: Hire the 22-year-old. Listen to them. Let them teach you. And then use your experience to translate their AI-native speed into real business outcomes.
Because in the end, the companies that win won’t be run by the most AI-native people—they’ll be run by the leaders who figured out how to fuse generations, technologies, and mindsets into something neither could achieve alone.
Want to see how AI-native teams are restructuring their GTM playbooks? Subscribe to B2B Pulse for weekly playbooks, raw data, and actionable frameworks—no fluff, just execution.