As a Senior C# WPF Software Developer you will make Coolblue work using brand-new Vanessa applications. 1000+ colleagues use your applications on a daily basis.

What you tell your friends you do ‘I’m the glue that connects the pretty screens to the data.’

What you will really be doing

• Develop WPF applications software with a slick and intuitive interface.
• Buddy up with the designers and Web API developers.
• Deliver quality work, which is easily maintainable and future-proof. Concerning the 3-tier application itself, we like MVVM, since it helps in making our applications loosely coupled.
• Consume the data from our web services, so you can focus on creating an intuitive user interface.
• Write testable code that will be continuously tested and deployed by TeamCity and Octopus Deploy, and will have a real effect on live environments.
• Coach and provide feedback to fellow developers.
• Think about technical choices, such as our architecture, tools and processes.

How will you be doing this?

• You will actively participate in your multidisciplinary team’s Scrum process.
• You will receive and pro-actively get feedback from end users and developers. After evaluation of this feedback you might incorporate it in a new iteration.
• You will actively think about technical choices, such as our architecture, tools and processes. Choices that were made in the past are not rules.
• You open pull requests, review the code and give feedback that makes your team even better.
• You will perform code-reviews in order to provide feedback that makes your team even better, and to maintain a high level of quality in our code bases.
• You will work in a motivated team to deliver on sprint commitment.
• You will actively improve overall software quality. Write SOLID and testable C# code.
• There is always a budget for good ideas.

What we have worked on last quarter Creating an application with a slick and intuitive GUI for our financial department, which uses our SOA to consume and store the data, enabling them to perform the part of their day-to-day operations in regards to dealing with suppliers.

What a day in the office might look like Today is the first day of the new sprint. Yesterday you and your teammates demoed the work of the former sprint. The round of applause, the future users gave to your team was well deserved, since the WPF application is showing some serious advantages over the current way of working, and is looking very slick to beat. ‘Sure’, you think, the end result was good, but things could’ve gone a little better. In the retrospective following the demo you’re able to praise the good end result and vent some constructive feedback. After the small replay in your head, you assign the top user story to yourself. The debtors from the financial department want to be able to approve or reject the agreements the purchasers create, in order to be a second set of eyes.

You walk by the web services team, thinking that for now you’re going to have to mock the calls regarding the agreements, but the service containing the functionality has already been released. Attached to the user story is a smooth design, with new icons and storyboards. You spot the use of an element that doesn’t exist in our WPF toolkit yet. You’re going to take until lunch to decide how you will implement the control.

Team You will be working in a dedicated and smart team with three to five other developers, each of them with their own specialization, ranging from XAML, the ins and outs of the upcoming C# 6, Unit tests and somebody who knows Git inside out. Your team will be complemented by a Scrum Master and a Product Owner. Each of these roomies will challenge you, both technically and in a game of Nerf.