13 categories Beginner to Advanced Real scan tools Used by job seekers worldwide
530+ Practice Questions
13 QA Categories
3 Difficulty Levels
Real Scan Reports

See what TestHawk actually finds.

These are real scan results from live sites — not mock data. Run your own scan in seconds.

Domain scanned
alteredstates.realityexplorers.net
4 pages · Scanned April 2026
47 /100
5 Critical
5 High
8 Medium
16 Low
🐛 JavaScript 7 🔒 Security 8 📈 SEO 15 🔗 Broken Links 4
Domain scanned
quay.io
3 pages · Scanned April 2026
28 /100
0 Critical
1 High
9 Medium
19 Low
♿ Accessibility 12 📈 SEO 9 🔒 Security 6 🐛 JavaScript 2

These are real bugs found in under 30 seconds. What will TestHawk find on your site?

⚡ Scan Your Site Free → Browse all reports

10 Questions, On Us

Click any question to see the answer — plus why interviewers actually ask it.

Manual Testing Beginner
What is the difference between smoke testing and sanity testing?
+
Smoke testing is a broad, shallow pass on the major features of a build — it verifies the app launches, critical flows work, and the build is stable enough for further testing. Sanity testing is narrow and focused: after a bug fix or small change, you verify that specific area works correctly without running the full suite.
Why asked: Tests fundamental QA vocabulary. Candidates who conflate these two reveal gaps in foundational knowledge that would slow them down on the job.
Manual Testing Beginner
How would you test a login form? Walk me through your approach.
+
Start with the happy path (valid credentials), then: invalid password, non-existent email, empty fields, SQL injection attempts (' OR '1'='1), case sensitivity on email vs. password, fields exceeding max length, special characters, account lockout after N failed attempts, concurrent login from two devices, and "forgot password" flow. On mobile: autocomplete, clipboard paste, keyboard behavior.
Why asked: Classic open-ended question to assess systematic thinking. Strong candidates go beyond the happy path immediately and structure their approach (positive → negative → boundary → security).
Automation Intermediate
What is an XPath selector and when would you use it over CSS selectors?
+
XPath is an expression language for navigating XML/HTML tree structures. Use it when: elements lack reliable IDs or CSS attributes, you need to traverse parent-to-child or sibling relationships (../preceding-sibling), or locate elements by text content (//button[text()='Submit']). CSS selectors are faster and more readable for stable attributes — prefer them unless you need the traversal power of XPath.
Why asked: Automation engineers spend significant time writing reliable selectors. This question reveals whether you understand tradeoffs, not just whether you've heard of XPath.
Accessibility Intermediate
Explain WCAG 2.1 Level AA and why it matters for QA.
+
WCAG 2.1 Level AA is the accessibility standard most laws reference (ADA, EN 301 549, AODA). It organizes requirements into four principles — Perceivable (text alternatives, captions, sufficient contrast ≥4.5:1), Operable (keyboard-accessible, no seizure-inducing content), Understandable (readable text, error identification), and Robust (compatible with assistive tech like screen readers). QA engineers are responsible for catching violations before legal exposure occurs.
Why asked: Accessibility is increasingly a legal requirement, not a nice-to-have. Companies want QA engineers who understand compliance, not just functionality.
Security Advanced
What is a race condition bug and how do you test for one?
+
A race condition occurs when two concurrent operations compete for the same shared resource and the outcome depends on their execution order. Classic examples: applying a discount coupon twice simultaneously, double-booking an appointment slot, or crediting a bank account from two concurrent requests. To test: use tools like Apache JMeter or write parallel requests in code to hit the endpoint simultaneously. Check the database state afterward — if you got two credits or two coupon applications, the race condition is confirmed.
Why asked: Race conditions cause real production incidents (financial discrepancies, overselling). Senior QA roles expect you to test concurrency, not just happy paths.
530+ more questions across 13 categories

Manual Testing · Automation · API Testing · Security · Accessibility · Performance · Mobile · Agile · SQL · CI/CD · and more

Unlock All Questions →

What You Get

Built to get you hired.

Not just flashcard questions. Real tools, real reports, real differentiation when you walk into that interview.

🎯

530+ Interview Questions Across 13 Categories

Every question sourced from real QA interviews at software companies. Organized by topic and difficulty so you drill your weak spots first.

Manual Testing Automation API Testing Security Accessibility Performance Mobile CI/CD SQL Agile / SDLC +3 more
▶ Manual Testing — Intermediate "Explain boundary value analysis." → Click to reveal answer ✓ Why interviewers ask this Progress: 47 / 530 complete
📈

Beginner → Intermediate → Advanced

Start at your level. Progress through difficulty tiers as your confidence builds. Each answer includes the "why" behind the question so you actually understand it, not just memorize it.

Beginner Intermediate Advanced
🔍

Practice With Real QA Tools

Scan any URL with the same tools used in real QA roles. Catch accessibility issues, broken links, security headers, performance signals — hands-on, not hypothetical.

📋

Bring a Scan Report to Your Interview

Generate a real QA audit report on a live website and walk your interviewer through it. No other candidate does this. It's the fastest way to stand out when everyone else is reciting definitions.

Accessibility & Compliance Coverage

WCAG, GDPR, CCPA — the compliance topics increasingly tested in QA interviews. Understand what Level AA actually means and how to test for it, not just that it exists.

🛡️

Security Testing Fundamentals

SQL injection, XSS, CSRF, race conditions, broken authentication — the security concepts QA engineers need to know and how to actually test for them in practice.


Pricing

Start for $7.99. Grow from there.

Interview Prep gets you hired. Starter and Pro are for teams that need ongoing scanning after the job offer.

🚀
Launch Special — 50% off Starter, Pro & Scale for your first 3 months. Discount applied automatically at checkout. Limited time.
Best for Job Seekers
Interview Prep
$7.99/mo
5 scans included
Practice Q&A bank + scan credits to build your interview portfolio.
  • 530+ interview Q&A
  • All 13 categories
  • Beginner → Advanced tracks
  • 5 real scan reports / mo
  • Export reports for interviews
  • "Why asked" explanations
Get Interview Prep — $7.99/mo →
Starter
$9.99/mo
$19.99
for first 3 months · then $19.99/mo
For freelancers & lean teams. Ongoing QA scanning after you land the role.
  • 10 scans / month
  • Full issue reports (20+ detectors)
  • Email reports & health scoring
  • Export to Markdown, JSON, CSV
  • 30-day scan history
  • GitHub auto-scan
Get Started — $9.99/mo →
Scale
$99.50/mo
$199
for first 3 months · then $199/mo
For agencies & high-volume teams. Unlimited scans, no per-project limits.
  • Unlimited scans
  • Full interview Q&A bank
  • All Pro features included
  • Team dashboard
  • Custom integrations
  • Dedicated support
Start Scale — $99.50/mo →

🚀 Launch pricing: 50% off first 3 months on Starter, Pro & Scale.  ·  Try a free scan now →

By purchasing, you agree to our Terms and Privacy Policy

Built for teams that ship weekly.

Got the job? TestHawk runs autonomous QA scans on your entire app — no test scripts, no maintenance. Catch bugs before your users do.

Try a Free Scan →
🚀

Pre-Launch Audits

Run a full scan before every release. Catch accessibility gaps, broken flows, and security issues before your users find them. No test suite required.

⚙️

GitHub CI/CD Integration

Auto-scan on every push or PR. Get a health score and issue report so your team catches regressions before they reach production.

Accessibility by Default

20+ WCAG checks on every scan. Flag contrast issues, missing labels, and keyboard traps before they become compliance liabilities.


How It Works

Scan any site. Get a real report.

Paste any URL and get a full QA audit in ~30 seconds. Perfect for generating your interview portfolio piece.

Scanning your app… this takes about 30 seconds
Results in ~30 seconds
Step 01
🔗

Paste Any URL

Drop in any URL — staging, production, or a site you're studying. TestHawk starts crawling immediately. No account needed to try it.

Step 02
🤖

AI Runs the Audit

TestHawk maps the app, discovers pages, triggers forms, tests flows, and checks for accessibility, security, and performance issues.

Step 03
📋

Get a Real Report

A structured report with every issue categorized by severity. Health score from 0–100. Export to Markdown, JSON, or CSV — bring it to your interview.


Your next QA role
is closer than you think.

Get 50 top QA interview questions + weekly tips delivered to your inbox — free.

Join 1,200+ QA teams leveling up their skills — free, no credit card
By signing up, you agree to our Terms and Privacy Policy