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

      UNKNOWN

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur UNKNOWN | Offres d’emploi chez UNKNOWN | Salaires chez UNKNOWN | Avantages sociaux chez UNKNOWN
      Entretiens chez UNKNOWNEntretiens d’embauche pour Software QA Tester chez UNKNOWNEntretien chez UNKNOWN


      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 Software QA Tester

      24 mai 2026
      Candidat à l'entretien anonyme
      Pune
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez UNKNOWN (Pune)

      Entretien

      Interview process had 3 rounds for QA role. Round 1 was a technical discussion with 30+ questions covering manual testing, API testing, Agile, SQL, bug reporting, testing concepts, and scenario-based questions. Round 2 was a detailed F2F discussion of around 1 hour where interviewer went deep into my project experience. I was asked to explain the complete application flow, draw dashboard structure, explain UI elements, discuss modules, and identify possible loopholes in the application. Initially I was informed that the F2F would be the final round, but later an additional round was scheduled with a Senior Architect. This round was more focused on reasoning and justification behind decisions rather than technical concepts. There were repeated cross-questions around topics like why I chose Playwright over Selenium, why I wanted to move toward a lead role, career direction, etc. I was also asked how I got the interview opportunity and whether I was referred by someone, even though I had applied online directly. The complete process took almost a month and final feedback was shared after about a week from the last round.

      Questions d'entretien [1]

      Question 1

      Questions asked during interview process: Round 1 – Technical Round Tell me about yourself Explain your current project Difference between functional and non-functional testing Smoke vs sanity testing Regression testing Severity vs priority Static testing Verification vs validation White box testing Agile process in your organization Role of QA in sprint planning RTM Bug leakage vs bug release Key elements of bug report API testing in Postman SQL queries (duplicate email, 2nd highest salary) How do you know testing is complete? Scenario-based testing questions Excel upload testing scenarios How would you handle developer disagreement? Production issue handling Round 2 – F2F Technical Discussion Explain complete project flow Draw your dashboard UI Draw profile/menu flow Explain modules in detail Find possible loopholes in your application Real-time testing scenarios Explain defects found in project Agile workflow in project Questions around product understanding and business flow Round 3 – Senior Architect Round Why did you mention bug/test case numbers in resume? Why do you want to become QA lead? What will you do to become lead in next 5 years? Why are you learning Playwright instead of Selenium? Selenium is also improving, then why Playwright? Are you learning Playwright just because people are using it? Why do you want to work with international teams? What do you do in free time to improve technically? Where do you see yourself in next 5 years? Why this QA path and not something else?
      Répondre à cette question