Sr Software Development Engineer - Core Platform Integration

Workday•Pleasanton, CA

1d•$160,100 - $285,100•Hybrid

About The Position

The Core Platform Integration Team is a new centralized team within Workday’s Core Services organization that sits at the intersection of Workday's IPE (Infrastructure Platform Engineering) organization and our acquired companies. Workday has acquired several companies in the last couple of years that run multiple services across cloud service providers AWS and GCP with their own infrastructure patterns, CI/CD pipelines, and operational practices. Our charter is to bring these companies onto CP2, Workday's cloud-agnostic "paved road" platform, so that 100% of services can run on any CSP. That means migrating workloads off CSP lock-in services (managed databases, proprietary queues, vendor-specific identity, etc.) and onto standardized CP2 building blocks for compute, networking, observability, CI/CD, and security. This is a small, high-leverage team working directly with acquisition engineering leads, IPE platform owners, and Workday SREs. We operate in the open, driving architecture review boards, building migration scorecards, sizing onboarding effort, and producing the roadmap that shapes both what the IPE platform must build and what acquired teams must refactor. The work is technical, cross-organizational, and high-impact. As a Senior Software Engineer on this team, you'll be one of the hands-on technical engineers working closely with acquired company engineering teams to plan, implement, and execute their migration to CP2. You'll own the technical delta analysis for assigned acquisitions, design the migration approach, and write the code, IaC, and automation that gets services moved.

Requirements

7+ years of software/infrastructure engineering experience, with at least 3 years operating production workloads on AWS and/or GCP.
Proficiency in using the latest AI tools (Claude Code, Cursor, Augment) as a force multiplier to accelerate code understanding, migration work, and documentation.
Bachelor’s degree in Computer Science, Engineering, or related discipline, or equivalent practical experience.
Strong, current Kubernetes experience (EKS, GKE, or equivalent). You can debug a misbehaving pod, write a sane Helm chart and reason about networking and resource limits.
Production proficiency in Terraform (Terragrunt a plus) as your primary IaC tool, and experience refactoring IaC across accounts/projects/regions.
Strong coding skills in Go and/or Python for automation, migration tooling, and operators, not just glue scripts.
Solid CI/CD experience (GitHub Actions, GitLab CI, Jenkins, ArgoCD, Flux, or Harness) and comfort redesigning pipelines, not just maintaining them.
Working knowledge of observability stacks (Prometheus, Grafana, OpenTelemetry, GCP Operations Suite, or equivalents) and what good SLI/SLO instrumentation looks like.
Practical experience with at least one managed cloud database (Aurora, Cloud SQL, Spanner, RDS) including migration or replication.
Strong collaborator. You know how to earn trust with a team whose code you're about to change.
You write clearly. Migration plans, RFCs, and runbooks are part of the job.
You're pragmatic about "paved road" tradeoffs — you can hold the line on standards without being dogmatic when an acquisition has a legitimate reason to deviate.
You're comfortable with ambiguity. The first few acquisitions will not have a clean playbook; you'll help write it.

Nice To Haves

Multi-Cloud experience with GCP and AWS.
Familiarity with secrets management, IAM least-privilege design, and basic security hygiene (vulnerability scanning, image signing, mTLS).
Experience with security auditing and compliance frameworks.

Responsibilities

Partner with engineering leads at 2–3 assigned acquired companies to inventory their services, dependencies, and CSP-specific footprint (managed DBs, IAM, networking, queues, secrets, observability stack, etc.).
Produce a per-service migration plan: what stays, what gets refactored onto CP2 paved-road components, and a T-shirt-sized effort estimate (S/M/L).
Rewrite Terraform/Terragrunt modules to target CP2, port CI/CD pipelines, swap CSP-locked services for CP2 equivalents, and re-instrument observability (logs, metrics, traces, SLOs) to Workday standards.
Identify gaps in the CP2 paved road and feed concrete, well-scoped feature requests back to IPE platform teams — with enough technical specificity that they can be prioritized and built.
Help establish repeatable migration patterns (a "playbook") so future acquisition onboarding is faster than the first.
Be an active participant in Architecture Review Boards, separating hard blockers (re-architecture required) from soft blockers (tool swaps), and help drive consensus across IPE and acquisition teams.
Collaborate with teams across multiple locations and time zones, communicating effectively and building strong relationships with colleagues in diverse locations.