Travel Agent

$20–35/hrrate as listed

Experienced travel agents review and grade AI-generated itineraries, booking logic, and destination advice for accuracy and practicality. Work is remote and task-based through micro1, with observed pay between $20 and $35 per hour depending on assessment results and task type.

Summary, eligibility guidance and screening preparation are prepared by Sidequest from the platform's posting. Check the source listing before applying.

What the work involves

You are the reality check on travel content an AI model produces. A typical task queue includes multi-city itineraries with unrealistic connection times, hotel recommendations that no longer exist, visa and entry-requirement claims stated with false confidence, and fare rules summarized incorrectly. You read the model's output, decide whether a real client could act on it without harm or wasted money, and write a short rationale that explains the failure precisely — "the LCC transfer at CDG assumes airside connection that isn't available on separate tickets" rather than "this is wrong."

Other work formats appear depending on the project: side-by-side comparisons where you rank two responses, rubric scoring across dimensions like factual accuracy, feasibility, and completeness, and prompt authoring where you write realistic client scenarios the model is expected to handle. Some projects ask for a corrected gold-standard answer alongside the critique.

What the platform screens for

micro1 runs an AI-led interview before any project assignment. It probes for verifiable industry experience — GDS systems you've actually operated, consortium or host agency affiliations, IATA or CLIA credentials, destination or product specializations. Expect follow-up questions that go a layer deeper than your first answer; generalists who describe travel in terms of vibes rather than fare construction, supplier terms, and entry rules tend not to advance. Written clarity matters as much as knowledge, since your rationales become training signal.

Logistics

Fully remote and asynchronous; you claim tasks from a queue rather than working set shifts
Volume fluctuates by project — some weeks offer 5 hours, others 25+
Pay observed in the $20–35/hr range, not guaranteed; rate typically reflects assessment score and project complexity
Contractor engagement, paid per approved task or tracked hour depending on the project

What they look for

Customer Service
Reading Comprehension
Scheduling
Negotiation
Sales

Before you apply

Would you pass this screen?

Drawn from what this listing actually requires. Answered in your browser — nothing is sent to us, and we do not store your answers.

Have you booked travel professionally using a GDS system, reviewed travel itineraries for accuracy, or worked in travel agency or travel-content quality assurance within the past 5 years?
Active travel booking or QA experience · required
Do you hold or have you held an IATA certification, CLIA certification, consortium or host agency affiliation, or equivalent travel-industry credential?
IATA, CLIA, or travel-industry credential · preferred
Can you name a specific destination region, visa regime, or travel product category (e.g., rail passes, LCC booking rules) where you have hands-on professional experience and can speak to current, non-obvious details?
Specialist knowledge of a major destination or product · preferred
Is English your primary working language, and have you written detailed explanations, critiques, or documentation in English professionally?
Written communication in English · required

0 of 4 answered

Included with this listing

Interview prep — 11 questions

Matched to what this platform's screening actually measures. Answer each out loud in 60–90 seconds: claim → concrete example → implication.

What it tests: Whether the candidate has hands-on experience with actual booking tools (Amadeus, Sabre, Galileo) versus theoretical knowledge, and depth in at least one system—critical for spotting realistic vs. impossible itineraries.
A strong answer: Name a specific GDS (Amadeus, Sabre, or Galileo), describe how long you used it professionally, and give one concrete detail about how it works—seat selection, fare rules display, or connection time rules—that shows you've actually navigated it.
Where people lose it: Saying 'I'm familiar with GDS systems' or naming systems without specifying which you truly used day-to-day; vagueness signals you're relying on secondhand knowledge when evaluating model outputs requires operational certainty.