Software Engineering Manager II, Augmented Reality

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.

The Google Augmented Reality team is a diverse group of experts tasked with building the foundations for great immersive computing and building helpful, delightful user experiences. We're focused on making immersive computing accessible to billions of people through mobile devices, and our scope continues to grow and evolve.

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, role, and aligned 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 ideas and roadmap within the scope of the team, and 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).