Skip to content
mlmentorship

Free prep resources

Prepare for the role and loop, not the title alone.

Follow one ordered role path, then add only the domain supplement that appears in the actual job and recruiter-provided round breakdown. Everything else is optional breadth.

Subscribe to get the printable workbook by email. Linked examples and blank tracking sheets. Print your saved map below for your own routes and dates.

Before choosing a path

Company titles are inconsistent. Ask for round formats, implementation style, project expectations, and the day-to-day research/modeling/engineering/product mix. If the recruiter cannot provide detail, use the typical rounds in the readiness check and mark uncertainty as risk.

Choose one role

Optional level overlay

Staff through senior-principal ML

Keep the role-specific technical bar, then prove problem selection, cross-team direction, portfolio judgment, delegated technical authority, succession, and reversible strategy.

Open 11-step level path →
Frontier format overlaysAdd one only when recruiting confirms the format.

Agentic codebase

Use when: The recruiter names an existing repository or authorized coding agent.

Replace one implementation repetition with the agentic evaluation-service lab. Practice mapping, bounded delegation, diff review, and proof.

Open practice →

Technical presentation

Use when: The loop includes a project presentation, job talk, or artifact defense.

Prepare 30 minutes around three decisions and reserve 15 minutes for interrupted questions.

Open practice →

Research work sample

Use when: The assessment uses a notebook, API, paper, model, or open-ended investigation.

Run the black-box lab and produce a five-minute claim, evidence, uncertainty, and next experiment readout.

Open practice →

Values and mission

Use when: The loop includes a dedicated values, safety, mission, or senior-leadership discussion.

Prepare four real tensions and practice independent judgment under principled pushback.

Open practice →

Performance trace

Use when: The role centers on kernels, accelerators, training throughput, inference, or systems performance.

Use the released accelerator challenge or inference scheduler and keep an experiment ledger.

Open practice →
Domain supplementsAdd only the technical subject used in the actual role.

A domain supplement changes examples and depth. It does not replace implementation, project evidence, behavioral judgment, or confirmed rounds.

Specialist-domain boundary

The core library is deepest in LLMs, recommendations, general ML, training, and systems. For specialized CV, speech, or RL loops, use the concept collections below for foundations, but obtain a domain-specific paper/project mock from someone current in that field.

What the core library does not yet cover deeply

This site does not attempt to replace general algorithms or SQL interview preparation. The implementation questions stay here only when the task is fundamentally about ML: attention, training-loop diagnosis, memory-bounded retrieval, or mergeable evaluation metrics. Use external, current material for general data structures, framework internals, streaming-data infrastructure, privacy/compliance implementation, advanced causal inference, or a specialist research frontier.

How to use a path

Attempt each linked question before reading, diagnose with its rubric, and schedule retries. Run the simulation only after every expected round has a baseline.