Skip to content

JD Knowledge Map

Quick overview Map JD skill keywords to this handbook's pages and knowledge points: a 20+ row "skill keyword → page" mapping table, paired with a "can do / can't do / sort of" three-tier labeling system, to generate a personal study plan and study order.

JD Knowledge Map ​

In one sentence: this page maps skill keywords from hiring JDs one-to-one to this handbook's pages and knowledge points, using a "can do / can't do / sort of" three-tier labeling system to translate "role requirements" into "a personal study plan."

After reading Module Overview & Job Landscape and the JD List, you should have 2–3 target roles and their three-layer skill keywords. Now the task is: map each skill keyword to a concrete knowledge point, and grade yourself.

1. Why Use a "Can Do / Can't Do / Sort Of" Label ​

Most people facing a JD think "I sort of know a bit of everything" — that vagueness is the root cause of interview failures. The three-tier system forces you to give a clear answer:

  • Can do: Can independently execute, explain the principles clearly, handle follow-up questions;
  • Sort of: Have used it but can't explain it clearly, or understand the theory but lack hands-on experience — this is the most dangerous tier and also the one you should prioritize;
  • Can't do: Never encountered it at all. Add to the study queue by priority.

The gold standard for labeling "Can do"

For a knowledge point, you must be able to do at least two of these three things to call yourself "can do": (1) explain the core principle for 10 minutes without notes; (2) write code to reproduce a minimal example; (3) articulate its trade-offs with other methods. Just "having used it" doesn't count.

2. Skill Keyword → Page Mapping Table ​

The table below maps high-frequency JD skill keywords to corresponding pages in this handbook (this is your study plan map — use it directly to grade yourself):

Skill KeywordRelated Knowledge PointsHandbook PageCategory
Transformer / AttentionSelf-Attention, multi-head, positional encodingTransformer Architecture, Attention MechanismArchitecture
BackpropagationChain rule, automatic differentiationBackpropagation & Automatic DifferentiationFundamentals
Neural Network FundamentalsForward pass, layers, lossNeural Network Fundamentals, Loss Functions & Output LayersFundamentals
Training OptimizationGradient descent, Adam, LR schedulingOptimization & Gradient Descent, Training Recipes & Hyperparameter TuningTraining
Initialization & NormalizationXavier, BN/LNInitialization & NormalizationTraining
Overfitting & RegularizationDropout, weight decay, early stoppingOverfitting & RegularizationTraining
Evaluation MetricsPrecision/recall/F1, AUC, NDCGDeep Learning Evaluation & Experimentation, Evaluation in PracticeEvaluation
Data EngineeringData cleaning, annotation, imbalance handlingData & Data Engineering, Datasets & Tool ArchiveData
CNNConvolution, pooling, receptive fieldCNNs & Computer VisionArchitecture
RNN / Sequence ModelingLSTM, GRU, sequence tasksRNN & Sequence ModelingArchitecture
LLM Fine-tuningInstruction fine-tuning, LoRA, alignmentLarge Language Models (LLMs)LLM
RAGRetrieval, vector DBs, augmented generationLarge Language Models (LLMs)LLM
MultimodalImage-text alignment, fusionMultimodal ModelsDirection
Generative ModelsVAE, GAN, diffusion modelsVAE & GAN, Diffusion Models & Generative AIDirection
Reinforcement LearningMDP, policy gradient, applicationsDeep Reinforcement Learning, Deep RL ApplicationsDirection
Recommender SystemsCTR prediction, recall & rankingDeep Learning Recommender SystemsDirection
Graph Neural NetworksGraph convolution, message passingGraph Neural NetworksDirection
Speech & AudioAcoustic modeling, ASR/TTSSpeech & AudioDirection
Pre-training & Representation LearningSelf-supervised, pre-training paradigmsRepresentation Learning & Pre-trainingFundamentals
DeploymentServing, inference optimizationMLOps & Model DeploymentEngineering
Distributed TrainingData parallel, hybrid parallelTraining Recipes & Hyperparameter TuningEngineering
Debugging & DiagnosisExploding/vanishing gradients, NaNDebugging & Diagnosis, Common Pitfalls & Anti-patternsEngineering
Framework SelectionPyTorch/JAX/framework comparisonHow to Choose Frameworks & ToolsEngineering
Interpretability & FairnessExplainability, biasInterpretability & FairnessEngineering
Hands-on PracticeBuilding from scratch, portfolioBuilding a Deep Learning Project from Scratch, Portfolio ProjectsPractice
Paper Reading SkillsPaper reading methods, frontiersGetting Started, Frontier ProgressResearch

