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

      Server Density

      ¿Esta es tu empresa?

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Server Density | Empleos en Server Density | Sueldos en Server Density | Prestaciones en Server Density
      Entrevistas en Server DensityEntrevistas para el cargo de Remote Python Developer en Server DensityEntrevista en Server Density


      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 Remote Python Developer

      7 abr 2016
      Candidato de entrevista anónimo
      Remote, OR
      Sin ofertas
      Experiencia negativa
      Entrevista promedio

      Solicitud

      Me postulé en línea. El proceso tomó 1 día. Acudí a una entrevista en Server Density (Remote, OR) en abr 2016

      Entrevista

      On applying I was immediately asked my salary expectation and then asked to submit a written comparison of SQL vs non SQL databases. On submitting this I was asked to complete a code review. I completed the code review in Python 3 and despite clearly stating this, their reviewers mistakenly failed it as they were unable to run it without understanding the reason why. Upon explaining this to their CEO, they 'gave it another go' (not before admitting they actually had problems setting up a virtual env to run Python 3!) before finally claiming that the <10 'app' lacked documentation and was therefore 'incomplete'. The example had clear tests showing how to use it. I also have a well documented open source project tested against multiple Python versions in my Github. The one lesson I learned from this experience was not to complete any kind of tests before actually learning more about the job. It appears that besides their incompetence, Server Density don't respect or value the time of their applicants.

      Preguntas de entrevista [1]

      Pregunta 1

      Compare and contrast mongodb and mysql. Create a basic tornado app.
      Responder pregunta
      3
      avatar
      Respuesta de Server Density
      9y
      We ask all candidates to complete a short coding exercise to solve a particular problem. The specification is left vague to allow the candidate to show their initiative in not just writing a solution but also demonstrate how they write tests, include documentation and package the project to run e.g. using a virtualenv. On this occasion, the supplied code had almost zero documentation and contained incomplete packaging to allow us to run the code (requirements.txt was incomplete). We used a virtualenv which installed the requirements.txt but virtualenv 3.4 creates a python2.7 environment. The code was also not tested against multiple Python versions because "I didn't think anyone would actually run it so didn't think it was necessary to do this". We offered the candidate a second opportunity and whilst the code was changed, the tests and documentation were not. There were also no instructions for using the server once it was running and we had to read the source to figure out how to use it. As a result, we decided not to proceed with the application due to lack of care shown in an interview situation, which we felt reflected poorly on how the candidate would work in the future.