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

      Netdata

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Netdata | Empleos en Netdata | Sueldos en Netdata | Prestaciones en Netdata
      Entrevistas en NetdataEntrevistas para el cargo de Go Software Engineer en NetdataEntrevista en Netdata


      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 Go Software Engineer

      16 ago 2021
      Candidato de entrevista anónimo
      Róterdam
      Sin ofertas
      Experiencia negativa
      Entrevista promedio

      Solicitud

      Me postulé a través de un reclutador. El proceso tomó 4 semanas. Acudí a una entrevista en Netdata (Róterdam) en ago 2021

      Entrevista

      Process with basically 3 interviews. First one with the recruiter, second one with a manager with some level of technical questions but nothing too deep. Then a take home assignment which I described in the questions asked part below. Then an interview with the very arrogant COO. For me the last interview lasted 10 minutes because the COO started the interview right out of the gate just pointing out mistakes I made in the assignment, but all of the "mistakes" were explained and reasoned about in the README of the project. And I pointed out that all the answers to his questions were in the README he said he didn't like my attitude and cut the interview short. Meaning, the team that reviewed the project didn't even take the time to read the documentation presented with the project. This is exactly the reason companies need to stop giving coding assignments. The candidate spends hours and sometimes days which he take out of his family time, and companies like Netdata do not give the proper value. I am actually happy this didn't workout, because with a COO like this, this is definitely not a company I would like to work for.

      Preguntas de entrevista [1]

      Pregunta 1

      Deliverables: 1. The microservice written in golang 2. A brief documentation outlining your design/implementation decisions 3. A unit and end-to-end test suite for your implementation In this assignment we want you to design a new feature for Netdata cloud that allows users to receive notifications for the triggered alarms in a non-intrusive manner. To achieve that you need to create a microservice which will consume events from two topics. You will also need to create a publisher to send the AlarmDigest to the notification service. Subscribe to topics on Nats and Publish to it also. Notes 1. For the purposes of this challenge you can assume that your service will be part of an event driven system, with multiple microservices that communicate via messaging. 2. In the context of this challenge, nats will act as the message broker. 3. Our broker cannot guarantee in-order delivery of the messages 4. Our broker can guarantee at-least-one delivery for all topics 5. Your solution should be capable of handling any amount of messages 6. Your solution should be able to scale horizontally. 7. It is very important that all active alarms are eventually sent to the user, alarms should not be lost. 8. Ideally a user shouldn’t receive the same alarm twice, if its status has not changed since the last digest email. 9. Active alarms should be ordered chronologically (oldest to newest)
      Responder pregunta
      1