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