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

      Goodlord

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Goodlord | Empleos en Goodlord | Sueldos en Goodlord | Prestaciones en Goodlord
      Entrevistas en GoodlordEntrevistas para el cargo de Frontend Developer en GoodlordEntrevista en Goodlord


      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. Indeed, Inc. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Indeed, Inc.

      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 Frontend Developer

      20 may 2024
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia positiva
      Entrevista promedio

      Solicitud

      Me postulé en línea. El proceso tomó 3 semanas. Acudí a una entrevista en Goodlord en may 2024

      Entrevista

      The process was great from my end, I got to meet amazing people I wish I could've worked with but as life would have it, it just wasn't meant to be. I've nothing but praise for the people who interviewed me and I wish the best of luck to the company moving forward.

      Preguntas de entrevista [1]

      Pregunta 1

      General questions about Frontend Stack centered around JavaScript, React, and TypeScript.
      Responder pregunta
      2
      avatar
      Respuesta de Goodlord
      1y
      Thank you so much for your review - I must apologise for the delayed response, I am not sure how it got missed! We are really pleased that you had a positive experience with us, this is exactly what we strive for. Hopefully our paths will cross again one day, in the meantime we wish you the very best of luck!

      Otras evaluaciones sobre las entrevistas para el cargo de Frontend Developer en Goodlord

      Entrevista para Frontend Developer

      2 may 2025
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia negativa
      Entrevista fácil

      Solicitud

      Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en Goodlord en abr 2025

      Entrevista

      I applied for this mid-level React/Typescript role even with senior-level experience and agreed to proceed. This was my first call’s experience. No senior oversight: The engineering manager/tech lead that was meant to be in the meeting never showed (we waited ~5 min, then started). That left a junior-mid engineer to make the sole pass/fail decision for someone with proven commercial experience in the exact tech stack they need. Minute-detail rejection: Apparently having 8+ years of commercial TypeScript/React was not enough because I framed some answers in broader more verbose context. Feedback focused on my answers being too long rather than on substance and depth. And also I did not come across as having enough TS experience despite being asked (paraphrasing) "What is your TS experience and how did you use it in your codebase" and having answered along the lines of "structuring types in dedicated reusable files, typing functions/components/api responses well using interfaces/types/enums, using TS reasonably vs using it as intricate OOP patterns" apparently means I never worked with Typescript. Time-keeping: Call ran 30 min over the booked slot, which I was ok with but this further suggests weak interview training/structure. Inconsistent criteria: Other Glassdoor reviews echo the same: very small slip ups outweigh overall capability. That pattern feels less like "high bar" and more like arbitrary and unfair filtering as others have clearly experienced. Advice to candidates: - Expect to give answers more like you’d give a recruiter doing box-checking questions rather than being assessed by a truly experienced engineer for the first round if the engineering manager / tech lead does not show up. - If the tech lead is a no‑show, ask whether they'll join a later stage—otherwise you may be judged by someone who can't properly assess you. They may want yes/no type answers rather than contextual expertise and won't be able to intuit your experience from verbose, thoughtful responses like a lead/manager might - Don’t take a rejection personally; it seems they have a track-record of optimising for quick eliminations based on my and others’ experiences on Glassdoor. I am writing this review to give feedback that I think should be public and genuinely help applicants process their experience. - Please see other Glassdoor reviews, how they have responded to candidate feedback over the years is quite telling and likely what you might experience. Advice to Goodlord: 1. Make sure a senior engineer is present in first‑round technical screens. Early oversight prevents false negatives. 2. Tighten interview structure. If you value brevity, state that upfront and ahead of time. Keep the meeting to the allotted time. If any candidate is being verbose then actively train your interviewer to fight back against it to keep the interview within the 45 minutes time frame. Something like “We have only 45 minutes to go through exactly X questions, so let’s keep things concise to be mindful of time please” is enough as soon as you spot a hint of verbosity. 3. Ask yourself what you really want or even if you truly want to hire for this role. 8+ years of continuous React/TypeScript work should not be discounted because a candidate offers verbose context. Re-assess your criteria for what being experienced in React/TS means. I’ve been hired (and hired excellent engineers) for exactly the same style of conversations in the past.

      Preguntas de entrevista [1]

      Pregunta 1

      General questions about how aware am I about what it is that they do, security, typescript, React, my experience etc
      1 respuesta
      avatar
      Respuesta de Goodlord
      11mo
      Thank you for taking the time to share your feedback here, and again for raising your concerns with us directly over email on 2 May. We genuinely appreciated the opportunity to have that initial conversation. We’d like to address your points in turn: 1. Interviewer experience and structure All of our interviewers complete structured training, including shadowing and reverse-shadowing, to ensure they’re well equipped to make fair, consistent, and effective assessments. Our Tech Lead sometimes attends calls, but this was not the case in your interview. The engineer you met is a valued mid-senior member of our team with strong commercial experience – someone we would absolutely consider a “truly experienced engineer.” To suggest that an interviewer is unable to assess a candidate effectively simply because they are not in a leadership role goes against the principles of respect, trust, and fairness that we hold across our team. We believe strongly in empowering capable engineers to take responsibility in the hiring process – and in applying and maintaining consistent standards, regardless of seniority or job title. 2. Assessment criteria and decision-making We appreciate that every company assesses candidates differently, and that feedback can be disappointing when it doesn’t align with expectations. Our process is designed to evaluate both technical ability and the capacity to communicate and problem-solve clearly in real time – all key aspects of how we work at Goodlord. We use a structured rubric and scoring framework to ensure fairness and consistency. We do not optimise for “quick eliminations”; we optimise for thoughtful, consistent hiring decisions that result in quality hires. We’ve successfully hired ten engineers through this approach in the current financial year, and have seen them thrive within the team – so we’re confident in the criteria we use. That said, we’re always learning and evolving, and your feedback contributes to that. 3. Interview timing and communication style We recognise that your interview overran. The intention was to give you space to fully articulate your thoughts, but we appreciate your point about the need for clearer timekeeping. As promised in our follow-up email, this has already been fed back to the team, and we remain committed to ensuring structure and clarity at every stage of the process. Thank you again for engaging with us both privately and publicly. We respect your experience and wish you all the best in your ongoing search and future opportunities.