How to use this table

This table only includes knowledge points that "need dedicated study." If you've already systematically studied a corresponding page through the Learning Paths, just mark it as "can do" — no need to re-study.

3. Generating a Study Plan: Three-Step Method ​

Step 1: Grade Yourself ​

Compare the table above with each skill keyword appearing in your target role's JD, labeling each as "can do / sort of / can't do." Focus on the JD's hard requirements — the bonus qualifications can be filled in later; the threshold layer must be prioritized.

Example (LLM Application Engineer):

Skill KeywordLabelRationale
TransformerSort ofCan call the API but can't explain the attention formula
PyTorchCan doBuilt complete training scripts independently
Distributed TrainingCan't doOnly run on single GPU locally
LLM Fine-tuningSort ofRan LoRA but don't understand the principle

Step 2: Prioritize ​

Order by priority from high to low:

  1. Threshold + Can't do: Highest priority — may directly determine whether your resume passes screening;
  2. Threshold + Sort of: Second priority — filling in the "can explain clearly" capability;
  3. Bonus + Can't do / Sort of: Fill in if time allows — determines whether you can stand out.

Within the same priority, order by "study cost → high": reading a concepts page > running a notebook > building a complete project. Use the Progressive Tutorial: Three Versions Running to warm up before tackling harder knowledge points.

Step 3: Generate Study Order ​

Write the prioritized results into a checklist with deadlines, for example:

OrderKnowledge PointTarget PageSuccess CriteriaTimeline
1Attention MechanismAttention MechanismCan derive softmax(QKᵀ/√d)V by handWeek 1
2Training OptimizationOptimization & Gradient DescentCan explain the difference between Adam and SGDWeeks 1–2
3LLM Fine-tuningLarge Language Models (LLMs)Run LoRA fine-tuning on an open-source modelWeeks 3–4
4Distributed TrainingTraining Recipes & Hyperparameter TuningUnderstand and reproduce the DataParallel exampleWeeks 5–6

4. Study Focus for Three Typical Profiles ​

Profile A: Career Changer / Beginner ​

Background: Knows Python, halfway through the DL fundamentals pages. Study focus: Master the three pages on Neural Network Fundamentals, Backpropagation & Automatic Differentiation, and Optimization & Gradient Descent, with code reproduction. Then pick one case-study page for a project based on your target direction. Don't chase LLMs right away — without a solid foundation, your resume and interviews will fall apart under follow-up questions.

Profile B: CS/ML Graduate Student ​

Background: Has taken courses, reads papers, but lacks hands-on practice. Study focus: Move "sort of" and engineering skills forward — Training Recipes & Hyperparameter Tuning, Debugging & Diagnosis, MLOps & Model Deployment; simultaneously use the Paper Map to connect classic papers in your field into a system, preparing for the "research deep-dive" section of interviews.

Profile C: Software Engineer Pivoting to Algorithm ​

Background: Strong at coding, weak in ML theory. Study focus: Build Math Primer, Loss Functions & Output Layers, and Deep Learning Evaluation & Experimentation — these are "frequently asked in interviews but rarely used in engineering." Your strength (engineering ability) should be reflected in quantified results on your resume — see Capability Match.

5. Self-Assessment During Study ​

After finishing each knowledge point, go to the Interview Question Bank and self-test with related questions:

  • Can you talk about it for 3 full minutes without notes?
  • Can you answer a "why not use another method?" follow-up?
  • Can you write a minimal code example under 20 lines?

If you pass all three, change the skill keyword from "in progress" to "can do." In this way, your study plan itself becomes your career progress tracker — more controllable than blindly grinding problems.

Further Reading ​

References ​