IBM Is Tripling Entry-Level Hiring: What the AI Jobs Narrative Gets Wrong, and What Nonprofits Can Learn
In February 2026, IBM announced it would triple its entry-level hiring in the U.S., even as artificial intelligence reshapes what those roles look like. The decision directly contradicts the prevailing narrative that AI is eliminating junior positions, and the reasoning behind it carries real implications for how nonprofits think about their own staffing, leadership pipelines, and AI adoption strategies.
When IBM's chief human resources officer Nickle LaMoreaux announced at Charter's Leading with AI Summit that the company would triple entry-level hiring in 2026, the news cut against a well-worn storyline. Across the technology industry, companies have been using AI adoption as justification for headcount reductions, hiring freezes, and the gradual elimination of roles that once served as entry points for early-career workers. IBM's move signals something different: a long-term bet on human talent even as AI handles an increasing share of the task-oriented work those roles once contained.
LaMoreaux was direct about the stakes. "The entry-level jobs that you had two to three years ago, AI can do most of them," she acknowledged. But she didn't stop there. "You have to rewrite every job," she added, describing a transformation that isn't just about reducing headcount but about reconfiguring what early-career workers actually do. The companies that triple down on entry-level hiring now, IBM argues, will be the ones with the leadership depth and institutional knowledge to compete successfully three to five years from now.
For nonprofit leaders, this story deserves close attention. The sector faces many of the same forces IBM is navigating: AI tools that can automate routine work, pressure to do more with constrained budgets, questions about which roles to fill and which to let attrition reduce, and a growing recognition that the organizations that emerge strongest from this transition will be those that invested in their people rather than simply cutting them. IBM's reasoning isn't just relevant to tech giants. It's a framework that applies directly to mission-driven organizations thinking carefully about their workforce strategies.
What IBM Actually Did, and Why It Matters
IBM's 2026 entry-level hiring push isn't a reversal of its earlier AI commitments. The company has been actively deploying AI across its operations for years, and it has been candid that automation has reduced demand for certain routine functions. In 2023, IBM made headlines when it paused hiring for roughly 7,800 roles it expected AI to replace. That decision reflected a genuine reckoning with AI's capacity to handle back-office and administrative functions.
What's changed is the strategic framing. Rather than treating AI as a permanent headcount replacement, IBM is now describing it as a tool that elevates what human workers do, particularly at the entry level. Software engineers in these new roles will spend less time on routine coding tasks and more time interfacing with clients and understanding their broader needs. Human resources staff will shift from answering every question to managing AI-assisted workflows and handling the complex situations that require genuine human judgment. Customer service roles will focus on the emotionally nuanced interactions that automated systems handle poorly.
The company is also making a specific bet about talent pipelines. LaMoreaux's warning that organizations cutting entry-level roles risk "hollowing out" their future leadership isn't abstract. In five years, those companies will need mid-level managers and senior strategists, and they will discover that the pipeline of candidates with the institutional knowledge, relationship experience, and organizational understanding to fill those roles simply doesn't exist. Junior roles don't just produce value in the present. They produce the senior leaders of the future.
IBM's Entry-Level Transformation
How early-career roles are being redesigned for the AI era
- Software engineers shifting from routine coding to client consulting and solution design
- HR staff managing AI chatbot workflows instead of answering every question directly
- Analysts focusing on strategic interpretation of data rather than data collection
- All roles now require AI fluency as a baseline competency
The Hollow Pipeline Problem
What happens when organizations cut too many junior roles
- Mid-level vacancies unfillable in 3-5 years due to missing development stages
- Institutional knowledge gaps when no one has grown up inside the organization
- Increased hiring costs as organizations compete for scarce experienced talent externally
- Cultural continuity risks when leadership positions are filled entirely by external candidates
The Nonprofit Parallel: A Sector Under Similar Pressure
Nonprofits face a version of exactly the dilemma IBM is navigating, often with fewer resources and more acute constraints. When a small development team discovers that AI can handle first drafts of grant proposals, routine donor acknowledgments, and data-entry-heavy prospect research, the immediate temptation is to reduce that team. Why hire a junior development associate when AI can produce the outputs that role was historically hired to generate?
IBM's experience suggests that this reasoning, while superficially sound, misunderstands how organizations actually develop capacity over time. The junior development associate isn't just producing first drafts and entering data. She is learning the organization's major donor relationships, developing her instincts for what funders respond to, building her own professional network, and becoming the person who will be running development in seven years. That learning process cannot be compressed or outsourced. It requires time, mentorship, and direct experience with real work.
This doesn't mean nonprofits should ignore AI's capacity to take on routine work. The point is more nuanced: the routine work that AI handles should free junior staff to do more of the relationship-building, strategic thinking, and mission-critical engagement that genuinely develops professional capability. A junior program coordinator who is no longer spending half her time on data entry can now attend more community meetings, build relationships with partner organizations, and develop the contextual judgment that makes a great program manager. That's the same logic IBM is applying to its software engineers.
Reframing What Junior Roles Produce
The shift from task output to organizational development
When evaluating whether to fill or eliminate a junior position, organizations often focus exclusively on the task outputs that role generates. IBM's framework invites a different question: what organizational capabilities does this role develop over time?
Traditional view of junior roles:
- Produce specific task outputs (drafts, data, reports)
- Reduce workload pressure on senior staff
- Cost-effective labor for routine functions
IBM-informed view of junior roles:
- Build the institutional knowledge base of future leaders
- Develop the judgment and relationships that AI cannot replicate
- Create the leadership pipeline for the organization's 5-10 year future
Gen Z's AI Advantage, and What Nonprofits Can Do With It
One of the more striking observations in IBM's announcement is the role of Gen Z's AI fluency. LaMoreaux noted that young candidates are often arriving with stronger AI skills than their more experienced peers, having grown up using these tools naturally and experimentally rather than adopting them under organizational pressure. For IBM, this is a feature, not just an incidental characteristic of younger workers.
Nonprofits are encountering the same dynamic, sometimes uncomfortably. Executive directors with decades of experience are being asked to rapidly develop AI competencies that a recent college graduate may have already internalized. Program staff who have spent years developing deep subject matter expertise find themselves learning alongside volunteers who can navigate AI tools more intuitively. This creates real tension around professional hierarchy and authority, but it also creates real opportunity.
Organizations that can create structures for genuine bidirectional learning, where experienced staff share mission context, relationship knowledge, and strategic judgment while younger staff contribute AI fluency and tool familiarity, tend to develop the strongest AI capabilities fastest. This requires letting go of the assumption that seniority always correlates with expertise, particularly in areas where the technology itself is newer than the junior employee's career. An article we've published on navigating situations where younger staff know more about AI explores this dynamic in more depth.
What Gen Z Brings to Nonprofit Teams
- Natural fluency with AI tools developed through personal and academic use
- Comfort with iteration, experimentation, and rapid tool-switching
- Exposure to the latest AI capabilities through personal exploration
- Fresh perspective on workflows that experienced staff may take for granted
What Experienced Staff Still Provide
- Deep mission context and understanding of community nuance
- Funder relationships and donor trust built over years
- Judgment about when AI outputs need human correction
- Organizational memory and strategic continuity
Rewriting the Job, Not Eliminating It
IBM's LaMoreaux offered a deceptively simple principle: "You have to rewrite every job." This isn't a clever slogan. It's an operational challenge that requires significant investment of time and leadership attention. Most organizations, when they discover AI can handle certain tasks, respond by trying to figure out whether they still need the person doing those tasks. IBM is suggesting a different question: if we no longer need this person to do those specific tasks, what higher-value work can they now do instead?
For nonprofits, this distinction matters enormously. A grants manager who spent 40% of her time drafting routine report sections now has that time available. The question is whether the organization helps her redirect it toward relationship-deepening conversations with funders, strategic thinking about portfolio development, or mentoring junior development staff, or whether it simply notices that she seems to have more slack and starts adding unrelated administrative tasks to fill the gap. The first outcome compounds the AI investment. The second wastes it.
Rewriting jobs well requires honest conversations about what the organization most needs from each role, what the person in that role is best positioned to contribute given their unique expertise and relationships, and how AI can genuinely complement rather than simply replace their work. Nonprofit leaders who are actively redefining roles for the AI era are finding that these conversations, though time-consuming, produce clarity about organizational priorities that staff at all levels find motivating rather than threatening.
A Framework for Rewriting Nonprofit Jobs in the AI Era
Practical questions for each role when AI changes the task landscape
Step 1: Audit what the role currently does
Map the full range of tasks, estimating how much time each consumes. Identify which tasks are primarily about generating a specific output versus which require human judgment, relationships, or contextual knowledge.
Step 2: Identify what AI can realistically handle
Be honest about AI's actual capabilities in the specific context of your organization. Drafting is different from final writing. Data collection is different from data interpretation. Don't assume AI handles something well just because it can produce an output.
Step 3: Define the higher-value work the person could do with recovered time
This is the step most organizations skip. What relationship-deepening, strategic thinking, community engagement, or mentorship work has been consistently deprioritized due to time pressure? That's where the recovered hours should go.
Step 4: Rewrite the job description and performance expectations accordingly
If the role is genuinely changing, the formal expectations need to reflect that. A grants manager evaluated primarily on number of applications submitted will optimize for volume. One evaluated on funder relationship quality will invest differently.
Step 5: Invest in AI training so the transition is supported
Expecting staff to simply figure out how to use AI without structured support tends to produce inconsistent adoption and frustration. Organizations that invest in structured AI training for their teams see faster and more effective integration.
The Long Game: Leadership Pipelines and Succession in the Nonprofit Sector
Nonprofit leadership succession is already one of the sector's most underaddressed challenges. Executive directors who have led organizations for a decade or more often leave without adequate succession plans in place. Development directors who hold the organization's most critical funder relationships frequently transition without documenting those relationships or developing internal candidates to inherit them. The absence of strong internal pipelines forces expensive and often unsuccessful external searches.
IBM's argument about hollow pipelines applies with particular force in this context. Nonprofits that respond to AI-driven efficiency gains by cutting junior and mid-level positions will not only lose the short-term organizational development those roles provide, they will also further compound a succession challenge that was already serious before AI entered the conversation. The grants coordinator hired today who is thoughtfully developed through roles of increasing responsibility is the development director of 2030. The program assistant who learns the organization's theory of change, builds relationships with community partners, and develops her analytical skills becomes the program officer who can actually lead a portfolio.
Organizations that have done serious work on AI-assisted succession planning are increasingly recognizing this dynamic. The tools that help identify and develop internal talent candidates are most powerful when there's actually a bench of internal candidates to work with. That bench doesn't build itself. It requires consistent investment in entry and mid-level hiring even when AI creates opportunities to reduce headcount.
Signs Your Pipeline Is Thinning
- Senior hires are consistently made externally rather than from within
- Junior staff tenure is declining as there's no visible path for growth
- Institutional knowledge lives primarily with 2-3 people who are approaching retirement
- New mid-level hires take 12+ months to become effective due to context gaps
Pipeline Health Investments
- Consistent junior hiring even during budget pressure, prioritized strategically
- Structured mentorship that connects junior staff with senior knowledge holders
- Clear growth pathways with explicit milestones and timelines
- AI tools that help document and transfer knowledge between roles
What This Means for Nonprofit AI Strategy
IBM's decision doesn't mean every organization should immediately hire more people. It means that the decision about whether to hire, reduce, or hold headcount should be made on long-term strategic grounds rather than on the short-term observation that AI can handle certain tasks. The organizations that will use AI most effectively aren't the ones that are minimizing their human investment. They're the ones that are maximizing the productivity of their human investment by giving people better tools.
This requires a meaningful shift in how nonprofits think about their AI strategy overall. It's not primarily a technology procurement question. It's a workforce development question. Which roles will be most transformed by AI? How should those roles be redesigned to capture the highest value from the combination of AI capability and human expertise? What investment in training and development is needed to make that combination work? And what does the organization need from its staff five years from now, working backward from that to inform hiring decisions today?
Nonprofit leaders who are navigating the question of which roles AI will change versus eliminate are increasingly finding that the binary framing (replace versus keep) misses the more important question of how to evolve. IBM is not keeping entry-level roles unchanged. It is actively redesigning them to extract higher value from the people in those roles. That's a more ambitious and more effective approach than either wholesale elimination or unchanged preservation.
Four Principles for Nonprofit Workforce Strategy in the AI Era
1. Measure long-term pipeline value, not just immediate task output
When evaluating whether to fill a role, include the future leadership value that role develops, not just the present-year work it produces.
2. Redesign roles before reducing them
When AI reduces the task burden of a role, the first response should be identifying what higher-value work that person can now do, not whether the role can be eliminated.
3. Invest in AI training as a workforce investment, not a technology investment
The organizations that get the most from AI are those whose people know how to use it well. Training is a prerequisite, not an afterthought.
4. Use Gen Z's AI fluency as an organizational asset
Rather than treating younger staff's comfort with AI as a curiosity, create structures for sharing that fluency across the organization while junior staff gain institutional context from senior colleagues.
Talking to Staff About This Without Adding to AI Anxiety
One of the practical challenges nonprofit leaders face is how to communicate about AI's impact on jobs in a way that is honest without being destabilizing. Many staff members are already anxious about whether AI will affect their positions. The IBM story offers a genuinely useful counternarrative, but it requires some care in how it's presented.
The honest version of the IBM message is this: AI will change what every role does. Some tasks that have historically been part of your job will be handled more efficiently by AI tools, and that's going to free you up to do work that has more impact and requires more of your expertise. We're going to invest in helping you develop those AI skills and in redesigning roles to get the most from the combination of AI and human judgment. We're not planning to use AI as an excuse to reduce our team. We're planning to use it to make our team more effective.
This message only lands if the organization follows through. Staff who hear reassuring talk about AI augmentation but then watch colleagues' roles quietly disappear over time will correctly identify the gap between rhetoric and reality. Leaders who are navigating staff conversations about AI and job security find that the most effective approach combines honest acknowledgment that roles are changing with concrete evidence that the organization is investing in its people rather than treating them as interchangeable with automation.
The Strategic Case for Investing in People Alongside AI
IBM's decision to triple entry-level hiring isn't a rejection of AI or a sentimental defense of the status quo. It's a calculated long-term bet that the organizations with the deepest human talent pipelines will outperform those that treated AI as a permanent headcount replacement. The reasoning is sound, and it applies to nonprofits with at least as much force as it does to technology companies.
The nonprofits that will serve their communities most effectively in 2030 and 2035 are being shaped right now by the hiring and development decisions their leaders are making today. Organizations that are hollowing out their junior roles, even rationally and with good budgetary intentions, are also hollowing out the leadership bench that will need to navigate whatever the AI landscape looks like in a decade. Organizations that invest in rewriting roles, developing talent, and building genuine AI fluency across their teams are building something more durable.
IBM's LaMoreaux put it plainly: the companies three to five years from now that will be most successful are those that doubled down on entry-level hiring in this environment. Nonprofit leaders would do well to test that logic against their own organizations, and to make hiring and development decisions that reflect a long-term view of what their mission requires.
Thinking Through Your AI Workforce Strategy?
We help nonprofit leaders navigate the intersection of AI adoption and workforce development, from rewriting job descriptions to building internal AI capability across teams at every level.