Quality Analyst / QA Engineer

About Travel booking is unforgiving territory. Inventory is live, prices shift in milliseconds, and a bug in the booking confirmation flow isn’t just a ticket — it’s a passenger who missed a flight. We’re looking for a QA Engineer who fundamentally understands the travel domain: someone who has worked inside an OTA, aggregator, or travel-tech platform and knows what it means to test against a GDS, validate real-time fare rules, and uncover the kind of race conditions that only appear under live inventory pressure. This role is for someone who reads a user story and immediately starts identifying all the ways it can fail before development even begins. What You’ll Do

• Own the complete QA lifecycle — test planning, case design, regression testing, defect tracking, and release sign-offs.
• Perform API testing across booking, pricing, search, and availability systems beyond just happy-path validation.
• Identify systemic quality gaps and improve QA processes proactively.
• Participate actively in sprint discussions and product reviews by raising edge cases and failure scenarios early.
• Work closely with Product and Engineering teams to ensure quality is built into the system from the beginning.
• Test real-time systems where data changes dynamically between search and booking flows.
• Prioritise regression testing intelligently in fast-moving release environments.
• Maintain high-quality defect documentation with clear reproduction steps, severity, expected vs actual behaviour, and environment details.

Who Is the Right Fit

• Has prior experience working in a travel-tech environment such as OTAs, aggregators, airline systems, hotel tech, or GDS-connected platforms.
• Is comfortable testing APIs using tools like Postman or REST-assured and reading raw JSON responses.
  
• Understands real-world booking system behaviour, fare changes, stale inventory, and race conditions.
• Is proactive, detail-oriented, and naturally thinks in edge cases.
• Can independently drive quality instead of waiting to be told what to test.
• Is familiar with sprint workflows and tools like JIRA.
• Enjoys improving system reliability over time, not just closing tickets.

Not a fit if:

• You don’t have travel domain experience.
• Your experience is limited to UI/manual testing without APIs.
• You’ve never worked with defect tracking or sprint tooling.
• You prefer passive execution over proactive quality ownership.