Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      LinkedIn

      Parte di Microsoft

      Azienda coinvolta

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su LinkedIn | Offerte di lavoro di LinkedIn | Stipendi di LinkedIn | Benefit di LinkedIn
      Colloqui di LinkedInColloqui per Site Reliability Engineer presso LinkedInColloquio di LinkedIn


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Site Reliability Engineer

      4 mar 2016
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto più di una settimana. Ho sostenuto un colloquio presso LinkedIn nel mese di feb 2016

      Colloquio

      I was contacted from a Campus rescruiter on linkedin. He set up a phone interview to tell me more about the role. The phone interview was good, he explained the role, what they expect from interns and what our responsibilities were. He then said I'll be asking you some basic questions, if you give right answers, then you'll have the next technical round. The questions were on bash, tcp, processors, and finally he gave me a list of IP addresses and asked which ones are public and which ones are private (it weren't as easy as 127.0.0.1 or 192.168.0.1). He was satisified by my answers and told me to send my availability date for the interview. I had a phone-screen interview. Most of the questions were the one posted here. I focussed more on Linux Fundamentals like learning about fork, runleves, init, docker, application deployment and port numbers. The e-mail said it would have scripting questions on Application deployment, filesystem traversal, log parsing. I couldn't get the role. I was expecting it because I focussed more on Linux than scripting. But the recruiter who contacted me, actually called and gave me the news. He was kind and told me to apply next year and or drop him an e-mail when I graduate and also told me to practice scripting if I want this position because it basically revolves around scripting and automation.

      Domande di colloquio [3]

      Domanda 1

      Fizz buzz question. Modifications: 4 and 6 instead of 3 and 5. Linked, in and LinkedIn instead of Fizz, buz and fizzbuzz.
      Rispondi alla domanda

      Domanda 2

      Log parsing
      Rispondi alla domanda

      Domanda 3

      Recursive call of LinkedIn api using REST.
      1 risposta
      10

      Altre recensioni di colloqui per Site Reliability Engineer presso LinkedIn

      Colloquio per Site Reliability Engineer

      24 giu 2022
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza negativa
      Colloquio facile

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. Ho sostenuto un colloquio presso LinkedIn nel mese di giu 2022

      Colloquio

      There were two rounds 1.operation round 2.coding round both rounds were easy answered all questions which interviewer agreed are correct .still din't get feedback why i was rejected. They have standard questions which will be asked in every interview . I don't know how they are evaluating candidates.

      Domande di colloquio [1]

      Domanda 1

      Operations asked three questions 1.ssh how will it work 2.send one file from one server to 10,000 3.how to monitor three tier architecture coding 1.FizzBuzz 2.recursion 3.log parsing you can see answers here https://yumminhuang.github.io/note/sreinterview/
      Rispondi alla domanda
      3

      Colloquio per Site Reliability Engineer

      5 apr 2021
      Candidato anonimo a colloquio
      Nuova Delhi
      Nessuna offerta
      Esperienza negativa
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso LinkedIn (Nuova Delhi) nel mese di feb 2021

      Colloquio

      The Hiring process was long, lasted over a month. I had an initial Hacker Rank coding round, followed by first round of interview, then second round and then final round which consisted of 4 rounds of interview. I had referred previous interview experiences on Glassdoor and that helped to prepare. The questions were mostly similar. I got a rejection mail after the first round but then again I got a call for second round. They never answer when we call back. That's what I felt very bad about it.

      Domande di colloquio [5]

      Domanda 1

      First round was based on Networking. TCP/IP, ARP, DNS resolution, Sharding, Scaling, caching, server management concepts were covered.
      Rispondi alla domanda

      Domanda 2

      Second round was scheduled only for Linux Memory management. Entire Memory management questions were asked. How it works, why is it required, Virtual memory, swap memory, swappiness and all.
      Rispondi alla domanda

      Domanda 3

      Code review round they gave 3 codes and I had to find bugs. 1 was for storing backup, 2nd was parsing logs and 3rd one I don't remember.
      Rispondi alla domanda

      Domanda 4

      System design was okay. They gave situations and asked how to design system in that scenario. We were allowed to ask questions to check if we were in tbe right track.
      Rispondi alla domanda

      Domanda 5

      The last one was Troubleshooting There was an Apache server and we had tk debug jt. It had 500 and 400 errors. I wasn't able to solve any in this round.
      Rispondi alla domanda
      13

      Colloquio per Site Reliability Engineer

      23 mar 2021
      Dipendente anonimo
      Bengaluru
      Offerta accettata
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso LinkedIn (Bengaluru) nel mese di gen 2021

      Colloquio

      The process started with an online coding challenge. It had three coding questions around LeetCode medium level, one DBMS query, and around 20 MCQs involving Networks, DBMS, Linux, etc. Following that, there were two technical interviews and one host manager round. The first technical interview was a Service Architecture round where I was asked to scale a ride-hailing application to handle about 10000 requests/min. It was a 1.5 hour round. In the second interview, I was tested a lot on Data Structures, Networking, Linux administration, troubleshooting. Certain questions were very tough, like in what port do you attach your hard drive, but I guess they asked that to check our limits, and they weren't deciding questions. The last round was a Hiring Manager round close to a typical HR round, but I had certain technical questions about my projects.

      Domande di colloquio [2]

      Domanda 1

      Scale a ride-hailing application so that it handles ~10,000 requests/minute. This was a 1.5-hour-long discussion with follow-ups, including Consistent Hashing. They also challenged multiple of my design claims which I had to think about on the spot.
      Rispondi alla domanda

      Domanda 2

      Questions on DNS, Linux Inodes, Message Queues, Processes, Fork and VFork, Kernel, Linux Boot Process, etc.
      Rispondi alla domanda
      4

      Le migliori aziende per "stipendio e benefit" vicino a te

      avatar
      Amazon
      3.7★Stipendio e benefit
      avatar
      Google
      4.5★Stipendio e benefit
      avatar
      HENNGE
      3.8★Stipendio e benefit
      avatar
      xneelo
      3.8★Stipendio e benefit