Sign up to save your podcasts
Or
Share EP 10 — Rubrik's Ajay Sabhlok on Embedding Architecture as The IT Decision Layer
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
EP 10 — Rubrik's Ajay Sabhlok on Embedding Architecture as The IT Decision Layer
Ajay Sabhlok made architecture the gatekeeper for every IT decision at Rubrik, not a review function that validates choices after they're made. This structural shift meant architects evaluated tools, processes, and vendor capabilities before budget conversations happened. The outcome: scaling from 700 employees to IPO without the shadow IT proliferation or rationalization projects that typically emerge when business units control procurement.
The execution reveals how it works. At VMware, he performance tested Salesforce Service Cloud despite enterprise customers not doing that, found telecom provider bottlenecks, and co-developed DR capabilities with their product team. At Rubrik, every enterprise tool passes through a quarterly board with the CFO, CRO, and co-founder before purchase approval. When sales requested territory management software, the CRO delayed it three years until manual processes actually broke at scale.
His "comprehensive thinking" framework maps failure scenarios during discovery, not after implementation. It's why Rubrik declared cloud-only infrastructure early and centralized all software budget authority under IT.
Topics discussed:
View all episodes
By PromethiumAjay Sabhlok made architecture the gatekeeper for every IT decision at Rubrik, not a review function that validates choices after they're made. This structural shift meant architects evaluated tools, processes, and vendor capabilities before budget conversations happened. The outcome: scaling from 700 employees to IPO without the shadow IT proliferation or rationalization projects that typically emerge when business units control procurement.
The execution reveals how it works. At VMware, he performance tested Salesforce Service Cloud despite enterprise customers not doing that, found telecom provider bottlenecks, and co-developed DR capabilities with their product team. At Rubrik, every enterprise tool passes through a quarterly board with the CFO, CRO, and co-founder before purchase approval. When sales requested territory management software, the CRO delayed it three years until manual processes actually broke at scale.
His "comprehensive thinking" framework maps failure scenarios during discovery, not after implementation. It's why Rubrik declared cloud-only infrastructure early and centralized all software budget authority under IT.
Topics discussed: