QA interview questions for remote roles, and how to answer them
By the QAAnywhere team · Published November 8, 2026
How remote QA interviews are structured
Remote QA interviews usually run over three to five video calls: a recruiter screen, a technical interview on testing, often a practical task (live or take-home), and a conversation about how you work with a team. The questions below are grouped the same way. For each, the goal is not a memorised answer but a clear structure you can apply to whatever the interviewer asks.
The topics reflect what remote QA listings stress. Among the 99 roles on QAAnywhere with a full description on 8 November 2026, 52 mentioned CI/CD, 42 mentioned APIs, 51 mentioned bug reporting or Jira, 22 mentioned Agile or Scrum and 17 mentioned SQL.
Test design questions
"How would you test a login page?" (or a search box, a file upload, a payment form)
This is the most common QA interview question, and it is about structure, not a list. A strong answer:
- Clarify. What kinds of login (password, single sign-on, two-factor)? Which platforms? Any lockout rules?
- Functional cases. Valid login; wrong password; unknown user; empty fields; case sensitivity; remember me; password reset link.
- Security. Rate limiting and lockout; error messages that do not reveal whether an account exists; passwords never in URLs or logs; session expiry.
- Usability and accessibility. Labels, keyboard navigation, screen reader announcements for errors, password managers working.
- Non-functional. Response time under load; behaviour when the identity service is slow.
- What to automate. API-level checks for the rules, a couple of UI tests for the main path, and the rest exploratory.
Ending with what you would automate, and at which level, shows you think like an engineer, not a checklist.
"You have two days before release and can't test everything. What do you do?"
Talk about risk: what changed, what users touch most, what would hurt most if broken (money, data, security), and what is already covered by automation. Then say how you would communicate what you did not test, and who decides whether to ship.
API testing questions
- "What is the difference between 401 and 403?" 401: not authenticated (missing or invalid credentials). 403: authenticated but not allowed.
- "How would you test a POST /orders endpoint?" Valid creation and the stored result; required and invalid fields; authorisation, especially one user acting on another's data; duplicates and idempotency; the response contract; side effects.
- "How do you handle test data for API tests?" Create it through the API in setup, keep tests independent, clean up afterwards, and never rely on shared hand-made data.
SQL questions
Many QA roles expect you to check data directly. Typical tasks:
- Find orders without a matching customer (a
LEFT JOINwithWHERE customer.id IS NULL). - Count orders per status (
GROUP BYwithCOUNT). - Find duplicate emails (
GROUP BY email HAVING COUNT(*) > 1).
Practise writing these by hand; some interviews use a plain shared document.
Automation questions
"How would you design a test automation framework for our web app?"
Cover layers (tests, page objects or screen models, API clients, test data builders, configuration per environment), how tests run (locally and in CI, in parallel), reporting, and how you keep it maintainable (code review, conventions, removing flaky tests). Mention what you would not automate.
"A test passes locally and fails in CI. How do you investigate?"
Look at the CI logs, screenshots, videos or traces; compare environments (browser version, screen size, time zone, data); check for timing problems and shared state between tests; reproduce with the CI configuration locally. Then fix the cause rather than adding retries. See the guide to flaky tests for more.
"Why not use fixed sleeps?" They make tests both slow (always waiting the full time) and flaky (sometimes not long enough). Wait for a specific condition instead.
Coding tasks. Expect an easy problem in your chosen language (reverse words in a string, find duplicates in a list, parse a small JSON response) or a short automation task such as writing one UI or API test. Talk through your approach while you code.
Process and collaboration questions
- "A developer says your bug is not a bug." Return to the requirement or the user impact, bring evidence (steps, logs, a screen recording), and involve the product owner if it is a question of intended behaviour. Stay curious rather than defensive.
- "How do you work in an Agile team?" Testing during the sprint, not after it; reviewing stories for testability before development; pairing with developers; automating as part of the definition of done.
- "What makes a good bug report?" A clear title, steps, expected and actual results, environment and evidence, and severity. The guide to writing bug reports goes into detail.
Remote-specific questions
Interviewers want to know you can work well without supervision:
- "Tell me about a time you were blocked and nobody was available."
- "How do you keep developers in another time zone informed?"
- "How do you decide when to message someone versus write it down in a ticket?"
Answer with real stories: the situation, what you did, and what happened. Mention written habits: clear tickets, short recorded walkthroughs, test notes that others can follow.
Questions to ask them
Good questions show judgement and help you decide:
- How is quality shared between developers and testers here?
- What runs in CI today, and how long does it take?
- What was the last serious bug that reached production, and what changed afterwards?
- How many testers are there, and in which time zones?
Preparing in a week
- Write out answers to the test design questions above for two products you know well.
- Do five small SQL exercises and five easy coding problems in your language.
- Prepare four stories: a great bug you found, a disagreement, an automation improvement, and a time you worked independently.
- Test your camera, microphone and screen sharing on the interview tool.
The roles below are the newest on the board. Each listing shows where you can work from, so check that before applying.