AI Training Contributor - Arabic (Egypt) - Remote

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive information. Must not invent or summarize away detail. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting mentions: "Your schedule, your rules. As an independent contractor, work when you want, as much or as little as you want. No fixed hours, no check-ins, no micromanaging." That's schedule info. Also "Get paid quickly and fairly. We respect your time and your expertise. Competitive rates, prompt payments, no chasing invoices." That's pay info. Benefits: "As a 1099 contractor, you won't receive benefits such as health insurance, paid time off, or retirement contributions, and hours are not guaranteed." That's benefits info (though it's stating lack of benefits). Also "Earn recognition for great work. Top contributors unlock higher rates, priority project access, and a platform to be seen as the expert you are." That's maybe benefits? But we can include Benefits section if there is specific content. The posting also mentions "Work on projects that actually matter." etc. But we need to decide sections. We have content about "About The Opportunity" (intro). Could map to "About the role". Then "What You’ll Deliver" -> Responsibilities. Then "Qualifications" -> Qualifications. Then "Why Collaborate with Lilt?" -> Benefits? Actually that's more about why work with them, could be Benefits or maybe "Why Collaborate". But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map "Why Collaborate with Lilt?" to Benefits (since it lists benefits). Also "What To Consider Before Applying" could be Requirements or maybe "Requirements". It includes things like not ideal as full time, fluctuating availability, 1099 contractor, etc. That's more like Requirements or Considerations. Could fit under Requirements. Also "How To Join Our Expert Community" is application instructions, which we must remove (per rule: remove application instructions). So we drop that. Also the later paragraphs about mission, etc. Could be considered "About the role" maybe but we already have that. Might be redundant but we can keep as part of About the role if substantive. However we must not repeat job title as heading, fine. We must not include boilerplate like EEO, privacy policy, AI hiring process, etc. So remove those paragraphs. Now we need to output HTML fragment with

headings and appropriate

or

