Developing Dev's resource offers insights, tutorials, and resources for software developers and technology enthusiasts. Readers can learn about coding best practices, software architecture patterns, and emerging technologies. With articles, tutorials, and code samples, Developing Dev provides  guidance and expertise for building software applications and advancing technical skills.

The Developing Dev

David Ronca shares lessons from his 36-year career, including 12 years at Netflix and time at Meta. He discusses Netflix's culture of avoiding brilliant jerks, rejecting 24/7 work expectations, and paying top of market. He explains his hiring philosophy: prioritizing fundamental engineering ability over leetcode performance, looking for systems thinking and technical intuition. He describes challenges scaling Netflix's flat structure as the company grew, the revolutionary culture memo, and lessons from joining Meta as a senior leader where he learned to build trust before driving change. He covers video encoding innovations, handling Covid-19 traffic spikes, and the importance of individual recognition at scale.

Retired Netflix Engineering Director On Regrets, Video Engineering, Hiring Stories

Its a long video, i also think it needs a longer summary. Made my n8n agent do it:
David Rumpka, an engineering director at Netflix and Facebook (Meta), shared insights from his 36-year career in engineering leadership. Early in his career, he experienced working with difficult but highly skilled engineers who were indispensable yet uncollaborative, and he saw how companies struggled when such individuals left. At Netflix, the culture was different; they did not tolerate “brilliant jerks” and emphasized teamwork and collaboration. The Netflix culture deck explicitly stated they did not value 24/7 work but rather valued impact within an 8-hour day, encouraging employees to be passionate about their work but maintain work-life balance.
Rumpka recounted how Netflix’s culture was revolutionary in the early 2000s, focusing on trust, freedom, responsibility, and hiring exceptional talent across all departments. However, as Netflix grew, the culture memo became aspirational rather than fully realized. The company initially had no engineering levels, treating all engineers as equals, which worked when the company was small but became problematic as the team grew and diversified in skill levels. This lack of formal leveling and objective performance evaluation made compensation and recognition challenging, leading to difficulties in retaining top talent.
Netflix used a “personal top of market” compensation model, where employees were encouraged to interview often to understand their market value. Managers would adjust salaries to match competitive offers, but without clear leveling, this system became unsustainable and opaque. Rumpka advocated for objective leveling systems to fairly recognize and compensate engineers, a change Netflix implemented after his departure.
Regarding hiring, Rumpka preferred evaluating candidates based on their engineering intuition and ability to understand complex systems rather than their performance on coding challenges like LeetCode. He believed foundational engineering skills—such as understanding complex systems, technical intuition, and decision-making under uncertainty—were innate and more important than coding speed or memorized algorithms. He shared examples of hiring engineers from non-software backgrounds who excelled due to their strong engineering mindset and ability to learn coding skills.
One of the strongest engineers he worked with was Jannis Katzanetus, who contributed significantly to video encoding technology at Netflix and Meta, including pioneering content-based encoding and codec evaluation models that balanced quality and bandwidth efficiency.
Rumpka joined Meta in late 2019 after initially interviewing in 2017 but declining an offer. At Meta, he led a large video processing team and faced the challenge of building trust with an established team. He emphasized the importance of relationships, listening, and understanding the team before making decisions. He learned that leadership is about building trust and that stepping into a well-functioning team requires patience and humility.
During the COVID-19 pandemic, Meta’s video systems faced unprecedented load, equivalent to a daily New Year’s Eve spike, requiring rapid problem-solving to maintain stability. Rumpka gained a deeper appreciation for Meta’s global impact, especially in regions where platforms like WhatsApp and Instagram are vital for communication and commerce, improving lives for billions.
Reflecting on work-life balance, Rumpka shared a personal story of being diagnosed with stage three colon cancer in 2004 after years of intense work hours at a startup. This experience forced him to prioritize health and balance, leading him to value companies like Netflix that discouraged 24/7 work culture. He advised engineers to plan their work-life balance intentionally, focus on high-impact tasks, and communicate priorities clearly with managers. Occasional intense work periods are acceptable but should be exceptions, not the norm.
Rumpka identified learning and growth as critical throughout his career. His early jobs developed his software engineering skills; his time at Netflix taught him leadership, hiring, firing, and cross-functional collaboration; and Meta taught him objective performance management and scaling engineering organizations. He highlighted Meta’s rigorous performance review process, which emphasizes individual credit and objective evaluation through data and calibration among managers.
A book that influenced him was “12 Secrets to Microsoft Success,” which introduced concepts like betting the company on big opportunities, embracing good failure, hiring the top 5% of engineers, dogfooding products internally, and managing hiring to focus on impactful projects. He noted that many modern tech companies have adopted and evolved these principles.
Rumpka expressed regret about spending his early career years at large, failing companies without focusing on growth. He advised engineers to seek hard problems to solve, continuously learn, and work for visionary leaders who can execute their vision. He emphasized the importance of financial planning from day one, managing spending and saving thoughtfully to achieve financial independence and flexibility later in life.