Amy Unger from GitHub discusses her transition from academic programming to for-profit tech, the differences between tech lead and deep diver roles, trade-offs in engineering projects, and the importance of value and service ethic in developer tooling. She shares insights on managing rushed feature requests, navigating product failings, mentoring, balancing coding with non-coding work, and learning from peers in a male-dominated environment.
Staff engineers roles vary across organizations, from tech leads to deep divers focusing on specific expertise areas.
Balancing organizational and project-specific responsibilities is crucial for staff engineers at GitHub, emphasizing aligning tasks with departmental goals and fostering mentorship.
Deep dives
Role of Staff Engineers at GitHub
There is no standard set of expectations for staff engineers at GitHub, varying across each organization. Common patterns include roles similar to tech leads and deep divers, focusing on specific expertise areas like git systems. The tech lead archetype is a frequent role at GitHub, emphasizing clear wins and immediate value delivery, whereas deep divers tackle larger problems over more extended periods.
Challenges Faced by Staff Engineer at GitHub
While transitioning beyond the tech lead position, staff engineers at GitHub encounter challenges balancing organizational and management responsibilities over project-specific tasks. With a focus on navigating meetings aimed at providing guidance and problem-solving assistance, the role becomes intricate in framing technical issues within broader business contexts. Prioritization and aligning tasks with departmental goals are key components of managing diverse responsibilities effectively.
Sponsorship and Mentorship in Staff Engineering
Sponsorship and mentorship play vital roles in staff engineering, where sponsorship involves ensuring tasks can be transitioned to team members effectively, balancing delegation and responsibility. Amy emphasizes the importance of trusting teammates and framing risks within a product's context when making decisions. While formal mentorship programs pose challenges, informal mentoring relationships with colleagues and learning from experienced staff engineers significantly impact professional growth and perspectives.
Amy Unger, our guest on today’s show, is passionate about providing a high-quality service to the customers who use the products she is working on. Amy has a diverse skill set and an equally diverse set of tasks that she undertakes weekly for GitHub, and at the core of everything she does is her drive to provide value. Amy came into the for-profit space from the academic programming space, and she explains the different experiences she has had in these realms. We discuss what a tech lead role consists of, in comparison to the deep diver role that Amy currently holds, the responsibilities that come with it, and why she loves what she does. Amy also shares her thoughts about trade-offs, and the considerations that all engineers should be making before they embark upon certain projects.