Free template · 2026

QA Analyst Job Description Template

A ready-to-use QA Analyst job description for 2026, with the interview scorecard and questions to hire one. Copy it as is or customize it free in about 15 seconds.

Includes the job description, an interview scorecard and questions for every round.

Mid-level in Latin America
$2,750/mo
Same role in the US
$7,500/mo
You save
Up to 63%

All-in monthly cost, 2026 rates.

Job description template
Copy text

QA Analyst

We’re hiring a Mid-level QA Analyst to ensure our products ship with high quality through practical test planning, thorough execution, and clear defect reporting. You’ll work independently on well-defined areas, partnering with engineering and product to reduce regressions and improve release confidence.

Responsibilities

  • Create and maintain test plans and test cases for web and/or API features based on product requirements and acceptance criteria
  • Execute manual testing and structured exploratory testing to validate functionality, edge cases, and regression risks
  • Design, maintain, and review automated tests at the appropriate level of the test pyramid (as needed) to support stable releases
  • Analyze defects, reproduce issues, validate root cause signals, and provide actionable bug reports with logs and environment details
  • Coordinate with engineering on defect triage, including prioritization support and verification of fixes
  • Track quality metrics (e.g., defect trends, test coverage indicators) and use them to recommend improvements to testing workflows
  • Support release readiness by validating critical flows and communicating risks clearly to stakeholders

Must-have qualifications

  • Hands-on experience executing manual testing for web and/or API products
  • Proficiency writing clear, reproducible defect reports (steps, expected vs actual, environment, and evidence)
  • Experience building and maintaining test cases and test plans aligned to requirements/acceptance criteria
  • Ability to perform structured exploratory testing and regression validation
  • Working knowledge of QA fundamentals including test levels, test design techniques, and severity/priority concepts

Nice to have

  • Experience using test management tools (e.g., Jira/Xray/TestRail) to manage test cases and results
  • Experience contributing to automated testing (e.g., Playwright/Cypress/Selenium/API test frameworks)
  • Experience with CI/CD-aware testing workflows (e.g., running tests as part of build pipelines)
  • Familiarity with basic monitoring/logging concepts to support debugging (e.g., reading logs, correlating traces)

What success looks like in 12 months

  • Quality validation for core product areas
  • Reduce recurring defects
  • Improve defect clarity and engineering throughput
  • Strengthen regression confidence
  • Evolve test suite and coverage signals

Logistics

  • Full-time (40 hours a week), remote from Latin America.
  • Working hours overlap with US business hours.

About the company

[About your company: what you build, your stage and team size]

Want it tailored to your stack, seniority and time zone?

Customize with the free generator →
Interview scorecard

Score every candidate against the same bar

Ensure reliable product releases by delivering effective test planning, execution, defect reporting, and quality signal tracking.

Outcomes to measure

What this hire should deliver in the first year. Replace [N] with your own targets.

  • Quality validation for core product areas. Measure: Complete QA coverage for [N] priority features/releases per quarter, with documented test plans and results for each
  • Reduce recurring defects. Measure: Reduce recurring production defects related to [top defect themes] by [X]% over 12 months
  • Improve defect clarity and engineering throughput. Measure: Increase defects meeting acceptance standards for reproduction evidence (e.g., environment, steps, expected/actual, attachments) to [X]% within [Y] months
  • Strengthen regression confidence. Measure: Achieve a regression pass rate of [X]% for defined critical flows in each release over the final [N] releases
  • Evolve test suite and coverage signals. Measure: Add or update [N] test cases and/or automated checks, improving coverage indicators by [X]% (measured via the team’s agreed reporting method)

Competencies and weights

What to evaluate, how much it counts and what a strong answer looks like.

Test planning discipline · 22%
Drives consistent coverage of requirements and acceptance criteria through clear test plans and cases. Evaluated in Round 1.

  • Weak: Creates partial test documentation that omits acceptance criteria mapping or edge-case considerations.
  • Meets the bar: Builds test plans and test cases aligned to requirements, including clear scope and expected results.
  • Strong: Translates requirements into comprehensive test coverage with explicit risk-based prioritization and traceability to acceptance criteria.

Defect reporting quality · 22%
High-quality defect artifacts reduce rework and speed up triage and fixes. Evaluated in Round 2.

  • Weak: Reports defects without reproducible steps, clear expected vs actual, or necessary environment/evidence.
  • Meets the bar: Submits reproducible bug reports with steps, expected/actual behavior, and relevant environment details.
  • Strong: Provides evidence that accelerates root-cause discovery (e.g., logs, screenshots/video, correlation with request/response) and validates fix verification criteria.

