Like Google's own ambitions, the work of a Software Engineer (SWE) goes way beyond just Search. SWE Managers have not only the technical expertise to take on and provide technical leadership to major projects, but also manage a team of engineers. You not only optimize your own code but make sure engineers are able to optimize theirs. As a SWE Manager you manage your project goals, contribute to product strategy and help develop your team. SWE teams work all across the company, in areas such as information retrieval, artificial intelligence, natural language processing, distributed computing, large-scale system design, networking, security, data compression, user interface design; the list goes on and is growing every day. Operating with scale and speed, our exceptional software engineers are just getting started -- and as a manager, you guide the way.
In Google Search, we're reimagining what it means to search for information – any way and anywhere. To do that, we need to solve complex engineering challenges and expand our infrastructure, while maintaining a universally accessible and useful experience that people around the world rely on. In joining the Search team, you'll have an opportunity to make an impact on billions of people globally.
Responsibilities: • Set and communicate team priorities that support the broader organization's goals. Align strategy, processes, and decision-making across teams. • Set clear expectations with individuals based on their level and role, and align to the broader organization's goals. Meet regularly with individuals to discuss performance and development, and provide feedback and coaching. • Develop the mid-term technical direction and roadmap within the scope of your team. Evolve the roadmap to meet anticipated future requirements and infrastructure needs. • Design, guide, and vet systems designs within the scope of the broader area, and write product or system development code to solve ambiguous problems. • Review code developed by other engineers and provide feedback to ensure best practices (e.g., style guidelines, checking code in, accuracy, testability, and efficiency).