Fragen in Vorstellungsgesprächen bei N26 für Site Reliability Engineer | Glassdoor.de

Fragen in Vorstellungsgesprächen bei N26 für Site Reliability Engineer

Vorstellungsgespräche bei N26

8 Bewertungen von Vorstellungsgesprächen

Erfahrung

Erfahrung
63%
12%
25%

Einladung zum Vorstellungsgespräch

Einladung zum Vorstellungsgespräch
50%
25%
25%

Schwierigkeit

3,5
Durchschnittl.

Schwierigkeit

Schwer
Durchschnittl.
Leicht

Hilfreich (2)  

Site Reliability Engineer-Vorstellungsgespräch

Anonymer Mitarbeiter
Angebot angenommen
Positive Erfahrung
Durchschnittl. Gespräch

Bewerbung

Ich habe mich online beworben. Vorstellungsgespräch absolviert bei N26.

Vorstellungsgespräch

The interview is highly technical. Breadth and depth seemed important for this position. Also, I liked that the interviews were structured and focused on various talents.

1. Screening
2. Take home challenge
3. Technical interview
4. Technical interview
5. Competency interview

Fragen im Vorstellungsgespräch

  • System design, TCP, HTTP, Security, SRE basics, Unix Networking   Frage beantworten

Antwort von N26

18. März 2019 – Recruiting Team

Thanks for sharing your hiring experience with us! We are glad to hear that you had a positive one and we are happy to having you here!

