Learning & Growth Leader - Culture & Employee Expereince, Microsoft

Microsoft Microsoft · Big Tech · Redmond, WA +1 · Business Management

This role is responsible for building the learning ecosystem and learning culture for Security Engineering at Microsoft. It involves designing and delivering technical programs, leadership development, and communities of practice, with a focus on AI-augmented security practices and systems thinking. The role also supports customer-facing engineers and inclusion communities.

What you'd actually do

  1. Design and deliver Security Learning — a live and on-demand curriculum spanning technical fluency, AI-augmented security practice, and learning experiences relevant to Microsoft Security's product surface.
  2. In partnership with the AI Transformation Lead, design CoPs as capability-building vehicles, not social forums: each should produce reusable artifacts, surface best practices, and compound the knowledge of the engineers who participate.
  3. Develop the systems thinking track for senior ICs and architects, and the agile leadership track for engineering managers — considering this paths from the perspective of a capability architect.
  4. Partner with the Talent Strategy Lead to build the development track for customer-facing engineers — the technical depth, deployment orientation, and systems thinking that make them effective in the field.
  5. Provide Inclusion Communities — affinity networks and employee resource groups within Security Engineering — with the operating infrastructure, templates, budget mechanisms, and event frameworks they need to run effectively.

Skills

Required

  • program management
  • process management
  • process improvement
  • learning & development
  • community building
  • technical curriculum design

Nice to have

  • drive adoption through scalable resources and community engagement
  • partner closely with matrixed teams and navigate across complex systems
  • storytelling and content strategy skills
  • designing and delivering learning programs in an engineering or technical organization
  • build communities that sustain themselves beyond launch
  • understanding of how engineers develop capability
  • hold both individual development and systemic scale simultaneously
  • supporting or operating affinity/ERG/inclusion programs

What the JD emphasized

  • AI-augmented security practice
  • systems thinking
  • agile leadership
  • technical depth
  • deployment orientation
  • capability milestones
  • reusable artifacts
  • surface best practices
  • compound the knowledge
  • operating infrastructure
  • templates
  • budget mechanisms
  • event frameworks