Responsibilities
End customer‑reported bugs and build an internal safety net that catches critical issues before release.
Triage and reproduce incoming bug reports, trace issues across logs, API calls, and session replays.
Test features in active development and run a regression suite before every release.
Establish QA sign‑off as a standard part of the release process.
Build the quality infrastructure from scratch, defining the strategy, automation, and processes the team currently lacks.
Define the testing strategy, standards, workflows, and documentation from the ground up.
Design and implement an automation framework covering UI, API, and regression suites.
Incrementally grow automated coverage of the highest‑risk flows without disrupting delivery.
Make quality a shared team capability by embedding QA thinking across the development lifecycle.
Track and report quality metrics so reliability is visible to the whole team.
Translate customer bug reports into actionable test cases and durable coverage.
Bring quality into requirements and design, not just release sign‑off.
Qualifications
Experience as the first or only QA engineer at a company or within a team, building a QA function from scratch.
Experience testing complex third‑party integrations (REST/SOAP APIs, external data providers, or similar).
Experience shipping test automation from zero, not just maintaining an existing framework.
Strong hands‑on manual and exploratory testing skills across functional and regression testing for web applications.
Deep API and integration testing, covering edge cases, error handling, data mapping, and contract validation between systems.
Proficiency in defect management and root‑cause analysis.
Judgment in regression risk assessment to define what “safe to ship” looks like for a given release.
Cross‑functional collaboration with developers, product, and customer‑facing teams, and ability to advocate for quality without slowing the team down.
Awareness of the travel/Global Distribution System domain (booking flows, PNRs, fare rules, availability) is a strong plus.
Experience or interest in early‑stage or growth‑stage startups and comfort building structure in ambiguity.
Fluency in English; other languages are a plus.
#J-18808-Ljbffr