Story: Leaving LinkedIn - Choosing Engineering Excellence Over Expediency
Mar 4, 2024
auto_awesome
A software engineer, Chris, shares his story of choosing engineering excellence over expediency while working at LinkedIn. The podcast delves into his challenges with remote work, company culture, and a critical incident. It explores the clash between innovation and project health, leading Chris to decide between compromising his beliefs or pursuing work aligned with his principles.
Balancing innovation with project health is crucial in advocating for principled engineering.
Managing technical changes in a large organization requires addressing scalability issues and balancing tech debt with business priorities.
Deep dives
Challenges at LinkedIn: Balancing Values and Job Demands
Chris Cricho, a senior staff engineer at LinkedIn, faced a dilemma where his core values clashed with the demands of his senior technical role. After leading critical projects like modernizing JavaScript in the LinkedIn desktop app, Chris ultimately quit out of frustration. The podcast delves into the challenges of managing big initiatives with many teams and balancing sustainable development practices with business needs for speed. The conflict between personal values and job demands led Chris to make the difficult decision to walk away from his role at LinkedIn.
Technical Scale at LinkedIn: Managing a Massive Codebase
Upon joining LinkedIn, Chris was struck by the sheer scale of the codebase and infrastructure, with millions of lines of code and thousands of services. As part of the infrastructure team, Chris focused on making the front end more manageable for a large team of engineers committing to the app. He encountered challenges in migrating code to incorporate JavaScript classes and emphasized the importance of automating such migrations at a massive scale.
Engineering Leadership at LinkedIn: Handling Technical Initiatives
LinkedIn's engineering faced challenges in coordinating large technical initiatives across numerous teams while maintaining product velocity. The podcast highlights the shift towards a service-oriented architecture due to scaling issues in the past and the need to balance tech debt with business priorities. Chris's experience reflects the complexities of managing technical changes within a large organization like LinkedIn.
Solving Technical Challenges at LinkedIn: Incident Response and Continuous Improvement
Chris navigated technical challenges at LinkedIn, including memory leaks impacting user experience. He emphasized the importance of resiliency, automation, and system improvements to prevent future incidents. The podcast delves into the collaborative effort to address technical issues while reflecting on the socio-technical nature of engineering problems and the significance of continuous improvement in software development.
What if your dedication to doing things right clashed with your company’s fast pace? Chris Krycho faced this very question at LinkedIn.
His journey was marked by challenges: from the nuances of remote work to the struggle of influencing company culture, and a critical incident that put his principles to the test against the company’s push for speed.
Chris’s story highlights the tension between the need for innovation and the importance of project health. This all led Chris to a pivotal decision: to stay and compromise his beliefs or to leave in pursuit of work that aligned with his principles.
He chose the latter. Join us as we dive into Chris’s compelling story, exploring the challenges of advocating for principled engineering in a world that often prioritizes quick wins over long-term value.