Bengaluru, 8th August 2025: In today’s fast-evolving world of software engineering, the most impactful leaders are those who not only adapt across scale, speed, and security, but redefine how DevOps is practiced in radically different environments. From building resilient systems at Hotstar to driving hyper velocity pipelines at MPL, and now shaping secure, human-centric platforms at Greytip Software, Abhishek Gaurav’s journey has been a master class in adaptive leadership and platform thinking.
In this candid conversation, Mr. Abhishek Gaurav, Senior Director at Greytip Software, sits down with Mr. Marquis Fernandes, who leads the India Business at Quantic India, to share how his DevOps philosophy has evolved across diverse industries. Together, they delve into why observability and cultural security are foundational to a future-ready SDLC, and how subtle leadership shifts, from control to coaching, have enabled Abhishek to uncover hidden talent and foster high-trust, high-performance teams. He also shares his unconventional productivity hacks, like timeboxing for chaos, and reflects on what it takes to design systems, and teams, that can thrive in ambiguity and deliver lasting impact.
From Hotstar to MPL to Greytip, you’ve worked in environments with vastly different scale and culture. How did your DevOps and leadership approach evolve to suit each organization’s unique needs?
At Hotstar, the focus was on ultra-scale reliability under extreme load, especially during live events with millions of concurrent users. Our DevOps mindset was built around resilience, observability, and chaos engineering. Speed and stability were critical.
At MPL, we shifted gears toward rapid iteration and high-velocity deployment pipelines, given the competitive nature of the gaming market. Here, infrastructure as code, automated compliance, and real-time telemetry were non-negotiable.
At Greytip, with greytHR, we’re building a mission-critical SaaS platform for HRMS, where data integrity, compliance, and user trust are paramount. My leadership approach now emphasizes secure DevOps, cross-functional collaboration, and long-term architectural thinking over quick wins.
In short, I’ve moved from reactionary scalability to proactive governance and platform stability, while adapting leadership styles from command-control in crisis to a more coaching and enablement-driven approach in SaaS.
If you had to design a future-ready SDLC from scratch in 2025, what would be its three most critical pillars, and why?
- Autonomous Quality Gates– Integrating AI-driven test, security, and performance checks that self-improve over time. This enables faster, safer releases without manual bottlenecks.
- Observable by Design– Making telemetry and tracing native to code artefacts and infrastructure from day one. It’s not just about monitoring it’s about enabling intelligent feedback loops.
- Human-Centric Security– Security that’s not just technical but also behavioural. Include identity, collaboration, and cultural elements in SDLC to make developers owners of secure coding practices.
What’s the quirkiest or most unconventional productivity hack you’ve picked up along the way?
“Calendar timeboxing for unplanned chaos.” It sounds paradoxical, but I block calendar slots labelled “Handle Emergencies.” It mentally prepares me to not panic when things go off-rails and when nothing breaks, I use it for reflection or mentoring. It’s like budgeting for a rainy day, but for cognitive load.
Also: walk-and-talk one-on-ones. Great for thinking aloud, reducing Zoom fatigue, and surfacing hidden blockers.
Leadership is also about digging into real team potential. How do you identify and nurture hidden talent in your team?
I look for people who ask “why” before “how.” They often have a curiosity that goes beyond tasks. I give them stretch assignments with real stakes internal POCs, tech talks, or leading post-mortems.
I also run “zero-blame retros” where juniors are encouraged to critique even senior designs. This not only surfaces their thinking but gives them confidence and visibility.
Mentoring happens in micro-moments code reviews, Slack threads, design critiques and I make a habit of pointing out growth opportunities when I see them.
To know more about us / publish your article, reach us at
www.quanticindia.com
marquis@quanticindia.com.
