Backend Developer at Jobs & Media Group | Groningen
Want to contribute to the next big thing in recruitment? Build websites and products that will become the new standard? We’re determined to turn the market upside down (internationally). In order to do so, we need reinforcement. People who are just as enthusiastic and energetic as we are, who think in possibilities and enjoy change and innovation. Do you thrive in a highly dynamic environment, can you deal with freedom and responsibilities and do you want to make an important contribution to great projects? Then we’re looking for you.
You will work within the Development department (currently 5 FTEs, with expansion plans) in central Groningen. Your colleagues work at the same location or in Amsterdam, many of them now work in PHP. In the future, Go will be used more and more.
As a Backend Developer you are responsible for developing job platforms and associated tooling for end users, customers and internal users. You develop job boards and recruitment websites with tooling. The system landscape consists of similar sites, including old and new CRM systems for the internal organization. The software you develop together with your fellow developers runs in the cloud, so if you have knowledge of that, it’s a nice bonus.
The software you write aims to help people find a new, suitable job. Our ambitions are endless, so you can learn a lot in a relatively short period of time. If you’re more experienced, you get the freedom to assist your younger colleagues in their learning process.
Your day starts with checking any new tickets varying from setting up a new system or optimizing the performance of existing code to creating new REST calls for the API. Perhaps one of the calls is related to the new to be built data lake. A ticket has already been attributed to you today. Because you’re specialized in back-end development, your software will be used by front-end and full-stack developers. That’s why it’s important to ensure the code can be used properly; you ensure, among other things, proper documentation of the formal parameters and the expected results. After completing your code, your tests and your documentation, you send your code to a reviewer. If you’ve done everything perfectly, they will send your ticket to a tester. This time it still needs some attention. Together you go through the comments again. Your solution is good, it was just not understood correctly. You decide to think of something else to create more clarity. You send your ticket again to the review queue, in the meantime you look at the metrics of the existing systems. Maybe you need to optimize something about that long-term call that suddenly seems to be used ten thousand times a day. But why is that? You decide, after reviewing a ticket from a colleague who has worked on a piece of system that you know well, to take a look at it …