Full-stack developer

What is a fullstack developer?

For us, a full stack developer means someone who can get along well in for example backend development and is healthy interested in front-end. But the other way can also be fine, so a good front-end developer who also likes to work on the back-end every now and then. It does not mean that you have to be a specialist in everything, we do not believe that either. Your expertise is therefore mainly in one of the parts, but you have clear interest and preferably also experience in the other parts.

Why do we find it important for employees to be full stack?

We are a team of enthusiastic developers, search and data engineers and data scientists. We believe very much in self-reliance. So as a team, you can tackle a project and do everything. Then it is not convenient if you have to ask for help for every adjustment to the part in which you do not specialize. We also think that developers get better when they understand the entire stack.

Which roles do we distinguish?

Backenders at Luminis mainly work in Java, we stay with up to date and and mainly work with Java 8/9. To be effective, we use a number of frameworks. Think of the Spring framework. Most projects are made with Spring boot. In addition, we look at libraries from the Netflix stack to build better applications. Many of our projects use a REST interface between the back and front of the application. Of course, this communication must be secure, so basic knowledge about matters such as CORS, Basic authentication, cookies, tokens and the like is a plus.

Because we are a team that does a lot of data, you should be interested in this at least. Experience with one or more types of data stores (MongoDB, Elasticsearch, Mysql / Postgres) is therefore a must. In addition, it is a plus if you have experience with technologies such as: Kafka, Spark, Flink.

We expect you to understand how to build good software. Can work with tools like: Intellij (or eclipse), Git and Maven. In addition, we are always working on bringing software to production, so experience with Linux and (application) containers is also a plus.

Finally, we expect that in the context of full stack you also understand what happens on the front-end. You have to understand what we mean by npm, grunt, webpack and bower. In addition, we expect basic knowledge of css and preferably also Sass / Less. Of course you have to be able to make some HTML pages and you prefer to have some experience with AngularJS and / or React. Many of our projects use frontend libraries such as Bootstrap and / or Material Design. So experience with this is certainly a plus.

As a frontender you are responsible for building usable products. We work a lot on reusable components, for example for AngularJS, but also for React. Of course you can deal with things like css / sass / less, html5, jQuery, npm, grunt, web pack. We also expect good insights into how to make a good dashboard and we expect you to constantly look for better techniques to build great products.

Because we work a lot with data, it is useful if you have experience with libraries that produce graphs and other data visualizations. Think of D3, but also implementations like C3js, amcharts, or maybe you know some better libraries yourself.

Because we work a lot in teams, we also want you to be able to do some basic things on the backend. Our basic architecture is a front-end linked via REST to the backend. It is useful if you can make your own Spring controllers in Java or if you do not mind putting a database on your machine yourself so that you can carry out successful projects together with backenders.