The Pulse: What will the Staff Engineer role look like in 2027 and beyond?

· Source: The Pragmatic Engineer · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Software Development & Engineering, Corporate Strategy & Leadership · Depth: Novice, quick

Summary

Uber's AI adoption metrics have been updated, revealing that 84% of developers are now using agentic coding tools, with 65-72% of code being AI-generated in IDEs, and 100% via command-line tools like Claude Code. Claude Code usage nearly doubled from 32% in December to 63% by February, while IDE-based tool usage has plateaued. Separately, previous reports on Block's job cuts were corrected, confirming layoffs occurred in January 2024 and March 2025. The brief also outlines upcoming topics including the future of Staff+ engineers in an AI-driven landscape, rising AI token costs for CTOs, Atlassian's 10% layoffs and their connection to AI investment, and an industry pulse covering AI-powered code reviews, licensing debates, and Big Tech's AI infrastructure spending.

Key takeaway

For engineering leaders assessing their AI strategy, Uber's updated adoption rates highlight the rapid integration of agentic coding. You should re-evaluate your team's AI tool usage and budget allocations, especially considering the reported plateau in IDE-based tool adoption versus the surge in command-line agent usage, and the rising concern over AI token costs. This data suggests a need to optimize AI spending and adapt to evolving developer workflows.

Key insights

AI-authored code is rapidly increasing, shifting developer roles and raising concerns about escalating AI infrastructure costs.

Principles

In practice

Topics

Best for: VP of Engineering/Data, Director of AI/ML, Software Engineer, CTO, AI Engineer

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by The Pragmatic Engineer.