At a Glance
- Tasks: Lead the charge on performance and reliability for critical platforms handling over €1 billion in revenue.
- Company: Bauer Media Outdoor, a pioneer in reshaping Out-of-Home advertising across Europe.
- Benefits: Competitive salary, dynamic work environment, and opportunities for professional growth.
- Why this job: Make a real impact on high-stakes projects while working with cutting-edge technology.
- Qualifications: Expertise in full stack engineering and strong AWS knowledge required.
- Other info: Join a modernisation programme with a focus on innovation and excellence.
The predicted salary is between 48000 - 72000 £ per year.
About Us
Bauer Media Outdoor is reshaping Out-of-Home advertising across Europe. Our network spans thousands of DOOH screens, data-driven delivery systems, and enterprise platforms that power scheduling, booking, content delivery, and performance reporting at scale. We are in the middle of a modernisation programme with new products, new infrastructure, and a reinforced engineering discipline. You will be part of a team raising the bar on reliability, observability, and non-functional excellence across our platforms.
The Role
You will be the technical lead for non-functional requirements across one of our most critical internal platforms. The system will ultimately be handling over €1 billion of revenue, supporting millions of transactions a day, enabling both internal and external customers, hence needs to do this without degrading performance or stability.
Your remit covers performance front end and back end engineering, architecture and design, reliability, resilience, observability, and capacity planning. Much of our estate runs on AWS, so you will bring strong cloud awareness and understand how architectural choices influence throughput, latency, cost, and scaling behaviour. This is hands-on work. You will define the NFRs, test them, break them, and enforce them, as well as working with architects and other lead engineers on ensuring architectures and designs meet these requirements.
Key Responsibilities
- Performance, Scalability & NFR Definition
- Define, document, and own non-functional requirements across areas such as performance, availability, reliability, scalability, observability, cost and security constraints.
- Build and execute performance, load, stress, concurrency, and soak tests shaped by the NFRs you set.
- Establish SLOs, SLAs, and SLIs that reflect real user demand and business outcomes.
- Model expected load and determine capacity baselines.
- Translate business workflows into measurable system behaviours: throughput, response time, peak concurrency, degradation thresholds.
- Quality Engineering & Observability
- Implement qualitative and quantitative testing patterns that validate each NFR.
- Strengthen observability using AWS CloudWatch, X-Ray, metrics, logs, distributed tracing, and event correlation.
- Define what “healthy” means for the platform and establish mechanisms to detect and predict deviation.
- Cloud, Architecture & Collaboration
- Influence architectural decisions and designs using evidence from performance modelling and NFR constraints including inputting into UX and front end design to align the customer experience with the reality of the product.
- Validate AWS scaling policies, resource limits, timeouts, and data access patterns.
- Provide clear, data-backed recommendations that highlight trade-offs between cost, performance, and reliability.
What We’re Looking For
- Expertise in full stack engineering, performance engineering, non-functional testing, and reliability engineering.
- Strong understanding of NFR categories: performance, availability, reliability, resilience, capacity, security constraints, operability, cost and maintainability.
- Solid knowledge of AWS architecture and how NFRs translate into cloud scaling behaviour, resource use, and service limits.
- Hands-on experience with performance tools: JMeter, Gatling, Locust, k6, or similar.
- Ability to diagnose bottlenecks across user experience, front end, application logic, APIs, databases, cloud infrastructure, and distributed systems.
- Someone who challenges assumptions early, brings evidence, and insists on technical rigour.
- Related environment maintenance, awareness and impact outcomes.
What Success Looks Like
- 3 Months
- NFRs are fully defined, documented, and agreed across engineering, product, and architecture.
- Performance baselines, SLOs, and capacity thresholds exist for all key workflows.
- Early bottlenecks across the AWS estate and application layers are identified with evidence.
- Initial performance test coverage and observability improvements are underway.
- 6 Months
- A stable, automated NFR validation framework is integrated into CI/CD pipelines.
- The platform handles expected load with predictable resource usage and minimal degradation.
- Dashboards expose real-time performance, concurrency behaviour, and NFR compliance.
- Engineers and product teams regularly use your insights to make architectural choices.
- 12 Months
- The system consistently meets or exceeds all core NFRs under real and peak load.
- Performance testing, resilience testing, and observability practices are fully embedded into delivery.
- AWS scaling behaviour is tuned, predictable, and cost-efficient.
- The platform supports 300+ concurrent users and multi-process workloads without instability.
- You are recognised internally as the authority on system performance, reliability, and non-functional rigour.
Lead Engineer (Performance and Reliability) in London employer: Bauer Media Outdoor
Contact Detail:
Bauer Media Outdoor Recruiting Team
StudySmarter Expert Advice 🤫
We think this is how you could land Lead Engineer (Performance and Reliability) in London
✨Tip Number 1
Network, network, network! Get out there and connect with people in the industry. Attend meetups, webinars, or even just grab a coffee with someone who works at Bauer Media Outdoor. Building relationships can often lead to job opportunities that aren’t even advertised.
✨Tip Number 2
Show off your skills! Create a portfolio or GitHub repository showcasing your projects, especially those related to performance engineering and AWS. When you apply through our website, include links to your work so we can see what you’re capable of.
✨Tip Number 3
Prepare for technical interviews by brushing up on your knowledge of non-functional requirements and performance testing tools like JMeter or Gatling. We want to see how you think and solve problems, so practice explaining your thought process clearly.
✨Tip Number 4
Don’t forget to follow up after interviews! A quick thank-you email can go a long way in showing your enthusiasm for the role. Plus, it keeps you fresh in our minds as we make decisions.
We think you need these skills to ace Lead Engineer (Performance and Reliability) in London
Some tips for your application 🫡
Show Your Technical Skills: Make sure to highlight your expertise in full stack engineering and performance testing. We want to see how your skills align with our needs, especially around non-functional requirements and AWS architecture.
Be Specific About Your Experience: When detailing your past roles, focus on specific projects where you defined and implemented NFRs. We love concrete examples that showcase your hands-on experience with performance tools like JMeter or Gatling.
Tailor Your Application: Don’t just send a generic CV! Tailor your application to reflect the key responsibilities and requirements from the job description. Show us how you can contribute to our modernisation programme and enhance reliability across our platforms.
Apply Through Our Website: We encourage you to apply directly through our website. It’s the best way for us to receive your application and ensures you’re considered for this exciting opportunity at Bauer Media Outdoor!
How to prepare for a job interview at Bauer Media Outdoor
✨Know Your NFRs
Make sure you have a solid understanding of non-functional requirements (NFRs) like performance, reliability, and scalability. Be ready to discuss how you've defined and implemented these in past projects, especially in cloud environments like AWS.
✨Showcase Your Hands-On Experience
Prepare to share specific examples of your hands-on work with performance tools such as JMeter or Gatling. Highlight any challenges you faced and how you overcame them, particularly in relation to diagnosing bottlenecks and improving system performance.
✨Demonstrate Your Cloud Knowledge
Familiarise yourself with AWS architecture and be prepared to discuss how architectural choices impact performance and cost. Bring examples of how you've influenced design decisions based on performance modelling and NFR constraints.
✨Be Ready for Technical Rigour
Expect to be challenged on your assumptions and methodologies. Prepare to back up your recommendations with data and evidence, showcasing your commitment to technical rigour and quality engineering practices.