• . For lists, we need to convert bullet points into
  • . The posting includes bullet-like sentences but not explicit bullet list. We need to identify lists: In "What You’ll Deliver" there are bullet-like lines: "Depending on the task, you may be asked to generate original content or assess AI-generated outputs." then "Deliver culturally relevant and appropriate content by applying local insight into tone, symbolism, visual cues, and market fit." then "Spot common issues such as visual artefacts, inconsistent style, translation errors, or cultural mismatches." then "Provide concise, structured annotations that can be used directly for model improvement." then "Apply evaluation guidelines consistently and participate in calibration and QA processes to ensure aligned scoring and judgment standards". These could be list items. In Qualifications: list items: "Native fluency in the target language", "Strong command of English", "Experience as AI reviewer, annotator, or evaluator preferred", "Comfortable working with both textual and audio/video materials", "Ability to follow detailed guidelines consistently and provide clear feedback", "High attention to detail and ability to thoroughly and accurately categorize content". Could be list. In "Why Collaborate with Lilt?" we have bullet-like sentences: "Your schedule, your rules. As an independent contractor, work when you want, as much or as little as you want. No fixed hours, no check-ins, no micromanaging." That's schedule but also benefit. Then "Get paid quickly and fairly. We respect your time and your expertise. Competitive rates, prompt payments, no chasing invoices." That's pay. Then "Work on projects that actually matter. Contribute to cutting-edge AI and language technology that is shaping how humans and machines communicate." Then "Be part of something bigger. Join a global community of linguists, subject matter experts, and language professionals who are advancing human knowledge together." Then "Grow without limits. As a Lilt contractor you get access to diverse, innovative projects that expand your portfolio and sharpen your skills across industries and domains." Then "Earn recognition for great work. Top contributors unlock higher rates, priority project access, and a platform to be seen as the expert you are." Then "Have fun doing what you love. Bring your language skills to life on projects that are as interesting as they are impactful." We could split into Benefits and Pay and Schedule sections. The posting explicitly mentions schedule and pay. So we should create Schedule section with content about flexible schedule. Pay section with content about competitive rates, prompt payments. Benefits section with content about no benefits (as contractor) plus other perks like growth, recognition, community, fun. However the rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule and pay. Benefits: it states lack of benefits, but also mentions other perks. Could still be considered Benefits section. We'll include Benefits. Now "What To Consider Before Applying" could be Requirements. It includes: Not ideal as full time job or primary income source. Work availability fluctuates with project demand, making this better suited as a supplemental income stream. As a 1099 contractor, you won't receive benefits such as health insurance, paid time off, or retirement contributions, and hours are not guaranteed. Requires reliable availability and commitment. Once you accept a task, we expect quality work and on-time delivery. Most tasks require a minimum of 2 hours per day or 10 hours per week. If your schedule is unpredictable, this may not be the right fit. Geographic restrictions may apply. We cannot engage contractors in regions subject to international embargo or sanctions. As a 1099 contractor, you are solely responsible for your own tax obligations. We recommend consulting a tax professional before engaging. That's more like Requirements/Considerations. We'll put under Requirements. Now "How To Join Our Expert Community" is application instructions, remove. Now the mission statements etc after that could be considered part of About the role? Might be redundant but we can include as part of About the role if it's substantive and not boilerplate. It's about mission, not boilerplate. Could be included. Now we must not include any legal/EEO/privacy etc. So remove those paragraphs at the end. Now produce HTML. Structure:

    About the role

    ... (combined intro and mission)

    Responsibilities

    • ...
    ...

    Requirements

    ... (considerations)

    Qualifications

    • ...
    ...

    Benefits

    ... (benefits info)

    Pay

    ... (pay info)

    Schedule

    ... (schedule info)

    We must ensure we don't create empty sections. All have content. Now we need to extract exact sentences, preserving all substantive information, not inventing or summarizing away detail. Must not omit details. So we need to copy the relevant text verbatim (or close) but we can format into

    or

  • . Must not add extra info not present. Let's gather text. About the role: The posting starts with "About The Opportunity We are seeking detail-oriented human reviewers with a strong understanding of their local cultural context to support a range of AI training and evaluation projects. In this role, you will work across diverse task types, including evaluating prompts and AI-generated outputs, reviewing and correcting text, analyzing multimedia content, contributing voice recordings, among others. You will contribute to ensuring high-quality results by applying careful judgment to factors such as accuracy, clarity, cultural appropriateness, brand alignment, and overall effectiveness in meeting task objectives. This work requires strong analytical skills, attention to detail, and nuanced judgment informed by real-world standards, local norms, and market expectations." Then later after mission: "AI is changing how the world communicates — and LILT is leading that transformation. LILT's mission is to make the world's information available to everyone, no matter the language they speak. Join our global community who thrive on innovation and excellence. Our collective knowledge, uniqueness, and skills deliver multilingual AI and human-verified services to Enterprises, Governments, and AI Developers around the world. Earn money. Have fun. Advance human knowledge. Work on diverse projects from anywhere, any time you want. Get paid quickly and fairly, and build your professional network in a supportive community—all through a streamlined application process tailored to your expertise." But the last sentence about application process is maybe considered application instruction? It mentions streamlined application process tailored to your expertise. Might be considered part of application instructions; but it's not a direct instruction like "submit your application". It's more generic. However the rule says remove application instructions. The earlier "How To Join Our Expert Community" is definitely application instructions and must be removed. The later paragraph about "Earn money..." is more promotional/mission. I'd keep it as part of About the role. Thus About the role paragraph can combine the first paragraph and the mission paragraph (excluding the "How To Join..." part). We'll need to ensure we don't include the "How To Join..." part. Now Responsibilities: The "What You’ll Deliver" section includes sentences. We'll convert each to
  • . List them exactly: - Depending on the task, you may be asked to generate original content or assess AI-generated outputs. - Deliver culturally relevant and appropriate content by applying local insight into tone, symbolism, visual cues, and market fit. - Spot common issues such as visual artefacts, inconsistent style, translation errors, or cultural mismatches. - Provide concise, structured annotations that can be used directly for model improvement. - Apply evaluation guidelines consistently and participate in calibration and QA processes to ensure aligned scoring and judgment standards. We must keep punctuation. Now Requirements: The "What To Consider Before Applying" section. We'll put as

    maybe multiple paragraphs? Could be one

    with all sentences. But we could break into multiple

    for readability. The rule says use

    for prose. So we can have multiple

    elements. Let's extract sentences: - Not ideal as a full time job or primary income source. - Work availability fluctuates with project demand, making this better suited as a supplemental income stream. - As a 1099 contractor, you won't receive benefits such as health insurance, paid time off, or retirement contributions, and hours are not guaranteed. - Requires reliable availability and commitment. - Once you accept a task, we expect quality work and on-time delivery. - Most tasks require a minimum of 2 hours per day or 10 hours per week. - If your schedule is unpredictable, this may not be the right fit. - Geographic restrictions may apply. - We cannot engage contractors in regions subject to international embargo or sanctions. - As a 1099 contractor, you are solely responsible for your own tax obligations. - We recommend consulting a tax professional before engaging. We'll keep each as separate

    or combine? Probably separate

    for clarity. Now Qualifications: list items: - Native fluency in the target language - Strong command of English - Experience as AI reviewer, annotator, or evaluator preferred - Comfortable working with both textual and audio/video