Level overlay
Keep your role path.
This sequence adds level evidence to Applied Scientist, MLE, Research Scientist, or Research Engineer preparation. It does not replace the role's coding, math, research, or systems bar. Choose the underlying role pathStart with a closed-book baseline
Design before reading the reference answer.
Use 60 minutes. Ask an observer to challenge the platform boundary, one technical invariant, the migration plan, and an upper-IC portfolio choice. Start the platform case- 01
Calibrate scope with evidence
Map stories by problem ownership, technical depth, influence, portfolio scope, delegated authority, durability, and succession.
- 02
Baseline a staff architecture case
Attempt the case closed-book before reading. Preserve contracts, migration, ownership, adoption, and reversibility.
- 03
Design an enterprise agent platform
Defend delegated authority, tool effects, durable execution, memory, evaluation, regional policy, and provider portability.
- 04
Study an annotated upper-IC mock
Compare each challenged turn, weak alternative, score change, and retry drill before repeating with new constraints.
- 05
Defend problem selection
Compare credible investments and explain the counterfactual cost of the work you chose.
- 06
Reframe an ambiguous mandate
Challenge the requested solution only when evidence supports a better problem definition.
- 07
Quantify architecture trade-offs
Turn quality, latency, reliability, staffing, and cost into an explicit decision frontier.
- 08
Defend high-scope ownership
Partition your decisions from team execution and connect influence to measured operating outcomes.
- 09
Expose a wrong bet and recovery
Show the disconfirming signal, cost of delay, stakeholder impact, and the direction you changed.
- 10
Practice influence under conflict
Explain incentives, evidence, and how the decision improved, including cases where your view changed.
- 11
Simulate the level bar
Run architecture, technical strategy, project, delegated-leadership, and retained-domain-depth rounds with an experienced observer.
Choose one domain transfer
Do not complete every case. Select the domain closest to the target role, then use a second domain only to test whether the upper-IC reasoning transfers.
Reasoning systems
Compute allocation, verification, serving, recovery, and portfolio choice.
Recommendation ecosystems
Coupled objectives, creator health, causal uncertainty, rollback, and governance.
Real-time multimodal systems
Temporal alignment, live latency, modality failure, privacy, and shared contracts.
Foundation-model data
Provenance, mixtures, contamination, deletion, infrastructure, and investment boundaries.
AI coding products
Repository context, safe execution, developer control, evaluation, and rollout.
Agent safety controls
Independent monitors, authority reduction, severe tails, evidence, and incident recovery.
Evidence gates
Staff
Show repeated cross-team impact, a technical boundary you owned, a wrong bet and recovery, measurable adoption, and hands-on depth under follow-up.
Principal
Add portfolio choices, multi-year checkpoints, shared-versus-local boundaries, reversibility, and evidence that other technical leaders can carry the direction.
Senior principal
Connect several principal-owned directions through durable doctrine, delegated authority, external adaptability, succession, and evidence that can reverse major choices.
Use the level overlay selectively
Do not force every answer to organization scope. Use direct technical answers for coding, math, and domain questions. Show level through the rounds that test architecture, project ownership, strategy, and influence.
Run the upper-IC simulation · Build the evidence stories · Open the Workbook