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

      Nesh

      ¿Esta es tu empresa?

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Nesh | Empleos en Nesh | Sueldos en Nesh | Prestaciones en Nesh
      Entrevistas en NeshEntrevistas para el cargo de Lead Software Architect en NeshEntrevista en Nesh


      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 Lead Software Architect

      8 ago 2021
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia negativa
      Entrevista promedio

      Solicitud

      Acudí a una entrevista en Nesh

      Entrevista

      I applied for Lead Software Architect with Nesh as the indeed ad stated "Responded to 75% or more applications in the past 30 days, typically within 2 days". Indeed ad also stated that they are "Urgently hiring". Initial phone/video interview followed by homework assignments. In this process, I became concerned about the company culture. Glassdoor shows active participation of the company. It is about tainting the glass on the door. Below are the questions from "Lead Architect Hypothetical Scenarios". I do not think that these are hypothetical rather their REAL scenarios (the company is good at misleading everyone). It clearly shows that they do not know how to manage a project. Based on their questionnaire, their employees are working very long hours, poor morale, hired cheap (i.e. robotic labor), high turnover, and they can not deliver! See the "Lead Architect Hypothetical Scenarios" questions below:

      Preguntas de entrevista [1]

      Pregunta 1

      - We have a new big-name customer that the sales team has told we can start work for them inside the month. We currently have planned efforts for the next 6 weeks already. How would you handle that? What could we have done to prevent that problem? * - Person-hours for this upcoming project will be spread between different projects throughout different weeks of this customer's project. How should the effort be planned out and divided up accordingly? * - We've already begun work for a customer, but we've discovered that there was a misunderstanding in how a feature works and the customer's suggestion on what we need to complete will add a significant amount of development time to the project. How could we resolve that so we're all happy? Could this have been prevented? * - We're getting a pattern of incoming bugs for Question/Answer combinations that used to work, but are now broken. How could this be mitigated/prevented? Is there a way around testing for qualitative answers like what we have? * - The morale is becoming poor toward the finish line of a product release and developers seem to be becoming spread thin. What should be done to help them out and make sure Nesh's product doesn't lose any quality in the process? What can be done next time? * - One of the developers isn't pulling their weight in terms of idea generation and autonomous discovery of solutions. In other words, they require every detail for every spec to be written out for them ahead of time before they can do any work. What would you do in that scenario? * - A developer quits in the middle of a project and helps us realize we have a very high bus factor. (# of team members hit by a bus / # team members total = how screwed you are) What do you do? How do we recognize a high bus factor early on and how do we mitigate that? * - We get to the end of a project and tell the customer that we have a 95% success rate in the questions that they've asked us so far. (the original agreed-upon success metric) They question our calculation methods saying that they haven't felt that it's been that high and think it's nowhere near that. How would you go about discovering what they're actually wanting and how they got there? How could we convince them otherwise? How could that have been prevented? *
      Responder pregunta