Senior Software Engineer, Java

About the role

This role owns the design and scaling of resilient back-end systems that power core financial operations. Collaboration with Product, Risk, Compliance, and Finance shapes secure and compliant services for a global user base. The position drives critical infrastructure for digital asset investing at scale.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

• Degree required.

What you'll do

These services form the foundation of secure and reliable financial operations for customers across Europe.

This practice safeguards platform stability and supports continuous feature delivery.

The work directly affects customer experience during high-volume trading and market events.

This effort ensures the platform remains competitive and technically modern.

Mentorship strengthens code quality and delivery speed across the engineering organization.

Requirements

The posting states a bachelor's degree requirement.

Demonstrate advanced hands-on experience with modern Java frameworks, using Java as the primary language. Mastery of these frameworks enables robust and efficient service implementation.

• Show expertise in relational and non-relational databases, with preference for Postgres and MongoDB experience. This skill ensures data integrity and performance across diverse storage needs.
• Prove ability to create, scale, and maintain public REST APIs with a focus on performance optimization. Well-designed APIs enable seamless integration and reliable user experiences.
• Apply practical knowledge of message-oriented middleware such as Apache Kafka or ZeroMQ for event-driven microservices. This knowledge supports resilient and decoupled system architectures.
• Bring familiarity with CI/CD pipelines, favoring AWS and Kubernetes backgrounds while welcoming experience across major public cloud providers. Automation of deployments reduces risk and accelerates releases.

Practical notes

Early application allows evaluation and alignment without immediate deadline pressure, with fast-tracking when a headcount is approved. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Backend engineering in financial technology relies on robust Java services, event-driven messaging, and scalable data stores. Modern development practices emphasize automated testing, cloud-native infrastructure, and continuous learning. Cross-functional collaboration with product, risk, and compliance teams is common in regulated environments.

Questions to ask

Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.