Principal Engineer I — Prepurchase Platform

Principal Engineer I — Prepurchase Platform

Full-Time 63000 - 77000 £ / year (est.) No working from home possible
Ticketmaster UK Limited

At a Glance

  • Tasks: Build high-availability systems and solve complex problems in a dynamic environment.
  • Company: Join Ticketmaster UK, a leader in event technology with a collaborative culture.
  • Benefits: Enjoy competitive salary, health benefits, and opportunities for remote work.
  • Other info: Be part of an inclusive team that values diversity and personal growth.
  • Why this job: Make a real impact on fan experiences while working with cutting-edge technologies.
  • Qualifications: Strong coding skills in Java and experience with high-traffic systems required.

The predicted salary is between 63000 - 77000 £ per year.

  • Job Summary
  • Principal Engineer I, Prepurchase Platform
  • Division: Ticketmaster UK Limited
  • Line Manager: VP Engineering, Accounts, Identity and Pre-purchase
  • Contract Terms: Full-time permanent, 40 hours per week
  • Team Overview

The Prepurchase Platform group owns backend services that power every fan's path to a ticket, handling event discovery, real‑time seat availability, and interactive venue experiences at massive scale.

Engineers build fast, resilient, and highly available systems capable of processing billions of API calls during peak on‑sales.

Role Overview

As a Principal Engineer, you will write code, build systems, and solve complex problems hands‑on.

You will reason carefully about distributed‑systems trade‑offs, lead platform modernization efforts, design event‑driven architectures, and maintain high‑reliability during high‑demand on‑sales, collaborating across multiple teams within the Prepurchase domain.

Responsibilities

  • Identify and act on production problems without prompting; treat any single 500 error reaching a fan as a problem to solve urgently.
  • Build end‑to‑end, high‑availability systems that handle extreme traffic spikes during high‑demand on‑sales without degradation.
  • Lead platform modernization initiatives migrating legacy services to cloud‑native, microservice‑based architectures.
  • Design and implement streaming and event‑driven solutions using Kafka/g RPC to enable real‑time data flow across services.
  • Embed deeply in specific service areas or work horizontally across teams to solve cross‑cutting problems.
  • Champion resilience patterns such as circuit breakers, graceful degradation, bulkheads, and auto‑scaling strategies.
  • Collaborate with the Enterprise Architecture team on architectural decisions and evolve engineering standards across the Prepurchase domain.
  • Partner with product, security, and SRE teams to align technical decisions with business priorities.
  • Drive observability improvements, instrument services for monitoring, alerting, and rapid incident response.
  • Identify and eliminate single points of failure, improving reliability and reducing on‑call burden.
  • Apply AI and machine‑learning tools to improve developer productivity, automate operational tasks, and enhance system capabilities.
  • Evaluate and introduce new technologies that improve performance, reliability, or engineering velocity.
  • Technical Skills
  • Proven ability to reason about distributed‑systems trade‑offs in scalability, consistency, availability, latency, and design defensible solutions under real constraints.
  • Strong experience writing production code and building high‑traffic systems at scale.
  • Expertise in Java (17+) and JVM internals, garbage collection, and performance tuning under load. Kotlin experience is a plus.
  • Hands‑on experience with a reactive, non‑blocking framework (Vert. x, Spring Web Flux, or equivalent) and asynchronous event‑driven service design.
  • Deep experience with stream processing and event‑driven architecture – Kafka Streams, Apache Flink, or equivalent – including stateful streaming, topology design, and managing local state stores (e. g.

Rocks DB) at scale.

  • Strong command of g RPC (including streaming RPC) and binary serialization formats such as Flat Buffers, Avro, or Protobuf with schema evolution via a registry.
  • Familiarity with Data‑Oriented Design for cache‑efficient code and efficient in‑memory state representation.
  • Experience with compact, search‑oriented data structures (e. g. Roaring Bitmap, succinct/bitset representations) for large in‑memory state.
  • Optional: Search engines (Elasticsearch, Solr) for discovery workloads, microservice design, service mesh (Istio/Envoy), API contract evolution, and backend‑for‑frontend patterns including Graph QL APIs and Web Socket subscriptions.
  • Hands‑on experience with AWS (EKS) and cloud‑native operations – Docker, Kubernetes, Helm, Kustomize, Terraform.
  • Proficiency with caching strategies (Redis, CDN caching) and high‑traffic systems.
  • Solid understanding of CI/CD pipelines (Git Lab CI) and progressive deployment strategies (blue‑green, canary).
  • Experience designing for high availability – multi‑region active‑active/active‑passive architectures, failover strategies, disaster recovery, and resilience under abuse.
  • Proficiency with AI/ML tools and techniques – using LLMs, AI‑assisted development, and automation to accelerate engineering workflows.
  • Familiarity with observability tooling: Grafana, Splunk, Prometheus, Open Tracing, or equivalent.
  • Strong understanding of security best practices – OAuth/OIDC, input validation, secrets management.
  • Track record of leading technical initiatives across multiple teams without direct authority.
  • Behavioural Skills
  • Systems Thinking – understand distributed systems as a set of trade‑offs, recognize failures emerging from system interactions and missing feedback loops.
  • Technical Vision – anticipate platform challenges and design systems that scale ahead of demand.
  • Domain Depth – invest effort in understanding systems fully before changing them, including history and constraints.
  • Ownership – take end‑to‑end responsibility for system health, performance, and reliability across the Prepurchase domain.
  • Influence Without Authority – drive architectural decisions and engineering standards through collaboration, not hierarchy.
  • Communication – explain complex technical trade‑offs clearly to peers and non‑technical stakeholders.
  • Composure Under Pressure – remain calm during high‑severity incidents and high‑demand on‑sales, delivering clear resolutions.
  • Continuous Improvement – identify opportunities to modernise, simplify, and strengthen systems and follow through.
  • Equal Opportunity Statement

