Software Development Engineer

Senior Software EngineerYour work days are brighter here.We're obsessed with making hard work pay off, for our people, our customers, and the world around us. As a Fortune 500 company and a leading AI platform for managing people, money, and agents, we're shaping the future of work so teams can reach their potential and focus on what matters most. The minute you join, you'll feel it. Not just in the products we build, but in how we show up for each other. Our culture is rooted in integrity, empathy, and shared enthusiasm. We're in this together, tackling big challenges with bold ideas and genuine care. We look for curious minds and courageous collaborators who bring sun-drenched optimism and drive. Whether you're building smarter solutions, supporting customers, or creating a space where everyone belongs, you'll do meaningful work with Workmates who've got your back. In return, we'll give you the trust to take risks, the tools to grow, the skills to develop and the support of a company invested in you for the long haul. So, if you want to inspire a brighter work day for everyone, including yourself, you've found a match in Workday, and we hope to be a match for you too.About the RoleAs 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.You will 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.).You will 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).If and as needed, you will 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.We will rely on you to 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.You will help establish repeatable migration patterns (a "playbook") so future acquisition onboarding is faster than the first.You will 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.This role involves collaborating with teams across multiple locations and time zones. You will need to be adept at communicating effectively and building strong relationships with colleagues in diverse locations.About YouYou're a senior engineer who has done cloud migration work before, not just designed it on a whiteboard. You've moved real services between clouds or onto an internal platform, hit the messy parts (stateful data, IAM rewiring, DNS, secrets, certificate pinning, undocumented dependencies), and shipped the migration to completion.Basic Qualification7+ 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.Other QualificationStrong, 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.Additional Preferred Skills: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.