Job Opportunities API

The Public Ledger of Openings

← Back to the ledger

Lead Platform Engineer-12 month fixed term contract

Ticketek Entertainment Group
CompanyTicketek Entertainment Group
CategoryUncategorised
LocationSydney
RemoteOn-site (inferred)
EmploymentNot stated
LevelNot stated
SalaryNot stated by the employer
Posted29 Jul 2026
Last verified2 Aug 2026
SourceEmployer ATS (workable)
Applications are handled by the employer, not by us.Apply on the employer's site →
Description
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 20 million tickets annually, connect with 14 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 You'll join Ovation, TEG's digital business, within a Technology team of motivated, ambitious IT professionals driving an integration-led innovation strategy. As Lead Platform Engineer, you'll drive a CI/CD modernisation program that decouples 254 deployment pipelines from a legacy monolithic system into self-contained, per-repo pipelines with canary deployments, automated rollback and smoke tests across a multi-region AWS environment. This is a hands-on leadership role: you'll set technical direction for a small team of platform engineers and personally build pipelines alongside them, owning the deployment experience for ~170 actively deploying services across Lambda, ECS Fargate, ECS Windows, EC2 and S3/CloudFront. Requirements Outcomes to Deliver In this role, success looks like: Program Delivery & Execution: Own the CI/CD modernisation program end-to-end, driving systematic migration of services from the legacy deployment system to self-contained pipelines, and delivering on a 16-week roadmap with a small team. Hands-On Pipeline Engineering: Personally build and ship CI/CD pipelines in GitLab CI, implementing CodeDeploy canary deployments, multi-region orchestration with manual gates, automated rollback on CloudWatch alarms, and smoke tests – leading by example. Team Leadership & Development: Lead, mentor and grow a small team of platform engineers – managing workload distribution, running standups, conducting performance conversations, and setting the standard for how the team operates. Platform Evolution: Once migration proves what's shared vs what varies across services, design and build the next layer – shared GitLab CI templates, CDK construct libraries for new services, and self-service tooling that lets development teams provision and deploy independently. Capabilities to Bring Delivery Leadership: a track record leading a small engineering team with delivery accountability against deadlines, having driven a migration or modernisation program in a live production environment, comfortable operating in a hands-on/leadership split. Technical Mastery: deep experience with GitLab CI/CD (multi-stage pipelines, environments, manual gates, shared templates, self-hosted runners), AWS CodeDeploy canary/blue-green deployments with automated rollback on CloudWatch alarms, and multi-region orchestration across Lambda, ECS/Fargate and EC2. Pragmatic Judgement: solid working knowledge of IAM cross-account roles, CloudFormation and SSM Parameter Store, strong shell scripting and AWS CLI fluency, and the judgement to choose the simple solution that works over unnecessary abstraction. Desirable Skills & Experience AWS CDK (TypeScript or Python) for self-service construct libraries Experience migrating away from legacy CI/CD systems (parallel running, flag-based cutover) .NET build pipelines (dotnet publish, zip packaging — not writing app code) DORA metrics and deployment frequency observability Developer experience design — self-service tooling, repo templates, internal platform thinking AW