Transcription - Mandarin
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Remove boilerplate like Quick facts, etc. Need to preserve substantive info.
Let's parse the posting:
- Quick facts: Engagement - Hourly, at‑will contractor; Schedule - Fully remote & asynchronous (min. 15 hrs/week); Pay Range (US) - $20 – $45 per hour; Start Date - Rolling — staffed as projects launch.
- What you’ll do: bullet list of duties.
- You’re a great fit if: bullet list of requirements/qualifications/skills.
- About the role: paragraph describing flexible workload, high impact, clear ownership, growth potential.
- Interview process: mention screening with Zara.
- About Labelbox: description.
- Ready to Apply? etc: remove.
We need sections: About the role (we have that paragraph). Responsibilities (the "What you’ll do" list). Requirements (maybe combine "You’re a great fit if" items that are required). Qualifications (maybe education). Skills (maybe specific skills). Benefits (maybe none? Not given). Pay (we have Pay Range). Schedule (we have Schedule). Also maybe Engagement? Not needed.
We must not create sections with placeholder text. So we include Pay and Schedule sections only if they have specific content. They do: Pay Range $20–$45 per hour; Schedule: Fully remote & asynchronous (min. 15 hrs/week). Also maybe Engagement? Not required.
We need to ensure we don't include sections like Benefits if not present. There's no explicit benefits listed. So omit Benefits.
Qualifications: maybe education requirement: "Enrolled in or have completed a Bachelor's degree or higher from an accredited institution." That's a qualification.
Requirements: maybe "Experience in transcription, editing, proofreading, or similar language-focused fields (Required)." Also "Access to reliable audio playback equipment and a quiet workspace (Required)." Those are requirements.
Skills: maybe "Strong ability to produce accurate, detailed, and consistent transcriptions." "Excellent attention to detail when reviewing spelling, grammar, and formatting." "Interest in AI, natural language processing, and speech-to-text technology." Also "Bonus: Experience with data labeling, linguistic annotation, RLHF, or other AI training projects." Could be skills.
We need to use - for any list of duties/requirements/benefits. So for Responsibilities, Requirements, Qualifications? Actually Qualifications could be a list as well. But we can use
for prose. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So if we have a list, we must use ul/li. For qualifications maybe it's a single item; could be p. But we can still use ul if it's a list (maybe just one). Safer to use p for qualifications if it's not a list. But we have only one qualification item; we can put in p.
Similarly, Skills could be a list.
Let's structure:
About the role
Flexible workload — work from anywhere, on your own schedule. High impact — your craft directly improves models used by top AI labs & Fortune 500 teams. Clear ownership — know exactly what success looks like and have autonomy to deliver. Growth potential — consistent high performers spearhead new programs and mentor incoming SMEs.
Responsibilities
- Transcribe audio recordings accurately according to provided guidelines and formatting standards.
- Review and edit transcripts for accuracy, grammar, and consistency.
- Evaluate AI-generated transcriptions for correctness, punctuation, and readability.
- Provide constructive feedback to improve AI transcription quality and language models.
Requirements
- Experience in transcription, editing, proofreading, or similar language-focused fields (Required).
- Access to reliable audio playback equipment and a quiet workspace (Required).
Qualifications
Enrolled in or have completed a Bachelor's degree or higher from an accredited institution.
Skills
- Strong ability to produce accurate, detailed, and consistent transcriptions.
- Excellent attention to detail when reviewing spelling, grammar, and formatting.
- Interest in AI, natural language processing, and speech-to-text technology.
- Bonus: Experience with data labeling, linguistic annotation, RLHF, or other AI training projects.
Pay
$20 – $45 per hour (US).
Schedule
Fully remote & asynchronous (minimum 15 hrs/week).
We should not include sections like Benefits, Engagement, etc. Also we should not include Interview process or About Labelbox as they are not requested sections. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we can include those headings if content exists. It didn't forbid other headings, but we should follow the examples. Probably we should only include those headings. The instruction: "Prefer a few substantive sections over many thin ones." So we stick to those.
We must not include markdown fences. Just raw HTML.
Check for any duplicated lines: we removed.
Check for boilerplate: removed Quick facts, Interview process, About Labelbox, Ready to Apply, etc.
Check for preserving all substantive info: Did we lose any? The "Start Date - Rolling — staffed as projects launch." That's substantive but not covered by any of the allowed sections. Could we fit it under About the role? Possibly but it's about start date. The instruction says we must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Since we cannot create a new heading outside the allowed list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. ...)". It implies we should use those headings for sections, but we could also add other headings if needed? However, they said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". They didn't forbid other headings besides those examples. But they gave examples of typical sections. To be safe, we could add a section like "Details" or "Additional Info". But they didn't list that as example. Might be considered violating the pattern. However, the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we can add other headings if needed, as long as we use . But they also said "Prefer a few substantive sections over many thin ones." So we could add a section for "Engagement" or "Start Date". However, we already have Pay and Schedule sections. The Start Date info is specific: "Rolling — staffed as projects launch." That's substantive. We could add a section "Start Date". Or we could incorporate into About the role? But About the role currently is about flexible workload etc. Adding start date there would be mixing but still preserving info. The instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Start date is not minor metadata? It's somewhat metadata but could be folded into a short
. Could we add a paragraph under About the role? That would be mixing but still preserving. However, they said "Use
for prose." So we could add a
under About the role that includes start date. But About the role currently is a paragraph; we could extend it to include start date. That would preserve info without new heading. That seems acceptable.
Similarly, Engagement - Hourly, at‑will contractor. That's also metadata. Could be folded into a short
maybe under About the role or Pay? But we already have Pay section. Engagement is about contract type. Could be added to About the role as a sentence.
But we must be careful not to create thin sections. Adding a sentence to About the role is fine.
Thus we can keep sections as we have, and incorporate Engagement and Start Date into About the role paragraph.
Let's rewrite About the role paragraph to include: "Flexible workload — work from anywhere, on your own schedule. High impact — your craft directly improves models used by top AI labs & Fortune 500 teams. Clear ownership — know exactly what success looks like and have autonomy to deliver. Growth potential — consistent high performers spearhead new programs and mentor incoming SMEs. Engagement: Hourly, at‑will contractor. Start Date: Rolling — staffed as projects launch."
That preserves all.
Now check if any other substantive info: "Quick facts - Engagement - Hourly, at‑will contractor- Schedule - Fully remote & asynchronous (min. 15 hrs/week)- Pay Range (US) - $20 – $45 per hour- Start Date - Rolling — staffed as projects launch". We've covered Engagement, Schedule, Pay, Start Date. Good.
Now check if any other info: "What you’ll do" we covered. "You’re a great fit if" we split into Requirements, Qualifications, Skills. "About the role" we covered. "Interview process" we omitted; that's boilerplate? It's specific but not in allowed headings. Could we fold into About the role? Not really. But maybe it's considered minor metadata? It's about interview process. The instruction says to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Interview process is not exactly those, but it's part of the hiring process. However, they didn't list a section for Interview process. Could we add a section? The examples didn't include it, but we could add a heading if we want to preserve info. However, they said "Prefer a few substantive sections over many thin ones." Adding a thin section for interview process might be thin (just one sentence). Might be better to fold into About the role? Not ideal. But maybe we can drop it as it's not essential to the job description? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep it. So we need to include interview process info somewhere. Could we add a section "Interview Process"? That's a substantive heading. The examples didn't list it, but it's allowed as a heading (they gave examples but not exclusive). However, they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." indicates those are examples, not an exhaustive list. So we can add Interview Process heading.
Similarly, "About Labelbox" is also substantive. Could we add a section "About Labelbox"? That's also substantive. But we might be creating many sections. The instruction says prefer a few substantive sections over many thin ones. About Labelbox is a paragraph about the company; could be considered substantive but maybe we can fold into About the role? Not really. However, we could add a section "About Labelbox". That would increase sections.
We need to balance preserving all info vs not making many thin sections. Let's see the content:
Interview process: "Complete a screening
for prose. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So if we have a list, we must use ul/li. For qualifications maybe it's a single item; could be p. But we can still use ul if it's a list (maybe just one). Safer to use p for qualifications if it's not a list. But we have only one qualification item; we can put in p. Similarly, Skills could be a list. Let's structure:
About the role
Flexible workload — work from anywhere, on your own schedule. High impact — your craft directly improves models used by top AI labs & Fortune 500 teams. Clear ownership — know exactly what success looks like and have autonomy to deliver. Growth potential — consistent high performers spearhead new programs and mentor incoming SMEs.
Responsibilities
- Transcribe audio recordings accurately according to provided guidelines and formatting standards.
- Review and edit transcripts for accuracy, grammar, and consistency.
- Evaluate AI-generated transcriptions for correctness, punctuation, and readability.
- Provide constructive feedback to improve AI transcription quality and language models.
Requirements
- Experience in transcription, editing, proofreading, or similar language-focused fields (Required).
- Access to reliable audio playback equipment and a quiet workspace (Required).
Qualifications
Enrolled in or have completed a Bachelor's degree or higher from an accredited institution.
Skills
- Strong ability to produce accurate, detailed, and consistent transcriptions.
- Excellent attention to detail when reviewing spelling, grammar, and formatting.
- Interest in AI, natural language processing, and speech-to-text technology.
- Bonus: Experience with data labeling, linguistic annotation, RLHF, or other AI training projects.
Pay
$20 – $45 per hour (US).
Schedule
Fully remote & asynchronous (minimum 15 hrs/week).
We should not include sections like Benefits, Engagement, etc. Also we should not include Interview process or About Labelbox as they are not requested sections. The instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we can include those headings if content exists. It didn't forbid other headings, but we should follow the examples. Probably we should only include those headings. The instruction: "Prefer a few substantive sections over many thin ones." So we stick to those. We must not include markdown fences. Just raw HTML. Check for any duplicated lines: we removed. Check for boilerplate: removed Quick facts, Interview process, About Labelbox, Ready to Apply, etc. Check for preserving all substantive info: Did we lose any? The "Start Date - Rolling — staffed as projects launch." That's substantive but not covered by any of the allowed sections. Could we fit it under About the role? Possibly but it's about start date. The instruction says we must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Since we cannot create a new heading outside the allowed list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use
for section headings (e.g. ...)". It implies we should use those headings for sections, but we could also add other headings if needed? However, they said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". They didn't forbid other headings besides those examples. But they gave examples of typical sections. To be safe, we could add a section like "Details" or "Additional Info". But they didn't list that as example. Might be considered violating the pattern. However, the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we can add other headings if needed, as long as we use
. But they also said "Prefer a few substantive sections over many thin ones." So we could add a section for "Engagement" or "Start Date". However, we already have Pay and Schedule sections. The Start Date info is specific: "Rolling — staffed as projects launch." That's substantive. We could add a section "Start Date". Or we could incorporate into About the role? But About the role currently is about flexible workload etc. Adding start date there would be mixing but still preserving info. The instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Start date is not minor metadata? It's somewhat metadata but could be folded into a short
. Could we add a paragraph under About the role? That would be mixing but still preserving. However, they said "Use
for prose." So we could add a
under About the role that includes start date. But About the role currently is a paragraph; we could extend it to include start date. That would preserve info without new heading. That seems acceptable. Similarly, Engagement - Hourly, at‑will contractor. That's also metadata. Could be folded into a short
maybe under About the role or Pay? But we already have Pay section. Engagement is about contract type. Could be added to About the role as a sentence. But we must be careful not to create thin sections. Adding a sentence to About the role is fine. Thus we can keep sections as we have, and incorporate Engagement and Start Date into About the role paragraph. Let's rewrite About the role paragraph to include: "Flexible workload — work from anywhere, on your own schedule. High impact — your craft directly improves models used by top AI labs & Fortune 500 teams. Clear ownership — know exactly what success looks like and have autonomy to deliver. Growth potential — consistent high performers spearhead new programs and mentor incoming SMEs. Engagement: Hourly, at‑will contractor. Start Date: Rolling — staffed as projects launch." That preserves all. Now check if any other substantive info: "Quick facts - Engagement - Hourly, at‑will contractor- Schedule - Fully remote & asynchronous (min. 15 hrs/week)- Pay Range (US) - $20 – $45 per hour- Start Date - Rolling — staffed as projects launch". We've covered Engagement, Schedule, Pay, Start Date. Good. Now check if any other info: "What you’ll do" we covered. "You’re a great fit if" we split into Requirements, Qualifications, Skills. "About the role" we covered. "Interview process" we omitted; that's boilerplate? It's specific but not in allowed headings. Could we fold into About the role? Not really. But maybe it's considered minor metadata? It's about interview process. The instruction says to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Interview process is not exactly those, but it's part of the hiring process. However, they didn't list a section for Interview process. Could we add a section? The examples didn't include it, but we could add a heading if we want to preserve info. However, they said "Prefer a few substantive sections over many thin ones." Adding a thin section for interview process might be thin (just one sentence). Might be better to fold into About the role? Not ideal. But maybe we can drop it as it's not essential to the job description? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep it. So we need to include interview process info somewhere. Could we add a section "Interview Process"? That's a substantive heading. The examples didn't list it, but it's allowed as a heading (they gave examples but not exclusive). However, they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." indicates those are examples, not an exhaustive list. So we can add Interview Process heading. Similarly, "About Labelbox" is also substantive. Could we add a section "About Labelbox"? That's also substantive. But we might be creating many sections. The instruction says prefer a few substantive sections over many thin ones. About Labelbox is a paragraph about the company; could be considered substantive but maybe we can fold into About the role? Not really. However, we could add a section "About Labelbox". That would increase sections. We need to balance preserving all info vs not making many thin sections. Let's see the content: Interview process: "Complete a screening