This guide is based on transcription listing descriptions that were read on 2026-10-01 and 2026-10-02. Listing descriptions do not confirm that any particular role is open today, that pay rates are current, or that eligibility criteria are unchanged. Verify those details at micro1 before applying.
The listings reviewed cover more than a dozen languages — Finnish, Norwegian, Danish, Spanish, Hindi, Mandarin, Korean, Japanese, Portuguese, Italian, French, German, Dutch, Cantonese, Tamil, and Telugu — and describe a range of tasks: transcription, transcript review, annotation, and communication with project coordinators. Run through the checks below before you put in an application.
Check 1 — How the work is paid
- The listing descriptions did not state compensation. None of the twenty-one descriptions read for this guide included a pay figure, rate, unit of payment, or minimum delivery volume. The page metadata for every listing also showed no pay information.
- Before applying, ask micro1 in writing: What is the unit of payment — per audio minute transcribed, per hour worked, per accepted task, or something else? What happens to a transcription that is rejected after you submit it?
- Do not assume that every hour you spend listening, reviewing, or annotating is a billable hour. The descriptions do not say, and the form of payment matters to your effective earnings. Confirm the contract terms before you accept work.
Check 2 — What your contract and your profession allow
- Check your current employment contract for exclusivity clauses or outside-work restrictions before taking on any secondary engagement.
- If you work in a field with a professional code — healthcare, law, journalism, research, or any licensed trade — check whether the transcription work you would actually perform raises questions under your professional rules. This guide does not decide that question for you; your professional body, your employer, or a qualified adviser is the right place to ask.
- Some descriptions explicitly identify contractor roles. Ask a qualified adviser how the actual contract affects your tax obligations in your jurisdiction.
Check 3 — Whether your country is on the list
The listings read for this guide named a long list of accepted applicant countries, including (among others) countries in South Asia, Southeast Asia, East Asia, Central Asia, Europe, Latin America, the Middle East, North Africa, and sub-Saharan Africa, as well as the United States and Canada. The list was the same across all twenty-one listings as of the dates they were read.
- Confirm your country of residence is still on the current list when you apply. Lists can change between the date a listing is posted and the date you read this guide.
- Country eligibility for applying is separate from eligibility for payment. Check whether micro1 can pay contractors in your country through its current payment providers.
Check 4 — Whether the work described is work you do
The listings describe several distinct tasks. Not every listing named all of them, and you should expect to be asked to do the ones your listing specifies.
- Verbatim transcription of audio. Listening to recordings and converting spoken language to written text accurately. Several listings emphasize capturing dialects, regional accents, and speaker nuances — not just the words.
- Review and editing of existing transcripts. Correcting errors, inconsistencies, and ambiguities in transcriptions produced by others or by automated tools. The French listing specifically described correcting machine-generated outputs.
- Annotation and metadata tagging. Adding labels, timestamps, speaker identification, contextual notes, or other structured metadata to audio files or transcripts according to project guidelines.
- Quality assurance. Evaluating transcriptions for consistency and adherence to standards, and flagging unclear audio or content that needs further review.
- Collaboration and feedback. Communicating with project coordinators in writing, clarifying requirements, and contributing suggestions for improving guidelines and processes.
The documented scope also includes Norwegian video transcription and Telugu audio, video, and text work, including segmentation and labelling. The written exercise below covers only checking a transcript against instructions and communicating uncertainty; it does not test listening, dialect recognition, video work, or segmentation.
If you are only comfortable with one of these tasks, check whether the specific listing you are applying to requires the others. The listings are not identical.
Check 5 — Whether you can do it to a spec
Every listing described following detailed, sometimes evolving, project-specific guidelines — not just general transcription conventions you may already know. Ask yourself:
- Can you apply a written style guide you have never seen before, quickly, and maintain it across many hours of audio?
- Can you distinguish what a speaker said from what you think they meant, and transcribe the former?
- Can you flag an ambiguity in writing — clearly enough that a coordinator who did not hear the audio can understand what the problem is — rather than guessing?
- Can you handle audio where two languages appear in the same clip? Several listings (Spanish, Hindi, Mandarin, Korean, Dutch) explicitly described bilingual audio.
- Can you work with dialectal variation in your language? Finnish, Norwegian, Tamil, Cantonese, and other listings specifically mentioned dialects and regional accents.
The written exercise below lets you practice following a supplied convention and reporting uncertainty. It cannot answer the listening or dialect questions above, or establish overall job readiness.
A written trial with explicit rules
The examples below are illustrative exercises created for this guide, not published micro1 assignments or interview questions.
This exercise prepares for checking a draft transcript against supplied instructions, preserving uncertainty, and reporting an issue to a coordinator. Every line below is invented for this article. There is no audio recording: the reference is a stipulated written input, not evidence of what a real speaker said.
Reference supplied by the fictional coordinator:
00:00 | S1 | I packed three blue cups.
00:03 | S2 | The label reads “luma”.
00:06 | S1 | [unclear: pack/back] it beside the box.
Draft to review:
00:00 | S1 | I packed 3 blue cups.
00:03 | S2 | The label reads luma.
00:06 | S1 | Pack it beside the box.
Local rules for this exercise only: keep the reference’s words, punctuation, timestamps, and speaker IDs exactly. Do not turn words into digits or translate them. Preserve the exact uncertainty marker and send a separate note naming the timestamp and unresolved alternatives. The fictional coordinator has stipulated these rules; they are not an industry standard or a micro1 specification.
Correct the draft and write that note before reading the answer.
Worked answer. The corrected transcript is exactly the three reference lines above: change “3” to “three”, restore the quotation marks around “luma”, and replace “Pack” with “[unclear: pack/back]”. Keep “it beside the box.” after that marker. The note can read: “00:06, S1: the supplied reference leaves pack/back unresolved. The transcript preserves both alternatives; please confirm whether a later version should resolve them.”
A transcript with only the digits corrected is still incomplete: the other two lines also need their specified corrections. A transcript that matches all three reference lines but omits the separate note is missing a deliverable; add the note without redoing the correct transcript. A note that mentions uncertainty does not make a transcript with a guessed word acceptable. These are checks against this exercise’s written rules, not a score of professional ability.
If a real task lacks a rule for uncertainty, ask the assigned coordinator before finalizing the affected segment. A notation you suggest is a provisional proposal; it becomes usable for that task only when the coordinator confirms the rule or approves a documented exception. Do not silently convert your proposal into a final deliverable. In this exercise, the reference and local rules already settle which marker to use.
Check 6 — Questions about the working setup
- Ask which playback, transcription, and annotation tools the project supplies or expects you to use. Several descriptions mention familiarity with transcription tools or platforms; check whether your chosen description frames that as a requirement or a preference.
- Ask how files and instructions are supplied and how completed work is returned. Confirm any equipment or connection requirements instead of inferring them from the word “remote”.
- For work in a script you do not normally type, check the required output format and practice entering invented text in your own working language. This is a preparation suggestion, not an additional requirement announced by micro1.
- Read the chosen description’s language and experience criteria literally. Several descriptions explicitly include English audio or bilingual work; do not extend one listing’s criteria to every language.
If every check passed: next steps
If you have confirmed that you are in an eligible country, that your contract allows outside contractor work, that you can perform all the tasks the listing describes, and that you have a clear answer on how payment works, you are ready to look at current openings.
When you apply, be specific about your transcription experience: the languages, the type of audio (conversational, broadcast, technical, multilingual), and any annotation or quality-review work you have done. The listings consistently ask for demonstrated experience, not just stated fluency.