Principal Software Engineer - Core Platform Integration

Workday Workday · Enterprise · Pleasanton, CA

Principal Software Engineer for Workday's Core Platform Integration Team, focused on migrating acquired companies' services onto Workday's cloud-agnostic platform (CP2). This role involves setting architectural direction, leading migration efforts, defining platform requirements, and bridging technical gaps between acquired teams and the core infrastructure platform. The engineer will establish migration playbooks, ensure adherence to standards, and mentor other engineers. The role requires deep expertise in multi-cloud environments (AWS/GCP) and experience with large-scale infrastructure integrations, with an emphasis on using AI tools to accelerate work.

What you'd actually do

  1. Own or co-own the overall migration architecture and reference patterns that all acquired teams onboard against: compute, networking (VPC/subnets/regional topology), data, identity, secrets, observability, CI/CD, and SRE practices.
  2. Lead or co-lead the Architecture Review Boards for each acquisition: separate the hard blockers (genuine re-architecture) from soft blockers (tool swaps), make the call on which CSP-locked services have acceptable CP2 substitutes today vs. which require new platform investment, and produce defensible T-shirt-sized effort estimates that senior leadership can plan against.
  3. Define the dual backlog that shapes the IPE platform backlog (features the paved road must build to unblock acquisitions) and the acquisition backlog (technical debt teams must clear). Drive prioritization across both with IPE leaders and acquisition GMs.
  4. Be the technical bridge between acquired-company engineering leadership and IPE. Acquisitions have with their own strong opinions and their own platforms, and have legitimate skepticism about replatforming. You earn their trust through technical credibility, then drive convergence.
  5. Set the bar for regional/sovereign architecture: data residency, regional ring deployment patterns, key management, and the elimination of CSP-specific control-plane dependencies. Make sure the migrations we ship today don't quietly recreate lock-in tomorrow.

Skills

Required

  • 12+ years of software and infrastructure engineering experience
  • deep production expertise across both AWS and GCP at organizational scale
  • Proficiency in using the latest AI tools (Claude Code, Cursor, Augment) as a force multiplier to accelerate code understanding, migration work, and documentation
  • read code fluently in Go and Python
  • debug a Kubernetes operator
  • know what a well-designed service looks like
  • led large multi-cloud migrations or M&A infrastructure integrations end-to-end and shipped them
  • owned the architecture, navigated organizational challenges, made the unpopular calls, and stayed accountable through the long tail of cutover, regressions, and operational handoff

Nice to have

  • experience with CP2, Workday's cloud-agnostic "paved road" platform
  • experience with CI/CD pipelines
  • experience with operational practices
  • experience with managed databases
  • experience with proprietary queues
  • experience with vendor-specific identity
  • experience with compute, networking, observability, CI/CD, and security building blocks
  • experience with SRE practices
  • experience with Terraform modules
  • experience with pipeline templates
  • experience with observability conventions
  • experience with SLO frameworks
  • experience with runbook standards
  • experience with regional/sovereign architecture
  • experience with data residency
  • experience with regional ring deployment patterns
  • experience with key management
  • experience with CSP-specific control-plane dependencies

What the JD emphasized

  • deep production expertise across both AWS and GCP at organizational scale
  • led large multi-cloud migrations or M&A infrastructure integrations end-to-end and shipped them
  • owned the architecture, navigated organizational challenges, made the unpopular calls, and stayed accountable through the long tail of cutover, regressions, and operational handoff