Backend testing doesn’t get much visibility, but it plays one of the most important roles in any system. If the backend isn’t working as expected, everything else tends to fall apart—no matter how polished the frontend looks. That’s why backend testing needs to focus on the things that matter most: integration between services, reliable data validation, and strong contract testing to keep everything connected and consistent behind the scenes.

​

My main languages for backend work are Java and Python, and over the past few years, these have been my playground.

​

At Aviva, I worked on testing microservices and REST APIs that powered key calculation engines. These systems were used to generate financial reports submitted to regulators, so we focused heavily on correctness, reliability, and traceability. As part of that work, we also supported a large migration from a legacy platform to AWS. This gave the company greater control over infrastructure, improved performance, and enabled more modern, cloud-native testing and deployment workflows.

​

At CreateFuture, I contributed to a FanDuel project built around event-driven architecture, where AWS Lambdas passed messages between services. I set up contract testing using PactFlow, writing contracts in both Java and Python to ensure that services could evolve independently without breaking communication. It was a key part of making the system scalable and stable.

​

Most recently, I was part of the ingestion team at Evoke, working on a trading platform where Kafka played a key role. We processed pricing data from external suppliers, and backend testing focused on validating data formats, ensuring message integrity, and making sure the data was accurate and reliable for downstream trading systems.

​

Across all of these projects, backend testing has been fully integrated into CI/CD pipelines, giving fast feedback and supporting continuous delivery across environments.