We are passionate and committed to our people and go beyond the rhetoric of diversity and inclusion.

You will be working in an inclusive environment and be encouraged to bring your whole self to work.

We will help you balance work and home life, support your professional and personal aspirations, and provide equal opportunities irrespective of gender, race, sexual orientation, religion, age, disability status or caring responsibilities.

#J-18808-Ljbffr

Principal Engineer I — Prepurchase Platform employer: Ticketmaster UK Limited

At Ticketmaster, we pride ourselves on fostering a vibrant and inclusive work culture that champions teamwork, integrity, and belonging. As a Principal Engineer I in London, you'll have the opportunity to work on cutting-edge technologies in a dynamic environment, driving innovation while collaborating with passionate teams dedicated to enhancing live event experiences. With a commitment to employee growth and a focus on work-life balance, we empower our engineers to thrive both personally and professionally.

Ticketmaster UK Limited

Contact Details:

Ticketmaster UK Limited Recruitment Team

StudySmarter Expert Advice🤫

We think this is how you could land Principal Engineer I — Prepurchase Platform

Join Local Tech Meetups

Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at Ticketmaster UK Limited or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!

Contribute to Open Source Projects

Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to Ticketmaster UK Limited.

Tap into Online Developer Communities

Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like Ticketmaster UK Limited.

Explore Job Boards Specifically for Tech Roles

Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like Ticketmaster UK Limited that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!

We think you need these skills to ace Principal Engineer I — Prepurchase Platform

Distributed Systems Design
Java (17+)
JVM Internals
Performance Tuning
Reactive Frameworks (Vert.x, Spring WebFlux)
Event-Driven Architecture (Kafka, Apache Flink)
gRPC

Some tips for your application 🫡

Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.

Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at Ticketmaster UK Limited.

Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Ticketmaster UK Limited and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!

Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!

How to prepare for a job interview at Ticketmaster UK Limited

Brush Up on Your Coding Skills

For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.

Know Your Tools and Frameworks

Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If Ticketmaster UK Limited uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.

Showcase Your Projects

Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.

Prepare for Behavioural Questions

While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.