We are a challenging organisation with self-managing developers. We don’t have account managers or project managers; thus the entire team is responsible for successfully delivering projects to our clients. In small teams, we work on projects for our clients, both onsite at their location and from our own offices.
We develop custom-made software systems, mainly for system integration, big data projects and backend solutions. For decades now, we have been building software using Java and the Java ecosystem, more recently expanding to other JVM languages like Scala and Kotlin. However, we are not fixed to one specific tech stack; instead we are always aiming to offer the best solution for our customers requirements.
We are active in the Open Source community; we have conference speakers, published book authors, etc.
Lunatech is recruiting SRE.
Site reliability engineering (SRE) is a discipline that incorporates aspects of software engineering and applies them to infrastructure and operations problems. The main goals are to create scalable and highly reliable software systems. A Site Reliability Team, SRE is “what happens when a software engineer is tasked with what used to be called operations.
A site reliability engineer (SRE) will spend up to 50% of their time doing “ops” related work such as handling issues, spending time on-call, and manual intervention. Since the software system that an SRE oversees is expected to be highly automatic and self-healing, the SRE should spend the other 50% of their time on development tasks such as adding new features, such as for scaling or automation. A site reliability engineer is usually either a software engineer with a good administration background or a skilled system administrator with knowledge of coding and automation.
In this role you will have a number of different responsibilities:
Most of our clients follow some form of Agile process, so as a developer you will typically help the more product- and business-focussed members with scoping and estimating units of work (usually “tickets”) that go into a project iteration (usually “sprints”). Then, during an iteration you will typically collaborate with the Team Lead and other team members to come up with solutions to address the requirements outlined in the tickets.
This is not for you if… You are used to someone else fixing your stuff. Not going to happen here. Your code—your call. You build it, care for it and fix it.
You expect hand-holding. There is no SCRUM master, no leader, no testing engineer, no sys-admin telling you what needs to be done. It's your decision and your responsibility.
So a typical day might involve:
We do not have an HR director, all applications are evaluated by your fellow future colleagues with Maaike our chief coordinator helping everyone.
1. Cognitive and Personality assessment
As a first step we ask you to take a 30 minutes , cognitive and personality assessment managed for us by Bryq. We are not using this as a selective criteria but rather as a way to have an extra dimension in our evaluation to ensure the best possible match with the role and our culture.
2. We review your CV
Our technical team reviews your technical skills and see if you can move to the next step. If not, now is not the right time, we do not have the projects that suit you or you do not have the technical level yet and in this case we will keep in touch for later :)
3. Getting to know each other
With a video call or at the office. The purpose is to understand why you applied, why we invited you, to introduce Lunatech and how we work. It is above all understand your background and know your projects and see if we'd be a match.
If not, now is not the right time, we do not have the projects that suit you or you do not have the technical level yet and in this case we will keep in touch for later :)
4. Technical Assessment
We send you a small technical assessment to do and we'll plan a review of your solution with you. You should be able to do the tasks within a few hours and it will help us understand where you are at technically.
5. Technical Assessment Review
You meet one of our experts in the field that interests you, it is also an opportunity to help you do your self-assessment and know your level. During this review we understand how far advanced you are technically and in term of software architecture, how well you understand and master software tooling. You leave potentially having met your future technical manager and hopefully you learned a few tricks.
If we are not convinced by your technical explanation, now is not the right time, we do not have the projects that suit you or you do not have the technical level yet and in this case we will keep in touch for later :)
6. Final interview
During this interview, we'll talk a bit more about you the person. In order to offer you a personalized course if you join Lunatech, you meet with a member one of our directors as well as Lunatech HR person.
Finally, we'll discuss the conditions and see if we can come to an agreement. We'll see more about you the person during this interview and your career wishes.
You leave with a vision of both the values we share but also the projects we propose.
7. And after?
Two possibilities are available to you:
The first: all the lights are green on both sides, in agreement with the technical department and the directors, we make you a proposal.
The second: now is not the right time, we keep in touch through our blog articles, our events and we will try again later!
To know more about Lunatech and our selection process check out our recruitment page .