Need help? Reach out to us
Back to library

Indian IT services

Xebia India Test Engineer Interview: Rounds, Questions and Preparation

For Test Engineer roles at companies like Xebia India

Share with friends

Preparing together? Send them this role's questions.

https://www.cynchrony.in/library/xebia-india-test-engineer

What the job involves

Test Engineers in Indian IT services verify software quality by designing and executing test cases, reporting defects, and ensuring applications meet requirements. They work closely with developers and business analysts in Agile teams, often on client projects across domains like banking, retail, or healthcare. Day to day involves manual testing, basic automation, and participating in defect triage and regression cycles.

Role and Technical Knowledge

  1. 1

    What is the difference between verification and validation in software testing?

    Explain that verification checks if we are building the product right (reviews, inspections) and validation checks if we built the right product (actual testing). Give a simple example like reviewing a requirement document vs executing test cases.

  2. 2

    Explain the defect life cycle with an example.

    Cover stages: New, Assigned, Open, Fixed, Retest, Verified, Closed, and possible Reopen or Deferred. Use a scenario where a login button fails and how it moves through each stage.

  3. 3

    What are the different types of testing you have learned, and when would you use regression testing?

    List functional, non-functional, smoke, sanity, regression, and retesting. Explain regression is done after code changes to ensure existing features still work, often before a release.

  4. 4

    How do you write a good test case? What are the key elements?

    Mention test case ID, description, preconditions, steps, test data, expected result, and actual result. Emphasize clarity, reusability, and traceability to requirements.

Practical Scenarios and Tools

  1. 5

    You find a defect but the developer says it is not reproducible. What do you do?

    Show a structured approach: gather exact steps, environment details, screenshots or logs, try different data sets, and demonstrate to the developer. Escalate if needed with evidence.

  2. 6

    How would you test a login page? List some test cases.

    Cover valid and invalid credentials, empty fields, SQL injection attempts, password masking, forgot password link, account lockout, and session timeout. Mention both positive and negative cases.

  3. 7

    Write a simple SQL query to find duplicate records in a table.

    Use SELECT column, COUNT(*) FROM table GROUP BY column HAVING COUNT(*) > 1. Explain what each part does and why it helps in data validation during testing.

  4. 8

    What is the difference between smoke testing and sanity testing?

    Smoke testing checks critical functionalities on a new build to decide if further testing is possible. Sanity testing checks specific functionality after a minor change to ensure it works.

Behavioural and Situational Questions

  1. 9

    Tell me about a time you found a mistake in your own work or someone else's. How did you handle it?

    Use STAR format: situation, task, action, result. Highlight honesty, attention to detail, and how you corrected it without blaming others.

  2. 10

    You are assigned to test a module you have never worked on, and the deadline is tight. How do you approach it?

    Show prioritization: understand requirements, review existing test cases, ask for help from team, focus on high-risk areas first, and communicate progress regularly.

  3. 11

    Describe a time you had to explain a technical issue to a non-technical person.

    Emphasize simplifying jargon, using analogies, and checking for understanding. Relate it to explaining a bug to a business analyst or client.

  4. 12

    How do you handle pressure when multiple defects are assigned to you at once?

    Talk about triaging based on severity and priority, using a to-do list, and keeping stakeholders informed. Show calm and organized approach.

HR and Company Fit

  1. 13

    Why do you want to join a service-based company like Xebia India rather than a product company?

    Focus on exposure to diverse clients, domains, and technologies. Mention learning opportunities, structured training, and the chance to work on large-scale projects.

  2. 14

    Are you willing to relocate to any city in India or work in different shifts?

    Be honest but flexible. If you are open, state it clearly. If not, explain your constraints politely. Service companies value adaptability.

  3. 15

    What are your salary expectations for this role?

    Research typical fresher salaries in Indian IT services. Give a range that is reasonable and mention you are open to company standards. Avoid giving a single rigid number.

  4. 16

    Where do you see yourself in three years as a Test Engineer?

    Show ambition to grow into automation testing, lead a small team, or gain domain expertise. Align your goals with the company's career path and continuous learning.

Coding round

Test Engineer interviews usually include a coding round. Practise planning the solution out loud, then review code the AI writes from your plan, in Python, Java, C++, C or JavaScript.

Ready to try it for real?

Take a timed test or talk through a mock interview for this role, then see your scores.

This is practice material for Test Engineer roles, written with AI. It is not a list of questions Xebia India or any other company has asked.