GlobalLogic interview questions

I applied for a Senior QA / QA Automation role. The project sounded genuinely interesting, especially because it involved train systems and potential travel/delegation between Cluj and Copenhagen. Unfortunately, the interview process did not match the seniority level of the position. The technical discussion felt mostly generic and theory-based, with basic testing definition questions rather than a practical assessment of automation architecture, web testing strategy, coding approach, CI/CD integration, debugging, maintainability, or real-world QA decision-making. What disappointed me most was the feedback received after the process. I was told that the role required a more advanced practical background in automation architecture, web testing, and coding skills. From my perspective, those areas were not meaningfully assessed during the interview, so the conclusion felt very broad and unsupported by the actual discussion. The rejection was communicated through LinkedIn, with wording about continuing to “grow technical expertise” and waiting for an opportunity that aligns with my “experience level.” For an experienced candidate, this came across as unnecessarily patronizing, especially after an interview that did not properly evaluate the areas mentioned in the feedback. Overall, the project seemed interesting, but the hiring process left a poor impression. For senior technical roles, I would expect a more practical, structured, and role-relevant assessment, along with more careful and specific feedback.

Fueron 3 entrevistas en total durante el lapso de unas 3 semanas. -Breve presentación con RRHH para contar experiencias previas y alinear expectativas -Charla técnica con lider QA para profundizar sobre los conociemientos adquiridos y requeridos -Entrevista con el potencial cliente para presentar el proyecto donde trabajariamos