Lead Engineer, Software Engineer

Job Summary

JOB TITLE: Lead Software Engineer, Kubernetes

Location: Remote, US

Division: Tech Ops

Line Manager: Manager, Kubernetes

Contract

Terms:

Permanent

The Kubernetes Team is part of the larger Ticketmaster Techops Division, and Infrastructure segment. Our team spans North America and Europe, running Kubernetes and Container systems across NA, EMEA and APAC regions, supporting 30K+ unique deployments. We have coverage in 5 timezones, and this role is aimed at an engineer who loves to automate, and improve processes that help global entry and onsales succeed.

Our team owns both the core deployment of Kubernetes, as well as ~60 supporting apps, and is undergoing a migration to EKS Hybrid Clusters, to span AWS and OnPrem Datacenters. You’ll join an oncall team of Principal and Senior engineers in ensuring secure, reliable and scalable systems are always online.

• Design and implement backend systems that abstract infrastructure concerns and enable self-service capabilities, focused on integration inside of Kubernetes
• Develop and support internal tools, APIs, and automation frameworks used by infrastructure and application teams
• Implement enhancements to CI/CD pipelines using Git Lab, focusing on security, repeatability, and observability
• Write clean, testable, and well-documented code that serves as an example for the team

• Contribute to backend architectures and patterns that scale across infrastructure domains
• Create design documents, system diagrams, and proof-of-concepts for your projects
• Leverage Kubernetes and infrastructure-as-code tools to deliver reusable software components and automation services
• Collaborate with Principal Engineers on architectural decisions and implementation approaches
• Understanding of Linux and Networking around TCP/IP around the scale of our network

• Partner with team leads to deliver on platform modernization initiatives
• Share knowledge and best practices with team members
• Provide technical guidance to junior engineers and participate in code reviews

• Build backend systems primarily in Go, Rust, or Python, focusing on maintainable, testable, and observable code
• Develop CLI tools, APIs, and services that improve the developer experience
• Use Terraform to integrate with existing infrastructure components
• Apply software engineering best practices to infrastructure automation, including testing and observability
• Work in an Agile environment (SAFe) with scoped work in Jira, delivering on sprint commitments
• Implement security controls and compliance requirements through automation
• Support critical issues as part of the team rotation, with focus on building systems that minimize operational burden
• Ability to troubleshoot real time and historical issues, with an eye towards long term solutions

• Strong experience as a backend or platform software engineer, with exposure to developer tooling or infrastructure automation
• Previous experience as a Kubernetes Admin, or Power User deploying distributed applications to clusters
• Solid programming proficiency in at least one of:
  Go, Rust, or Python, with willingness to learn others
• Experience building internal APIs, automation tools, or platform services
• Working knowledge of Git Lab CI/CD, and infrastructure-as-code tools like Terraform, Pulumi, or Ansible
• Understanding of observability and monitoring principles (e.g., Prometheus, Grafana)
• Good grasp of infrastructure concepts with a software engineering approach—this is not an operations or SRE role
• Experience working in Agile environments and comfortable with remote collaboration
• Nice to have:
  Certified Kubernetes Application Developer (CKAD) or Certified Kubernetes Administrator (CKA)

• Detail-oriented problem solver with strong analytical and debugging skills
• Self-motivated and comfortable working independently while knowing when to seek guidance
• Passionate about software craftsmanship, clean code, and continuous learning
• Clear technical communicator who can explain complex concepts to both technical and non-technical stakeholders
• Focu…