Java Developer Public Transport Payments

Working at NS means that you can make *the* difference in the dynamic world of sustainable mobility. You help keep the Netherlands accessible, for everyone. At NS, you get a lot of freedom. The possibilities to develop yourself are great. We promise you that no day is the same. And as one of the most beautiful employers in the Netherlands, we have even more to offer. For this position, including:

• Scale 60 = € 3,743 and € 6,491 gross per month (scale 60) (based on 36 hours - scaling based on work experience)

• The possibility of working from home and flexible working hours (in consultation)

• A 36-hour work week

• 3% end-of-year bonus, 8% holiday allowance, and an excellent pension scheme

• Upon good performance, you will receive a permanent contract after one year

• Your train travel in 2nd class is free; travel in 1st class is possible with a small personal contribution

• Your family travels for free during off-peak hours

• 144 hours of statutory leave (based on full-time employment) plus extra leave depending on age (minimum one week)

• The possibility to exchange 3 Christian holidays for 3 non-Christian holidays

• Discount on European train travel once you have worked at NS for 1 year

• A choice plan including, among others, a bicycle plan, extra pension accrual, or extra vacation days

Want to know more? View our employment conditions and collective labor agreement (CAO).

• Using Java 21+, Spring Boot and Microsoft Azure, you will develop software for ordering, delivering, and modifying the public transport pass.
• You are responsible for the entire DevOps cycle: from new functionalities and automated testing to monitoring, incident analysis, and production management.
• You work in a self-organizing team on an important chain within public transport payments and coordinate extensively with other development teams, platform teams, and external chain partners.

"With your Java knowledge, you don't just build new functionalities. Together with your team, you also ensure that public transport payments continue to work reliably every day."

As a Java Developer, you work according to DevOps principles. This means that development and management go hand in hand. Together with your team, you are responsible for the entire software lifecycle.

You develop and maintain Java functionalities and Azure components for the chain surrounding the ordering, delivery, and modification of the public transport pass.

This means that you:

• develop new functionalities using, among others, Java 21+ and Spring Boot;
• set up and implement automated tests;
• monitor applications and Azure components;
• analyze and resolve production problems and incidents;
• perform root cause analyses to determine why problems arise;
• take measures to prevent incidents from recurring;
• improve logging, monitoring, dashboards, and alerts;
• further automate deployments, tests, and management tasks;
• perform technical maintenance, upgrades, and lifecycle management;
• monitor availability, performance, data integrity, and ICT security;
• collaborate with other development teams, platform teams, service management, and external chain partners;
• explain technical topics clearly and make agreements regarding dependencies, interfaces, and responsibilities.

In doing so, you look beyond your own application. In the event of a change or incident, you want to understand what happens further down the chain. What does a change mean for another team? What does a chain partner notice? And what consequences can a malfunction have for travelers?

Therefore, in the event of a production problem, you do not just look for a quick solution. You use logs and measurements, for example, to find the cause, restore the service, and then look at how to prevent repetition.

Together with your team, you are constantly looking for the right balance between new functionalities, technical quality, maintenance, and operational stability.

Of course, you do not need to be able to do everything already. However, we are looking for someone who takes responsibility for software quality, remains curious, and enjoys collaborating.

You can analyze problems systematically and distinguish between a symptom and the actual cause. In the event of a malfunction, you look at logs and measurements before drawing conclusions.

You also dare to adjust or postpone a release if quality, security, or manageability requires it. You can explain why you are making that choice.

Because your software is part of a larger chain, you actively seek collaboration. You make dependencies clear, involve the right colleagues in a timely manner, and can explain technical choices understandably to people with different expertise.

You find new technology interesting. At the same time, in a production environment: we innovate deliberately. You experiment, learn from results, and ensure that production stability is not unnecessarily jeopardized.