What the IOL tests (and what it doesn’t)
The International Linguistics Olympiad (IOL) is a language-science puzzle competition for high school students (ages 14–19). Problems can be solved without prior knowledge of the dataset, as all necessary information is provided. Students earn points for accurate answers and clear reasoning. The IOL consists of a 6-hour individual contest and a 3–4 hour team contest.
Preparation focuses on quickly identifying patterns, testing hypotheses, and writing clear solutions rather than memorizing linguistics facts.
Core IOL problem types (with what to practice)
1) Language decipherment (texts, glosses, and translation)
You may be asked to match sentences to translations or decode unknown scripts.
- What you do: build a “mini-dictionary,” track recurring chunks, and test translations against all data.
- Common traps: assuming one-to-one word matches; missing different word orders; overlooking affixes that change meaning.
- Practice focus: alignment, reuse, and consistency checks.
2) Morphology (word formation and paradigms)
These problems require inferring tense, number, case, and other grammatical categories from examples.
- What you do: segment words and propose rules (e.g., plural suffix).
- Common traps: mistaking sound changes for irregularities; several morphemes fused together.
- Practice focus: paradigm completion and minimal pairs.
3) Syntax and grammar (structure and word order)
You infer constraints on sentence formation, such as word order and agreement.
- What you do: identify roles (who did what), using repeated markers.
- Common traps: treating optional particles as required; overlooking dual roles of markers.
- Practice focus: labeling functions and verifying your parsing.
4) Phonology (sound patterns and alternations)
You analyze sound occurrences and morphophonemic changes based on neighboring sounds.
- What you do: find distribution patterns and propose rules.
- Common traps: confusing spelling with sound; creating rules that only apply to some cases.
- Practice focus: environment-based rules and systematic checks.
5) Semantics and meaning (logic in language)
Some problems focus on meaning, such as quantifiers and tense distinctions.
- What you do: treat meanings as a constrained system and infer definitions.
- Common traps: applying English categories too literally; ignoring multiple meanings of words.
- Practice focus: contrast sets and writing predictive definitions.
6) Writing systems and scripts (orthography, transliteration, encoding)
These problems involve mapping symbols to sounds or reconstructing characters.
- What you do: build mapping tables and check representation types.
- Common traps: assuming an alphabetic structure; unreliable spacing.
- Practice focus: careful bookkeeping and incremental decoding.
7) Sign languages and non-spoken data (occasionally)
Some IOL problems use signed language or gesture data. You still identify units and structural rules.
A repeatable solving method (use it on every problem)
- Inventory the data: count examples; note knowns and unknowns.
- Start with the easiest anchors: identical words or obvious names.
- Propose a hypothesis: map your segmentation or rule clearly.
- Stress-test it: validate against every example.
- Answer last, explain always: IOL scoring rewards reasoning; show intermediate steps.
Training plan (8 weeks you can reuse)
- Weeks 1–2: Work untimed on past problems, rewriting official solutions.
- Weeks 3–4: Do timed problems (2/week) and maintain an “error log.”
- Weeks 5–6: Simulate half contests with strategy on skipping.
- Weeks 7–8: Complete a full mock set, focusing on clarity in solutions.
Resources (free and structured)
- Past IOL problems: Use the official IOL archive to understand formats.
- ScholarComp practice sets: Organize practice by type and track skills.
- Intro linguistics basics: Short courses can help with terminology.
- Discussion and peer review: Compare approaches in forums after attempting problems first.
Team round preparation (how to practice collaboration)
- Assign roles quickly: designate responsibilities among team members.
- Use “claim and proof” updates: state evidence supporting proposed rules.
- Plan for integration: agree on notation early for consistency.
Last-mile checklist for contest day
- Time management: set checkpoints and keep moving if stuck.
- Neat structure: use tables and clearly separate answers.
- Consistency pass: verify rules against every example before submitting.