WorkSeptember 9, 2026via Salesforce Newsroom

Pioneering Salesforce Engineering’s Agentic Shift: Part 2

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.

Key signals

  • Salesforce 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

The hook

15,000 engineers. One bet on agentic coding. How Salesforce scaled autonomous development across production systems.

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 across

The week's key stories, every Friday.

For practitioners and enthusiasts — free, in your inbox.

Free forever. No spam.

Pioneering Salesforce Engineering’s Agentic Shift: Part 2 | KeyNews.AI