QA Circle Jobs

All QA jobs / Resources

QA interview and CV resources

Short, practical notes for testers looking for their next role. Free, like the job board.

Before you apply: CV checklist

Six checks that take ten minutes and decide whether a recruiter reads on.

  • Put the tools you really use near the top.Selenium, Playwright, Postman, SQL, Jira. Recruiters and filters look for them first.
  • Write what you tested and what changed, not only duties."Tested checkout on web and mobile and caught a payment bug before release" says more than "performed manual testing".
  • Use only numbers you can explain in an interview.If you cannot say where a figure came from, leave it out.
  • Match the words in the job post.If it says "SQA Engineer", use that title for the same work on your CV.
  • Link to something real.A small automation project on GitHub, or sample test cases and bug reports with private details removed.
  • Keep it to one or two pages.Newest role first, saved as a PDF named with your own name.

Interview questions to practise

Say your answers out loud. Most of these come up in some form in QA interviews.

Testing basics

  1. What is the difference between severity and priority? Give one bug that is high in one and low in the other.
  2. What goes into a good bug report?
  3. Smoke, sanity and regression testing: when do you run each?
  4. How do you decide what to test when there is not enough time?
  5. Explain boundary value analysis and equivalence partitioning with an age field that accepts 18 to 60.
  6. What is the difference between a test scenario and a test case?

Automation

  1. What would you automate first, and what would you leave manual?
  2. How do you choose locators, and why do long XPath expressions break?
  3. Implicit wait, explicit wait and a fixed sleep: what is the difference, and which do you avoid?
  4. What problem does the Page Object Model solve?
  5. A test passes on your machine and fails in CI now and then. How do you investigate?

API testing

  1. What do 200, 201, 400, 401, 403, 404 and 500 mean?
  2. Besides the status code, what do you check in a response?
  3. What is the difference between PUT and PATCH?
  4. How would you test an endpoint that needs a login token?

SQL

  1. What is the difference between an inner join and a left join?
  2. Write a query that finds duplicate email addresses in a users table.
  3. Count orders per customer and show only customers with more than five.

Scenarios

  1. How would you test a login page?
  2. The build arrives late and the release is tomorrow. What do you do?
  3. A developer says your bug is not a bug. What next?
  4. Tell me about a bug that reached production. What did you change afterwards?

Free places to practise

Official guides and practice sites. All free, and all open in a new tab.

Stay safe while job hunting

  • Never pay for a job. A real employer does not ask for a fee, a deposit or money for training.
  • Apply on the company's own page or its official post, and check the company name and web address before you share documents.
  • Be careful with offers that arrive without an interview.

Ready to apply?

Browse the open QA roles, or join QA Circle to hear about new ones.