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

      Tinder

      Parte de Match Group

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Tinder | Empleos en Tinder | Sueldos en Tinder | Prestaciones en Tinder
      Entrevistas en TinderEntrevistas para el cargo de SRE/DevOps Engineer en TinderEntrevista en Tinder


      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 SRE/DevOps Engineer

      21 oct 2021
      Candidato de entrevista anónimo
      Los Angeles, CA
      Sin ofertas
      Experiencia neutra
      Entrevista promedio

      Solicitud

      Me postulé a través de un reclutador. El proceso tomó 2 días. Acudí a una entrevista en Tinder (Los Angeles, CA)

      Entrevista

      - Phone screening. - Team overview meeting. - Lunch. - Technical Interview. Someone once told me if you want to understand a company's DNA look at its products. Consider tinder's HQ. I grew up in Southern California, so I know what this part of Sunset Blvd is like. I imagine setting up an HQ here was the idea of a C-level person who was renting a house in the hills above the boulevard and bragged about celebrity neighbors. During my time outside the interview room nearly everyone I chatted with used to live in reasonable locations but had since moved into apartment buildings on Sunset Blvd. They were all young people, not raising families. Of course, this was before the pandemic. Remote work may be more an options now but choices like an HQ location reflect a company's DNA.

      Preguntas de entrevista [1]

      Pregunta 1

      The technical part of the interview was an experience. The interviewer who was also the manager of the team I was interviewing for jumped right into a question without a preamble. The question was about an on-call alert and how I would handle it. It was a very general question focused on HTTP status codes. I have a lot of on-call experience. I know a company can leave on-call responsibilities indeterminate if allowed to. This is why when you deploy an app or service you ensure the process for troubleshooting it is documented. Create alerts for critical components, indeed, but you control what's deployed and how, so you can control how to handle errors, how to describe alerts, so that the problem is clearer for the person on-call who you woke up. Projects should have runbooks, alerts and errors should be handled in specific internal ways that provide information to people on-call. I went into these details with the interviewer but he had tunnel vision for his question and continued to focus on HTTP status codes. In the end, I refused to answer his questions because he did not answer mine. Why was I being woken up by this general error when we control the pipes? By the way, knowing a specific HTTP status code (and there many of them) does not mean you're experienced. It means a service has failed so many times that that general error has dug into your memory. There was another person in the room with him, an intern. This intern then asked a coding question straight from a classroom. Reinvent something to do with strings like reversal or splicing, etc. Nothing wrong with that or the intern. This is more reflective of a manager who likes to bring interns to interviews or if not interns then someone who is believed to be more in touch with these academic coding questions. There were other parts of the interview that were just fine. Those two points I think paint a clear picture of the type of employee who would thrive there. If you are young and just out school, try this place you might enjoy it. If you're older, raising a family, value your personal time, consider the company's product because it will tell you who they are.
      Responder pregunta
      2