Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Scrumconnect

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Scrumconnect | Offres d’emploi chez Scrumconnect | Salaires chez Scrumconnect | Avantages sociaux chez Scrumconnect
      Entretiens chez ScrumconnectEntretiens d’embauche pour QA chez ScrumconnectEntretien chez Scrumconnect


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour QA

      22 nov. 2022
      Employé (anonyme)
      Londres, Angleterre
      Offre acceptée
      Expérience négative

      Candidature

      J'ai postulé via une autre source. Le processus a pris 2 mois. J'ai passé un entretien chez Scrumconnect (Londres, Angleterre)

      Entretien

      After 1st round of interview offer was given after 1 month. I have accepted the offer and was expecting to join. But after accepting the offer they scheduled 2nd round of interview and no response after that. It was not a good corporate ethic and human behavior to ditch the candidate without any communication after providing the offer. No work ethics. Please be clear with your process before you interview anyone and communicate the same. If you are not intended to retain candidate please don't give false hope by providing offer. You are not only spoiling your company's name and also making someone questioning their self worth and personal life.

      Questions d'entretien [1]

      Question 1

      Java based questions and Manual testing
      Répondre à cette question

      Autres retours d’entretien d’embauche pour un poste comme QA chez Scrumconnect

      Entretien pour Quality Assurance

      13 mars 2026
      Candidat à l'entretien anonyme
      Londres, Angleterre
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Scrumconnect (Londres, Angleterre) en mars 2026

      Entretien

      Interview Process at ScrumConnect Consulting QA - OAT The process consisted of two rounds, both competency-based and focused heavily on real-world experience rather than theory. Round 1 covered Operational Acceptance Testing (OAT), Failover Testing, Disaster Recovery, and a stakeholder management scenario specifically, how you would push back on releasing a product with a known defect. Basic monitoring knowledge and infrastructure awareness were also tested. Round 2 went deeper, covering performance, load, and stress testing, API testing and validation, and the difference between public and private domain testing. Interviewers specifically referenced Azure DevOps, Azure Monitor, ServiceNow, and Putty, so familiarity with the Azure ecosystem is essential. If you have a UX or development background, expect questions on how that experience adds value to your QA work. However be warned after completing both rounds, there was zero response. Two emails sent over two weeks went completely unanswered. No outcome, no rejection, nothing. For a professional services company, this is a poor reflection of their candidate experience.

      Questions d'entretien [1]

      Question 1

      Round 1 Questions Q1 Where did you apply OAT (Operational Acceptance Testing)? Q2 Give an example of something you tested in OAT. Q3 What is Failover Testing? Can you give an example? Q4 How would you convince a stakeholder NOT to release a product when there is an existing issue? Q5 What is Disaster Recovery testing and how have you approached it? Q6 If CPU memory is fully consumed, how would you empty/free it? Describe how you would set up an alert notification via Gmail. Round 2 Questions Q1 What tools have you used for Monitoring? Q2 Give an example of Failure Testing from your experience. Q3 Based on your CV, what experience do you have specifically for OAT? Q4 What is different about testing for a Public domain vs. a Private domain? What would you do differently for a Public domain? Q5 What tools have you used in your experience? (Interviewer noted: Azure DevOps, Azure Monitor, ServiceNow, Putty) Q6 What does 'early testing of OAT' mean to you? Q7 Explain API testing and validation — how do you approach it? Q8 Have you done any development work? If so, what kind? Q9 What is performance testing? Q10 What is load testing and stress testing? How do they differ? Q11 Explain User Centric experience — how does your UX background inform your testing approach? Q12 Why did you choose to do a Masters in UX? Q13 What is your current role and what types of testing do you carry out? Q14 What is your expertise in QA? Q15 What is Business User Testing and how have you conducted it? Tips for Future Candidates • Be ready to give specific real-world examples for OAT, Failover, and Disaster Recovery — generic answers won't stand out. • Know your monitoring tools inside out: Azure Monitor, Azure DevOps, ServiceNow, Putty were all discussed. • If you have a UX background, be prepared to explain how it adds value to your QA and testing approach. • Stakeholder management is key — prepare a structured answer for how you'd push back on releasing with a known defect. • Understand the difference between load, stress, and performance testing with clear definitions and examples. • API testing knowledge is essential — be ready to explain validation approaches and tools you have used.
      Répondre à cette question