Once again, after showing great interest in how to scale LinkedIn's hyper-custom move to Kubernetes, I was invited to join the official Kubernetes team at LinkedIn. In this role I am diving deep on our internal kubectl plugins, how we deploy stateful systems at scale and the DX for doing so.

Transitioned to the Graph engineering team at LinkedIn, where I brought LinkedIn's sophisticated, hyper-performant Graph technology to Kubernetes. This included taking the lead on the path towards database containerization and contributing back to the overall LinkedIn Kubernetes strategy. As a result we discovered how to efficiently and performantly containerize our Graph database, while showing how Kubernetes improved its operability. During this process I also showed how the company could make use of Kubernetes' flexibility to greatly increase our capacity headroom while greatly reducing the amount of idle hardware needed to run it at a very high level of availability.

After showing great interest in the internal LinkedIn movement for IaC, I transitioned to the internal Terraform team early on. I was able to contribute many features to this greenfield project, and work tightly with leadership to engineer a path towards IaC for thousands of engineers and dozens of internal services. I lead the product vision and was a primary mover in the development of internal standards for IaC as a concept.

This position allowed me to exercise my passion for building great products from all stages and pieces of the stack. Unfortunately, this project was placed on pause and I moved on to my next internal role, modernizing the LinkedIn stack for a Kubernetes-forward world.

Worked on reliability and performance features in Feed & Economic Graph products as part of the wider "Social Graph" SRE team . In addition to constant monitoring and insurance of availability of various large scale systems, I developed several product features including backup procedures for internal Feed services. Other various tasks range from GC tuning on large scale, high performance systems to observability automation and process building within the org. As any other SRE, I dedicated one week out of every quarter to ensuring oncall remained manageable for the next person.

During my time on this team I managed many acute production issues, seeing each through to resolution and postmortem – with a severe focus on user experience. I also managed several longer term issues and initiatives to resolution, working with stakeholders across the company well into the parent organization (Microsoft) to secure lasting results.