Software Engineer - Fintech (L1)

Katanox; Amsterdam; On-site; EUR 35,000 - 55,000; Full time

Job summary

Katanox is seeking an early-career Software Engineer for the Techuity team in Amsterdam to join a finance-focused domain. You will pair with senior engineers, own small pieces end-to-end, and grow into owning a service.

The role emphasizes correctness, data integrity, and operational excellence, with on-site collaboration across hubs in Amsterdam, London, and New York. English fluency is required.

Qualifications

• Around zero to two years of professional experience, or a strong internship and side-project record.
• Solid fundamentals: data structures, algorithms, testing, and enough system design to reason about a service boundary.
• Working knowledge of Kotlin or Java, or another typed language and a clear interest in Kotlin.

Responsibilities

• Build and extend finance-related Kotlin/Java services with tests and code review.
• Work on event-driven flows where reservations become payments and accounting entries.
• Own services in production: trace, fix, and add checks to prevent recurrence.

Skills

Kotlin

Java

Data structures

Algorithms

Testing

System design

English fluency

Education

Degree welcome but not required

Job description

We are hiring an early-career Software Engineer for the Techuity team in our Amsterdam hub.

About Katanox

Katanox is building the infrastructure layer for hospitality: software that connects hotels and travel buyers and moves money between them. Our platform brings distribution and payments into one workflow (contracting, connectivity, reconciliation, and settlement), so partners can operate with less fragmentation and fewer manual handoffs.

For engineers, this means building reliable systems that handle complex B2B workflows and real financial constraints, with a focus on data integrity, auditability, security, and operational excellence. We're headquartered in Amsterdam with hubs in London and New York.

About the role

You’ll join the Techuity team, which owns the finance domain at Katanox: the systems that work out who gets paid what, move the money, and prove afterward that it was done correctly. Every reservation on the platform becomes a set of accounting entries, a fee, a payout to a hotel, and a record an auditor or a regulator can check. Our accounting, billing, payment, and KYC services are what make that happen.

Money code is unforgiving in a way most software is not. A rounding error or an event processed twice is not a cosmetic bug, it is someone's money in the wrong place, and the fix has to be traceable. That constraint is also what makes the domain a good place to learn: you get fast, honest feedback on whether your code is correct.

This is an L1 role. We expect you to arrive with solid fundamentals and real curiosity, not years of production experience. You will pair with senior engineers, own small pieces end-to-end from your first weeks, and grow into owning a service yourself.

What you will work on

• Build and extend our Kotlin finance services: accounting entries, fee and invoice calculation, payouts, and the KYC checks that verify the companies we pay, with tests and code review.
• Work on event-driven flows where a reservation turns into a payment, an accounting journal, and an invoice as events pass between services, and every step has to be repeatable and correct.
• Ship features to the internal back office our finance and compliance colleagues use daily to review KYC cases and check the books.
• Own your services in production: when a payout does not land, or a journal does not balance, you trace the event, fix the cause, and add the check that catches it next time.

What you will grow into

• Owning one of the finance services end to end, from design to rollout.
• The harder correctness problems: idempotency, reconciliation, and audit trails that still hold up years after the fact.
• Weighing in on architecture decisions with the senior engineers you pair with.

What we are looking for

• Around zero to two years of professional experience, or a strong internship and side-project record. A degree is welcome but not required.
• Solid fundamentals: data structures, algorithms, testing, and enough system design to reason about a service boundary.
• Working knowledge of Kotlin or Java, or another typed language and a clear interest in Kotlin.
• Care for correctness and detail. You would rather write the test that proves the totals balance than assume they do.
• Curiosity about how money actually moves. No finance background needed, we will teach you double-entry accounting, payouts, and what KYC is for.
• Fluent in English, and based in or around Amsterdam.

How we work

A cornerstone of our culture is in-person collaboration. We follow a "hub" model with unique hubs in Amsterdam, London, and New York, where we regularly collaborate face-to-face, onboard customers and colleagues, hold design sessions, and host events.

We do not hire for strictly remote roles. We expect people to spend meaningful time in our hubs because this is how we maintain our culture, build trust, and move quickly together.

We're also a financially regulated company. That means high standards for security, auditability, and decision-making. This means your work ships with the rigor and reliability you'd expect from systems that move real money.

Our values

At Katanox, our values are the blueprint for how we work together and build our product.

• Team over the individual, no ego: We prioritize the success of the whole team over individual agendas. We win together, share credit, and leave egos at the door.
• Data beats excitement: We welcome bold ideas, but we commit based on evidence. We use data, experimentation, and clear hypotheses to decide what to build.
• Dare to do: We are proactive, take smart risks, and move from talking to doing. We learn by shipping and improve through iteration.
• See it, own it, and close it: When we spot a problem or opportunity, we take responsibility to drive it to completion instead of assuming someone else will.
• We apply radical candor: We care personally and challenge directly. We give and receive honest feedback so we can grow faster as individuals and as a team.
• In person first, call second: We prioritize in-person collaboration in our hubs to build trust, move quickly, and solve hard problems together.
• Build collaboratively: We actively involve the right people, share context early, and co-create solutions across teams and disciplines.
• Iterate fast and pragmatically: We ship small, learn quickly, and avoid over-engineering. We focus on solutions that work in reality, not just in theory.