Principal Group Engineering Manager

Microsoft Microsoft · Big Tech · Hyderabad, TS, IN · Software Engineering

Lead a team responsible for foundational systems and services that power GitHub’s internal engineering and development workflows, focusing on improving how GitHub engineering teams build, test, and ship software across the company. This includes CI/CD platforms, developer tooling, virtualized infrastructure, and paved paths. The role involves people leadership, technical depth, and operational ownership impacting daily developer experience and product quality for millions.

What you'd actually do

  1. Collaborating with engineering teams, product management, customers, and engineering leadership to align on and understand the problems we want to solve
  2. Unblocking obstacles for your team members as they solve GitHub’s most critical problems, often via real-time conversations in Slack or Zoom and with asynchronous communication in GitHub Issues, PRs, Discussions, and Projects
  3. Communicating effectively to stakeholders and leadership of progress and risks
  4. Coordinating work within the team and stakeholders, building relationships, and identifying opportunities and areas of improvement
  5. Ensuring the team produces good architectural design outcomes, secure and resilient systems, and quality code

Skills

Required

  • 9+ years' experience in software engineering, computer science, or related technical discipline
  • Proven experience maintaining and delivering production software coding in languages including, but not limited to, Go, Ruby, Rust, Python, JavaScript, C, C++, C#, Java
  • 3+ years’ experience leading engineering teams delivering complex infrastructure, platform, release, or validation systems.
  • Experience setting technical direction and driving execution across multiple engineers or teams in a complex cross-functional environment.
  • Proven ability to hire, coach, and develop engineers while maintaining high standards for technical quality and operational excellence.
  • Proven ability to partner across organizations, align stakeholders, and improve reliability, delivery predictability, and engineering effectiveness for business-critical systems.
  • Bachelor’s or Master's degree in Computer Science, Electrical Engineering, Electronics Engineering, Math, Physics, Computer Engineering, or related field

Nice to have

  • Experience leading or owning large-scale CI/CD and build systems, including monolith or monorepo environments, with a focus on reliability, performance, and developer experience.
  • Proven ability to run operationally critical platforms, including incident response, on-call leadership, observability, and cross-org escalation.
  • Track record of cross-team collaboration and influence, working with application owners and platform teams to drive best practices and paved paths.
  • Familiarity with test infrastructure and quality challenges at scale, including diagnosing CI failures and reducing flaky tests.
  • Experienced people manager able to balance execution, operational stability, and long-term platform investment in complex, high-change environments.
  • Experience driving strategy and execution across multiple dependent engineering teams.
  • Excellent written and verbal communication skills
  • Passion for fostering good engineering practices and processes
  • Experience recruiting and retaining healthy teams, managing performance, and calibrating expectations
  • Experience working remotely and collaborating with distributed teams.

What the JD emphasized

  • complex infrastructure
  • platform
  • release
  • validation systems
  • complex cross-functional environment
  • high standards for technical quality
  • operational excellence
  • business-critical systems
  • large-scale CI/CD
  • build systems
  • monorepo environments
  • reliability
  • performance
  • developer experience
  • operationally critical platforms
  • incident response
  • on-call leadership
  • observability
  • cross-org escalation
  • cross-team collaboration
  • influence
  • best practices
  • paved paths
  • test infrastructure
  • quality challenges at scale
  • CI failures
  • flaky tests
  • execution
  • operational stability
  • long-term platform investment
  • high-change environments
  • multiple dependent engineering teams