Fullstack Java Developer Arnhem

About the CIW team

As a Fullstack Developer you work closely with the other Developers in the Customer Integration Workflow (CIW) team to deliver new functionality and keep the current applications up and running.

CIW follows and relies on DevOps practices. This means developers are not only creating new functionality, but they are also actively monitoring and maintaining the components. They have a Developer-of-the-Week schedule, which means that every week there is one Developer with the special task of communicating with the stakeholders and external parties about outages or bugs and other questions that may arise. They also maintain their own DTAP environments, and rely on a combination of acceptance tests, application probes with alerting and contract testing to make sure their components are healthy and compliant. 

The Developers of the CIW Scrum team work closely together, by doing (pre)refinements, bi-weekly technical meetings, story kick-offs, pair programming sessions and peer-reviews. They also have a lot of fun with each other, having drinks every month, to celebrate successes. They mostly work from home, except for the one day per week on which the entire team comes to the office in Arnhem. 

About the components

Our client has several applications and services that are created and maintain. Their backends are comprised of Java (17) and Kotlin applications based on Spring. They mainly provide REST endpoints to other services or to frontends. They use Camunda as their process engine and store their data in PostgreSQL and DocumentDB's on AWS. 

Their frontend applications are Angular applications, using OpenAPI generated clients to connect to their endpoints. They use ngRx for reactive state management. Their build pipeline is fully automated, relying on GitHub and Tekton to build the artifacts. Their applications are mostly deployed as docker containers on their Kubernetes platform using argoCD. They use OpenShift to manage and monitor what is going on, and they use Elastic with Kibana for their logging. 

They rely on a GitOps strategy and they have their entire build pipeline and server setup as configuration on GitHub. All of them use IntelliJ as their preferred development environment, combined with Docker (desktop) to run applications locally. They use Sonar to ensure code quality, and Dependabot to keep their dependencies up to date.