Platform Engineer

Ticketek Entertainment Group (TEG) is a Live Experience Group that helps people discover, access and experience the unforgettable. We believe Life is better live®.

With over 50 years in live entertainment, we sell more than 30 million tickets annually, connect with 30 million fans across Australia and New Zealand, and bring 18,000+ events to life each year. Headquartered in Sydney, we operate globally across eight pillars: Ticketing, Live Touring, Sport, Immersive Experiences, Customer & Data Solutions, Venues, VIP Experiences and Partnerships. Through our integrated operating model, we bring the best live content, ticketing and technology to our partners and create unforgettable memories that last a lifetime

Our values guide everything we do: we partner with purpose, empower boldness within clear boundaries, and celebrate human connection – always putting the fan first.

The Role

As a Platform Engineer with TEG, you'll join a hands-on team of 4-6 engineers driving a CI/CD modernisation program that decouples 254 deployment pipelines from a legacy monolithic deployment system into self-contained, per-repo pipelines with canary deployments, automated rollback and smoke tests across a multi-region AWS environment.

Working alongside the Lead Platform Engineer, you'll migrate services to modern GitLab CI pipelines against an agreed Pipeline Construction Standard, helping deliver the deployment experience for ~250 active repositories across Lambda, ECS Fargate, ECS Windows, EC2 and S3/CloudFront compute types, spanning 4 production regions.

Requirements

Outcomes to Deliver

In this role, success looks like:

• Pipeline Engineering & Delivery: Build and ship CI/CD pipelines in GitLab CI, service by service, implementing CodeDeploy canary deployments, multi-region orchestration with manual gates, automated rollback on CloudWatch alarms and smoke tests.
• Service Migration: Migrate each service from the legacy deployment system onto these self-contained, per-repo pipelines — running old and new in parallel for zero-risk cutover, validating against live production traffic, and confirming the service is healthy before moving on to the next.
• Pre-Migration Audit: Complete a pre-migration audit for every service before touching its pipeline, identifying what to keep, redesign or remove so dangerous patterns from the legacy templates aren't carried forward.
• Technical Execution: Make pragmatic, well-scoped engineering decisions within the agreed architecture and Pipeline Construction Standard, favouring the simple pipeline that works over unnecessary abstraction, and raise any proposed deviations with the Lead rather than solving them in isolation.