Andere Bewertungen von Vorstellungsgesprächen für N26

  1.  

    Site Reliability Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in Berlin
    Kein Angebot
    Negative Erfahrung
    Durchschnittl. Gespräch

    Bewerbung

    Ich habe mich auf Empfehlung eines Mitarbeiters beworben. Der Vorgang dauerte 3 Wochen. Vorstellungsgespräch absolviert im September 2018 bei N26 (Berlin).

    Vorstellungsgespräch

    The process was followed by screen call with the recruiter, take home code challenge to be dome in 72 hours, and on site interview.

    The first interview with the recruiter was OK, after 2 days or so I received the code challenge to do in home. I've asked to postpone the challenge for the next week, because I was exhausted from the longest incident we faced in my company (I am SRE). It came as a surprise that the recruiter said it could not be postponed, and had sent the code challenge saying to complete as much as I could.

    I was shocked by that. After this bizarre attitude, I just continued the code challenge in respect to the person who had referred me.

    I personally liked a lot of the test, it's a low level network task which stresses you a bit.

    I receive an email for the next round which would be a on-site visit and talk to two SRE one hour each.

    The first SRE was a pretty nice guy, he asked me to introduce myself, we reviewed the solution, what could be better, what I am doing at my company, what was my last project, how to do monitoring etc…

    I had a positive feeling from that conversation and it was pretty well in my point of view.

    The second SRE was a nice guy too. He again asked to introduced myself and I had to repeat all. Besides he asked low level question about networking, the conversation was more focused in security. I am not a security specialist at all and I said this to him. I was trying to pull the conversation to reliability engineering and operations work i.e (incident management, resilience (chaos), alerting, monitoring, SLOs & SLIs, troubleshooting, capacity planning, high available and resilient architectures), we talked very shortly in the end of the interview about a incident and nothing more than that. In my point of view the interview was more for SecDevOps and not SRE. I asked if they have rebranded their DevOps team to SRE and he said YES.

    Since the interview was focused on security and they don’t have DevOps (they are all SREs), I got the impression that they are unable to focus on doing site/service reliability work, we haven’t discussed any of the core concepts of site reliability engineering, maybe they are or will IDK.

    I asked for feedback to the interview process, and as usual I haven't received any. Unfortunately it's like that, you spent time you don't have for the company and you don't get a quick reply, it does not need to be too sophisticated, just say: "We need folks with deeper knowledge of security or something like that. However we liked 'this' and 'that' skill of yours" so we candidates don't stay guessing for months what could be better, and perhaps apply again in a near future. If no feedback is given, it's very unlikely the candidate will apply again,

    Fragen im Vorstellungsgespräch

    • SSL/TLS, FTP, Security all the things, Linux Networking, TCP/IP and more security   Frage beantworten

  2. Hilfreich (2)  

    Site Reliability Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in Berlin
    Kein Angebot
    Negative Erfahrung
    Schweres Gespräch

    Bewerbung

    Ich habe mich online beworben. Der Vorgang dauerte 6 Wochen. Vorstellungsgespräch absolviert im Oktober 2018 bei N26 (Berlin).

    Vorstellungsgespräch

    The interview process looked smooth initially. Went through all the stages and a low level socket programming assignment which I did. I got through all the stages until the final stage.
    After this they requested for references which I provided and then they sent a rejection without stating reasons. I sent an email to ask for a more detailed feedback which wasn't responded to. It's a shame I spent so much energy trying to work with a company I'm a huge fan of and they can't even grace you with an honest feedback after so much effort.

    Fragen im Vorstellungsgespräch

    • Technical tests. Questions on SSL, SSH, TCP and IP protocols. The OSI Model, Linux Shell and Kernel.   Frage beantworten

    Antwort von N26

    18. Dez. 2018 – Recruitment Team

    Thanks for sharing your experiences with us. We want to make sure all candidates are given constructive feedback after they invest time and effort into the hiring process.

  3. Hilfreich (4)  

    Site Reliability Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in Berlin
    Kein Angebot
    Neutrale Erfahrung
    Schweres Gespräch

    Bewerbung

    Ich habe mich online beworben. Der Vorgang dauerte mehr als 4 Wochen. Vorstellungsgespräch absolviert im Oktober 2018 bei N26 (Berlin).

    Vorstellungsgespräch

    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 excerise 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 reasearching 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 aswell. 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.

    Fragen im Vorstellungsgespräch

    Antwort von N26

    29. Okt. 2018 – Recruiting Team

    Thanks for sharing this detailed description of your interview experience with N26! Over the past months we have made it a priority to give all rejected candidates constructive feedback. That is why... Mehr


  4.  

    Site Reliability Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in Berlin
    Kein Angebot
    Positive Erfahrung
    Schweres Gespräch

    Bewerbung

    Ich habe mich über einen Personalvermittler beworben. Der Vorgang dauerte mehr als 2 Wochen. Vorstellungsgespräch absolviert im Dezember 2018 bei N26 (Berlin).

    Vorstellungsgespräch

    Coding test of the low level networking type.
    Next is interview rounds about TCP, networking, SSL, ci and cd. Know your TLS.
    Dunno past this, got rejected. Overall sounded like smart people.

    Fragen im Vorstellungsgespräch

    Antwort von N26

    18. Dez. 2018 – Recruitment Team

    Thanks for sharing your experiences with us.


  5.  

    Site Reliability Engineer-Vorstellungsgespräch

    Anonymer Mitarbeiter in Berlin
    Angebot angenommen
    Positive Erfahrung
    Schweres Gespräch

    Bewerbung

    Ich habe mich über einen Personalvermittler beworben. Der Vorgang dauerte mehr als 4 Wochen. Vorstellungsgespräch absolviert im Februar 2019 bei N26 (Berlin).

    Vorstellungsgespräch

    One of the toughest interview processes I've ever experienced. The people in there really know what they are asking and will crush you if you try to fool them. They will, literally, extract every drop of your knowledge. Don't even think about mentioning a protocol or system characteristic which you don't truly grasp all the intrinsic details - they will ask more and more about it.

    A few questions about Operating Systems, but no kernel-internals questions like Google/Facebook. The main focuses are on Networking and Security (never forget they are a bank). Know the OSI Model inside out. Some questions start at the Application Layer (7) and go all the way to the Physical Layer (1). Know TCP, UDP, DNS, HTTP, SSH and specially TLS and VPN. Many questions on reliable and secure ways of transferring data. Knowing the handshake details for both TLS 1.2 and 1.3, specially their differences what is SNI/encrypted-SNI, is the least expected. Other security questions like symmetric and asymmetric private/public key cryptography.

    The whole process will look like:

    1. Recruiter/HR interview
    2. Take-home test (72h deadline, 4-8h work time)
    3. Two rounds of technical interviews
    4. Engineering Lead interview

    Fragen im Vorstellungsgespräch

    • How does your computer gets IP/netmask/gateway information when connected to a network? Explain the DHCP protocol. Describe each of the DORA stages. Which is the source IP on the packet that goes in the "Discovery" phase?   Frage beantworten

  6.  

    Site Reliability Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in Berlin
    Kein Angebot
    Positive Erfahrung
    Durchschnittl. Gespräch

    Bewerbung

    Ich habe mich auf Empfehlung eines Mitarbeiters beworben. Der Vorgang dauerte 3 Wochen. Vorstellungsgespräch absolviert im Juli 2019 bei N26 (Berlin).

    Vorstellungsgespräch

    The interview process is composed by:
    - a first call with the HR,
    - a coding homework about network/security
    - 2 interview with two guys of the tech team .

    I was stopped after the 2 technical interviews because I didn't have enough proficiency about cloud and SRE concepts.

    Fragen im Vorstellungsgespräch

    • The HR asked me about my leaning on study new things and keeping me up to date with technology.   Frage beantworten
    • From the tech team, the questions were about SRE concepts and technical details about TLS and other protocols. Other questions were oriented to the cloud and DevOps.   Frage beantworten
    • I appreciate the feedback, in fact they offered to do a call to explain better my gaps.   Frage beantworten

  7.  

    Site Reliability Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch
    Kein Angebot
    Positive Erfahrung
    Durchschnittl. Gespräch

    Bewerbung

    Ich habe mich online beworben. Vorstellungsgespräch absolviert bei N26.

    Vorstellungsgespräch

    The interview was scheduled with some kind of mail bot. Then we connected via Google Meetings and recruiter ask me several questions about my expertise. I've gоt follow-up mail same day.

    Fragen im Vorstellungsgespräch

Verpassen Sie nicht Ihren Traumjob
Laden Sie Ihren Lebenslauf hoch, um sich schnell und einfach für Jobs zu bewerben. Bewerben leicht gemacht!