At a Glance
- Tasks: Lead the charge in defining and testing non-functional requirements for critical platforms.
- Company: Join Bauer Media Outdoor, a leader in reshaping Out-of-Home advertising across Europe.
- Benefits: Competitive salary, flexible working options, and opportunities for professional growth.
- Why this job: Make a real impact on high-stakes systems handling over €1 billion in revenue.
- Qualifications: Expertise in full stack engineering and performance testing, especially with AWS.
- Other info: Dynamic team environment focused on innovation and excellence.
The predicted salary is between 36000 - 60000 £ 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 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 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. This gives potential employers a tangible way to see what you can do and how you approach problem-solving.
✨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. Practice explaining your thought process clearly, as communication is key when discussing complex engineering concepts.
✨Tip Number 4
Don’t forget to apply through our website! It’s the best way to ensure your application gets seen by the right people. Plus, it shows you’re genuinely interested in joining the team at Bauer Media Outdoor.
We think you need these skills to ace Lead Engineer 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, so don’t hold back on showcasing your experience with tools like JMeter or AWS!
Define Your NFR Approach: Since this role is all about non-functional requirements, explain how you would define and document these for our platforms. Share any past experiences where you’ve successfully implemented NFRs and the impact it had.
Be Hands-On: We love a hands-on approach! In your application, mention specific projects where you’ve been involved in performance engineering and how you tackled challenges. This will show us you’re ready to dive right in.
Apply Through Our Website: Don’t forget to apply through our website! It’s the best way for us to keep track of your application and ensure it gets the attention it deserves. We can’t wait to hear from you!
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) and how they apply to the role. Be ready to discuss specific examples of how you've defined, documented, and tested NFRs in your previous projects.
✨Showcase Your AWS Expertise
Since much of the work involves AWS, brush up on your knowledge of AWS architecture and scaling behaviours. Prepare to explain how architectural choices impact performance and cost, and be ready to share any hands-on experience you have with AWS tools.
✨Demonstrate Performance Engineering Skills
Familiarise yourself with performance testing tools like JMeter or Gatling. Be prepared to discuss how you've used these tools to identify bottlenecks and improve system performance in past roles.
✨Prepare for Technical Challenges
Expect to face technical questions that challenge your assumptions. Bring evidence from your past experiences to back up your answers, and don't shy away from discussing trade-offs between cost, performance, and reliability.