Work / 03 / 05Parking OperationsMicroservices
QA transformation
Lead QA Engineer · QA Transformation
I led QA on the core project of Europe's largest parking operator, a microservices platform. I set the test strategy, processes, test stages and definition of done, and built and led the QA team working inside the delivery pipeline.
- Role
- Lead
- Architecture
- Microservices
- QA team
- Led
Overview
The client is Europe’s largest parking operator. They were scaling a core platform built as microservices and needed QA to scale with it. I joined as Lead QA Engineer on the core project and was responsible for how quality was handled across the delivery pipeline.
What I owned
- The QA strategy: processes, test stages and which types of testing happen in each phase
- QA in continuous delivery, which matters a lot with microservices because each service ships on its own schedule and the tests have to keep up
- The QA team: I hired and led it, gave out work based on experience, and mentored where needed
- Definition of done for each development stage, agreed together with development and project management
- Worked with development and project management leads to set the quality bar for client deliverables
Stack
Most services were C# on .NET, with some JavaScript and Java. Testing covered UI (Selenium, Puppeteer), APIs (Postman and custom clients) and contract-level checks.
Looking back
Testing microservices with a monolith-style approach doesn’t work, because running everything end to end gets too slow, but you still need quality gates. Most of my work there was deciding which test layers to invest in first and in what order.