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

      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

      Greenbits

      ¿Esta es tu empresa?

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Greenbits | Ofertas de empleos en Greenbits | Sueldos en Greenbits | Beneficios en Greenbits
      Entrevistas de GreenbitsEntrevistas para el puesto de Senior Rails Developer en GreenbitsEntrevista de Greenbits


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empresas

      • Cuenta gratuita de empresa
      • Centro de empresas

      Información

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

      Trabaja con nosotros

      • Anunciantes
      • Empleo
      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 de primera mano.

      Búsquedas de empleo

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

      Entrevista de Senior Rails Developer

      15 mar 2018
      Candidato de entrevista anónimo
      Portland, OR
      Sin oferta
      Experiencia negativa
      Entrevista fácil

      Solicitud

      El proceso duró 2 meses. Acudí a una entrevista en Greenbits (Portland, OR) en nov 2017

      Entrevista

      TL;DR - CTO was distracted the whole phone screening. Company as a whole had poor communication. Job description and actual expected duties did not align. Ultimately withdrew application. ---- I received multiple emails from an external recruiter and decided to have a phone call to discuss the position and sent them my resume. The phone call was positive for both of us, so I was moved into the internal recruitment pipeline. I was contacted by someone a couple days later to set up the 30 minute phone screen with the CTO the following week. The phone call with the CTO left much to be desired. He spent half the time talking about the company, reiterating everything that the original recruiter said to me. He seemed distracted the whole time, including when it was my time to speak. He only asked a couple questions, I can't even remember what they were now, because they were so generic. The only one I can remember is "any questions for me?" During the whole call, which lasted less than the full 30 minutes, he gave the impression that he had better things to do with his time. The recruiter followed up two weeks later saying that they were excited to move forward with the process. That was a surprise to me, because I didn't get the feeling that the CTO was excited at all. I expressed that I had some reservations about working for a startup and asked some follow-up questions, including what the interview process would look like. Up until this point, I had no idea what the process would require of me or entail. The person I emailed with was prompt and courteous with their replies, but spelled my name wrong on a number of occasions. While that is not a huge deal, I believe when you are conducting business, it is reasonable to expect that small courtesy. Despite the many red flags, I scheduled an remote video interview for the following week. When it came close to the interview, I had been left with such a bad impression of the company and CTO that I decided to withdraw my application. Again, the recruiter was prompt and courteous. To my surprise, I received an invite to the repo the day I had my interview scheduled. It was apparent that my withdrawal had not been communicated. It was also interesting that the job posting was for a Ruby/Rails development position but the code challenge involved npm/yarn and react.

      Preguntas de entrevista [1]

      Pregunta 1

      What's the most challenging project you worked on?
      Responder pregunta
      1