Taro Logo

Site Reliability Engineer Interview Experience - Berlin, Germany

October 1, 2018
Neutral ExperienceNo Offer

Process

There are at least 5 stages.

I got to the fourth.

First is your typical HR screening call.

Then you get the coding challenge, which you have up to 72 hours to resolve.

If you expect a "build this infra, deploy this, and tune this up" or something like that, forget it.

It is a pure coding exercise which in my case involved low level networking.

It was quite hard for me but I put a lot of effort, spent a whole weekend at home researching and doing it, and finished it on time.

After a week, HR schedules the two next technical interviews with members from the team.

The interviewers were nice.

One hour each, no bs, purely technical.

I will not post the questions for a matter of respect, but they ask about the coding challenge, and other things as well.

90% was security related.

Remember this is a bank.

Two days after my last interview, I receive the rejection email with a generic feedback message.

I worked so much but it was not enough, not even for a not-Senior level role, but I have to get over it, this is just how it works.

Although I would have loved to get specific feedback so I can see where I failed and improve.

Questions

I learned a lot about networking and security.

Was this helpful?

Interview Statistics

The following metrics were computed from 9 interview experiences for the N26 Site Reliability Engineer role in Berlin, Germany.

Success Rate

11%
Pass Rate

N26's interview process for their Site Reliability Engineer roles in Berlin, Germany is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive44%
Neutral11%
Negative44%

Candidates reported having mixed feelings for N26's Site Reliability Engineer interview process in Berlin, Germany.