Platform Engineering, Leader

Job Overview

The Platform Engineering team is responsible for devising, implementing, and improving the processes (and associated platforms) that help engineers succeed in making Saviynt the best Identity Security Platform possible. The cloud native platform(CNP) team is responsible for improving and accelerating all aspects of internal software development for Saviynt’s portfolio of products - including new hire onboarding, developer/test infrastructure, CICD tooling and Saviynt's production reliability.

As an Engineering manager, you will ensure that help engineers do their best work and help us scale our business growth, act as an advocate of engineering practices and initiatives that keep code-quality and team velocity high

Key Responsibilities

• The Infrastructure team manages our cloud architecture and platform tooling, maintaining Infrastructure-as-Code standards, automating pipelines, and designing secure, observable, and future-proof systems


• Collaborate closely with Engineering Excellence, Quality Engineering, InfoSec, Product, and Design to synthesize requirements and prioritize impactful investments.


• You’ll define and execute the technical and organizational strategy for Saviynt’s internal platform, balancing scale, simplicity, and developer empowerment


• You’ll help shape core platform capabilities, reduce complexity for product teams, and invest in growing a strong, inclusive team culture


• Define and execute a cohesive strategy for Saviynt’s multi-cluster, cross-region compute and infrastructure platforms that prioritizes simplicity, performance, security, and scale


• Partner with engineering and product leaders to deeply understand developer needs and drive platform improvements that boost development velocity


• Shape platform abstractions that streamline compute scaling, infrastructure provisioning, and network management for engineering teams


• Contribute to the evolution of our Cloud Platform vision by applying first-principles thinking to complex technical and organizational challenges


• Invest in your team’s growth through mentorship, clear expectations, and opportunities for technical and leadership development

Required Qualifications

• 3+ years of engineering leadership experience, including managing or overseeing multiple technical domains


• 9+ years of hands-on experience building and operating distributed systems or infrastructure in a cloud-native environment


• Experience working in a startup environment desired


• Proven ability to lead multiple technical domains (e.g., compute, networking, automation) under a unified platform strategy


• Strong leadership skills with the ability to collaborate and build relationships across organizations, bridge gaps between teams, and successfully influence without authority


• Strong technical judgment with the ability to define clear charters and structure teams for speed, clarity, and cross-functional alignment


• Demonstrated success in hiring, mentoring, and retaining top engineering talent while fostering an inclusive and high-performing culture

Preferred Qualifications

• Deep expertise in Kubernetes, cloud networking, service meshes (e.g., Istio or Linkerd), and Infrastructure-as-Code tools like CDK or Terraform.


• Experience architecting AWS-native solutions, including VPC design, IAM, and multi-account strategies


• History of delivering platform capabilities that measurably improved developer experience and operational efficiency.


• Strong background in infrastructure automation, observability, and platform reliability best practices.


• Experience building internal developer platforms, libraries, or CI/CD pipelines that abstract cloud complexity (e.g., via Backstage).


• Experience managing cloud vendor spend, cost attribution, and optimization across a large organization.

Outcomes

In 2 months you’ll have fully ramped on overall Cloud Engineering including developer experience at Saviynt

In 3 months you’ll have taken complete ownership of executing Platform Engineering processes

In 6 months you’ll have started to identify areas for process improvement across the Engineering team

In 12 months there is a significant improvement