Tech check / Fresh check / 01-tech-roadmap.md

Senior Python + AI — Technology Roadmap

Updated 17 min read source
On this page8
  1. Layer 1 — Foundations
  2. Layer 2 — Backend
  3. Layer 3 — Data
  4. Layer 4 — Cloud & Ops
  5. Layer 5 — Frontend (the fullstack claim)
  6. Layer 6 — AI / LLM (the differentiator)
  7. Suggested order
  8. Coverage note

Senior Python + AI — Technology Roadmap

Checklist format. Tick what you can explain and defend under questioning, not what you’ve used.

Every theme links to the notes that answer it. Same convention as Company B (AdTech) — prep map and Tech Check — Theme Navigation: tick the box once reviewed, bold is the primary note, the rest add depth.

Priority: 🔴 core (asked in most interviews) · 🟡 important (asked for your target roles) · 🟢 breadth (nice to have)


Layer 1 — Foundations

🔴 Python

🔴 Python Typing

🔴 Python Async

🔴 Testing

🔴 Git

🔴 Bash / Linux

🔴 Docker

🟢 Kubernetes


Layer 2 — Backend

🔴 FastAPI

🔴 Pydantic v2

🔴 SQLAlchemy 2.0

🟡 Django + DRF

🔴 API Design


Layer 3 — Data

🔴 PostgreSQL

🔴 pgvector

🔴 Redis

🔴 Celery


Layer 4 — Cloud & Ops

🔴 AWS

🔴 CI/CD

🔴 Observability

🟢 IaC


Layer 5 — Frontend (the fullstack claim)

🟡 TypeScript

🟡 React

🟢 Next.js


Layer 6 — AI / LLM (the differentiator)

🔴 LLM Fundamentals

🔴 RAG

🔴 Evaluation

🔴 Agents

🔴 MCP

🔴 LLM Security & Ops


Suggested order

When Focus Why
Now MCP server → RAG eval harness Small, named gaps, and both produce artifacts
Next PostgreSQL tuning → pgvector benchmarking Strongest depth signal, already your stack
Then Async correctness → FastAPI internals Asked everywhere, cheap to solidify
Ongoing Django ORM → Frontend → system design out loud Breadth maintenance

Keep a decisions.md per project: what you chose, what you rejected, why. Interview stories are hard to manufacture under pressure and trivial to harvest from notes.

Coverage note

Checked 2026-08-21: every theme above resolves to at least one existing note — nothing on this roadmap is uncovered by the corpus. Where a theme lives inside a larger note rather than its own file, the section name is given after the link.