Haroon Khan is a Senior Software Engineer based in London with 11 years of experience building low-latency, event-driven systems and microservices for financial services. He specializes in Core Java, reactive stacks (Spring WebFlux), and streaming architectures using Apache Kafka and Apache Flink to deliver real-time monitoring, trade clearing and risk solutions. Comfortable across the full delivery lifecycle, he practices TDD/BDD, implements resilient retry strategies, and deploys containerized services to AWS and Azure Kubernetes environments. His background includes deep domain knowledge of FIX/FIXML and ISO20022 standards and hands-on work with Elasticsearch, in-memory grids and regulatory reporting systems. An active contributor to Baeldung’s Scala tutorials and Spring Boot examples, he focuses on refactoring for maintainability and adding robust retry patterns in reactive apps. Known for turning complex, high-throughput requirements into pragmatic, well-tested solutions, he blends engineering rigor with a keen eye for system organization.
10 years of coding experience
13 years of employment as a software developer
BSc, Computer Science, BSc, Computer Science at Brunel University London
Contributions:12 reviews, 149 commits, 137 PRs in 1 year 8 months
Contributions summary:Haroon's commits focused on implementing and improving retry mechanisms within a Spring WebFlux application. The user implemented retry strategies, including backoff and fixed delay approaches, and added methods to show different retry strategies within the application. The user also included unit and integration tests to validate these functionalities.
Supporting code for the tutorials on https://www.baeldung.com/scala
Role in this project:
Back-end Developer
Contributions:1 review, 6 commits, 5 PRs in 1 month
Contributions summary:Haroon primarily focused on refactoring and modularizing the Scala code within the repository. Their contributions included splitting existing modules into smaller, more manageable units, such as scala-core and scala-core-2. These changes involved significant code reorganization, including the creation of new files and restructuring of existing ones, demonstrating a focus on code maintainability and project organization, as well as splitting out additional scala modules. Additionally, the user's work extended to test file modifications and the addition of new modules, further structuring and expanding the project's codebase.
sbtscalascala3
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.