Senior Engineer, Risk Engineering

About the role

Senior Engineer, Risk Engineering at Bullish will design and maintain the high‑performance computational backbone that protects the exchange’s trading operations. The role bridges quantitative finance and systems engineering, focusing on low‑latency JVM services that calculate margin, stress scenarios and portfolio exposures in real time.

Key responsibilities

• Develop and maintain scalable, low‑latency JVM services and APIs with rigorous memory‑management and performance tuning.
• Translate complex risk models into robust, well‑tested code in close collaboration with senior technical leadership.
• Work with quantitative analysts and product teams to implement reliable solutions for financial products and risk calculations.
• Continuously refactor and optimise the existing codebase to improve automated testing, performance and maintainability.
• Write clean, documented code, participate in code reviews and champion agile best practices.

Required profile

• 5+ years of professional experience as a Java backend engineer.
• Strong sense of ownership and ability to thrive in a fast‑moving startup environment.
• Advanced proficiency in Java, multi‑threading, concurrency and JVM performance tuning.
• Hands‑on experience with automated testing, unit/integration testing and test‑driven development.
• Familiarity with Agile methodologies, design patterns, DRY principles and microservices architecture.
• Experience with modern DevOps tools such as Git, Docker, Kubernetes and cloud platforms (GCP preferred).
• Foundational understanding of financial products, risk management concepts (e.g., SPAN, VaR) and strong analytical skills.
• Bachelor’s degree in Computer Science, Engineering or a related technical field.

Required skills

• Java
• Multi‑threading and concurrency
• JVM performance tuning
• Unit and integration testing, TDD
• Microservices architecture
• Git, Docker, Kubernetes
• Google Cloud Platform (GCP)
• Kotlin (nice to have)
• Chronicle Queue (nice to have)
• Event‑sourced architectures, columnar databases (nice to have)