Three roles, three very different relationships with the math

AI Field Guides

The same AI landscape looks completely different depending on your seat. An architect treats models as black boxes with shapes, costs and behaviors; an ML engineer opens the box and needs applied math fluency to train, tune and debug what's inside; a research scientist works where the math itself is the product. Pick your track.

How much math each role actually needs

Share of the underlying mathematics required to do the job well

AI Solution Architect system-design intuition Solution Architect — ~10% (arithmetic for budgeting and resource estimation) 10% ML Engineer applied frameworks ML Engineer — ~50% (optimization, tensor shapes, loss behaviors) 50% AI Research Scientist theoretical math Research Scientist — 100% (calculus, statistics, game theory) 100% 0 25 50 75 100%
Each track has its own guide below — from black boxes (10%) through the math under the hood (50%) to the mathematical frontier itself (100%).