news.volyx.in

I ignore the spotlight as a staff engineer (lalitm.com)

547 points by todsacerdoti · 232 days ago · 243 comments on HN

Article summary

The article discusses the author's experience as a Staff Engineer at Google, where they have chosen to focus on building internal tools and infrastructure rather than seeking the spotlight. This approach has allowed them to build long-term systems and earn the trust of their customers, who are other engineers within the company. The author argues that this path can lead to a more meaningful and high-impact career, even if it doesn't come with the same level of external recognition. By prioritizing depth and technical ownership, the author has been able to create lasting value and make a significant impact on the company.

Main themes

  • Staff Engineer role
  • Internal tools and infrastructure
  • Long-term systems building
  • Technical ownership
  • Career development
  • Big Tech company culture

What commenters say

  • Some engineers believe that building internal tools and infrastructure can be a fulfilling and impactful career path, even if it doesn't come with external recognition.
  • Others argue that this approach can be risky, as it may not be valued by management or lead to career stagnation.
  • There is a tension between the need for technical expertise and the pressure to prioritize executive visibility and short-term goals in big tech companies.
  • Some commenters believe that the current culture in big tech companies often prioritizes flashy features and external validation over deep technical work and long-term value creation.
  • Others argue that engineers should focus on building solid code and making projects move forward, rather than trying to sell themselves to leadership.
  • The importance of setting appropriate incentives and evaluating contributions in code is highlighted as a key challenge in managing engineering teams.
  • Some engineers feel that their work is underappreciated and that they are only recognized when something goes wrong, rather than for their preventative work.
  • There is a need for a cultural shift in big tech companies to value and recognize the importance of deep technical work and long-term systems building.