AI-ENGINEERING
    intermediate

    Dataset Engineering

    AI Engineer path · lesson 97 of 124
    The idea
    Teaching by worked examples. A hundred carefully chosen problems with correct, well-explained solutions teach more than ten thousand scraped off a forum — and neither teaches a topic that appears in none of them, however many you add.
    How to use
    Start with the triad: drag quantity to maximum while leaving coverage low, and watch the score refuse to move.
    Three dials, one outcome. They are not interchangeable, and only one of them is usually the thing holding you back.
    55%
    60%
    3.2k
    35% task performance
    Reasonably balanced. From here, more of the same data is the weakest of the three moves available to you.
    quality
    fix first
    coverage
    fix second
    quantity
    fix last

    Key insight

    The order is quality, then coverage, then quantity — and teams reliably work it backwards, because quantity is the only one of the three you can increase without deciding anything.

    Build a fine-tuning dataset

    Sequence

    Order the dataset pipeline.

    Tap a piece, then tap where it goes — or drag it. Tap the tray to take one back.

    1. 1Drop a step here
    2. 2Drop a step here
    3. 3Drop a step here
    4. 4Drop a step here
    5. 5Drop a step here
    6. 6Drop a step here
    6 pieces left to place

    Test your knowledge

    20 questions
    Question 1 of 20
    Score: 0

    The correct priority order for dataset work is:

    The short version

    Teaching by worked examples. A hundred carefully chosen problems with correct, well-explained solutions teach more than ten thousand scraped off a forum — and neither teaches a topic that appears in none of them, however many you add.

    In more depth

    Dataset Engineering

    Once you decide to finetune, the model stops being the interesting variable and the data starts.

    The triad, in priority order

    1.Quality — correct, consistently formatted examples. Annotator agreement is a hard ceiling on your metric.
    2.Coverage — do the examples span the cases you actually see? A case in no example cannot be learned at any size.
    3.Quantity — returns are logarithmic. Fix last.

    Teams reliably work this backwards, because quantity is the only one you can increase without deciding anything.

    Where data comes from

    Human annotation — highest quality, dollars per example. Risk: annotator disagreement caps your metric.
    Production logs — perfectly on-distribution and already paid for. Risk: feedback loops encode yesterday's limitations as ground truth.
    Public datasets — free to download, expensive to trust. Risk: licensing and contamination.
    Model-generated — cheap at any scale. Risk: inherits the generator's blind spots; unverified synthetic data causes collapse.

    Synthesis needs a verifier

    A unit test, compiler, schema validator, database lookup, a second model asked to check, or a human on a sample. Synthetic data is a multiplier on a verifier, not a substitute for data. The held-out eval set must never be synthetic.

    Processing pipeline

    Deduplicate → Clean → Quality filter → Decontaminate → Format & split. Dedup and decontamination are pure upside. The quality filter has the highest leverage and the highest risk — filters trained on "good writing" have repeatedly stripped dialects along with the junk.

    How much?

    50–500 to change format/tone · 1k–10k for a narrow task · 10k–100k to distil a large model into a small one · do not finetune to add knowledge — retrieval is cheaper, updatable and citable.

    Interview Questions

    Google
    Meta
    Amazon
    OpenAI
    Anthropic
    Google
    Meta
    Netflix
    Amazon
    Microsoft
    OpenAI
    Google
    Meta

    Love this visualization?

    Sign up to track your progress, earn achievements, use the AI assistant, and access your personal learning dashboard.

    100% free • No credit card required