New Playbook for an EM's First 30 Days

A .NET architect shared a focused playbook for a new engineering manager's first 30 days. The advice prioritizes conducting 1:1s, shipping quick, tangible wins to build credibility, studying team postmortems to understand history, and aligning on success metrics with leadership.

The transition from a senior Individual Contributor (IC) to an Engineering Manager (EM) requires shifting focus from personal output to multiplying the team's impact. Former Twitter Director of Engineering, David Loftesness, suggests a 90-day framework focusing on owning your education, finding a rhythm, and finally assessing if the role is a fit. This initial period is less about immediate changes and more about learning, building trust, and understanding team dynamics. A key distinction for new managers is understanding the difference between technical leadership and people leadership. Technical leaders influence through expertise in system design and innovation, while people leaders focus on team development, performance, and morale. Effective managers learn to blend both styles, applying technical guidance during architectural decisions and people-focused leadership to resolve conflicts or address performance. For engineers building internal libraries, a focus on Developer Experience (DX) and API design is crucial. A well-designed API is easy to work with, hard to misuse, and provides clear feedback, which accelerates integration and reduces frustration for other engineers. Best practices include using resource-oriented URLs with nouns, implementing consistent error handling, and providing comprehensive documentation with examples. The landscape of frontend development is rapidly changing with the introduction of AI-powered tools. AI assistants like GitHub Copilot can automate repetitive coding tasks, generate UI components from prompts, and even assist in debugging, allowing developers to focus on more complex problem-solving. This shift requires a mindset of AI as a collaborator that enhances, rather than replaces, engineering judgment. To optimize performance in complex applications, WebAssembly (Wasm) allows developers to run code written in languages like C++ and Rust at near-native speeds in the browser. This is particularly useful for CPU-intensive tasks such as real-time 3D rendering, video editing, and complex data visualizations, offloading heavy logic from the JavaScript thread for a smoother user experience. The new React Compiler automates performance optimization by memoizing components and hooks at build time, reducing the need for manual `useMemo` and `useCallback`. The compiler transforms code into an optimized version with caching logic, aiming to provide performance by default without adding complexity for the developer. Modern frontend frameworks are increasingly adopting signals-based reactivity for more efficient state management. Inspired by frameworks like Solid, libraries like Preact Signals create objects whose `.value` property, when accessed within a component, automatically triggers a re-render upon change, ensuring the UI stays in sync with the state efficiently. Effective 1:1 meetings are a cornerstone of people management, serving as a dedicated space for growth, feedback, and building psychological safety, not for status updates. These meetings should be employee-driven, with a flexible agenda that covers career development, challenges, and overall well-being. Consistency is key, with most experts recommending weekly or bi-weekly meetings to foster trust and address issues proactively.

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.