Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empleadores

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      LinkedIn

      Parte de Microsoft

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de LinkedIn | Empleos en LinkedIn | Sueldos en LinkedIn | Prestaciones en LinkedIn
      Entrevistas en LinkedInEntrevistas para el cargo de Site Reliability Engineer en LinkedInEntrevista en LinkedIn


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empleadores

      • Cuenta de empleador gratuita
      • Centro de empleador

      Información

      • Ayuda
      • Pautas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de autorización de cookies

      Trabaja con nosotros

      • Anunciantes
      • Oportunidades laborales
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información desde adentro.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista para Site Reliability Engineer

      1 de abr de 2020
      Candidato de entrevista anónimo
      Sunnyvale, CA
      Sin ofertas
      Experiencia neutra
      Entrevista promedio

      Solicitud

      Me postulé en línea. El proceso tomó 3 meses. Acudí a una entrevista en LinkedIn (Sunnyvale, CA) en mar 2020

      Entrevista

      Fairly standard interview process for these types of companies. An initial screening, followed by two rounds of phone interviews, and finally an on-site interview. The on-site interview had to be swapped for a virtual interview due to COVID-19. PROS: - The coding portions of the interview were all relevant to the job. They were not just toy examples. - The turnaround time after each interview was extremely quick - Most people were easy to talk to, which made each interview feel relatively quick - You set your own pace for the interview rounds. Some of my rounds were over a month apart. - The recruiters ask for your feedback to them after each round - The interviews were actually easier than I thought they'd be, except the last round I wasn't given as much guidance on what to study as the first two rounds, so I spent time on useless info. CONS: - The interview questions were more like a shotgun blast across a wide range of topics rather than focusing on anything in particular. It went from as low level as how/when shared libraries are loaded when starting an application to as high-level as designing video streaming service. - Before the final round, you are handed off to a different recruiter - Based on browsing this site, they seem to use the same questions for each candidate. It makes me feel like they are just a cog in the wheel with no real input to the process. With nothing being tailored to the candidate, it feels like they don't actually care about your strengths and weaknesses outside of their own perceptions. - The interviewers do not look at your own LinkedIn profile or resume until they are in the process of interviewing you. Therefore their questions against your background are either stock or ad-lib. There is little to suggest most interviewers care about your history or interests. - They count on their name a little too much to persuade you that its worth taking a hit to your salary and/or quality of living. Especially if you are relocating from a more affordable area. The benefits are not substantially different from my current employer. - Some disconnect between recruiters and interviewers, which is pretty common. For example, I repeatedly said this would be a change in both domain and roles for me, and I wasn't sure I'd be a good fit, even though I was interested and more than willing to learn. I do have extensive experience other tech domains. I was assured that there would be an extensive training process for the role, and the experience, while important, didn't matter quite as much as the ability and interest to learn the job. The feedback I received after the final interview indicated that experience was in fact one reason I didn't get the job; they wanted someone who could hit the ground running, even though the position was being held open indefinitely and there would be a training period after hire. - Feedback was almost non-existent after the last interview. Whereas I talked directly with the recruiter after every other round, the last round feedback was left as a voicemail. They did not solicit my feedback. TIP: Go through the second Google SRE book, the workbook.

      Preguntas de entrevista [11]

      Pregunta 1

      How do make a variable in a shell script available after the script exits (assume the shell script was sourced)?
      1 respuesta

      Pregunta 2

      How do you change the priority of a running process?
      1 respuesta

      Pregunta 3

      Coding test: Parse a (syslog) file to get various fields from the logs and message counts. Associate counts with the processes that logged them.
      Responder pregunta

      Pregunta 4

      Describe how SSH works.
      1 respuesta

      Pregunta 5

      Describe how curl works. What happens when you call the command? Describe the process of loading libraries, parsing arguments, DNS resolution, etc.
      Responder pregunta

      Pregunta 6

      You have Gigabytes of data that needs to periodically be synced from a producer to a large number of consumers. How do you approach it? Hint: the data set isn't necessarily entirely new each time it needs to be synced, so only sync the data that has changed.
      1 respuesta

      Pregunta 7

      You take over a new service and discover it has no monitoring. What monitoring would you put in place within the first week to ensure the service is working? Within the first month? How do you monitor failures which are local to a region?
      Responder pregunta

      Pregunta 8

      You will be asked to role play a scenario where the number of registrations for a service has dropped to 0 for the past 6 or so hours, setting off an alert. You will have to go through an incident response and elevation. You will be asked to write simple reports that are suitable for giving high-level status to a manager.
      Responder pregunta

      Pregunta 9

      You will be shown several architecture diagrams and asked various questions, like "what happens when database X goes down?", or "How to speed up requests from service Y?". Caching plays a big role in almost all responses.
      Responder pregunta

      Pregunta 10

      You will be asked to do live troubleshooting of an Apache (httpd) web service. You will not be given many details by the recruiter, so it's easy to study the wrong thing here. It ended up that you need to be familiar with the httpd config file and Aliases. You need to be familiar with how to change Linux filesystem permissions, but you can ignore that you are running on RedHat and you won't need to touch SELinux permissions. Be careful of one problem where they will have two nearly-identical file names, except one has a hypen and the other Unicode dash character. They look very similar in many fonts. Make sure you know how to do a simple GDB backtrace. You will be asked to debug a segfault and work around it (via simple file rename).
      Responder pregunta

      Pregunta 11

      You will have to perform a code review of several pieces of code. Focus on logic errors, not stylistic issues. I don't remember all the code samples, but one was about doing file backups, where they manually implemented extension parsing and copied over ".1" files to ".2", etc. without ensuring the order of the copy.
      Responder pregunta
      38

      Otras evaluaciones sobre las entrevistas para el cargo de Site Reliability Engineer en LinkedIn

      Entrevista para Site Reliability Engineer

      24 de jun de 2022
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia negativa
      Entrevista fácil

      Solicitud

      Me postulé a través de un reclutador. Acudí a una entrevista en LinkedIn en jun 2022

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 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/
      Responder pregunta
      3

      Entrevista para Site Reliability Engineer

      5 de abr de 2021
      Candidato de entrevista anónimo
      Nueva Delhi
      Sin ofertas
      Experiencia negativa
      Entrevista difícil

      Solicitud

      Me postulé a través de un reclutador. El proceso tomó 4 semanas. Acudí a una entrevista en LinkedIn (Nueva Delhi) en feb 2021

      Entrevista

      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.

      Preguntas de entrevista [5]

      Pregunta 1

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

      Pregunta 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.
      Responder pregunta

      Pregunta 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.
      Responder pregunta

      Pregunta 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.
      Responder pregunta

      Pregunta 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.
      Responder pregunta
      13

      Entrevista para Site Reliability Engineer

      23 de mar de 2021
      Empleado anónimo
      Bengaluru
      Oferta aceptada
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Me postulé en línea. El proceso tomó 4 semanas. Acudí a una entrevista en LinkedIn (Bengaluru) en ene 2021

      Entrevista

      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.

      Preguntas de entrevista [2]

      Pregunta 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.
      Responder pregunta

      Pregunta 2

      Questions on DNS, Linux Inodes, Message Queues, Processes, Fork and VFork, Kernel, Linux Boot Process, etc.
      Responder pregunta
      4

      Las mejores empresas en cuanto a "Remuneración y prestaciones" cerca de ti

      avatar
      Amazon
      3.7★Remuneración y prestaciones
      avatar
      Google
      4.5★Remuneración y prestaciones
      avatar
      eBay
      4.0★Remuneración y prestaciones
      avatar
      Amazon Web Services
      3.9★Remuneración y prestaciones