Software Development Engineer, Amazon

• Experience in AWS services
• Bachelor's degree or above in computer science, computer engineering, or related field
• 5+ years of professional software development or platform engineering experience
• 3+ years of hands-on experience administering and operating CI/CD platforms (Jenkins, GitLab, or similar) at scale
• 2+ years of experience with code review systems (Gerrit, GitLab, or GitHub Enterprise)
• 2+ years of experience with infrastructure as code (CDK or CloudFormation)
• Proficiency in Python, Bash, and at least one of: Groovy, Go, or TypeScript
• Experience with Linux systems administration and networking fundamentals

Desirable

• We're seeking a Software Development Engineer to architect, build, and operate the CI/CD platforms that accelerate silicon development at Annapurna Labs
• In this role, you'll own Jenkins, Gerrit, and GitLab as highly available, scalable services—enabling hundreds of chip design and verification engineers to build, test, and integrate their work with speed and confidence
• You'll treat these platforms as products: self-service, observable, resilient, and continuously improving
• You will design and operate CI/CD platforms at scale—multi-controller Jenkins with Configuration as Code, Gerrit with high-availability replication, and self-managed GitLab with autoscaling runners
• You'll build these as a service: self-service onboarding for new teams, multi-tenancy with resource isolation, shared pipeline libraries, and automated agent provisioning
• You'll deploy and manage all CI/CD infrastructure using AWS CDK, utilize Spot strategies for cost-efficient build farms, and architect for high availability with automated failover and disaster recovery
• You will build comprehensive observability into every layer—pipeline health dashboards, build time Service Level Objectives (SLOs), queue depth alerting, and resource utilization metrics—giving both your team and your customers real-time visibility into platform performance
• You'll establish incident response processes, conduct capacity planning, and proactively identify bottlenecks before they impact developer productivity
• You'll continuously evaluate new capabilities (Jenkins Kubernetes operators, GitLab Geo replication, pipeline-as-trace with OpenTelemetry) and drive adoption of best practices across the engineering organization
• You might start your day reviewing pipeline health dashboards—checking build queue depths, agent utilization, and job success rates across Jenkins controllers
• Mid-morning, you could be deploying a Gerrit configuration change through your CI/CD pipeline (yes, CI/CD for CI/CD), validating replication health across sites, and then pairing with a design team to onboard their new project into the shared pipeline framework
• In the afternoon, you might be implementing autoscaling policies for GitLab runners to handle a surge in verification regressions, debugging a flaky Jenkins shared library, or building a new self-service interface that lets teams provision isolated build environments without filing a ticket
• You'll balance immediate customer needs—unblocking a team whose builds are queued behind capacity constraints—with longer-term platform investments like migrating to Jenkins Configuration as Code or implementing pipeline observability with distributed tracing