Exploratory testing rigor · 18%
Captures issues not covered by scripted cases and identifies high-value regression risks. Evaluated in Round 1.

  • Weak: Explores inconsistently or relies on ad-hoc checking with limited documentation of observations.
  • Meets the bar: Uses structured exploratory sessions and documents findings with clear reproduction pathways.
  • Strong: Applies hypotheses and charters to systematically explore risk areas, uncovering actionable defects and regression gaps.

Independent execution · 16%
Mid-level ownership requires reliable progress without constant guidance on well-defined work. Evaluated in Round 2.

  • Weak: Requires frequent clarification to complete assigned QA work and misses agreed deliverables.
  • Meets the bar: Plans and executes assigned test work reliably, communicates blockers, and meets deliverable expectations.
  • Strong: Proactively clarifies scope, drives completion with minimal oversight, and anticipates downstream impacts on release readiness.

Regression readiness ownership · 12%
Ensures stability by validating critical flows and reducing release risk through disciplined regression checks. Evaluated in Round 3.

  • Weak: Validates only happy paths and does not clearly assess regression impact or release readiness risks.
  • Meets the bar: Performs regression validation for defined critical flows and reports risks based on evidence.
  • Strong: Identifies regression patterns, expands coverage where risk indicates, and communicates release readiness with specific, evidence-backed guidance.

Quality communication · 10%
Clear collaboration with engineering/product is essential for triage, verification, and quality decision-making. Evaluated in Round 3.

  • Weak: Communicates quality concerns vaguely or without actionable context for stakeholders.
  • Meets the bar: Communicates findings, defect status, and verification outcomes clearly with appropriate detail.
  • Strong: Aligns stakeholders on quality signals, supports triage with concise analysis, and drives agreement on next actions.
Interview questions

Questions for every interview round

Each round has an owner, a time box and questions that test the competencies above.

Round 1: Test design & exploratory thinking
QA Lead · 45 min

  1. Walk me through how you turn requirements and acceptance criteria into a test plan and test cases. How do you decide what to prioritize first?
  2. Describe a time exploratory testing found an issue that scripted testing missed. What was your approach and what evidence did you capture?
  3. Give an example of a regression risk you identified. How did you determine which areas to re-test?

Round 2: Defect reporting & independent ownership
Senior QA Engineer · 45 min

  1. Tell me about a defect you reported that led to a fast fix. What did your report include (steps, expected/actual, evidence, environment)?
  2. How do you verify a bug fix? What does “done” look like for you before a change can be considered resolved?
  3. Share an example of QA work you owned independently. How did you plan, execute, and communicate progress without waiting for direction?

Round 3: Release readiness & quality communication
Engineering Manager · 45 min

  1. Describe how you validate critical flows before a release. How do you balance time constraints with risk-based coverage?
  2. How do you communicate quality risks to engineering or product stakeholders when you find issues near release?
  3. Tell me about a time you used quality metrics or defect trends to recommend improvements. What did you change and what was the result?

Red flags to watch for

  • Treats defect reports as “notes” instead of actionable reproduction artifacts (unclear steps, missing evidence).
  • Cannot explain how they derive test cases from requirements/acceptance criteria or relies only on ad-hoc testing.
  • Struggles to describe a structured regression strategy for critical flows or frequently misses repeated issues.
  • Provides vague communication about findings (no specific risks, no clear next actions or verification criteria).

How much does it cost to hire a QA Analyst in Latin America?

In 2026, a senior QA Analyst in Latin America costs $4,250 to $4,875 a month all-in, versus $8,750 in the US: up to 51% less. Mid-level starts at $2,750.

Country

Mid-level

Senior

Argentina

$2,750

$4,250

Brazil

$3,125

$4,625

Colombia

$2,750

$4,250

Mexico

$3,250

$4,875

United States

$7,500

$8,750

Monthly cost in USD, all-in: the talent's salary plus Teilur's flat 20% fee, from our 2026 rates. The United States row shows what the same role typically costs there.

Compare costs in the calculator →

Frequently asked questions

What does a QA Analyst do?

Typical responsibilities include: create and maintain test plans and test cases for web and/or API features based on product requirements and acceptance criteria; execute manual testing and structured exploratory testing to validate functionality, edge cases, and regression risks; design, maintain, and review automated tests at the appropriate level of the test pyramid (as needed) to support stable releases. The full list is in the template above.

How much does it cost to hire a QA Analyst in Latin America?

In 2026, a senior QA Analyst in Latin America costs $4,250 to $4,875 a month all-in, versus $8,750 in the US: up to 51% less. Mid-level starts at $2,750.

Can I customize this QA Analyst job description?

Yes. Teilur's free Job Description & Scorecard Generator rewrites it for your stack, seniority, time zone and hiring urgency in about 15 seconds. No sign-up needed.

More free hiring tools

Keep going with the rest of your hire.

See all free tools →

Need to fill this role?

Teilur shortlists pre-vetted QA Analysts from Latin America in about 5 days. Flat 20% of what you pay, no subscription.