Pioneering Salesforce Engineering’s Agentic Shift: Part 2
15,000 engineers. One bet on agentic coding. How Salesforce scaled autonomous development across production systems.
Why it matters
A major tech company's internal deployment of agentic development tools across its entire engineering org signals how the workforce is adapting to AI autonomy — and reveals the real operational challenges of scaling agent-assisted work beyond pilots.
The key facts
9 to knowSalesforce Engineering deployed agentic coding practices to 15,000 engineers
Initial pilot (May 2026) by Srinivas Tallapragada preceded org-wide rollout
Challenge: scaling from greenfield projects to production systems at enterprise scale
Part 2 of internal documentation series on agentic transformation
15,000 engineers affected by agentic shift
Scaled from greenfield pilot (May 2026) to production systems
Salesforce Engineering internal deployment
Production system constraints (not side projects)
Part 2 of a documented series on organizational transformation
Go to the source
Salesforce Newsroomsalesforce.com
Publisher excerpt: Key Takeaways In May, Srinivas Tallapragada shared what happened when Salesforce Engineering went agentic. This is the story of how we scaled that work across 15,000 engineers. It’s one thing to talk about agentic coding on a greenfield side project. It’s a different problem entirely to do it…