Avantages
Exposure to modern cloud, infrastructure, platform engineering, and DevOps technologies. Opportunity to work on large-scale enterprise systems and mission-critical production environments. Talented engineers and opportunities to learn from experienced peers. Exposure to complex operational challenges and enterprise-scale platforms.
Inconvénients
The India-based DevOps organization is heavily driven by operational metrics, ticket closures, status reporting, and activity tracking. The Director and Senior Manager have established a culture of close oversight and frequent monitoring of day-to-day activities. Leadership involvement often extends into routine engineering tasks and minor implementation details that could be delegated to team leads and senior engineers. Engineers are expected to provide frequent updates and justify progress on even small tasks, creating an environment that can feel more focused on supervision than trust and ownership. Decision-making is concentrated at higher management levels, reducing autonomy, slowing execution, and limiting opportunities for engineers to take ownership. Engineering teams are often evaluated based on ticket handling, responsiveness, and operational support rather than automation, platform improvements, reliability, scalability, innovation, and long-term business impact. The strong emphasis on ticket metrics creates the wrong incentives. Engineers who eliminate recurring operational work through automation may receive less recognition than those who continue to manually handle large volumes of tickets. The result is that teams become focused on managing work rather than eliminating it. Significant focus on operational support leaves limited time for technical debt reduction, platform engineering, architectural improvements, reliability engineering, and long-term quality initiatives. Teams often feel pressure to demonstrate activity rather than outcomes, leading to a reactive culture focused on firefighting instead of proactive engineering. Process, governance, and operational discipline are important in any enterprise environment. However, excessive focus on approvals, reporting, ticket metrics, and management oversight can create unnecessary bureaucracy and slow execution. In many successful engineering organizations, process exists to enable teams rather than control them. The current culture often feels more focused on adherence to process than on engineering outcomes and customer value. Following the SAP acquisition, many employees hoped to see a stronger engineering-first culture with greater empowerment, innovation, trust, and long-term investment in platform engineering. However, the experience has felt more focused on operational control, reporting, process compliance, and efficiency metrics than engineering excellence. While SAP is recognized for engineering excellence and innovation, the local DevOps culture does not always reflect those expectations. Many engineers expected greater autonomy, ownership, and outcome-based leadership following the acquisition. There is a growing perception among some employees that the increasing focus on metrics, oversight, and cost optimization creates uncertainty around long-term career growth and job security, negatively impacting morale and engagement. The environment can at times resemble a service-delivery organization rather than a modern platform engineering organization focused on automation, reliability, scalability, and continuous improvement.