📍 CURRENT STATE SNAPSHOT
docs/adr/.Basis: Full application of the MARKET_ANALYSIS_v9_3.md evidence base (never applied to this file) plus fresh July 2026 verification research. Every structural change below traces to that companion document's source register or to the July 2026 re-verification. The complete v9.2 roadmap is preserved unmodified in the Archive section at the bottom of this file.
docs/adr/ directory of numbered, immutable ADRs (context → decision → consequences) and a C4 context diagram (Level 1) alongside the existing Mermaid architecture diagram; lead flagships add a C4 container view (Level 2). (2) the Stage 3 deliverable "one production agentic workflow with … a written architecture decision record" is upgraded to an ADR set + architecture-defense rehearsal (present-and-defend the design against a reviewer, mirroring the FDE panel format). Rationale (evidence-first): ADRs and C4 are the artifacts a hiring manager can interrogate — they turn "I built X" into "here is why I chose X over Y and what it cost," which is exactly the decomposition signal the Applied-AI/FDE loop tests. Cost: $0 (documentation discipline on work already being built). Declined — logged as evaluated, not selected: the TripleTen AI Systems Engineering program itself ($18,000, 9-month) — admission-gated above the current profile, no audited outcomes, and its distributed-systems depth (Kafka, Cassandra, K8s, Terraform, gRPC, service mesh) is already routed through OMSCS Computing Systems (~$8–9K, accredited MS) at lower cost with a degree attached; the RAG/eval/observability half of its curriculum duplicates PolicyPulse + the three-layer eval spine + Arize Phoenix already in the plan. No structural change; version stays v10.0.#dist-s1/2/3 Distribution block folded into each stage body, each with step-by-step setup/join instructions: (S1) local-first + build-in-public — HackGreenville Slack (RefactorGVL 501(c)(3)) + stack-matched local meetups (Greenville Data Science & Analytics, Greenville Python, Upstate AI) + weekly LinkedIn build-in-public that doubles as the AWS-CB content prerequisite; (S2) dbt Community Slack (~100k, timed to DataVault ship, #i-made-this with verified etiquette) + AWS Community Builders (Builder Center, AI-Engineering/Data category) + a Charlotte/Atlanta referral-geography target list; (S3) conference/meetup speaking on-ramps + weighting the apply list to the consultancy-delivered FDE-in-fintech ecosystem (Deloitte/Accenture APBG/PwC). Evidence corrections applied: AWS-CB 2026 applications closed 21 Jan 2026 → target Jan 2027 (not immediate); the doc's "$500 credits / 50% re:Invent / free CloudAcademy" benefits are unconfirmed (verified: 100% cert-exam voucher, promo credits, builder-only sessions); dbt community is ~100k (not ~50k); the doc's Palantir "AI Engineer Socials" could not be verified as a named program and is flagged lower-priority (current Palantir events skew defense/veteran). Cost: $0 (all free communities/meetups; AWS-CB free). Additive-only; archive untouched; no structural teardown; version stays v10.0.pyproject.toml but named no package/environment manager or lockfile, leaving the "reproducible build" claim implicit. Researched against live July-2026 vendor/practitioner sources. Adopted — uv (Astral) as the default Python package/env manager across every project (the 2026 successor to pip + virtualenv + pip-tools + pyenv; Rust-based, lockfile-native). (1) Production standard upgraded — uv.lock now sits beside pyproject.toml in the non-negotiable standard and every scope doc, making the deterministic/reproducible-build claim explicit; project Dockerfiles move from pip install to the lockfile-strict uv sync --frozen idiom (faster, byte-reproducible images). (2) Stage 1 learning — uv added to the Production Python skill line and as a new Core-Course row (Astral's official docs as source-of-truth + Al Sweigart's Invent with Python quickstart as the terse command reference); uv is a CLI tool, not a framework, so the row is docs + one targeted tutorial (~2 hrs), not a multi-week course. The 1099-pipeline pip → uv migration is folded in as a build-in-public artifact (reinforces the CORRECTION 12 Distribution cadence). (3) Conda — ⏸️ CONDITIONAL, one project only — added as a conditional Core-Course row (Anaconda's own "Conda Basics"), scoped to Crucible only, and only if it grows heavy numerical / CUDA / C++ (BLAS/compiled) backends where Conda's binary channels beat wheels; uv alone covers PolicyPulse + DataVault. Evidence corrections applied to the source doc: Anaconda's Conda courses are free-tier, but the Conda Fundamentals certification (Basics + Essentials) is paid-subscription-gated — so it is logged as learning/portfolio evidence, not a recruiter credential (same tier as the Udemy/NVIDIA-DLI completion-cert rule; don't pay for the badge); and the widely-repeated "Astral is now part of OpenAI" line was not asserted (unverified against a primary source — framing kept to "Astral, makers of Ruff"). Cost: $0 (uv free; Conda course free if ever triggered). All 14 project scope documents updated in parallel (standard line + Dockerfile idiom; Conda note in Crucible only). Additive-only; archive untouched; no structural teardown; version stays v10.0.uv.lock, but C4/ADR were the only production-standard items carrying no learning row, no skill-plan line, no toolchain, and no rollout trigger — while the Stage 2 Distribution block already assumed DataVault would ship "with its C4 diagram + ADRs." A timing contradiction sat alongside it: the deliverable was placed in Stage 3, but the standard applies from S1 and DataVault's S2 ship is the first repo a hiring manager opens. Research finding — no credential exists: courses for C4 and ADR do exist, but there is no proctored, recruiter-recognized certification for either (no vendor exam, no Coursera Professional Certificate) — consistent with this roadmap's own "badges ≠ credentials" rule and the <16% hiring-manager cert-weighting datapoint from CORRECTION 7. The correct add is therefore a source-of-truth learning row plus tooling, not a cert line. Market weight verified: ThoughtWorks Technology Radar rates Lightweight Architecture Decision Records in the ADOPT ring (its strongest) and prescribes storing them in source control rather than a wiki — exactly the existing docs/adr/ pattern; AWS publishes a first-party ADR process guide (Prescriptive Guidance, incl. lifecycle, FAQ and a worked example) and a follow-up best-practices post distilled from 200+ ADRs; the Azure Well-Architected Framework features ADRs — i.e. both clouds on this track endorse the practice. Simon Brown's canonical C4 book shipped via O'Reilly on 21 Jul 2026. Adopted: (1) 🆕 Stage 1 Core Course #17 — "Architecture Documentation: C4 + ADR source-of-truth pack" (c4model.com incl. its diagram review checklist and interactive example + free creator talk · AWS Prescriptive Guidance ADR guide · adr.github.io · Fowler's bliki entry). FREE, ~4-5 hrs, ❌ no certificate — matching the vendor-official pattern of Confluent/HashiCorp/Astral/dbt Labs; placed in Stage 1, resolving the timing contradiction. (2) 🆕 "Architecture communication" layer added to the Stage 1 Skill Plan with the ADOPT-ring / dual-cloud market signal. (3) 🆕 Toolchain named — one model, two outputs: Structurizr DSL as the single version-controlled model source (on the ThoughtWorks Radar under Diagrams as code), exported via structurizr-cli to Mermaid for the README — satisfying "C4 alongside Mermaid" from one source instead of two drifting artifacts; Structurizr Lite is free and self-hosts in Docker (already required). ADR template: MADR or Nygard, one only. (4) Rollout bound to a named pass — C4 + first ADRs are written in the same documentation pass as the 1099 pipeline's pip → uv migration (one pass, not two; doubles as build-in-public content), with a hard gate that DataVault's set exists before the Stage 2 dbt-Slack ship post. (5) 🆕 Architectural katas named as the architecture-defense rehearsal mechanism — the Stage 3 deliverable previously named the rehearsal but no method. Ted Neward's katas frame each problem as an RFP where you discover unstated requirements by questioning a "customer," then defend your technology choices under challenge — the decomposition round and the client simulation in one exercise, and free (architecturalkatas.com · The Kata Log · tedneward/ArchKatas). Method: one kata/month M21–M30 → C4 + 3–5 ADRs → self-score against the c4model.com review checklist → present out loud. (6) ⏸️ O'Reilly platform added as a Stage 3 conditional — bundles Simon Brown's ~3-hr creator-taught C4 live course, the C4 book, and the moderated Architectural Katas series; $129/quarter (never the $499 year), triggered only at the M12–14 apply window and only after checking two cheaper routes: ACM Skills Bundle (~$75/yr — but live-event coverage is unconfirmed) and Georgia Tech library access to O'Reilly for Higher Education (unverified for GT; both logged as open items, not asserted). (7) ✅ Snapshot open-dependency closed — the data-portfolio README v8.9 drift is resolved (verified against the live README: v10.0 badge, v10.0 roadmap link, full production standard incl. C4 + ADR). Declined — logged as evaluated, not selected: the two Udemy C4/architecture courses (duplicate free first-party material; Udemy completion certs already rated near-zero weight) · Pluralsight's C4 course (sold as instructor-led professional services for teams, not individually purchasable) · architecture certifications generally (TOGAF / iSAQB CPSA — off-trajectory and unverified; revisit only if a target employer names one). Cost: $0 committed (~$129 conditional if the O'Reilly trigger fires for one quarter). Additive-only; archive untouched; no structural teardown; version stays v10.0.signalcore boundary spec): FIX protocol · a time-series database · market-data ingestion with point-in-time correctness enforced at the storage layer · event-driven / low-latency design patterns. These convert Crucible from "well-engineered backtester" into market-data infrastructure evidence, and each is an additive layer on work already scheduled — no new project, no new spend. (5) 🆕 Falsification-list entry — the quant lane is PhD-weighted; Crucible's defensible claim is execution-safety and market-data engineering, never alpha. (6) 🆕 Employer Program — Domain Credential Track section added, mapping the Daybright program: RPF (ASPPA Retirement Plan Fundamentals — six modules, open-book, untimed, unlimited attempts, ~30–50 hrs study; refreshed April 2026) adopted as the single employer-funded domain credential; SIE logged as a case-by-case reimbursement ask (it is the mandatory foundational half of the Series 7, which sits on Daybright's approved schedule); QKA deferred with reasoning (18 courses in two packages of nine, ~11-week suggested schedule, QKA-1 package $835, and a prerequisite of three years' plan-administration experience or the RPF certificate); CFA · CFP · CAIA · CIMA · the actuarial track logged as evaluated-and-declined despite carrying the largest bonuses — the decisive objection being structural rather than workload: these pay only "upon attaining designation," and each gates that designation behind a work-experience requirement this background plausibly cannot satisfy (CFA's qualified hours must be directly related to the investment decision-making process, which retirement plan administration and data engineering both fail), making the bonus potentially unreachable after ~1,000 hours of study. 🆕 Corrected in-place: an earlier draft of this correction stated CFA was "roughly 900 hours each level" — wrong by ~3×; the accurate figure is ~300 hours per level, ~1,000–1,150 total for a career-changer. Conclusion unchanged, number now correct. 🆕 Falsifier added: large asset managers do weight the CFA culturally, so if the Stage 3 apply list ever shifts toward BlackRock / Fidelity / Vanguard, CFA Level I alone warrants reconsideration. 🆕 CEBS reclassified out of the declined set to ⏸️ CONDITIONAL (Month-8 decision point) on a material distinction: unlike CFA/CAIA/CIMA it carries no work-experience requirement whatsoever, so the $1,000 bonus is genuinely reachable; its curriculum is developed by the Wharton School (a 45-year IFEBP partnership), clearing the roadmap's university-rigor test. The recommended form is RPA, not full CEBS — the five-course program splits into a health track (GBA 1–2), a retirement track (RPA 1–2: qualification requirements, DC/DB, ESOPs, IRAs, SECURE 2.0 — the exact material DataVault, PolicyPulse and FormSense model) and a bridge; taking RPA alone (3 courses) gives ~85% domain relevance instead of ~40%, at ~$2,235+ instead of ~$3,725+, over ~1–1.5 years instead of ~3, with every course still counting toward CEBS later. ⚠️ RPA is not on the employer schedule (CEBS is), so it is a case-by-case ask — argued on the grounds that the RPA courses are a literal subset of the already-approved CEBS curriculum. 🆕 Ladder-fork note added: ASPPA (RPF→QKA→…) and IFEBP/Wharton (RPA→CEBS) are separate ladders that do not stack; ASPPA reads to TPAs and recordkeepers, IFEBP/Wharton reads to consultancies and enterprise benefits buyers — and since the Stage 3 apply list is weighted toward consultancy-delivered FDE-in-fintech, the Wharton brand arguably has the better external portability. Sequencing confirmed unchanged: RPF first and only RPF (~30–50 hrs, open-book, untimed, unlimited attempts, on the bonus schedule, and the ASPPA gate regardless); the ladder itself is not chosen until Month 8. Open items flagged, not asserted: ⚠️ Daybright's schedule names "RPF-1, RPF-2" — the superseded two-exam structure — so the bonus mapping onto the current six-module course is unconfirmed and must be resolved in writing with the program administrator before enrolment; ⚠️ whether Daybright or an affiliate is a FINRA member able to sponsor Series 6/7 is unverified; ⚠️ whether OMSCS (online-only) students qualify for Georgia Tech Library Bloomberg Terminal reservations is unverified — the terminal exists at Price Gilbert, Grove Level and is restricted to current GT faculty, students and staff, but distance-student eligibility was not confirmed; ⚠️ the current CQF price was not asserted (no primary source checked). Declined — logged as evaluated, not selected: JPMorgan Investment Banking and Bank of America Global Markets Sales & Trading Forage job simulations (ungraded, 3–5 hours, no assessments, built for the undergraduate summer-analyst pipeline; Forage's own guidance is to list them as an extracurricular activity, and practitioner forums call them "pretty meaningless as experience points" — for a career-changer targeting engineering they are neutral at best and risk signalling target-role confusion) · CQF and CFA (practitioner screening evidence above) · QuantInsti EPAT (⚠️ evidence quality poor — nearly all located reviews are vendor-hosted; the content overlaps what Crucible builds) · WorldQuant University MScFE (tuition-free and DEAC-accredited, but stacking a second master's alongside OMSCS violates the roadmap's own "replace, not stack" discipline) · CMT. Not adopted from this review (declined at approval): the proposed Employer-Track factual correction regarding Azure-certification reimbursement status, and the proposed Stage-1 deliverable amendment binding the scope-change conversation to the program's pre-approval mechanism. Cost: $0 committed (CS 7646 is $0 marginal; RPF employer-funded; SIE $100 only if the reimbursement ask is declined and the item is elected). Additive-only; archive untouched; no structural teardown; version stays v10.0..cursor/rules/ production-standards pack against the roadmap surfaced the same gap class as CORRECTION 13 (uv.lock) and CORRECTION 14 (C4/ADR): a standard asserted with no implementation named. Finding — three unnamed standards: (a) the Stage 1 skill line required "no-print logging discipline" and the AI rule required per-query observability, but the only named mechanism was stdlib logging.basicConfig with %s interpolation — which produces unqueryable prose lines and leaves every third-party logger (LLM SDKs, httpx, Airflow, Neo4j, PyTorch) emitting an unrelated format; (b) the AI rule required "retry logic with exponential backoff" but named no library, no jitter policy and no idempotency rule; (c) secrets guidance was raw os.environ.get() despite Pydantic already being mandatory and src/config/settings.py already existing in the standard project tree. Adopted — (1) structlog over stdlib logging via structlog.stdlib.ProcessorFormatter. structlog documents four stdlib-integration strategies; only ProcessorFormatter renders foreign (non-structlog) records through the project’s own processor chain via its foreign_pre_chain, which is precisely the requirement — one format for our logs and our dependencies’ logs. Rendering within structlog was declined (third-party output stays unformatted) and python-json-logger was declined (the stdlib formatter owns the event dict, so context silently drops and exceptions are swallowed — the library’s own documented caveat). (2) 🆕 A redaction processor becomes the PII choke point — masking moves from a helper function that must be remembered at each call site to a processor in the chain that runs on every event dict including third-party records echoing prompts or request bodies. For an ERISA-adjacent portfolio this is the single highest-value line in the change set, and it composes with the existing regex baseline in guardrails.py rather than replacing it. (3) 🆕 stamina adopted as the retry standard — an opinionated wrapper over tenacity written by the author of structlog, which auto-detects structlog and logs each scheduled retry through the configured chain, so retry storms become visible with no extra code; capped attempts and total time, jittered backoff, transient errors only, idempotency required on any retried write. Raw tenacity is retained as the escape hatch for policies stamina cannot express; hand-rolled while/sleep loops are barred. (4) 🆕 pydantic-settings named as the single configuration entrypoint — BaseSettings with extra="forbid", required values carrying no default (fail fast at startup, not at 2am mid-pipeline), and every credential typed SecretStr, which masks the value in repr() and model_dump() so a secret cannot leak through a debug print, a traceback or a config dump. (5) Output destination corrected to 12-Factor — stdout only, with rotation and shipping owned by Docker/systemd/the aggregator; the previously specified logs/ai.log and per-domain log files become derived views filtered downstream, since a second handler duplicates and interleaves lines. A WatchedFileHandler remains available as an explicit opt-in for long unattended local runs (Crucible backtests, AFC collectors) — never the default, never in a container. (6) 🆕 An OpenTelemetry trace-correlation processor is stubbed now, activated in Stage 3 — zero cost today, and it prevents a rewrite of every call site when Arize Phoenix / LangSmith land in the S3 observability layer. (7) Structured logs become testable assertions — structlog.testing.capture_logs lets tests assert on fields rather than regex-matching sentences, so audit trails, guardrail activations and reconciliation outcomes get real coverage; cache_logger_on_first_use must be False in tests or assertions silently run against stale config. Contradictions resolved in place: the production-standards checklist previously mandated %s/%d lazy formatting — correct for stdlib, wrong under structlog, where payload data belongs in keyword arguments — and the AI observability block used extra={...}; both are rewritten rather than layered. Learning line (per the CORRECTION 14 rule that no standard ships without one): added to the Stage 1 Production Python skill line as a source-of-truth docs pack (structlog’s Standard Library Logging and Logging Best Practices pages, plus the stamina and pydantic-settings docs) rather than a course row — these are libraries with authoritative documentation, not frameworks, matching the uv precedent from CORRECTION 13; ❌ no certificate exists or is sought. Rollout bound to a named pass: folded into the same 1099-pipeline documentation pass as the pip → uv migration and the first C4/ADR set — one pass, not three — with the first ADR recording the ProcessorFormatter decision and its rejected alternatives. Declined — logged as evaluated, not selected: loguru (competing global configuration; does not route foreign stdlib records through a project-owned chain the way ProcessorFormatter does) · python-json-logger (redundant once ProcessorFormatter is in place) · Pydantic Logfire (vendor-coupled; revisit only if it outperforms Arize Phoenix at the Stage 3 observability decision point) · a dedicated error-tracking service (Sentry) (deferred — no user-facing production surface yet). Cost: $0 (all four libraries are free and open-source: structlog MIT/Apache-2.0, stamina MIT, tenacity Apache-2.0, pydantic-settings MIT). All 14 project scope documents to be updated in parallel (standard line + src/observability/ in the tree). Additive-only; archive untouched; no structural teardown; version stays v10.0.<details> blocks, following the #finopt10 / #dist-s* convention so the section does not dominate the active body) — the three tiers under one brand (free videos · Pro at ~$25–30/mo · Coursera-hosted, covered by Coursera Plus and unaffected), with the price flagged for live re-verification because the help centre deliberately declines to publish a figure. (2) All 20 active DeepLearning.AI course rows corrected in place across Stage 1 (5), Stage 2 (4) and Stage 3 (11): FREE → FREE (videos) and ✅ Yes → ⚠️ Pro only, each linking to the new section. Coursera-hosted DeepLearning.AI rows (marked "Included"), the Anthropic Academy rows and Neo4j GraphAcademy were verified correct and left untouched. (3) 🆕 Lab research recorded — labs are browser-hosted JupyterLab with provider keys supplied (a few need a free third-party key), notebooks downloadable individually or as a workspace with several sets mirrored under the https-deeplearning-ai GitHub org, and courses carry an explicit "End of Access to Lab Notebooks" warning → operational rule: download every notebook during the paid month, because the artefacts outlive the subscription and the environment does not. Decisive enabling fact: certificates earned and progress remain on the account after reverting to Free, which is what makes a one-month sprint rational rather than wasteful. (4) 🆕 Per-stage lab-dependency map added — 🔴 S1 highest (Improving Accuracy · Building & Evaluating Advanced RAG · MCP primer = the eval spine and RAG Triad that become PolicyPulse's blocking gates); 🔴 S2 high (Pre-processing Unstructured Data · Knowledge Graphs for RAG · Vector Databases = embedding pipeline as data infrastructure, messy-PDF extraction, GraphRAG entry); 🟠 S3 medium, a separate month (Agentic AI is the most lab-heavy single row; plus Evaluating AI Agents, LangGraph ×2, Document AI, Automated Testing for LLMOps, PEFT, vLLM); ⚪ AI Prompting for Everyone needs no lab slot. (5) 🆕 Four rows removed from the Pro dependency entirely — the Anthropic-origin S3 rows (MCP Advanced Topics, Agent Skills, Claude Code) route through Anthropic Academy per CORRECTION 10: free, hands-on, official Anthropic certificate. (6) Ruling — Pro is rented, never subscribed: monthly only, never annual; Sprint 1 = all nine S1+S2 lab rows batched into one month (~12–15 hrs of labs) timed to the PolicyPulse eval-harness build, every notebook downloaded; Sprint 2 = remaining S3 labs, one month, ~$30 conditional, timed to the S3 agentic build. (7) 🆕 AMD AI Developer Program logged as ⏸️ OPTIONAL, free tier only — it is open-enrolment, so membership carries no résumé signal and must not be listed as one (the decisive contrast with AWS Community Builders, where selection is the credential); joined, if at all, for one complimentary month of DeepLearning.AI Pro (which takes Sprint 1 to $0) and $100 in AMD Developer Cloud credits (MI300X 192 GB, ~$1.99/hr ≈ 50 hrs, DigitalOcean GPU Droplets) — ⚠️ credits expire 30 days from deposit and a payment method is required even to claim them, so claim only against a scheduled workload; the one legitimate use identified is a PolicyPulse substrate benchmark (one eval suite, one corpus, three inference substrates, reporting retrieval quality / latency / cost-per-query) which the Apple-Silicon stack cannot run. ROCm Blogs external submission (GitHub, AMD editorial discretion) logged as a conditional S3 publication on-ramp only if AMD-specific results ever exist. Declined — logged as evaluated, not selected: the AMD ROCm Certification Program (Associate launched 24 Jul 2026; Professional later 2026; Expert early 2027) on four grounds: wrong layer (it validates ROCm/HIP kernel and memory optimisation, RCCL multi-GPU, vLLM/SGLang serving, Kubernetes + AMD AI Studio — GPU-infrastructure engineering, a neighbouring profession); no local practice loop (ROCm does not run on Apple Silicon — Metal/MLX is a different architecture — so every hour is metered rented cloud against Ollama at $0 unlimited); no track record (days old, no hiring/salary/posting data, failing this file's own evidence rule); no slot ("replace, not stack", with five S3 exams already committed). Market context recorded: NVIDIA holds ~86% of 2026 data-centre GPU revenue and CUDA's ecosystem lock-in is unbroken, so ROCm depth is an ecosystem bet, not a near-term hiring signal. Falsifier: revisit only if a target employer names ROCm or AMD Instinct. Credential canon untouched — a DeepLearning.AI short-course Accomplishment is a completion certificate (Udemy/DataCamp tier, never a Certifications line) and the Surviving Nine (+1 conditional) stands unchanged. Snapshot corrected — the Current State Snapshot read "Corrections 1–14 applied" while the changelog already ran through 16; now 1–17. Cost: $0 committed (~$30 conditional if Sprint 2 fires; $0 for both sprints if the AMD free month covers Sprint 1). Additive-only apart from the 20 in-place cell corrections and the snapshot count; archive untouched; no structural teardown; version stays v10.0.docs/adr/, Dockerfile, eval table, demo GIF, CI, "What I Learned"). Neither said anything about the order a reviewer encounters them in or the language layered on top — so a reviewer met a stack list first and the evidence last. Adopted: (1) 🆕 Production / Cost / Architecture block added (always-visible ruling plus one collapsible <details> block, per the #dlaipro17 / #finopt10 convention). Every flagship README leads with three headings in order — ① Production · ② Cost · ③ Architecture — and every résumé bullet beneath a project answers one of the three; anything answering none is cut. No artifact added, none removed: the entire CORRECTION 8/14 standard stands unchanged. Cost: $0 — it reorganises what is already being built. (2) 🆕 Evidence base recorded with its limits. The framing originated in a single, partly-paywalled 2026 Databricks-focused hiring guide (candidates over-certify while managers value evidence; Production/Cost/Architecture generate callbacks) and was corroborated before adoption: on Production, a 2026 ATS guide reports managers reject résumés reading as a generalist scripting in Python rather than a production pipeline operator, with throughput at pipeline level as the first filter, and a recruiter-facing guide prescribes explicit production cues ("in production", "owned", "on-call", "migrated") and tying tool lists to bullets showing production use; on Cost, a senior-reviewer annotation guide states FinOps for data is a 2026 hiring priority that most résumés hand-wave, and an independent ATS guide reports Greenhouse scorecards require a measurable performance delta — bullets without a runtime, cost or volume figure render blank on the recruiter view and are auto-deprioritised; on Architecture, the strong-bullet definition of named metric against a baseline + method + scope, plus "name the platform and the deploy story, not 'used AWS'". ⚠️ Source-quality flagged in-file: these are résumé-industry and career-content publishers, not peer-reviewed research — adoption rests on convergence across independent 2026 sources plus one checkable mechanism (the Greenhouse/Workday parsing claim), and is recorded as directional. Consistent with, and not disturbing, the CORRECTION 7 finding that <16% of hiring managers rank certifications in their top three résumé signals — this structure is a way of presenting evidence, which is what that finding says counts. (3) 🆕 Parse-failure ruling — diagrams stay in repos. A 2026 ATS guide names the recurring data-engineering failure mode: an architecture diagram rendered as an image, which the parser skips entirely. This roadmap mandates Mermaid + C4 on every project, which is correct for the README where GitHub renders them; the résumé carries the text of the architecture (named components, deploy path, contracts) and a link to the repo. Constraint on surfacing, not a change to the artifact standard. (4) 🆕 Bullet formula: Action + What + Outcome + Proof with the three senior components (named metric against a baseline · method · scope), capped at 4–6 bullets per project, tested by "if it can't answer so what? quickly it isn't doing its job". Honesty discipline binds above the formula: numbers only when defensible in interview; where a metric can't be shared, substitute scale and reliability outcomes (tables, jobs, refresh cadence, incidents, users) as the guidance explicitly endorses — never invent a figure to fill the shape. Cost/speed wins must state the SLA they held to, since a win hiding a reliability regression is the documented bait-and-switch reviewers watch for. (5) 🆕 ERISA constraint made explicit for DataVault — standing rules unchanged (synthetic data only in public repos; financial figures never in public documents): permitted = mechanism, architecture, reliability posture, non-identifying relative deltas, and the regulatory constraints that shaped the design (itself the scarce signal and an ADR topic); prohibited = absolute dollar amounts, participant or plan data, client identifiers, employer-identifying volumes. Consequence recorded rather than hidden: DataVault's public Cost section will be thinner than a normal portfolio project's, and that is correct — the compensating strength is Production, a genuinely deployed depended-upon system most applicants cannot claim at all. Crucible likewise carries no P&L, returns or account figures — methodology and risk control only. (6) 🆕 Per-project map added — DataVault 🟢 Production / 🟡 constrained Cost / 🟢 Architecture; PolicyPulse's Cost story is the strongest available and is produced directly by the CORRECTION 17 substrate benchmark (cost-per-query and latency across inference substrates); Crucible on compute-per-sweep; FormSense and AFC lighter, with Cost explicitly optional — do not manufacture a Cost section where there is nothing to report. (7) Adoption is lazy by design: applied at each flagship's next README touch (no retro-rewrite sprint), propagated to the three public-facing documents at their next alignment pass, and résumé bullets restructured at the Months 12–14 apply window — not before, because that is when they are first read. Snapshot corrected to 1–18. Additive-only apart from the snapshot count; archive untouched; no structural teardown; version stays v10.0.<details> per the #pca18 / #dlaipro17 convention. Tier 1 — production evidence (the three flagships, presented per Production / Cost / Architecture): wins the offer, passes the technical screen (76% of hiring managers say portfolio work can outweigh formal education; a Fortune 500 manager reports hiring bootcamp grads who had built streaming platforms over certified candidates who could not write a basic SQL window function). Tier 2 — accredited degree (OMSCS MSCS): durability and portability; the same MSCS as on-campus, acceptance under 50% for Spring 2025, 72% say degree level still matters and 65% say a master's justifies higher pay. Tier 3 — proctored vendor exams (the Surviving Nine +1): filter-clearing, not winning — the fastest-moving engineers show a recognised cert plus a portfolio with real pipeline code, and certifications matter most for career changers proving baseline competence, after which portfolios and domain expertise outweigh them. Tier 4 — Coursera Professional Certificates and Specializations (IBM GenAI Engineering, AWS Data Engineering, Coursera-hosted DeepLearning.AI): the capstone is the deliverable, not the PDF — matching the existing mid-tier ruling, which is left in place. Tier 5 — completion certificates (Udemy, DataCamp, DeepLearning.AI Accomplishments, Anthropic Academy): skills evidence only, never a Certifications line, per the <16% finding recorded in CORRECTION 7. 🆕 Three qualifications recorded so the ladder is not read as absolute: (a) Tier 1 outranks Tier 2 for hiring but the degree outranks everything for visa frameworks, foreign employers and credential-verified contexts — the order is context-dependent, which matters directly to the Spain path; (b) the employer domain credential track and the optional SIE / BMC block are deliberately not ranked — they sit on a separate axis because their value is the ERISA / regulated-finance moat, a differentiator rather than a competence signal, and ranking them against DP-700 would be a category error; (c) Anthropic Academy is flagged as an anomaly inside Tier 5 — first-party, free, hands-on, and the Pro-free route for four Stage 3 rows per CORRECTION 17, so better provenance than its tier implies, though the tier still governs how it is listed. Operative consequence stated once: Tiers 3–5 are filter-clearing instruments; only Tiers 1 and 2 are differentiators — and the scarcest asset in this file appears in neither column, because it is the regulated-finance domain edge on the separate axis. ⚠️ Source-quality flagged in-file: the percentage figures are from résumé-industry and career-content publishers, not peer-reviewed research — directional only, with the practitioner material and the CORRECTION 7 datapoint carrying the weight. Deduplication reviewed and deliberately NOT executed — a full occurrence audit of the active body found the fragments to be dispersed applications of the rulings, not duplicated rulings (see the review note recorded with this correction), so nothing was removed; the table is an index over them. Snapshot corrected to 1–19. Additive-only apart from the snapshot count; archive untouched; no structural teardown; version stays v10.0.data-engineering slug — the 2026-reviewer pick for exactly this career-changer profile and the correct DEA-C01 on-ramp. (4) dbt ecosystem currency: Fivetran + dbt Labs merger completed 1 Jun 2026 with dbt Core v2.0 + open-source Rust Fusion engine shipping same-day; dbt Learn verified alive post-merger; links updated courses.getdbt.com → learn.getdbt.com; Stage 2 dbt learning noted as Fusion-era. (5) HuggingFace row consolidated: HF renamed and expanded the NLP Course into the LLM Course (fine-tuning + reasoning-model chapters added; classic NLP maintained; chapter-level certificate now offered) — the row listed the same course twice; now once. (6) LangGraph currency: LangChain 1.0 + LangGraph 1.0 went GA Oct 2025 (API stable until 2.0); the two DeepLearning.AI LangGraph shorts predate 1.0 and are annotated conceptual/secondary; LangChain Academy elevated to API-current primary for LangGraph. (7) 🆕 Stage 1 row 11.5 added by approval: Streamlit's 30 Days of AI challenge (Jan 2026 successor to #30DaysOfStreamlit: LLM calls → chatbots → RAG apps on Streamlit + Snowflake Cortex; previews the Stage 2 Snowflake choice; Cortex caveat logged). (8) MITx 6.00.1x currency caveat added (live on edX at the recorded URL, but materials still cite Python 3.5 — credential + computational thinking hold; modern-Python idiom comes from CS50P/uv). Verified-and-held-as-written (live-checked this pass): IBM GenAI Engineering PC (16 courses, ACE-recommended), Mode SQL Tutorial, SQL for Data Science (UC Davis — still a 2026 top pick), KodeKloud Docker (Coursera), Packt Docker & K8s Masterclass (updated May 2025), GenAI with LLMs (AWS+DLAI — fundamentals age slowly, still in 2026 top lists), Total TypeScript tutorials, IBM RAG & Agentic AI PC; all 20 DeepLearning.AI rows, Anthropic Academy rows, Astronomer, Databricks Academy, Snowflake PC, Confluent, HashiCorp, Neo4j and the full cert canon stand as verified by Corrections 3/4/5/10/17 earlier this month with no contradicting signals found. Cost: $0 (every added/swapped item is free or Coursera-Plus-included). Additive-only apart from in-row corrections and the snapshot count; the three swapped/superseded originals are preserved verbatim in the Archive; no structural teardown; version stays v10.0.pre-commit appeared zero times in this 615 KB file and in 11 of 14 project scope documents, while the standard already required ruff, mypy, Conventional Commits and CI. The gap: every quality rule was declared and CI-enforced, but nothing enforced anything at the commit boundary, so the first place a defect could be caught was the last place it was looked for. Researched against live August-2026 vendor and practitioner sources. Adopted — pre-commit as a named production-standard tool with a pinned, tiered hook set. (1) Governing rule (the part that matters more than the tool): the hook set is a strict subset of the CI gate — CI remains authoritative and no check exists locally that does not also run in CI. This forecloses the common portfolio defect where hooks and CI silently disagree, which is a discrepancy an interviewer will find. (2) Tier A (all 14 repos): pre-commit-hooks basics + detect-private-key; astral-sh/ruff-pre-commit with ruff-check --fix ordered before ruff-format, because the linter's fix behaviour can emit changes that then need reformatting (the hook id is ruff-check; the retired bare ruff id is not used); astral-sh/uv-pre-commit → uv-lock, which converts the CORRECTION 13 reproducible-build claim from an assertion into an enforced invariant; gitleaks for secret scanning. (3) Tier B — nbstripout on the notebook-bearing projects (DataVault, ODI, FormSense, AFC, Crucible): this extends the CORRECTION 16 PII choke point from the logging boundary to the git boundary and is the commit-time enforcement of the synthetic-data-only rule, which otherwise depends on remembering to clear notebook output every single time. On DataVault it is the demonstrable form of the ERISA deposition-test guardrail. (4) Tier C — conventional-pre-commit on the commit-msg stage: Conventional Commits was already canon but was declared, never enforced; it is now enforced, installed via pre-commit install --hook-type commit-msg. (5) mypy deliberately excluded — CI-only, recorded as an ADR. The mirrors-mypy hook passes --ignore-missing-imports by default, silently degrading third-party types to Any and producing different results than running mypy directly; if ever wanted locally it must be a local hook with language: system running uv run mypy and pass_filenames: false. The exclusion is a decision with a tradeoff, so it is logged, not omitted. (6) Known risk logged as an ADR — version drift: .pre-commit-config.yaml pins tool versions independently of uv.lock, so upgrading ruff via uv leaves the hook on the old pin and local checks diverge from CI; mitigation is sync-with-uv (or sync-pre-commit-deps) plus a scheduled pre-commit autoupdate --freeze. (7) prek — evaluated, not selected, with a falsifier (same treatment as AMD ROCm in CORRECTION 17): prek is a Rust drop-in alternative that reads the identical config file, ships as a single dependency-free binary, uses uv natively, and is already adopted by CPython, FastAPI, Apache Airflow and Ruff — a clean fit with the ruff → uv Rust-toolchain pattern. It is not adopted now because .pre-commit-config.yaml is the artifact a reviewer recognises and, since prek reads that same file, migrating later stays free and reversible; adopting early buys speed and spends recognisability. Falsifier: adopt if hook install/run time becomes a measured friction point against the 25 hrs/week schedule. (8) Stage 1 learning — amended by the CORRECTION 21 addendum below. pre-commit added to the Production Python skill row, the same treatment uv received in CORRECTION 13: docs plus one authoritative tutorial, no course, no certificate, and platform badges remain barred from Certifications. (9) Adjacent contradiction found and fixed: seven scope documents carried format.sh # Auto-format (black + ruff) in the agentic-harness tree — a stale artifact, since ruff format superseded black and this roadmap's standard names ruff and never black; corrected in place rather than opened as a separate correction. (10) AFC v9.0 §13 held the only existing pre-commit config sketch and it was stale — unpinned, using the retired ruff hook id, and listing mypy in the form that triggers the trap above; rewritten to the pinned, current-id form. Cost: $0 (all hooks free and open-source; no service, no subscription). All 14 project scope documents plus the SignalCore boundary spec updated in parallel — SignalCore takes Tier A + Tier C only (no notebooks; no README/demo standard applies to a pure-computation library) and its §6 governance records that the leakage, golden-value and restatement-replay gates stay CI-side, since a hook that runs a backtest is a hook that gets bypassed with --no-verify. Additive-only; archive untouched; no structural teardown; version stays v10.0.stefaniemolin.com/articles/devx/pre-commit/, ~2 hrs, free). Selected on provenance rather than popularity: Molin is a Bloomberg software engineer who authored hooks that ship in the ecosystem (the numpydoc docstring-validation hook; an EXIF-stripping hook) and speaks at PyCon and EuroPython — she teaches the tool from the inside — and her setup guide is the most independently vetted writing on the topic, featured in PyCoder's Weekly #624, Python Bytes #379, the Real Python Podcast #220 and Talk Python #482. Four separate editorial endorsements is the nearest thing to peer review this subject has. The series maps onto what CORRECTION 21 now requires: Setup Guide teaches the args:-vs-pyproject.toml decision — configuration must live in a config file, not in hook args, to stay consistent across CI, hooks and in-editor checks, which is the version-drift ADR arrived at from the other direction; Behind the Scenes explains that a repo has exactly one .git/hooks/pre-commit executable and that pre-commit install installs the tool's own executable as that hook, which is what makes modular multi-language hooks possible — this is the interview answer, not trivia; Hook Creation Guide covers writing a custom local hook, directly relevant because an ERISA/PII-specific check has no upstream equivalent; Troubleshooting Guide covers the cache and environment errors that otherwise cost hours. Caveat recorded: her examples still show rev: v0.1.5 and the retired bare ruff hook id — read the series for the reasoning and take the configuration from CORRECTION 21. That staleness is itself instructive: it is exactly the drift the pinning discipline exists to catch. Secondary, optional: Talk Python #482 (the Molin episode, ~1 hr, free, passive) as a companion. Evaluated and rejected, with reasons: (a) MLOps Coding Course §5.2 — the obvious candidate, but it has migrated to lefthook + mise and no longer teaches the pre-commit framework; its principles section is excellent and independently corroborates the CI-subset rule adopted above (keep hooks fast; formatters and linters in pre-commit, the full test suite in pre-push; pin the toolchain), so the reasoning is worth reading and the config is not. Logged explicitly because this finding will otherwise cause confusion on a later re-evaluation. (b) Coursera — nothing, despite Coursera Plus making it zero marginal cost; no course treats pre-commit as a subject and it appears at most as a passing mention inside Git or software-engineering surveys. (c) Hypermodern Python Tooling (Jolowicz, O'Reilly 2024) — the only book-length treatment and it does carry a dedicated pre-commit chapter, but it is Poetry-centric and predates uv-as-default, the ruff-check rename and the uv-lock hook; paying to then mentally patch three of its core choices is a poor trade against the 25 hrs/week budget. Revisit only if O'Reilly access arrives free via OMSCS. (d) Udemy / DataCamp — barred by standing policy (CORRECTIONS 4 and 7) and nothing substantive found regardless. (e) Real Python reference page and the pydevtools handbook — both current and accurate, but they are references, not instruction; pydevtools is retained as the currency-checking source for maintenance (it already tracks mypy 2.0, ty-pre-commit and prek). Evidence ruling: the artifact is the claim here — the shipped .pre-commit-config.yaml plus the two ADRs (mypy exclusion; version drift) — not a completion badge. Distribution note: “why mypy is not in my pre-commit hooks” is a strong LinkedIn technical-tips post under the existing three-pillar cadence: a real, non-obvious, defensible finding with a citable primary source that demonstrates judgement rather than tool-listing. Cost: $0. Time: ~2 hrs, absorbed into the Stage 1 Production Python block. Now tracked as row 1️⃣8️⃣ of the Stage 1 Core Courses table, mirroring row 1️⃣7️⃣ (C4 + ADR) — the established convention for a learning row under a production standard that has no course and no credential behind it, so it is visible and followable in the same place as everything else without implying a certificate exists. Additive-only; supersedes item (8) by amendment, deletes nothing; archive untouched; version stays v10.0.Spark + Python co-occurring more often than Spark + Scala. Consequence: the highest-return "additional language" is depth in the one already held — window functions, query optimisation, warehouse cost awareness, and the Snowflake + SQL / dbt + Snowflake posting pairs — and PySpark is named explicitly as the capturable posting-signal differentiator, reachable through Python with no Scala required. ❌ Rust — evaluated, not selected: the premium is real ($110K–$210K global, senior US $170K–$300K+, postings +35% YoY, TIOBE 13 → 7) but concentrates in senior systems/infrastructure and crypto (systems Rust pays 15–25% above application Rust at equal seniority), and in data engineering the practitioner consensus is that Rust is the language the tools are written in and consumed through Python bindings — Polars, DataFusion, delta-rs — which this roadmap already consumes via ruff and uv at zero language-learning cost; even pro-Rust analysis concedes the general premium compresses as the talent pool doubles roughly every 18 months. Falsifier: re-evaluate at Stage 3 only if Crucible's live-execution path presents a genuine latency/memory-safety requirement — decided by ADR then, not by a course now. ❌ Go — evaluated, not selected: popular and well paid (median $145K–$165K, 15–20% above equivalent Python/JS backend roles; ~12% of client API calls per Cloudflare Radar) but its role concentration is cloud providers/infrastructure, fintech transaction systems and the cloud-native ecosystem — the DevOps/backend/platform lane declined above — and it is absent from DE/AE posting bars. Falsifier: a Stage 3 target employer naming Go in a posted JD. ❌ Java — evaluated, not selected: present at 22.6% of DE postings and 22% of AI-engineer postings, but concentrated in legacy Spark/Hadoop and enterprise JVM shops — the segment PySpark is displacing — with the practitioner verdict that Java and Scala are not required for most DE roles; Scala (17.5%) declined on the same grounds. Falsifier: a target employer posting a JVM-first data platform role. ❌ JavaScript as a separate sprint — declined as redundant: JavaScript appears in 3.4% of DE postings, and more decisively TypeScript is a superset of JavaScript, so the existing Stage 2 row 18 sprint already is the JavaScript sprint. Recorded for the avoidance of doubt: Java and JavaScript are unrelated languages sharing a 1995 naming decision and nothing else. ⚠️ Evidence-quality flagged in-file: the posting percentages come from data-education and interview-prep publishers analysing job-board corpora (a 1,000-posting and a 4,000+-posting analysis among them), not peer-reviewed research; adoption rests on convergence across four independent 2026 analyses producing consistent orderings plus practitioner corroboration, and is recorded as directional — the same standard applied in CORRECTIONS 18 and 19. (5) 🔨 TypeScript + MCP Server Sprint upgraded and re-timed (Stage 2 row 18). Gap found: the sprint shipped an MCP server but produced nothing at the AI-application layer — the layer 2026 sources identify as TypeScript's actual job (Python for the model, TypeScript for the things around the model). Vercel AI SDK added as the Week-2(b) build target — not a course, a deliverable: a streaming Claude-powered UI over PolicyPulse's existing retrieval. Selected on adoption evidence: 62% of TypeScript projects started in 2026 use it, it is the named industry standard for streaming AI UIs, and it is model-agnostic across 25+ providers with the Anthropic-fallback pattern already in production use — matching this file's provider-agnostic architecture. Guardrail recorded: TypeScript stays the last mile only; the same sources are explicit that TS frameworks lack the depth for complex multi-agent collaboration and long-horizon planning, and that agent-core work belongs in Python — so PolicyPulse, AFC and Crucible remain Python-primary. Timing re-anchored: the "~M14" placement was set against the pre-resignation calendar; the sprint now sits immediately before the compressed Q1 2027 apply window so the MCP/TS evidence is fresh at interview, and it is subordinate to DataVault S2 — it never competes with the evidence gate. (6) ⏸️ Packt "Ultimate TypeScript Course" added as OPTIONAL overflow only (per approval). Recorded honestly: this course was not previously in this file (all prior Packt references are the Docker & Kubernetes Masterclass), so this is an addition, not a restoration. Coursera-Plus-included ($0 marginal), ~7 hours, shareable certificate — which is Tier 4/5 on the CORRECTION 19 credential ladder and never a Certifications line. Partial amendment to the v8.9 ruling that declined Coursera TypeScript material as frontend/framework-heavy: that ruling addressed specializations, and this single course covers Node.js alongside browser targets, so the objection applies only in part — the amendment is logged rather than left as a silent contradiction, and the v8.9 ruling otherwise stands. Taken only if the free Total TypeScript tutorials leave a gap; Total TypeScript remains the primary Week-1 spine. (7) Snapshot corrected — the Current State Snapshot read "Corrections 1–20 applied" while the changelog already ran through 21 + addendum; now 1–22. (8) Scope-document propagation deliberately NOT executed in this correction — the 14 project scope documents, the 5 public-facing documents and the 1099_reconciliation_pipeline README (still carrying retired career-path framing) are held for a separate pass after this file is settled, by approval. Cost: $0 (Vercel AI SDK is free and open-source; the Packt course is Coursera-Plus-included; every ruling above is a decline or a confirmation). Additive-only apart from the snapshot count and the two in-row edits to Stage 2 row 18; no course removed, no ruling deleted, no hours figure changed; archive untouched; no structural teardown; version stays v10.0.vercel/ai-sdk-fundamentals-starter). Selected on the same logic that made the HF MCP Course primary in this row: free, vendor-official, hands-on and credentialed. Four supporting reasons recorded: (a) it is v7-current — it teaches the Output.object() API for structured generation and the instructions property for system prompts, where most AI SDK material in circulation is v3-era and stale; (b) Zod carries over directly from this row’s Week 1, so no new prerequisite is introduced; (c) the pedagogy matches this file’s no-vibe-coding standard — it is explicitly not a watch-and-copy tutorial, starting from broken code, progressing through better patterns, using production tools (AI Elements, Zod schemas, Server Actions), debugging real errors and schema validation, with every lesson producing runnable code; (d) its three sections — Foundations, Invisible AI (classification/summarisation) and Conversational AI — map onto the Week-2(b) deliverable directly. (2) 🥈 SECONDARY (optional, per approval): Scrimba — "Build a Support Agent with Vercel AI SDK" (hosted on Coursera). Content maps closely to PolicyPulse rebuilt in TypeScript: vector databases, embeddings, RAG, tool calling, agentic systems, LinkedIn-shareable certificate. ⚠️ Cost unverified — the Coursera page shows Free Trial status, so Coursera Plus coverage must be confirmed at enrolment rather than assumed; if not covered, it is skipped, not purchased. ⚠️ Evidence-quality flag: the 2026 roundup ranking this the best hands-on Vercel AI SDK course is published by Scrimba about Scrimba’s own course — vendor self-promotion, not independent review. The syllabus was verified independently and the content stands on its own; the ranking claim itself is discounted and carries no weight in this selection. Certificate remains Tier 4/5 on the CORRECTION 19 ladder — never a Certifications line. (3) 📖 REFERENCE (free, no certificate): the AI Hero Vercel AI SDK tutorial — TypeScript-focused coverage of streaming, structured outputs, tool calling and agents, authored by Matt Pocock, the same author as the Total TypeScript Week-1 spine already in this row; adopted for instructor continuity at zero cost. (4) ⚠️ PRIVACY-ROUTING AMENDMENT recorded. The official starter repo ships Vercel AI Gateway, which routes prompts through Vercel. Under this file’s privacy-first model-routing rule that is not acceptable for anything but synthetic data: the gateway is swapped for the direct @ai-sdk/anthropic provider (a one-line change the SDK’s provider-agnostic design makes trivial — and an ADR-worthy decision in its own right), and the Week-2(b) build runs synthetic data only. (5) ⚠️ NARROW v8.9 EXCEPTION logged. This material is Next.js/React-based, which brushes the v8.9 ruling declining Coursera TypeScript content as frontend/framework-heavy. The exception is admitted on a single narrow ground: the Week-2(b) deliverable is a UI, so the frontend layer is the target rather than a detour — unlike a general TypeScript specialization. The v8.9 ruling otherwise stands, as does the CORRECTION 22 guardrail that TypeScript remains the last mile only and PolicyPulse, AFC and Crucible stay Python-primary. Cost: $0 for the primary, reference and the SDK itself (free and open-source); the secondary is conditional on Coursera Plus coverage and is otherwise skipped. Additive-only apart from the snapshot count and one in-row addition to Stage 2 row 18; no course removed, no ruling deleted, no hours figure changed — the CORRECTION 22 hours deferral stands; archive untouched; no structural teardown; version stays v10.0.19 chosen over the 16.5-style fractional precedent, because sibling numbering would understate the point of the split — these are different purposes, not variants of one course. (4) ⏱️ Time budget — NO NET TIME ADDED (per approval): row 19 is carved from row 18’s existing 2-week block, not added on top (Weeks 1–2 MCP/TS core → Week 2(b) onward row 19); row 18’s duration cell is marked shared and the total is unchanged. This was decided deliberately because the hours model remains frozen at 25 hrs/week pending the CORRECTION 22 deferral — adding time here would have quietly spent hours not yet allocated. (5) Pointer added in row 18 to row 19 so the split is navigable without editing the older changelog entries. (6) Snapshot corrected 1–23 → 1–24. Cost: $0 — no course added, removed or substituted; this is a presentation split of existing content. Archive untouched; no ruling deleted, no hours figure changed; version stays v10.0.<details>/<summary> disclosure blocks, each with a short bold lead line left visible and the full text one click away. Visible height drops to roughly 450 (row 18) and 410 (row 19) characters — at the table median. (2) House pattern reused, not invented: this is the identical in-cell markup already used in the Stage 1 Core Courses table (the MIT 6.00.1x row), including its inline summary styling — so no CSS was added or modified and the file gains no new dependency. (3) Summary labels are content-specific ("Resources, rulings & row-19 split note", "Build target, learning sources & amendments", "Timing detail", "Full rationale") rather than generic, so the two rows remain distinguishable while collapsed. (4) ⚠️ Known tradeoff, accepted by decision: collapsed <details> do not expand when printed, and this file carries @media print rules plus page-break-inside: avoid on tables. A global print override was considered and declined — it would have altered all 25 existing <details> blocks across the file for the benefit of two, a blast radius out of proportion to the gain. Falsifier: revisit if this file is ever routed to a print/PDF deliverable, at which point the override becomes worth its reach. (5) Snapshot corrected 1–24 → 1–25. Cost: $0. No course added, removed or substituted; no ruling deleted; no hours figure changed — the CORRECTION 22 deferral stands; all cell text preserved verbatim inside the disclosure blocks; archive untouched; version stays v10.0.TypeScript + Zod | S2 (Month-14 sprint) — the timing CORRECTION 22 had already retired. Re-anchored to the pre-Q1-2027 apply window. This is the one non-additive edit in this correction and it is a correction of a stale assertion, not a change of ruling. (3) 🆕 AI SDK framing updated to AI SDK 7 (released 25 June 2026, i.e. after CORRECTIONS 22–23 were drafted; now at ai@7.0.35, 16M+ weekly downloads). Adopted: @ai-sdk/otel with a single registerTelemetry() registration so the TypeScript last mile emits into the same Arize Phoenix / OTel backend as the Python core — no second observability stack; and AI SDK 7 telemetry’s allowlist model (includeRuntimeContext) recorded as a PII constraint that crosses the language boundary — the boundary is a language boundary, not a policy boundary. Noted but not scoped: MCP Apps as an S3 candidate for PolicyPulse’s approval-gated write tools, with a falsifier. (4) 🛑 AI SDK 7 tool approvals evaluated and explicitly DECLINED on Crucible’s live path. The SDK now ships per-tool user-approval, approval functions, HMAC-signed approvals and WorkflowAgent durability across delayed approvals — a close paper match for the HITL gate. Declined because an approval mechanism reachable from the agent’s own application layer is not a control that survives the threat model Crucible exists to demonstrate; the sign-off and kill-switch stay in the Python core, behind the Wall. Two-condition falsifier recorded (server-side enforcement retained AND the adversarial suite extended to prove the TS layer cannot bypass, forge or replay an approval). Consistent with the vendor’s own framing — the SDK documentation is explicit that it does not solve agent security. (5) Evidence upgraded. The last-mile guardrail previously rested on the same sources that recommended the SDK; it now carries independent corroboration — a June 2026 practitioner review draws the identical boundary unprompted and names this portfolio’s exact shape (agents across Python services, queues and data pipelines → treat the SDK as a layer, not an orchestration standard). The gateway-swap ADR now rests on two grounds, not one: privacy, and architecture over platform (the same review warns that assuming Gateway + Workflows + Sandbox + Observability + Next.js together makes teams drift into a platform decision before an architecture decision). Primary-source adoption figure (16M+ weekly downloads) recorded alongside the third-party 62% figure, which is retained but marked directional. (6) CORRECTIONS 24–25 evaluated — no propagation required, and recorded as such rather than silently skipped: both are roadmap-internal presentation changes (row 18→19 split; <details> collapse) and no scope document references roadmap row numbers. (7) Out-of-scope drift — two of three fixed, one declined on evidence. Fixed: the retired 5-stage numbering surviving in PolicyPulse v2.0 and FormSense v2.0 tables now carries an additive stage-numbering legend note (old 1→S1, 2→S2, 3→S2/S3 boundary, 4 and 5→S3) rather than a renumber — renumbering those tables would be a structural teardown requiring its own capability audit, and the authoritative block already rules that it wins on conflict; two stray S4 labels outside tables were corrected to S3 directly. CORRECTION 16 is now cited explicitly in PolicyPulse v2.0 (an observability/ package in the project tree) and StreamSmart v2.0 (a skills-table row) — the content was already present in both files’ production-standard line; only the citation was missing. ⚠️ Declined: the proposed portfolio-wide Python 3.11+ → 3.12 change was not made. This file specifies no Python version anywhere, so there was no roadmap standard to align to, and the 17 affected lines across 10 scope documents are already internally consistent at 3.11+. Changing them would have introduced drift, not removed it. Falsifier: apply the change only once a Python version is pinned in an authoritative artifact (AGENTS.md, .cursor/rules/python-production-standards.mdc, or a committed pyproject.toml requires-python) — and pin it in this file at the same time. (8) Deliberately NOT propagated: the Packt TypeScript course (Tier 4/5 credential — belongs in this file’s course tables, not a project scope); WorkflowAgent / HarnessAgent adoption (would pull TypeScript past the last mile — watchlist only, notable because HarnessAgent runs Claude Code and OpenCode, both in the active harness); and a TypeScript layer for DataVault, ODI, AFC or FormSense (no UI deliverable scoped — the absence is recorded in-file as a decision with a falsifier, not left as an omission). (9) The five public-facing documents and the 1099_reconciliation_pipeline README remain outstanding; the stale attention-flow-catalyst README is logged and deferred by approval — it will be corrected when that project is next worked. (10) Snapshot corrected 1–25 → 1–26. Cost: $0. No course added, removed or substituted; no ruling deleted; no hours figure changed — the CORRECTION 22 hours deferral stands; scope-document version numbers deliberately unchanged (Last Updated only) under additive-only governance; archive untouched; no structural teardown; version stays v10.0.3.12+), per approval. This closes the gap CORRECTION 26 declined to guess at: this file previously specified no Python version anywhere, so the 3.11+ figures in the scope documents had nothing to align to. There is now an authoritative pin. Single-source rule: the version is declared once per repo as requires-python = ">=3.12" in pyproject.toml, and four consumers read from that one declaration — [tool.ruff] target-version = "py312", [tool.mypy] python_version = "3.12", the Dockerfile base image, and the CI matrix. A mismatch between any consumer and requires-python is a CI failure, not a lint warning — the same enforcement discipline uv.lock gets from the uv-lock hook under CORRECTION 21, and the same one-source-no-drift principle already applied to Structurizr→Mermaid (CORRECTION 14) and structlog (CORRECTION 16). Propagated to all 13 scope documents: 17 skills/tech-stack lines, 6 Dockerfile FROM python:3.11-slim base images and 1 CI matrix entry corrected. Falsifier: raise the floor only when a named dependency in a committed lockfile requires it, or when 3.12 leaves security support — never to chase a release. (2) 🧹 PolicyPulse v2.0 and FormSense v2.0 restructured onto the 3-stage scale (per approval) — the structural teardown CORRECTION 26 deferred. Capability audit run first, per governance. Trigger: both files carried the retired 5-stage numbering in four tables each — capability, MCP tool, guardrail and development-phase — which CORRECTION 26 could only paper over with a legend note. Mapping applied: old 1 → S1; old 2 → S2; old 2→3, old 3, old 4 and old 5 → S3. 54 table rows renumbered across the two files (26 + 28); zero rows deleted — every capability, tool and guardrail survives with its content intact and only its stage label changed. The five CORRECTION 26 legend notes are removed as superseded, which is the one deletion in this correction and is a deletion of text this correction itself made obsolete. (3) ⚠️ Three judgment calls recorded rather than made silently. (a) GraphRAG intro moved from PolicyPulse’s S2 "Cloud" phase to its S3 "Intelligence" phase: the governing block places GraphRAG in S3, so leaving it in the S2 infrastructure phase would have re-created the contradiction the renumber exists to remove. Content moved, not deleted — the S3 phase now carries the full intro → deepen arc in one place, and the multi-hop exit criterion moved with it. (b) The five build phases in §17 are retained, not collapsed to three: build sequencing within a stage is not duplication, and merging them would have destroyed per-phase exit criteria. Only the stage column changed. (c) The "Platform" phase is tagged end-state product surface — beyond the portfolio evidence bar in both files. Multi-tenant SaaS, RBAC, Slack/Teams and OnBase integration are product features of the end-state architecture, not portfolio evidence; mapping them to S3 without the tag would overstate what the 3-stage arc actually commits to shipping. No fourth stage was introduced to accommodate them. (4) Residual 5-stage prose corrected — four "Stage-4" references in body text (PolicyPulse §6; FormSense §6, §6.2, §9) now read S3, and a broken table-of-contents anchor (#18-project-evolution-5-stages, a dead link in both files since the v10.0 realignment) is repaired. (5) A closing note is added before §18 in both files stating the scale, the mapping and the fact that no row was removed — so a future reader can verify the renumber was lossless without diffing against an archived copy. (6) ⏸️ React — evaluated, NOT added as a learning-track item (see the ruling logged with this correction). Recorded here so the absence is a decision with a falsifier rather than an omission. (7) Scope-document version numbers again deliberately unchanged (Last Updated only) — the PolicyPulse and FormSense restructure is a renumber onto the governing scale, not a change of scope, and no capability was added or removed. (8) Snapshot corrected 1–26 → 1–27. Cost: $0. No course added, removed or substituted; no hours figure changed — the CORRECTION 22 deferral stands; archive untouched; version stays v10.0.python3.14t) is explicitly NOT used: free-threading is where the C-extension wheel-compatibility problems live, this portfolio has no CPU-bound multicore workload that would benefit, and chasing wheel availability is pure schedule tax against 25 hrs/week with zero portfolio value. (b) Airflow constraint-file caveat recorded before it is hit, not after: a known open issue reports the Airflow 3.14 constraint files out of sync between the published Docker image and pip/uv install. Documented workaround — fall back to constraints-3.13.txt for the Airflow service only, which is a constraint-file selection and not a second Python version; the interpreter stays 3.14. Falsifier restated: raise the floor only when a named dependency in a committed lockfile requires it, or when 3.14 leaves security support — never to chase a release. 3.15 ships October 2026 and is explicitly not adopted on release. ⚠️ Evidence flag: several early-2026 articles claim 3.14 was still in alpha and advise waiting for an October 2026 stable release. That is incorrect — 3.14 shipped October 2025 on the normal annual cadence — and those sources are discounted. The Airflow documentation and issue tracker are primary and were relied on instead. Propagated to all 13 scope documents; zero 3.11 or 3.12 references remain. (3) 🎯 Model-call ownership resolved — the gap the scope documents had left open. With a TypeScript last mile in scope, two designs were possible and no document ruled between them, which meant the CORRECTION 23 privacy amendment was protecting an undefined surface. Ruling: Pattern B (the Next.js route handler owns the model call and calls retrieval as a tool) for the single-turn chat; Pattern A (Python owns everything) for the agentic loop. The S3 evaluator-optimizer loop, GraphRAG fusion, access-control retrieval and three-layer eval stay entirely in Python — no agent core crosses the language boundary, and the CORRECTION 22 guardrail is unchanged. The split follows the guardrail's principle — the loop is Python, the turn is the last mile — rather than treating the language boundary as a blunt instrument. Pure Pattern A was declined because it would force the last mile to re-implement streaming, tool-call normalisation and structured output in Python purely to satisfy a language rule, rebuilding exactly what the SDK exists to provide, for no evidence gain. ⚠️ Consequence: the privacy amendment is now load-bearing rather than moot. Under Pattern B the route handler sees the full prompt, which is precisely why the Gateway is declined for the direct @ai-sdk/anthropic provider and why the corpus stays synthetic. Under Pattern A the question would not have arisen. Falsifier: revisit if a single turn ever needs more than one model round-trip plus tool calls — at that point it has become a loop, and a loop belongs in Python. (4) 🎨 React named as an outcome, NOT added as a learning-track item, reversing the CORRECTION 27 §6 placeholder. React was already in this file unnamed — Vercel Academy is Next.js/React-based, the narrow v8.9 exception already admits it, and StreamSmart v2.0 has specified React since before v10.0 — so the real choice was name what is already there, or leave it unclaimable. Row 19 amended in place: no new row, no new course, no net hours, $0. Scoped to table-stakes competence (components, hooks, state, streaming UI, calling a typed API); Redux, React Native, testing libraries and SSR internals declined. Stage 2 (AE/DE) declined outright — React is absent from AE/DE posting bars on the same evidence that retired standalone JavaScript in CORRECTION 22, and a React block would be a second item competing with DataVault S2, which is the evidence gate. ⚠️ Evidence recorded honestly because it cuts both ways: real FDE postings do name React ("strong with TypeScript on the backend and React (or equivalent) on the frontend"), while practitioner hiring guidance calls tool-listing a weak-posting signal and says the FDE will learn whatever stack the customer runs. Both are true; the resolution is that React is table-stakes, not a differentiator. Note the prevailing phrasing is "React (or equivalent)" — the requirement is a framework. 📦 (5) Electron / desktop packaging explicitly declined. The deliverable ships as a browser page at a URL. A reviewer will click a link; they will not download an unsigned executable, and macOS blocks it without an Apple Developer certificate. Code signing and auto-update are packaging work with zero portfolio signal. Recorded because the desktop route is a natural-looking detour — the Claude desktop app, Cursor, VS Code and Slack are all Electron, i.e. web apps in a window, so the same React code would run there; the reason to decline is career economics, not capability. ⚠️ (6) One tension logged, not acted on: a subset of FDE postings also wants TypeScript on the backend, which sits against the CORRECTION 22 last-mile guardrail. No change made — the guardrail is correct for a Python/SQL data-platform profile with an ERISA moat, and those TS-first full-stack roles are a different lane. The CORRECTION 22 falsifier already covers it. (7) Scope-document version numbers again unchanged (Last Updated only). (8) Snapshot corrected 1–27 → 1–28. Cost: $0. No course added, removed or substituted; no hours figure changed — the CORRECTION 22 deferral stands; archive untouched; no structural teardown; version stays v10.0..git/hooks/pre-commit plumbing under CORRECTION 21. Version control had no course, no row and no exit criterion anywhere in a file that otherwise specifies tooling down to the hook stage. (2) 🥇 Google — Introduction to Git and GitHub selected (Coursera Plus, ~20 hrs, shareable certificate) over IBM — Getting Started with Git and GitHub (~10.5 hrs). Decided on syllabus depth against the actual gap, not brand or duration: the Google syllabus covers the staging area, the HEAD alias, rebasing, conflict resolution and the pull-merge-push workflow — the material a solo developer gets stuck on — while IBM is weighted toward the GitHub web UI, forking, and a final project that asks the learner to create and share a public repository. ⚠️ That capstone is the disqualifier: the deliverable IBM builds toward is already built seven times over, at a production standard IBM does not teach. Paying hours to be taught to create a public repo, by a course whose hands-on work is explicitly browser-based with no local install required, is negative value against a 25 hrs/week budget. (3) ⚠️ Anti-stack finding — the decisive practical reason, and it would have been missed without checking this file first. The IBM course is a component course of IBM Applied Software Engineering Fundamentals, which is already recorded here as the row-14 secondary option under CORRECTION 11. Taking it standalone would double-buy the same hours if that fallback is ever activated — a direct violation of the replace-not-stack rule. The Google course belongs to a different specialization (Google IT Automation with Python) that this file does not carry, so no overlap exists. (4) ⏱️ Scoped to ~8 hrs, not the full ~20 — the course is entered to close a specific gap, not completed for its own sake. Install, first-repo and account-setup modules are skipped as already-evidenced; the branching, rebase and conflict modules are the target. Recorded so a future reader does not treat the published duration as the committed hours. (5) Credential position stated plainly: the certificate is a Coursera shareable — Tier 4/5, never a Certifications line under the CORRECTIONS 19 ladder. The value here is skill, not credential; neither candidate is proctored and neither changes the credential stack. (6) Placement: inserted as row 3️⃣.5 — after SQL foundations, before the LLM-API work — using the decimal convention already established by row 1️⃣1️⃣.5, so no existing row is renumbered. The Stage-1 "Containerization & shipping" skills row is amended to name branch → PR → review → merge explicitly, since that is the competency being added rather than Git generally. (7) ⚠️ Honest limitation recorded: a course cannot supply team-workflow evidence, because a solo portfolio has no second contributor to review against. The falsifiable proof is behavioural, not the certificate — the flagship repos should show feature branches and self-reviewed PRs rather than direct commits to main, which is the artifact a reviewer can actually check. Falsifier: drop the course entirely if that branch-and-PR habit is established on the flagships first — at that point the material is redundant and the hours return to the build. (8) Cost: $0 (Coursera Plus). No course removed or substituted; no hours figure changed — the CORRECTION 22 deferral stands; archive untouched; no structural teardown; version stays v10.0. Snapshot corrected 1–28 → 1–29.<details> summary. (2) The duration cell is collapsed on the same standard, with the visible value changed from the published "~20 hrs (4 weeks) · target ~8 hrs" to "~8 hrs committed" — the published duration is not the commitment, and the scan-level figure should be the number that binds. Full timing detail, including the IBM secondary's conditional ~10.5 hrs and the combined ~18.5 hrs worst case, sits behind the summary. (3) Zero content removed — this is a presentation-only change; every sentence written in CORRECTIONS 29 and 30 survives verbatim behind the disclosure. (4) Like CORRECTIONS 24–25, this is roadmap-internal presentation and does not propagate to any scope document. (5) Snapshot corrected 1–30 → 1–31. Cost: $0. No course added, removed or substituted; no hours figure changed; archive untouched; version stays v10.0.Goal: AI-builder scope at the current employer … no comp reset and Exit criterion: documented internal scope change by Month 8. A reader arriving from the public README saw the retired premise, not the ruling. Five prose sites are now re-anchored — the Stage 1 goal box, the Stage 1 exit criterion, the progression-table row, the "Fallback logic (explicit)" paragraph and the Current State Snapshot. Every superseded sentence is preserved verbatim, struck through in place, with the new ruling appended — so the contradiction is visibly resolved rather than silently overwritten. (2) 🏷️ "Internal AI Builder" retained as the Stage 1 name, by approval — and the reasoning is worth recording because the obvious move was to rename it. The build work does not stop: the flagships continue shipping through the two-month handover, so the work label is still accurate. What was false was the employment premise attached to it — elevation, employer funding, "no comp reset". Separating the two was cheaper and more honest than a rename, which would have forced a renumber across three public documents for no gain. ❌ Collapsing three stages to two — evaluated, not selected: the S2/S3 distinction is a skills boundary, not an employment boundary, and it survives the resignation untouched. Falsifier for both: revisit if a reader ever reports reading the stage name as a current job title. (3) 💳 All certifications ruled self-funded — no employer reimbursement applies to any credential in the canon, and the costs are now documented rather than assumed. Verified list prices (USD, exam fee only, single attempt): AI-901 $99 · AB-620 $165 · DP-700 $165 · AWS DEA-C01 $150 · NCA-GENL $125 · Databricks GenAI Associate $200 · Neo4j Certified Professional $0 · AI-103 $165 · CCA-F ~$125. Microsoft prices on two tiers — $99 Fundamentals, $165 Associate/Expert/Specialty — which is why AI-901 sits below the rest. Committed eight ≈ $1,029 (AB-620 conditional — CORRECTION 37); optional lakehouse slot adds $165–$200; conditional dbt AE adds ~$200 (corrected from $0 — CORRECTION 37); conditional AB-620 adds ~$165; full-canon ceiling ≈ $1,594, spread across S1–S3. ⚠️ Two figures are flagged rather than asserted: CCA-F pricing and its Partner Network access route both post-date the Pearson VUE migration and must be confirmed at booking; dbt AE is widely reported as free but is conditional and unscheduled, so it carries no committed cost. ❌ Treating the total as a reason to trim the canon — evaluated, declined: ~$1,194 across roughly two years is not a constraint that should drive credential selection, and this file already ranks shipped systems above every certification on the ladder. The cost is documented so it can be scheduled, not so it can be optimised. Falsifier: revisit if the ceiling clears ~$2,000 or if any single credential exceeds $300. (4) ✅ DP-750 reinstated as an OPTIONAL lakehouse-slot candidate — the vacatur is withdrawn, and the reasoning is worth recording because it reverses an earlier draft of this same correction. An intermediate draft vacated DP-750's ranking on the grounds that its preference rested on reimbursement. That reasoning was sound but the remedy overshot: removing an option is a heavier action than removing a preference, and it left the slot empty for no benefit. The correct outcome is narrower — DP-750 loses its preferred status and keeps its place. The lakehouse slot is therefore three co-equal options, take exactly ONE, matched to a target employer's stack, never stacked: DP-750 $165 · SnowPro Core COF-C03 $175 · Databricks DE Associate $200. No default is set, deliberately: with the funding advantage gone the three sit within $35 of each other, and the deciding input is the target employer's stack, which is not knowable until the apply window. Falsifier: set a default the moment a target-employer shortlist shows a clear lakehouse majority. (5) 🐍 Python 3.12 propagation gap closed on the public surfaces. CORRECTION 28 recorded propagation to all 13 scope documents with "zero 3.11 or 3.12 references remain" — but the public-facing documents were not in that pass, and the Learning Journey README still declared Python 3.12 and mypy (3.12). Corrected to 3.14, with the standard-GIL-build constraint stated publicly rather than left as an internal note — the constraint is engineering-judgment evidence and reads as such to a reviewer. (6) 📊 Absolute manual-hours figure removed from both public documents. The claim 95% time reduction (4–6 hrs → 15 min/week) carried an absolute manual-hours figure, which contradicts this file's own Flagship 2 Cost ruling ("manual hours removed. No absolute figures") and the disclosure box the README itself prints. The relative delta (95%) is compliant and is retained; only the parenthetical is dropped. ❌ Amending the disclosure rule to permit the figure — evaluated, declined: the rule is load-bearing for a regulated-domain claim, and loosening it to preserve one parenthetical trades a compliance posture for a detail no reviewer is screening on. (7) 🔤 TypeScript last mile surfaced publicly for the first time. CORRECTIONS 22, 23, 26 and 28 established the Vercel AI SDK build target, its learning source, the AI SDK 7 framing and the Pattern A/B model-call ruling — and none of it appeared in either public document; "TypeScript", "Vercel" and "React" each returned zero hits. Added, with the last-mile guardrail stated alongside so the addition cannot be read as a pivot away from Python. (8) 🌿 Git collaboration competency surfaced (CORRECTIONS 29–30): branch → PR → review → merge. Recorded per CORRECTION 29's own honest limitation — the claim is only made where the repos show the behaviour; it is a build target, not a completed claim. (9) 🎯 Target-role order corrected on the public surfaces to Analytics Engineer first door, Data Engineer parallel (CORRECTION 22 §3), which both documents had rendered as an undifferentiated dual-target. (10) 🟢 Availability stated plainly — available 9 October 2026 — in the first screen of both public documents. Recorded bluntly because the prior state was the costliest defect in this pass: the public profile announced an active internal track and no external search, i.e. it told every reader the candidate was unavailable, eight weeks before he was. (11) 🏷️ Flagship 2 named consistently as DataVault / 1099 Data Platform, matching the portfolio table; the public documents had used "1099 Data Platform" while reserving "DataVault" for the S3 layer, against a file whose own priority order reads DataVault → PolicyPulse → Crucible. (12) 🎖️ Skill-badge wall retained by approval, re-tiered rather than cut. A Core Stack tier is promoted above the wall; the remainder is relabelled Broader toolkit & Stage 2–3 build targets. ❌ Cutting the wall to evidenced-only — evaluated, not selected: it serves a real skills-tracking function for the builder, and the tiering fixes the scan problem without destroying that. The honesty risk is handled by the relabel, which stops unevidenced tools from reading as claims. (13) ⚠️ Evidence-quality flag on the presentation research. The 2026 "what recruiters look for in a GitHub profile" literature is overwhelmingly published by vendors selling README templates, profile-enrichment services and portfolio coaching — one guide argues against badge walls and then instructs the reader to embed that vendor's own badge. Treated as directional only. The one thread with independent backing is research summarised from Carnegie Mellon findings that hiring managers favour verifiable signals of project ownership — which this file's proof-over-keywords thesis already encodes. No presentation decision in this correction rests on the vendor sources alone. (14) Hours model untouched — the CORRECTION 22 deferral stands. 25 hrs/week is unchanged in the banner, the weekly-allocation table and every downstream time budget. Stated explicitly because item (6) also concerns an hours figure, and the two are unrelated: that one is operational hours in a business-impact claim, this one is the study budget. (15) Snapshot corrected 1–31 → 1–32. No new spend and no change to what is bought — the correction reclassifies the entire certification canon from partially-reimbursed to fully self-funded (≈ $1,194 committed, ≈ $1,394 ceiling) and documents the per-exam prices that were previously left implicit. This is a change in who pays and in what is written down, not in what is pursued. No course added, removed or substituted; no ruling deleted — every superseded sentence is preserved verbatim in place; archive untouched; no structural teardown; version stays v10.0.fct_document_reviews grain is one row per (packet, review run). (8) ERISA constraint applies unchanged — synthetic corpus only; no employer, recordkeeper, sponsor or vendor names; no participant or plan data; no absolute figures. (9) Provider strategy (ADR-009): provider-agnostic across three named substrates — Anthropic, Azure OpenAI via Microsoft Foundry, local Ollama — one eval suite, gates run per substrate; Copilot Studio and the M365 Agents SDK declined with recorded falsifiers. (10) Propagation: overview strip (3 → 4 flagship projects), snapshot portfolio line, Portfolio section heading + decision note + new Flagship 4 row + FormSense scope boundary, Build Progression (all three stage rows, priority line, relevance ranking), résumé Tier-1 evidence list. (11) 🆕 ANNOTATION POLICY CHANGED — this supersedes the strikethrough-in-place convention. Superseded text is no longer struck through in the body, and inline correction markers are no longer added to body sections; sections now carry final text only. Change history lives here in the changelog, which remains the sole record. Applied retroactively: 7 strikethrough spans, 7 red correction markers, and 70 inline correction annotations were removed from the live body; prose cross-references to changelog entries (for example "per CORRECTION 22") are retained as citations. The Archive remains byte-identical and this changelog is untouched. (12) Consistency sweep: stale employer-reimbursement language corrected to self-funded in six live-body locations (overview strip, Stage-1 proctored credentials, Stage-1 milestone, DP-750 conditional ×2, Build Progression certs rows), per CORRECTION 32. Project-scope count 14 → 16. Cost: $0. No course added or removed; certification canon stands at 9 committed + 1 conditional; no hours figure changed; no structural teardown; version stays v10.0.<details> blocks (S1 · S2 · S3 · v9.2 audit), following the #dlaipro17 / #pca18 / #finopt10 convention, placed after Certifications so the Tier-5 ruling sits beside the ladder that governs it. No CSS added or modified. (2) Governing rule: books are Tier 5 on the CORRECTION 19 ladder — skills evidence only, never a Certifications line, and they earn a slot only where a production-standard item has no learning source — the same test Core Courses #17 (C4 + ADR) and #18 (pre-commit) already pass. The certification canon is untouched at 9 committed + 1 conditional. (3) 🆕 Buy-at-stage-entry rule adopted — never buy upfront, and re-verify the edition at every purchase. The rule is derived from a defect in this file's own archive rather than from principle: v9.2 committed to Designing Data-Intensive Applications at 1st edition (2017) and the 2nd edition shipped March 2026 (Kleppmann + Riccomini), so a book bought ahead of when it is read is a book that goes stale before it is opened. (4) 🆕 Aging principle recorded as the selection criterion: books split into three groups that age at different rates — foundations age best, system design ages moderately, framework and vendor books age fastest — and no agentic-AI canon exists because the field outruns the publishing cycle. This is the book-layer analogue of the badges ≠ credentials rule and is what drives every framework decline below. (5) Six committed purchases + one owned. S1: Robust Python (Viafore) 🥇 — the only book mapping 1:1 to the production standard, selected on a checkable mechanism (the ZenML engineering team publicly credits it as the basis for adopting mypy across their codebase, naming its legacy-codebase chapter — which is the 1099 retro-migration), with a currency caveat that it predates PEP 695 generics; AI Engineering (Huyen) 🥇; Python Testing with pytest 2nd ed. (Okken) 🥈 — testing was load-bearing everywhere (CI gates, eval gates, PostCheck's frozen 200-packet golden set, the CORRECTION 16 §7 capture_logs assertions) with no learning source at all, and Okken co-hosts Python Bytes, already one of the four editorial vettings behind the Molin series; Fluent Python 2nd ed. (Ramalho) 📖 already owned — $0, reference tier, consumes no slot, so no replace-not-stack conflict arises. S2: The Data Warehouse Toolkit 3rd ed. (Kimball & Ross) 🥇 — dbt Labs' own dimensional-modeling guide teaches Kimball's four-step process (business process → declare the grain → dimensions → facts), which is literally the ruling PostCheck runs under (fct_document_reviews grain), with no OMSCS overlap; read the principles chapters and SCD material only, since reviewers consistently fault its use-case-based organisation. S3: Fundamentals of Software Architecture 2nd ed. (Richards & Ford, 2025) 🥇 — closes the gap CORRECTIONS 8 and 14 left open by making ADRs and C4 mandatory while sourcing them from free web pages only: it carries a dedicated ADR chapter and a diagramming chapter naming C4 explicitly, and Neal Ford is also the author of the Architectural Katas series already named in CORRECTION 14 §5 as the rehearsal mechanism, so book and method share a source; its First Law ("everything in software architecture is a trade-off") is the FDE decomposition script. Hands-On Large Language Models (Alammar & Grootendorst) 🥈 — literacy-tier by design, which is the correct depth given the ML-Engineer stage was cut. (6) 🔄 AI Engineering moved from the v9.2 Stage-4 slot to Stage 1 by ruling — this file makes evaluation literacy ⭐ the Stage 1 differentiator and PolicyPulse v1 ships with eval gates in Stage 1, so a book that improves those gates in month 3 outperforms the same book read in month 25; it is foundations-tier and carries forward to S2 and S3 without being re-bought. (7) ⏸️ Two S2 conditionals, neither committed: DDIA 2e held on an anti-stack falsifier (OMSCS Computing Systems covers distributed systems and OMSCS substitutes overlapping self-study; buy if that course is skipped, or at the Q1 2027 apply window for a system-design round); Vector Databases (Borwankar, 2026) declined for now under this file's own evidence rule — no review history, the identical objection recorded against AMD ROCm in CORRECTION 17. 🆕 Finding worth recording: the AI-focused-DE half of Stage 2 was audited and found already covered — the "AI-adjacent data" row is served by three DeepLearning.AI rows flagged 🔴 S2-high in the CORRECTION 17 lab map (Pre-processing Unstructured Data · Knowledge Graphs for RAG · Vector Databases) plus AI Engineering carried from S1, so a book there would stack on paid labs already budgeted, not fill a gap. (8) 🚫 S3 third slot deliberately left empty with a falsifier — no agentic-AI canon exists; revisit at M21 only for a title with independent review history and framework neutrality. (9) 🗄️ All 15 archived v9.2 book entries dispositioned in a fourth block: 1 promoted (AI Engineering), 3 demoted or superseded, 8 retired, 1 held as optional depth (Build a LLM From Scratch — deeper than literacy, rebuilds the depth v10.0 cut), 1 edition-corrected, 1 carrying a factual error. 🚨 Two errors found in the archived tables and corrected here rather than in the archive: (a) the Data Smart row credits "Jordan Goldmeier, 1st Edition (2014)" — the 1st edition is John W. Foreman, October 2013, and Goldmeier authored the 2nd edition (2023); the row conflated the second-edition author with the first-edition year; (b) the DDIA edition error above. 🚨 Anti-stack finding: Fundamentals of Data Engineering is demoted because Joe Reis is the instructor of the DeepLearning.AI Data Engineering Professional Certificate already committed as Stage 2 Core Course #4 (CORRECTION 20 §3) — same author, same lifecycle framework. (10) ❌ Evaluated, not selected, each with a falsifier: Building LLMs for Production (Bouchard & Peters — commonly misattributed to "Caelen", who is a different author) on four grounds: it reads more as an applied research text than a practical engineering guide per its most substantive review, it is LangChain/LlamaIndex-centric (fastest-ageing tier), its endorsements come substantially from the surrounding ecosystem rather than independent review (the same discount applied to the Scrimba self-ranking in CORRECTION 23), and it is redundant against AI Engineering + Hands-On LLMs; LLM Engineer's Handbook (framework tier); Analytics Engineering with SQL and dbt (reviewer-noted redundant early chapters, dbt-Cloud-weighted against this roadmap's dbt-Core-with-CI posture, and Fusion-era stale — dbt Learn stays the source of truth); Hypermodern Python Tooling (already declined in the CORRECTION 21 addendum; re-logged only to prevent re-opening). (11) ⚠️ Evidence-quality flagged in-file: much of the 2026 "best AI books" literature is affiliate-monetised roundup content — no selection rests on a roundup alone; each rests on convergence across independent sources plus a checkable mechanism (a named chapter, a named practitioner adoption, or a primary vendor page). (12) O'Reilly platform route re-verified and NOT taken — the CORRECTION 14 conditional is $129/quarter, not per month, and would cover most of these titles; the buy route was elected by decision, and the O'Reilly conditional stands unchanged for its live-event and Katas value. (13) Snapshot corrected 1–32 → 1–34 — it had gone stale by two, still reading 1–32 while CORRECTION 33 was already logged. Cost: six books across ~32 months, purchased at stage entry; no figure asserted here, since editions and prices must be re-verified at purchase — the same discipline applied to the CCA-F booking flag. No course added, removed or substituted; no certification added; no hours figure changed — the CORRECTION 22 hours deferral stands; archive untouched and byte-identical; additive-only apart from the snapshot count; no structural teardown; version stays v10.0.1099_reconciliation_pipeline assumed pandas by default rather than by decision. (1) 🔀 Ruling — two engines, one boundary. This is a division of labour, not a migration. Polars is the default for new pipeline code (ingestion, schema enforcement, normalization, bulk transforms); pandas is retained deliberately at two named boundaries — writing into an existing .xlsx template via openpyxl, and hand-off to matplotlib / plotly / scikit-learn / PandasAI. The boundary is the rule; the engine names are downstream of it. (2) 🎯 The reframe recorded, because it outranks the question asked. For an Analytics-Engineer-first target the dataframe library is the second decision — the first is how much logic leaves dataframes entirely for dbt. DataVault's four reconciliation engines (A/B/C/D) belong in tested dbt models, not in either dataframe library; the dataframe layer's job shrinks to ingestion and rendering. A reviewer cares far more that Engine B's age-based tax-code logic is a CI-gated dbt model than whether the residual Python reads pd or pl. (3) 🛑 No rewrite of the shipped 1099 pipeline. It is live and production-evidenced; churning working code is not evidence. It is frozen as the "before", and the runtime/memory delta becomes a headline metric for the S2 writeup — the same shape as PostCheck's deterministic-parser-vs-flattened-baseline headline (CORRECTION 33 §5). (4) 🚨 VERIFIED AGAINST THE VENDOR: no Polars certification exists. The Polars Academy is in-company B2B training only — Polars Foundations (½ day), Polars Essentials (1 day), Polars Plugins (1 day), booked by contacting the Academy team — plus a curated list of third-party self-paced courses. There is no exam, no proctored credential and no badge to earn. The certification canon is therefore untouched at 9 committed + 1 conditional, and no Stage-2 exam row is added. Recorded explicitly so a future reader does not re-open the search. (5) ❌ All four self-paced routes the vendor itself endorses fail this file's existing rulings — checked, not assumed. DataCamp ×3 (Introduction to Polars, free, 3 hrs · Data Transformation with Polars · Scaling and Optimizing Data Pipelines with Polars) — DataCamp is Polars' own named learning partner, which is the strongest case any of these has, but it was declined with a falsifier in CORRECTION 4 on near-zero credential weight and that ruling is not reopened for a free 3-hour course. Udemy — Data Analysis with Polars (Liam Brannigan, a Polars contributor; endorsed by Ritchie Vink; kept current to release 1.30.0) — genuinely the best-provenanced of the four, and still declined under CORRECTION 7; the provenance is logged so the falsifier has something to bite on. Coursera — Polars from Zero (Pragmatic AI Labs) is Coursera-Plus-included at $0 marginal, which made it the obvious pick until the syllabus was actually read: it is a Rust course, part of the Rust for Data Engineering Specialization, and its deliverable is three Rust CLI binaries. That collides head-on with CORRECTION 22's Rust decline — whose whole reasoning was that Rust is the language these tools are written in and consumed through Python bindings, Polars named as the example. Declined; $0 is not a reason to take the wrong language. Xebia Academy — Polars Essentials (€750, in person, Netherlands) declined on cost and geography. (6) 🆕 The learning slot goes to the books layer (Tier 5), Stage 2 — not to the course table. Python Polars: The Definitive Guide (Janssens & Nieuwdorp, O'Reilly, 1st ed. 2025) added as ⏸️ CONDITIONAL. It passes the CORRECTION 34 test — a production-standard item with no learning source — on a checkable mechanism rather than a roundup: it is the title the vendor's own Academy lists as the definitive guide, its foreword is by Ritchie Vink, the creator of Polars, both authors wrote it while colleagues at Xomnia — the company where Polars was created, and every example and dataset ships in a public GitHub repository, so the exercises are runnable rather than readable. It covers the eager, lazy and streaming APIs and is explicitly built around unlearning pandas habits, which is the actual failure mode here. ❌ Effective Polars (Matt Harrison) evaluated and not selected — self-published with no independent review history, the identical objection recorded against Vector Databases in CORRECTION 34 §7 and AMD ROCm in CORRECTION 17. (7) ⏸️ Conditional, not committed — and the condition is stated. The free primary sources are the first stop: the Polars user guide, the migration pages and the API reference. Buy the book only if the DataVault ingestion-layer rewrite stalls on concepts the docs do not close — lazy-plan reasoning, streaming, or the expression model. ⚠️ Edition caveat under the CORRECTION 34 §3 buy-at-stage-entry rule: the 1st edition (2025) predates the 1.24 streaming-engine GA, so re-verify the edition at purchase; a 2nd edition would supersede this row. (8) 📍 Stage 2, not Stage 1 — placement reasoned, not defaulted. The boundary is an S2 hardening act tied to DataVault's evidence gate, and Stage 1 hours are owed to the eval spine. Stage 1 code already shipped in pandas and stays shipped. (9) ⚠️ The real cost is harness friction, and it is mitigated in the rules rather than hoped away. LLM assistants routinely emit pandas method signatures against Polars objects — reported by practitioners against current frontier models, not a theoretical risk — which lands directly on a dual-harness Cursor + OpenCode workflow. Mitigation: a Polars idiom block added to python-core.mdc naming the six most common wrong calls (df[mask], in-place assignment, groupby, rename(columns=), apply, reset_index) so the harness is corrected by rule rather than by review. (10) 📉 Counter-evidence recorded, because it cuts against the decision. Polars carries near-zero posting weight — roughly 0.009% of UK permanent vacancies against pandas at 0.62%, a ~65× gap, and US postings that name it overwhelmingly phrase it as "Pandas, PySpark, or Polars" — an alternative, never a requirement. It is therefore never claimed as a credential and never listed as a differentiator. The value banked here is the ADR-able boundary decision and the .explain() plan artifact, which are proof-over-keywords evidence; the library name on a skills wall is worth approximately nothing. (11) 🚨 Source-quality flag — a widely-surfaced 2026 comparison asserts pandas 3.0 was pushed back to alpha. That is false. pandas 3.0.0 shipped 21 January 2026 and stood at 3.0.5 on 22 July 2026, bringing a dedicated string dtype, Copy-on-Write by default, microsecond datetime resolution and a pd.col() expression API borrowed from Polars. That source is discounted and must not be cited publicly; the primary release notes were relied on instead — the same discipline applied to the Python-3.14-still-in-alpha claims in CORRECTION 28. Consequence for the ruling: pandas 3.0 is the retained-boundary floor, and code written against 2.x chained-assignment behaviour is a defect. (12) 🚫 Recorded before it is hit, not after: pl.DataFrame.write_excel is xlsxwriter-based and cannot write into an existing formatted template — an open upstream feature request. The Matrix correction-file template path stays openpyxl permanently, which is why the pandas boundary is a boundary and not a transition. Polars' read path is unaffected and uses the Rust calamine engine via fastexcel. (13) ⚠️ Open-core risk logged as an ADR line, not a blocker. Polars is VC-backed (€18M Series A led by Accel, following a $4M seed) with Polars Cloud and Polars Distributed as the commercial products; the core library is MIT. pandas has no commercial sponsor. Falsifier: revisit if any capability this portfolio depends on moves behind the Cloud paywall. (14) ❌ Narwhals — evaluated, not adopted. It would let signalcore accept either frame type and is already transitively present in the lockfile via plotly, so adoption would be nearly free. Declined because adding an abstraction layer before a second consumer exists is speculative generality, and this file's own replace-not-stack discipline treats an unused layer as a cost. Falsifier: adopt the moment signalcore has a real second consumer requiring a different engine. (15) 🛠️ Propagated to the Cursor rules the same day — python-core.mdc (engine policy, boundary table, schema-first reads, Polars idioms, converted docstring and type-hint examples), testing-and-eval.mdc (polars.testing.assert_frame_equal, the strict-dtype ruling, and two boundary tests), project-scaffold.mdc (dependency split), architecture-docs.mdc (standing ADR example), learning-mode.mdc, streamlit-patterns.mdc (LazyFrame caching defect) and git-workflow.mdc. observability.mdc and ai-sdk-patterns.mdc deliberately untouched — neither has a dataframe surface, and editing them to look thorough would be noise. (16) Scope-document propagation NOT executed here — the 16 project scopes and the 1099_reconciliation_pipeline README (still carrying retired career-path framing) are held for a separate pass by approval, the same deferral pattern as CORRECTION 22 §8. (17) Snapshot corrected 1–34 → 1–35. Cost: $0 committed (one conditional book, unpriced until purchase per CORRECTION 34). No course added, removed or substituted; no certification added — the canon stands at 9 committed + 1 conditional; no hours figure changed — the CORRECTION 22 hours deferral stands; archive untouched and byte-identical; additive-only apart from the snapshot count; no structural teardown; version stays v10.0.ruff, uv, pydantic-core, delta-rs — and CORRECTION 35 has just made Polars the default engine, which moves that substrate one layer closer to this portfolio than it was a week ago. (3) 🚦 Four activation triggers recorded, none of which auto-enrols. 🥇 (a) Polars plugins — the strongest and most likely, because it is internal to work already scoped: custom business logic that must run at native expression speed is written in Rust via pyo3-polars, and the Polars Academy sells a dedicated Plugins course; if a DataVault or PostCheck rule genuinely cannot be expressed in native Polars, the question stops being speculative. (b) Rust appears as a required line — not "Python, Go, or Rust" — in ≥3 postings on the actual Q1 2027 apply list. (c) A named target employer lists Rust or PyO3 in a posted JD. (d) Crucible's live-execution path presents a genuine latency or memory-safety requirement — the CORRECTION 22 falsifier, restated in the row so both live in one place. (4) ⚠️ Recorded pre-emptively: if a trigger fires, this specialization is probably still the wrong instrument. The career-adjacent entry point for a Python data engineer is PyO3 + maturin — writing Python extensions in Rust — not a general Rust-for-DE curriculum that rebuilds ETL, SQL clients, serverless and CI/CD in a second language already held in the first. Written down now precisely because a fired trigger creates urgency, and urgency auto-selects the nearest course. (5) 📊 The posting evidence restated, because the watchlist row must not be mistaken for a softening. CORRECTION 22 measured SQL 79.4% · Python 71–73.7% · Spark 41.1% · Java 22.6% · Scala 17.5% · JavaScript 3.4% — Rust did not clear the threshold to be counted at all. 2026 data sharpens rather than reverses this: postings +35% YoY, mid-level salaries clearing ~$130K, 45% of companies running some Rust in production — but concentrated in systems and infrastructure, with the explicit practitioner caveat that product and frontend teams hire Rust roughly never, and with enterprise adopters holding more Rust planned than deployed. Composite-index placement is #7–8 with a job market still a fraction of Go's, and the optimistic projection is conditional future tense — postings could move from #10–12 to #8–10 if the enterprise pipeline converts. Decisively: where Python and Rust do co-occur in a posting, the conjunction is "or", not "and" — structurally identical to the "Pandas, PySpark, or Polars" pattern recorded in CORRECTION 35 §10, and read the same way: a signal that the employer wants a competent systems thinker, not two languages. (6) ❌ Two Duke specializations evaluated and NOT selected — logged so the absence is a decision, not an omission. Python, Bash and SQL Essentials for Data Engineering (Duke — Behrman, Gift, Deza; 4 courses, ~4 months at 5 hrs/wk, 23,405 enrolled, 468 reviews) declined on four grounds: (a) beginner level is the disqualifier — course 1 states no prior Python experience required, against seven repos already running uv, ruff, mypy, structlog, pre-commit and CI, which is the identical objection recorded against the IBM Git capstone in CORRECTION 29; (b) 🔴 it collides with CORRECTION 35 — the first course is Python and Pandas for Data Engineering, i.e. it teaches as its foundation the pattern this file ruled against days earlier; (c) anti-stack — it sits strictly below four committed Stage 2 rows (IBM DE Foundations · SQL for Data Science · PostgreSQL for Everybody · DeepLearning.AI DE Professional Certificate with AWS); (d) its Bash course re-raises a rationale already ruled out in CORRECTION 30 (zsh on Apple Silicon). Building Cloud Computing Solutions at Scale (Duke; Cloud Computing Foundations · Virtualization, Containers and APIs · Cloud Data Engineering · Cloud ML Engineering and MLOps) declined as overlapping the Docker & Kubernetes Masterclass (row 9), Terraform Fundamentals (row 11) and AWS DEA-C01 preparation. Shared falsifier for both: revisit only if a Stage-2 gap analysis finds a topic with no learning source that they cover — and check the pandas-first framing against CORRECTION 35 before enrolling. (7) ⚖️ Duke and Pragmatic AI Labs are NOT treated as equivalent, and the distinction is recorded rather than assumed. The same three instructors produce the Duke DE specialization, the Duke cloud specialization and the PAIML Rust catalog — one content operation, two brands — but the Duke-branded tracks carry real third-party validation (23,405 enrolments, 468 reviews) that the Rust catalog does not. University branding is doing genuine work here, and flattening the two would be as sloppy as conflating them. (8) 🔄 CORRECTIONS 22 and 35 confirmed, not amended. This correction strengthens both: the one artifact that could have counted as a genuine counter-signal to the Rust decline — a whole specialization exists — turns out on inspection to be a supply artifact. No ruling is reversed and no falsifier is loosened. (9) 🪞 One incidental corroboration worth recording: the Duke DE specialization instructs learners to build a demo video and GitHub repository per solution for a portfolio employers can inspect — independent, university-branded support for this file's proof-over-keywords thesis. Noted as corroboration, not as a reason to enrol. (10) Snapshot corrected 1–35 → 1–36. Cost: $0 — the watchlist row is Coursera-Plus-included and commits 0 hours. No course added to the committed load, none removed or substituted; no certification added — the canon stands at 9 committed + 1 conditional; no hours figure changed — the CORRECTION 22 hours deferral stands; scope-document propagation not executed here; archive untouched and byte-identical; additive-only apart from the snapshot count; no structural teardown; version stays v10.0.microsoft.agents to microsoft_agents — pin versions and re-verify signatures against the docs. (5) 💲 PRICE ERROR CORRECTED — the dbt AE certification is ~$200, not $0. Two budget lines carried "conditional dbt AE adds $0 (commonly free)" while the exam row itself said ~$200 — the file contradicted itself. Current evidence backs the row: 65 questions · 120 minutes · 65% pass · $200 fee · online proctored via Talview, blueprint targeting dbt 1.7. The "commonly free" figure most likely derived from historical Coalesce and community voucher programs. ⚠️ Falsifier attached: Fivetran and dbt Labs have merged, and post-merger the community-voucher route is exactly the kind of program that quietly lapses — verify the exam and any voucher path still exist at booking. (6) ⏱️ dbt AE trigger tightened from reactive to observable. The former condition — "take only if AE applications stall" — fires during the apply window, while preparation runs 4–6 weeks; that lands exam prep in the middle of applying. Replaced with two forward-looking conditions: (a) the Q1 2027 apply list names dbt certification in ≥3 postings, or (b) DataVault S2 dbt models ship before the window opens with budget slack remaining. The underlying ruling is unchanged and was correct as written — the tested dbt project with CI is the primary signal and the cert is the tiebreaker, not the unlock. Only the timing moved. (7) ❌ DP-600 / Microsoft Fabric Analytics Engineer declined. Four grounds: (a) it would stack a second Fabric credential on top of the committed DP-700, breaking the one-per-slot rule; (b) its skill surface is Power BI, DAX and semantic models — a BI developer's credential wearing an AE title, not the dbt/warehouse-modeling AE this file targets; (c) the AE market clusters on dbt plus Snowflake/Databricks, not Fabric; (d) ⚠️ a definitional catch worth recording — the Coursera "Microsoft Fabric Analytics Engineer Professional Certificate" is not a certification at all; it is a course bundle preparing for the DP-600 exam, and under this file's standing rule a Coursera shareable is Tier 4/5 learning evidence, never a Certifications line. Falsifier: revisit only if the Q1 2027 apply list skews decisively to Microsoft shops — the same trigger as AB-620, and if that trigger fires, both are re-evaluated together as one Microsoft-specialization decision rather than piecemeal. (8) 🎓 NO UNIVERSITY OFFERS AN ANALYTICS-ENGINEERING SPECIALIZATION — searched and recorded so it is not searched again. Everything on offer is vendor or publisher: Edureka (Analytics Engineering with dbt — 3 courses, 8 weeks at 5 hrs/wk, ⚠️ AI-graded assignments, which is not third-party validation and is most of what a course credential is supposed to supply), Packt (Fundamentals of Analytics Engineering), and a Coursera own-brand pipeline specialization. This absence is structural, not an oversight: AE is a practitioner role defined largely by one vendor's tool and a set of workflow conventions; universities teach the components — databases, dimensional modeling, software engineering — but the role outruns curriculum committees. (9) 🏛️ The AE formalization already exists in three layers and needs no addition. Vendor-official credential → dbt Labs certification, proctored, which certifies the role rather than the tool; academic canon → Kimball & Ross, The Data Warehouse Toolkit, committed in the CORRECTION 34 books layer and precisely what a university AE course would assign; evidence → DataVault S2 reconciliation models as tested, CI-gated dbt models. OMSCS remains the recognized-university layer. An Edureka specialization would sit below all three and add a shareable that would never be listed — nothing added. (10) 📉 Budget restated. Committed drops from nine ≈ $1,194 to eight ≈ $1,029 as AB-620 moves out. Conditionals now: lakehouse slot $165–$200 · dbt AE ~$200 (was mis-stated as $0) · AB-620 ~$165. Full-canon ceiling ≈ $1,594, up from $1,394 — the ceiling rose because an error was corrected, not because scope grew. (11) Snapshot corrected 1–36 → 1–37. No course added, removed or substituted; no certification added — one moved committed → conditional; no hours figure changed — the CORRECTION 22 hours deferral stands; scope-document propagation not executed here; archive untouched and byte-identical; no structural teardown; version stays v10.0.microsoft.agents → microsoft_agents import-root churn already logged in CORRECTION 37 §4. (5) 🏛️ ADR-009 restated inside the row, not merely referenced. Agent 365 works with agents built on any SDK — explicitly naming the Claude Code SDK, OpenAI Agents SDK and LangChain — so the M365 Agents SDK is a channel layer, not a brain transplant: Anthropic SDK stays primary; Ollama stays mandatory for non-synthetic runs; synthetic data only on this surface, which routes through Microsoft cloud and must never touch the regulated path. (6) ✅ AE COURSE SEARCH CLOSED — no course or specialization is weighted by recruiters for Analytics Engineering, and four independent sources converge. Certificates are losing weight, with many programs teaching outdated tooling that does not match industry stacks; hiring managers weigh skills, portfolio, communication and business understanding in combination, with certifications working only alongside hands-on evidence; a 1,000-posting analysis concluded certifications help pass initial screens but never produce an offer alone; and portfolio guidance is blunt that 3–5 projects beat 10 certifications — with the README named as the single most-read file, often the only thing a hiring manager reads. Combined with CORRECTION 37 §8 (no university offers an AE specialization), this line of search is now closed and should not be reopened without new posting evidence. (7) 🎯 STRIKING EXTERNAL VALIDATION — recorded because it is the strongest corroboration of an existing standard found in any research pass. A Databricks hiring-manager guide names "the Certification Paradox — why having more certifications can sometimes signal less capability" and identifies three callback signals: Production, Cost, Architecture. Those are verbatim and in the same order the three mandated leading README headings in architecture-docs.mdc. This portfolio's README standard independently reproduces a hiring manager's scoring rubric. No change follows — the point is that no change is needed, and the standard should not be softened in any future propagation pass. (8) 📖 Theory-first learning affirmed as legitimate — a governing clarification, not a concession. "Evidence over credentials" governs what is SHOWN, not how learning happens. These are different axes and were being conflated. This file already sequences theory → practice (courses feed projects), and for a learner with 15+ years of business operations, building the conceptual map first is more efficient, not less — existing schemas give new concepts somewhere to attach. The failure mode this roadmap guards against is STOPPING at theory, not starting there. Recorded so no future pass mistakes the evidence standard for a prohibition on studying. (9) 📘 The theory-first AE path resolved with existing assets — nothing purchased. dbt Fundamentals (dbt Labs Learn, FREE, vendor-official — matching the Confluent/HashiCorp/Astral/Neo4j pattern) → Kimball & Ross, The Data Warehouse Toolkit, already committed in the CORRECTION 34 books layer and the university-grade AE theory text, since dimensional modeling is the part of AE that does not churn → dbt Labs' "How We Structure Our dbt Projects" (FREE, and separately noted as near-free points on the dbt certification) → then DataVault S2 models. ❌ Edureka Analytics Engineering with dbt declined — its assignments are AI-graded, which is not third-party validation, and third-party validation is most of what a course credential is supposed to supply. (9.5) 🔗 Link defect caught by the user on review and repaired same-session: row 1️⃣5️⃣ linked modules ①, ② and ④ but left ③ as plain text — the one module that actually wires Azure OpenAI to Teams, i.e. the most load-bearing of the four. Now linked, and its title corrected to the real one — Utilize an Azure OpenAI model to create an Agent, not "create an app". Row content expanded with what the module actually teaches, including the in-code retrieval vs Action Planner choice, which is a genuine ADR-able decision for PostCheck rather than a course detail. Lesson recorded: a partially-linked row is worse than an unlinked one — it reads as complete and the gap goes unnoticed. Any future row with enumerated sub-resources must have every item linked or none. (10) Snapshot corrected 1–37 → 1–38. Cost $0 — both new rows are free vendor-official paths. No certification added, removed or changed — the canon stands at eight committed + three conditional; no paid course added; no hours figure changed — the CORRECTION 22 hours deferral stands; scope-document propagation not executed here; archive untouched and byte-identical; additive-only apart from the snapshot count; no structural teardown; version stays v10.0.F2 switching is seamless) · local Ollama for planning. Both cloud providers are configured simultaneously — retaining OpenRouter costs nothing and removes the single-provider failure mode when a Go window blocks. (3) 💵 Go's limits are usage allowances, not spend. $12/5h · $30/week · $60/month are denominated in list-price value, not billing: the subscription is a hard $10 ceiling provided "Use balance" stays OFF in the Zen console, which makes Go block at its limits rather than bill through. The monthly cap binds before the weekly one ($30/wk would imply ~$129/mo against a real $60 ceiling), so the pacing target is ~$15/week, not $30. At 25 hrs/week that is roughly $0.56/hour, and the 5-hour cap will effectively never bind — budget monthly, check the console at the start of week 3. (4) ⚠️ Tier is value, not volume — and the ordering is counter-intuitive. A cheap reduced-tier model can buy more requests than a costly full-tier one: minimax-m3 FULL ~16,000/mo · deepseek-v4-pro REDUCED ~5,200/mo · glm-5.2 FULL ~4,300/mo · kimi-k3 REDUCED ~490/mo. DeepSeek V4 Pro on the reduced tier outruns GLM-5.2 on the full tier. Unverified and flagged as such: whether the $15 and $60 figures are separate per-model allowances or proportional draws on one shared $60 pool — the vendor docs do not say plainly. Watch the console during month 1; if mixed usage drains faster than expected, it is a shared pool. (5) 🤖 Agent surface — 11 agents, 6 primary + 5 subagents. Primary (Tab-selectable): plan (local Ollama, read-only) · plan-cloud (GLM-5.2) · plan-cloud-hard (Kimi K3) · build (GLM-5.2, edit: allow) · build-gated (GLM-5.2, edit: ask) · learn (local Ollama, edit: deny). Subagents (@-invoked): docs-sync · docs-fix · eval-guardian · pattern-scout · security-auditor. Plus 9 slash commands — /commit-msg /draft-issue /eval /labels /pr-prep /readme /review /task-brief /test. (6) 🚪 Two build gates, deliberately distinct — the distinction is the ruling. build gates after the write via git diff review; build-gated gates before the write per edit. Neither is universally correct. Pre-write gating suits unfamiliar libraries and single-file work, where the slowdown is the value; it is wrong for large multi-file refactors (the S2 Polars ingestion rewrite is the named case), because per-edit approval hides the whole-change picture and long prompt chains produce reflex approval — a gate that feels real but is not. Precondition binding on both: start every session on a clean tree, or git diff mixes agent edits with uncommitted work and the review stops being trustworthy. (7) 🎓 Model allocation reasoned, not defaulted. Planning runs on GLM-5.2 rather than the cheaper MiniMax M3 because plan output is the architecture every later build depends on, and a bad plan propagates silently where a bad diff does not; plan volume (~80–120 calls/mo) is low enough that M3's larger allowance buys nothing. DeepSeek V4 Pro declined for planning — tied with M3 on composite intelligence, and it can look frozen in Plan mode (reasoning-MoE plus ai-sdk thinking-stream), a poor fit for an interactive loop. GLM-5.3 excluded from the standing ladder: reduced tier, first-party benchmarks only, weights promised but not shipped, while GLM-5.2 sits on full tier with ~4× the requests. Falsifier: adopt 5.3 only on independent benchmarks plus published weights. (8) 🚫 Anthropic subscription OAuth prohibited in any third-party harness. On 9 January 2026 Anthropic deployed server-side checks rejecting subscription OAuth tokens outside official Claude Code; on 19 February 2026 the terms added an authentication clause barring Free/Pro/Max OAuth tokens from third-party tools and the Agent SDK, and OpenCode removed all Claude OAuth code the same day. An account ban is on record. API-key and OpenRouter routing were never affected — the prohibition is on the subscription shortcut, not on Anthropic models. Falsifier: Anthropic publishes a sanctioned third-party authentication path. (9) ⚖️ Claude Code evaluated and DECLINED — recorded as a decline, not an adoption. It was assessed as a scoped secondary for long multi-file refactors and for its Learning output style, which inserts TODO(human) markers asking the human to implement strategic pieces — the only native mechanisation of the conceptual-inquiry pattern found in the survey. It was not adopted: OpenCode's build-gated agent enforces the same invariant by configuration, and a second $20/mo harness could not be justified against a $10 flat subscription already covering the work. Falsifier: revisit if the S2 Polars rewrite proves that OpenCode's speed penalty (~78% longer on identical tasks in one head-to-head, part client-server overhead and part an LSP loop that catches real bugs) costs more than $20/mo of the 25 hrs/week budget. (10) 🚫 Also declined, with falsifiers. Roo Code — repository archived 15 May 2026, read-only; a workflow built on it would rest on a dead project. Windsurf / Devin Desktop — three ownership changes in two years (Codeium → Windsurf → Cognition, renamed June 2026) and two pricing-model changes in twelve months; platform risk unacceptable for a 32-month roadmap. Claude Code desktop GUI — writes to disk with no pre-write diff review, incompatible with the governing constraint even where the CLI is not. (11) 📋 Command-vs-agent distinction recorded, because it is a security boundary and not a style preference. An agent owns a model and a permission set; a command is a saved prompt. A prohibition written in a command body is persuasion; a permission denied in an agent is architecture. Consequence, recorded because it is easy to miss: a command specifying agent: build executes with build's write permissions even when invoked from a read-only plan agent — a command is a legitimate route into a more permissive agent, and subtask: true plus a model: override further decouple it from the active session. (12) ⚠️ Frontmatter syntax defect found and recorded. Command and agent files are Markdown, but the block between the --- fences is YAML: HTML comments there are parsed as part of the scalar value, silently invalidating the field with no error. Frontmatter takes #; the body takes <!-- -->. (13) 🧪 One behaviour left open by design: whether !`shell` template expansion respects the active agent's bash permission. If it does, the shell-running commands break under a bash: deny plan agent; if it does not, bash: deny is not a boundary against commands. To be settled by observation, not assumption — run /test once from local plan. (14) Cost: $10/mo committed (OpenCode Go), against $0 previously. See CORRECTION 41 for the net position. No course added, removed or substituted; no certification added or changed; no hours figure changed — the CORRECTION 22 deferral stands; scope-document propagation not executed here; archive untouched and byte-identical; additive-only apart from the snapshot count; no structural teardown; version stays v10.0. Snapshot corrected 1–38 → 1–39..cursor/rules/*.mdc files are retained and still load — OpenCode's instructions array reads them directly, so the rules layer survives the tier change intact and no rule file is rewritten or duplicated. (6) 🚫 Not propagated, and recorded rather than silently skipped: the v9.2 toolchain table carrying Cursor AI IDE — $20/mo — ⭐ Primary editor sits in the Archive, which is never modified. The live body carries no Cursor pricing cell, so this correction requires no body edit — the changelog is the whole of it. (7) ⚠️ One live-body phrase is now stale and is flagged, not edited: the CORRECTION 35 Polars discussion refers to a "dual-harness Cursor + OpenCode workflow". Under CORRECTION 39 §1 that is single-harness OpenCode hosted in Cursor. The mitigation it describes — the Polars idiom block in python-core.mdc — is unaffected and still correct, so the phrase is left for a future consolidated pass rather than reaching into another correction's prose here. (8) Cost: −$20/mo. No course added, removed or substituted; no certification added or changed; no hours figure changed; archive untouched and byte-identical; additive-only apart from the snapshot count; no structural teardown; version stays v10.0. Snapshot corrected 1–39 → 1–40.gitleaks and detect-private-key (Tier A, CORRECTION 21 canon) are the boundary; the prohibitions written into the OpenCode command prompts are advisory reinforcement, not gates — the same command-vs-agent distinction recorded at CORRECTION 39 §11, applied to data rather than permissions. ⚠️ Gap recorded, not closed: gitleaks is tuned for credentials and keys, not for SSN-shaped strings or personal names in a CSV fixture. A custom rule is the obvious remedy and is logged here as outstanding work rather than claimed as done. (5) 🖥️ Local planning retained regardless. plan stays pinned to local Ollama and small_model stays local, so session titles never reach a provider. The justification changes rather than disappears: not because repository code is sensitive — it is not — but because a planning session may carry production data shapes, real record structures or operational detail typed by the human that never enters the repository. The repository being public does not make everything typed into a session public. (6) ⚠️ Ollama :cloud tags flagged as a live hazard. Several models publish a :cloud tag alongside the local one; pulling the cloud tag does not give local inference and would silently void the §5 guarantee while appearing to honour it. Verify the tag, not the model name. (7) 📊 Local plan model — an evidence gap recorded honestly. Qwen 3.5 9B has no published benchmarks; at least one tracker lists it without benchmark rows rather than inventing them. The selection therefore rests on hands-on judgement, not evidence, and is recorded as such. Falsifier: if planning quality proves inadequate, the benchmarked alternative is Qwen3.6-27B (77.2% SWE-bench Verified, Apache 2.0) — but at ~17 GB Q4 it is tight on 16 GB unified memory; the documented 16 GB fits are gpt-oss:20b and Gemma 4 12B. (8) Cost: net −$10/mo recurring; $0 one-off. No course added, removed or substituted; no certification added or changed; no hours figure changed — the CORRECTION 22 deferral stands; scope-document propagation not executed here; archive untouched and byte-identical; additive-only apart from the snapshot count; no structural teardown; version stays v10.0. Snapshot corrected 1–40 → 1–41.build-gated diff review would not have caught, it is ceremony and should be dropped. (2) ⏱️ Hours model made explicit for the first time — and this is the first correction in the file to touch the hours governance. Every correction from 1 to 43 closes with “no hours figure changed”. That is no longer accurate to say, so the ruling is stated plainly rather than left implied: 🔒 the official hours model is 25 hrs/week. Exceptions to expand beyond it are granted on a case-by-case basis and are subject to review. The 25 hrs/week headline figure, the CORRECTION 22 deferral and every downstream schedule are unchanged — what changes is that expansion is now a named, reviewable instrument instead of an undocumented drift. An exception is not a permanent raise: each one is granted for a named item, carries a review point, and lapses when the item ships. ⚠️ Recorded honestly: this is looser than the capped variant discussed in session (25 base + a hard-capped extra-time allowance with a pause rule). The looser form is what was ruled; the cap is not part of this ruling and is not in force. Falsifier: if two consecutive review points find the exception standing rather than lapsing, the model has become 29 hrs/week by stealth and must be either re-based or re-capped. (3) 📜 Two exceptions granted under §2, both self-funded extra-time threads opening Week 9. (a) AB-620 — moved from CONDITIONAL to committed GO, superseding the conditional status recorded at CORRECTION 37. Self-funded; exam booked after 9 October 2026 (Day 82, the employment end date), so it cannot compete with the exit checklist. (b) Google — Introduction to Git and GitHub, extra-time thread, same Week 9 opening. ⚠️ Flagged for ratification, not asserted: the hours each thread consumes are not fixed here. §2 requires a named review point per exception and neither has one yet. Both remain subordinate to DataVault S2, the CORRECTION 22 evidence gate for the Q1 2027 apply window. (4) 📍 Snapshot count settled — the open item CORRECTION 43 flagged. C43 recorded that the CURRENT STATE SNAPSHOT still read “Corrections 1–38 applied” while the changelog ran through 43, and left it untouched “pending an explicit ruling” because C42’s number was reserved. That ruling is made here: the snapshot is corrected 1–38 → 1–43. This is the only live-body edit in this correction and it is a count, not prose. (5) 📐 Two ADRs recorded, one amended. ADR-001 §5a added — opencode.jsonc lives at the repository root, not in .opencode/, which holds agent, command and plugin directories only. Records two consequences: .opencode/ loads after project config, so an agent defined in both resolves silently to the markdown file (one home per agent — single-source-no-drift applied to the harness itself); and current docs specify plural subdirectory names with singular retained only for backwards compatibility. ADR-002 written — the Claude Code model ladder (Haiku for mechanical fan-out, Sonnet as floor and default, Opus for pattern-scout only), which had been running as an unrecorded preference. Its most consequential finding is not the tier split: ⚠️ on a subscription the scarce resource is allowance, not dollars, and every forked subagent opens its own context window — so fan-out may cost more than tier choice saves. ADR-002 §7 declines flat-Sonnet-everywhere with a falsifier that would delete the ADR, and §6 records a live hazard: a cybersecurity-flagged request can silently move a session to a fallback model and keep it there — which lands hardest on security-auditor, the agent most likely to trip it. (6) ❓ Not ratified here, deliberately. dual_harness_workflow.md v2.0 remains at PROPOSAL status with six open verification questions, the highest-priority being whether disable-model-invocation: true breaks explicit slash command invocation. Open questions are settled by observation, not by reasoning — the standing rule from the CORRECTIONS discipline — so this correction adopts the harness without ratifying the workflow document that describes it. Also outstanding and not closed here: the agent/ → agents/ rename (blocked on auditing scripts/build_claude_agents.py and the claude-agents-check pre-commit hook for hardcoded paths); the gitleaks PII gap recorded at CORRECTION 41 §4; and the stale “dual-harness Cursor + OpenCode” phrase in CORRECTION 35, which — note the irony — is now accurate again on its face but for the wrong reason, and is still left for a consolidated pass rather than edited inside another correction’s prose. (7) 🔒 Privacy boundary unchanged and restated, because the new harness narrows it. Claude Code has no local-model option — it reaches Anthropic’s servers only. The proprietary 1099 / DataVault production repository is never opened in Claude Code. Regulated work stays on OpenCode with the local Ollama plan model exactly as CORRECTION 41 §5 records. guard.py blocks reads under data/raw/, data/processed/, data/outputs/ and any .env as a backstop, but the real control is not opening the repository there at all — the CORRECTION 39 §11 command-vs-agent distinction applied once more to data rather than permissions. (8) Cost: $0. The Claude Code extension runs on the existing subscription; no new recurring or one-off spend. The CORRECTION 41 net position of −$10/mo is unchanged. AB-620 moves from conditional to committed within the existing self-funded certification canon — no new certification is added and none is removed; the Surviving Nine (+1 conditional) structure is untouched. No course added, removed or substituted. ⚠️ Hours governance changed — see §2; the 25 hrs/week figure itself is unchanged. Archive untouched and byte-identical; additive-only apart from the snapshot count; no structural teardown; version stays v10.0. Snapshot corrected 1–38 → 1–43 (settling the count C41 recorded and C43 deferred).signalcore, Crucible and AFC) — the largest single gap found in the audit: point-in-time correctness had no learning row anywhere in v10.0. Courses ①②④ are flagged as overlapping existing coverage and ⑦ (capstone) carries a two-part warning that DataVault already is that capstone and that the one-system-never-rebuilt principle breaks if the rubric forces a second architecture. Recognition caveat recorded honestly: the programme is new and low-enrolment, carries no recruiter recognition yet, and remains Tier 4 — never a Certifications line. Both market directions are logged, including the practitioner counter-evidence that "AI-focused DE" is often a renamed DE role with flat comp — a scope premium to negotiate, not a title to chase. Hard constraint: subordinate to DataVault S2, the CORRECTION 22 evidence gate for the Q1 2027 apply window. (4) 🆕 Stage 3 row 1️⃣6️⃣ added — IBM AI Engineering Professional Certificate, as a WATCHLIST row (0 hrs committed), by approval, mirroring the Rust watchlist instrument at Stage 2 row 2️⃣0️⃣. This is the classical ML / deep-learning track (scikit-learn, Spark ML, Keras, PyTorch, TensorFlow) — precisely the job family the v10.0 restructure cut. That ruling is unchanged; the row exists so the door is documented, linked, dated and falsifiable rather than closed by silence, and so a future re-check has a pre-vetted entry point. Four triggers recorded (real ML/DL openings on the live apply list · a named employer requiring model training · a loop rejection traced specifically to classical-ML depth · OMSCS electives spent on ML/DL, which makes the PC redundant by construction). Substitution order recorded: the OMSCS route outranks this PC under the existing degree-over-credential qualification, and its deep-learning content overlaps the Stage 1 IBM GenAI PC and the Stage 3 HuggingFace LLM Course. (5) Declines reaffirmed and logged as evaluated-not-selected: full IBM Data Engineering PC · Generative AI Engineering with LLMs (contained) · IBM AI Engineering PC for present enrolment (parked, not taken). ⚠️ Open item flagged, not corrected in this run: the CURRENT STATE SNAPSHOT still reads "Corrections 1–38 applied" while the changelog runs through 41 — CORRECTION 41 recorded a snapshot fix that is not reflected in the live text. CORRECTION 42 remains unwritten and its number is reserved, so the snapshot count is left untouched pending an explicit ruling. No course removed or substituted; no certification added or changed; no existing row deleted or reworded; the Surviving Nine (+1 conditional) is untouched; archive untouched and byte-identical; strictly additive; no structural teardown; version stays v10.0.Shared_SignalCore_Boundary_Spec §4). (2) 🛡️ The protective half is adopted. Crucible Full-Production §6.1a classifies every order as risk-reducing (moves toward flat, can never open or flip a position — bracket stop/target legs, time exits, tightened stops, kill-switch flatten) or risk-increasing (any entry, scaling in, any reversal, any loosened or cancelled stop). Bracket legs are signed with the entry and inherit its signature, so "zero unsigned live orders" holds while stops fire unattended; a deterministic flip test in the Python core rejects any exit that would cross zero. ADR required; adversarial tests added. (3) 🚫 The reversal half is declined as a safeguard (Full-Production §6.5): it adds exposure at the moment the system is shown wrong, commonly doubles size against micro-sizing, and its payoff is conditional — stop-loss rules lower expected return under a random walk and add value only under momentum (Kaminski & Lo, Journal of Financial Markets, 2014); in chop every false flip is paid twice. Short legs also face the SEC Rule 201 circuit breaker, borrow/locate limits and borrow fees, which Alpaca's paper environment does not simulate. (4) 🧪 Re-entered as a hypothesis: SAR-on-stop (Crucible Stage-1 §4.1) — overlay plugin, baseline = exit-to-flat on identical entries, reversal size ≤ parent, one reversal per trade, Rule 201 and borrow exclusions, pre-registered pass criteria, failures logged to the overfitting ledger; every reversal entry is a new proposal behind verifier + human sign-off. Backlog only — never Phase 1. (5) 🧩 Shared primitive: the Rule 201 restriction check became signalcore.shortsale.rule201_state (triggered / restricted / unknown arrays; acting on it stays in Crucible). AFC gained a descriptive §5.6 failed-signal follow-through analysis (kept in AFC by CORRECTION 46). Crucible scope references repointed to Shared_SignalCore_Boundary_Spec_v1_5.md. (6) Positioning: the story is "I evaluated a reversal rule and here is the ledger entry", never "it generates gains". Propagation: Crucible Full-Production v1.0, Crucible Stage-1 v3.1, AFC v9.0, AFC eval-first slice v1.3, Shared SignalCore Boundary Spec v1.5. Cost: $0. No course added, removed or substituted; no certification change; no hours figure changed; archive untouched; additive apart from the snapshot count; version stays v10.0. Snapshot corrected 1–44 → 1–46 (CORRECTIONS 45 and 46 now both written).AFC_PROJECT_REVIEW_2026-10-02.md), which found that AFC v9.0's backtest contradicted this file's positioning line ("no returns, no factor construction, no backtest"). Manuel's ruling: AFC keeps a historical backtest so any combination of triggers can be tested and trigger decisions are data-driven. (1) 🧭 Positioning amended in place — the superseded sentence is preserved struck-through in the positioning box with the new text appended: AFC is financial NLP/RAG with an eval spine plus a read-only event study reporting hit-rate lift over a base rate under statistical controls; no factor construction, no alpha/Sharpe/return claim; still not a quant project. The portfolio row carries the same note. (2) 🧱 Stage split: S1 Phase 1 = eval-first core (publishable first) → S1 Phase 2 = backtest v1 on the triggers that are point-in-time clean with free data (T1 insider P purchases and T5 dilution state on EDGAR acceptance times; T4 volume from prices) → S2 adds T2 (Wikipedia), T3 (news) and T6 (short interest) once the lakehouse stores each source with its knowledge time; full combination matrix by end of S2. (3) ⚖️ Mandatory controls — the price of keeping it: per-source knowledge time (an event drives an entry only if known before that session's open); survivorship-aware historical universe with as-traded screening; rolling walk-forward with embargo and a sealed final holdout; base-rate lift with Benjamini–Hochberg false-discovery control across every combination tested — with ~155 combinations at 5% significance and no real effect, about 8 would still look like winners by chance. (4) 🔧 Tooling replaced: the factscore package cannot install on the Python 3.14 floor (pins torch<2.0, openai<0.28) and its original InstructGPT-era models were shut down by OpenAI on 4 Jan 2024 → FActScore implemented as a documented protocol re-implementation; pandasai requires Python <3.12 and carries CVE-2024-12366 (prompt-injection RCE, CVSS 9.8) → validated text-to-SQL (sqlglot whitelist, read-only DuckDB). (5) 🧩 Shared contract fix: signalcore short-interest knowledge time is now the FINRA publication date, not the settlement date (Boundary Spec v1.5 correction) — protects Crucible as well as AFC. (6) 📝 CORRECTION 45 (stop-and-reverse ruling: placed in Crucible; protective stops as bracket legs signed with the entry; Rule 201 made a shared signalcore primitive) is reserved and remains unwritten pending Manuel's approval of its text — the same pattern as CORRECTIONS 42/43 — so the snapshot count is left untouched pending that ruling. (7) ⚠️ Open item, not executed here: the matching Falsification List entry in MARKET_ANALYSIS_v9_3.md needs the same amendment. (8) Propagation: ATTENTION_FLOW_CATALYST_SCOPE_v9_0.md, the new Stage-1 build sheet ATTENTION_FLOW_CATALYST_SCOPE_v9_1_STAGE1.md, and Shared_SignalCore_Boundary_Spec_v1_5.md. Cost: $0. No course added, removed or substituted; no certification added or changed; no hours figure changed; archive untouched; additive apart from the struck-through positioning sentence; no structural teardown; version stays v10.0. Addendum (same correction, same month): the AFC review batch was approved and applied — Stage-1 build-sheet decisions D-1 (single repo, package afc), D-2 (edgartools behind an adapter), D-4 (SelfCheckGPT library if it installs on 3.14, else prompt-variant re-implementation), D-5 (≥ 60 human-verified bases), D-6 (eval-first slice superseded by the Stage-1 build sheet; AFC Full-Production doc to follow), D-7 (tiered CI: deterministic on every PR, live evals nightly/on label, full runs manual), D-8 (judge provider ≠ analyst provider), D-9 (drop the ~50-stock cap if the power estimate requires) locked; AFC v9.0 hygiene fixes (repo tree, hardened Dockerfile, logging row, eval threshold directions, naming, stale version text); Crucible harness tree and Wikipedia knowledge-time note. Later the same day (D-6 completed), ATTENTION_FLOW_CATALYST_SCOPE_v9_0.md was promoted with git mv to ATTENTION_FLOW_CATALYST_SCOPE_v9_2_FULL_PRODUCTION.md — AFC's Full-Production scope, mirroring Crucible's split; section numbers preserved, build-level code moved to the Stage-1 build sheet's Appendix A, and S2 lakehouse / S3 read-only research-agent architecture added. No spend, hours or course change.ATTENTION_FLOW_CATALYST_SCOPE_v9_2_FULL_PRODUCTION.md (§5.7 new) and ATTENTION_FLOW_CATALYST_SCOPE_v9_1_STAGE1.md (§7B.9 new). Cost: $0. No course or certification added, removed or substituted; Stage-1 indicative duration +~2 weeks; archive untouched; additive; version stays v10.0. Snapshot corrected 1–46 → 1–47.ATTENTION_FLOW_CATALYST_SCOPE_v9_1_STAGE1.md §17 and timeline; ATTENTION_FLOW_CATALYST_SCOPE_v9_2_FULL_PRODUCTION.md take-order table. Cost: $0 (Coursera Plus + owned book). ~100 h of study added (~two-thirds required) inside the existing 25 h/week budget — no weekly-hours figure changed; no certification added, removed or substituted; archive untouched; additive apart from the reading-list counts and the snapshot count; version stays v10.0. Snapshot corrected 1–47 → 1–48. Addendum (same correction, same month) — layout-only pass on the three stage course tables: 43 long cells across 35 rows (Stage 1: 11 · Stage 2: 13 · Stage 3: 11) now show a one-line lead with the rest behind the same click-to-expand toggle already used on earlier rows (📝 Full rationale · 📚 Resources & notes · 🎓 Certificate detail · ⏱️ Timing detail). No course, cost, certificate, duration or rationale text was added, removed or reworded — verified by a text diff of every changed row. Rendered table heights: Stage 1 ≈ −46%, Stage 2 ≈ −27%, Stage 3 ≈ −24%. Row 1️⃣9️⃣ moved above the Stage 1 ⭐ Elective row so numbered rows stay in order.ATTENTION_FLOW_CATALYST_SCOPE_v9_2_FULL_PRODUCTION.md, CRUCIBLE_SCOPE_v1_0_FULL_PRODUCTION.md and CRUCIBLE_SCOPE_v3_1_STAGE1.md. (5) ⚠️ Flagged, not changed: the certifications table lists AI-901 at ~$165 while the Snapshot lists $99 (Microsoft Fundamentals tier) — needs a one-line ruling. Cost: −$125 committed. No course added, removed or substituted; no hours figure changed; archive untouched; version stays v10.0. Snapshot corrected 1–49 → 1–50.ATTENTION_FLOW_CATALYST_SCOPE_v9_1_STAGE1.md §17 and ATTENTION_FLOW_CATALYST_SCOPE_v9_2_FULL_PRODUCTION.md take-order table. No course or certification added, removed or substituted; no hours figure changed; archive untouched; version stays v10.0. Snapshot corrected 1–50 → 1–51.MARKET_ANALYSIS_v9_3.md. It does not — the positioning box's link points to this file's own Falsification List, whose quant-lane entry named only Crucible. That entry now covers AFC as well: its AI-powered predictive layer is measured prediction under controls (lift over base rate, BH-FDR, walk-forward + sealed holdout, beat-the-best-rule), never alpha. (3) 📄 Companion updated: MARKET_ANALYSIS_v9_3.md gains an October 2026 status block for its certification section (7 committed + 3 conditional; all self-funded; Claude exams Partner-Network-gated), two new falsification items (AFC's predictive layer read as an alpha claim; vendor-gated credentials), resolved statuses for its four July open items, a quarterly salary re-verification flagged as due, three new source-register rows, and an update log. The July analysis is preserved unchanged above each addition. (4) ⚠️ Flagged, not changed: the AI-901 row's purpose text still says it "proves the reimbursement path", while the Snapshot states no employer reimbursement applies to any credential — needs a one-line ruling. Cost: $0. No course or certification added, removed or substituted; no hours figure changed; archive untouched; version stays v10.0. Snapshot corrected 1–51 → 1–52. Addendum (same correction, same month): item (4) resolved — the AI-901 purpose now reads "Cheapest first certification and the Stage 1 credential anchor — self-funded, like every credential in this plan", matching the Snapshot's no-reimbursement rule. The archived v9.2 row keeps its original wording. No cost, count or schedule change.dbt_project.yml; 1099_reconciliation_pipeline is the pandas S1 core with CI. (5) 🚦 Two-trigger search adopted: Soft trigger — a public dbt slice of DataVault on synthetic data (staging → marts, generic + Box-7-derivation singular tests, dbt build in GitHub Actions CI, published dbt docs) — opens a narrow search: referral-led and domain-matched first (retirement recordkeeping / wealth-retirement fintech, then the Charlotte/Atlanta finance list). Full S2 ship stays the evidence gate and opens the broad ~Q1 2027 search. The dbt slice is S2 work done first, not new scope — it counts toward the gate. Falsifier: if 25 targeted or referred soft-trigger applications yield zero recruiter or hiring-manager screens, pause the narrow search and return those hours to S2 until the gate ships. (6) ⚠️ Flagged, not changed: the hours-model question deferred at CORRECTION 22 §2 is now load-bearing — search time after 9 October competes with the 25 hrs/week build budget — and needs its own ruling; no hours figure moved here. Propagation: Current State Snapshot, Stage 1 fallback-is-the-path note, Stage 1 exit criterion, CORRECTION 22 §3 (inline annotations only), Stage 2 referral-geography block. Cost: $0. No course, certification or book added, removed or substituted; no hours figure changed; archive untouched; version stays v10.0. Snapshot corrected 1–53 → 1–54.ASOF JOIN) runs in learning_journey as practice, not portfolio; AFC's Phase-1 kickoff lands on plan Day 83 under the AFC build sheet's early-artifact clause. AFC's own dbt work stays in S2, as the build sheet states; Crucible's position (third; live path built last) is unchanged. (5) 🔀 Flex items: AI Prompting for Everyone moves to a flex slot; the four S2 short DL.AI labs become flex inside the Sprint-1 Pro month. Falsifier: if the soft trigger slips past plan Week 12, these pull-forwards are reviewed before Q2 adds any new thread. Propagation: Current State Snapshot, Stage 1 exit criterion, Stage 1 Core Courses rows 5️⃣ and 🔟, Stage 1 Deliverables (IBM line), Stage 2 Core Courses rows 5️⃣ and 6️⃣, Build Progression (S1 row + AFC slot note), Falsification List (inline annotations only). Cost: $0. No course, certification or book added, removed or substituted; no hours figure changed (25 hrs/week); archive untouched; version stays v10.0. Snapshot corrected 1–55 → 1–56.dbt build as a blocking CI step (Day 52); dbt docs on GitHub Pages (Day 58); v0.1.0 (Day 62); v0.2.0 with an SCD Type 2 snapshot and an idempotent incremental model (Day 69); dbt model contracts in plan Week 11 (S2 work done first, CORRECTION 54 §5); Track B items #1–#5 on the public 1099_reconciliation_pipeline pulled forward to plan Weeks 8–10; AE interview reps from plan Week 6; dbt Advanced from plan Week 10. (5) 🚦 Soft trigger → plan Day 63 (end of Week 9), so the narrow search opens Day 64. Day 70 stays as the fallback if any of the four artifacts is not green — the search waits for evidence, not the calendar. Falsifier: if the soft trigger still slips past Day 70 despite the freed hours, or 25 targeted applications produce zero screens (CORRECTION 54 §5), hours were not the bottleneck — the guardrail is reviewed and market fit is diagnosed instead. Propagation: Current State Snapshot, Stage 1 exit criterion, Stage 1 Deliverables (PolicyPulse and AI-901 lines), CORRECTION 17 lab-dependency table (Sprint-1 timing note), Falsification List (inline annotations only). Cost: $0. No course, certification or book added, removed or substituted; no hours figure changed (25 hrs/week); archive untouched; version stays v10.0. Snapshot corrected 1–57 → 1–58.✅ 2026-11-03) · — not pursued (declined rows only). (3) 🚧 Seeded from the learning_journey README (12 Oct 2026): CS50x, Python for Everybody, Mode SQL, Google Git, KodeKloud Docker, Building with the Claude API, Introduction to MCP, uv, C4 + ADR, the pre-commit series and dbt Fundamentals are marked 🚧; every other row starts ☐. (4) ✍️ How to update: edit the cell text in VS Code and commit — the file stays the single, git-tracked record, so progress shows on GitHub Pages. Exams appear both in the stage exam tables and in the Surviving Nine table; mark both. (5) ✅ Checklists: the ☐ deliverable lists gain a class="done" option that renders ✅ — add it to any <li> when that deliverable ships. (6) Not given a column: skill-plan, practice-platform, toolchain, portfolio, credential-ladder, comparison and compensation tables (reference or open-ended, not completable), and the Archive. Cost: $0. No course, certification or book added, removed or substituted; no content cell reworded; no hours figure changed; archive untouched; version stays v10.0. Snapshot corrected 1–61 → 1–62.The 2026 market is saturated at the keyword layer and starved at the evidence layer. Hiring managers report resumes dense in RAG/evals/inference keywords with little substance behind them; referrals and shipped production systems dominate; larger companies screen inbound with AI because it is drowning in AI-generated applications. The winning position is not more certificates or broader titles — it is proof: production systems with evaluation gates, deployed in a regulated domain, with stories a hiring manager can interrogate.
The moat: ~15 years of finance operations + ERISA-regulated domain depth + an eval-first engineering discipline (DeepEval/RAGAS blocking gates, faithfulness thresholds). FDE demand concentrates in fintech and regulated industries; a financial-services background appears as an explicit plus in frontier-lab FDE specs. Every stage below compounds this moat instead of resetting it.
Companion evidence document: MARKET_ANALYSIS_v9_3.md — salary bands, source register with bias ratings, and the falsification list. Re-verified July 2026; 🆕 updated October 2026 to the v10.0 certification canon and CORRECTIONS 45–52 (CORRECTION 52).
| Total Timeline | Weekly Hours | Structure | Direct Investment |
|---|---|---|---|
| ~32 months (3 stages) Employment milestones at ~M8, ~M18–20, ~M30 |
25 hours/week (unchanged — see schedule below) | 4 flagship projects · 7 committed certifications (+3 conditional) · OMSCS parallel degree track (Computing Systems) | ~$700–900 personal (all certifications self-funded) + optional OMSCS tuition |
| Stage | Timeline | Role / Goal | Core Evidence Produced |
|---|---|---|---|
| Stage 1 | Months 1–8 | Internal AI Builder — work label retained; employment ends 9 Oct 2026, available from that date | Production Python/SQL discipline · Anthropic SDK · evals · MCP · AI-901 → AB-620 · Flagship #1 (PolicyPulse) v1 shipping with eval gates |
| Stage 2 | Months 9–20 | AI-Focused Data Engineer / Analytics Engineer (dual-target; first external move ~M18–20) | Tested dbt project with CI · orchestration · warehouse · data contracts · Docker/ECS · production-ops layer · DP-700 + AWS DE Associate · DE flagship production-hardened |
| Stage 3 | Months 21–32 | Applied AI Engineer → FDE track (~M30+) | Production agentic systems with eval frameworks as blocking gates · ML-literacy module · Databricks GenAI + Neo4j (+ CCDV-F/CCA-F if Partner Network access) · customer-facing evidence (talks, deployment stories) · decomposition interview readiness |
There is no longer a fallback — the fallback IS the path. The external search is the primary route, targeted Analytics Engineer first, Data Engineer in parallel, apply window ~Q1 2027. 🆕 CORRECTION 54: the narrow search opens earlier, at the soft trigger (public DataVault dbt slice shipped); the broad search still waits for the full S2 ship. The one clause that survives intact: not a Data Analyst search, under any circumstance. 🆕 CORRECTION 55: clarified, not reversed — generic analyst postings stay excluded; the bridge tier admits only in-domain technical data roles whose postings require SQL plus a warehouse or automation platform.
| Day | Time Blocks | Daily Hours | Focus |
|---|---|---|---|
| Monday – Friday | 4:30 AM – 6:00 AM 8:00 PM – 10:00 PM | 3.5 hrs/day | Morning: courses/videos · Evening: hands-on project work |
| Saturday | 5:00 AM – 8:30 AM 8:00 PM – 10:00 PM | 5.5 hrs | Deep work: flagship projects, production hardening |
| Sunday | 7:30 PM – 9:30 PM | 2 hrs | Week review, community/content, planning |
| TOTAL | – | 25 hrs/week | Consistency > intensity |
Goal (re-anchored, stage name retained by ruling): the build work is unchanged — production automations, the engineering foundation and Flagship #1 continue to ship, including through the two-month handover. What is retired is the employment premise: there is no internal elevation, no employer-funded certification of any kind, and no "no comp reset". "Internal AI Builder" is kept as the work label, not an employment claim. No external analyst search — that ruling stands unchanged (🆕 CORRECTION 55: the domain-bridge tier inside the narrow search is not an analyst search — see the Career Progression note).
Exit criterion (evidence gate, per CORRECTION 22): DataVault S2 hardening shipped. The internal-scope-change criterion is superseded — it is not achievable and is retained above only for changelog integrity. Primary path: external Analytics Engineer (first door) / Data Engineer (parallel) search, apply window ~Q1 2027. Available from 9 October 2026. 🆕 Soft trigger (CORRECTION 54): the public DataVault dbt slice opens a narrow referral-led, domain-matched search before the gate; the gate itself is unchanged and still opens the broad search. 🆕 CORRECTION 56: the v3.0 activation plans build the slice dbt-first from plan Week 7 and schedule the soft trigger for plan Day 70. 🆕 CORRECTION 58: pulled to plan Day 63, with Day 70 kept as the fallback; AE/DE ≥ Applied AI in hours every fortnight until the first screen. 🆕 CORRECTION 59: until this gate ships — the gate is the readiness point at which Applied AI becomes the majority lane, whether or not an offer has arrived. 🆕 CORRECTION 55: the narrow search's target list includes the domain-bridge tier.
| Layer | Skills & Tools | Market Signal (2026, verified) | Where It Lands in Stage 1 |
|---|---|---|---|
| Production Python | Typed Python, uv (Astral) + uv.lock · pyproject.toml + src/ layout, ruff/mypy, 🆕 structured logging (structlog + stdlib ProcessorFormatter), typed config (pydantic-settings), capped retries (stamina), 🆕 pre-commit (pinned hook set, commit-msg stage enabled) | Python appears in 71% of AI-engineer postings — the #1 required skill (analysis of ~1,000 postings, 365 Data Science 2026); fundamentals outrank flashy skills in real demand. 🆕 uv is the 2026 default package/env manager (replaces pip + virtualenv + pip-tools + pyenv); a committed uv.lock is what makes "reproducible build" real. | Python for Everybody · AI Python for Beginners · CS50 · uv (Astral docs + Al Sweigart quickstart) · 🆕 structlog docs (Standard Library Logging + Logging Best Practices) · stamina + pydantic-settings docs — source-of-truth pattern, no course exists · 🆕 pre-commit: no certification exists and no real course exists — learn from the Stefanie Molin four-article series (stefaniemolin.com/articles/devx/pre-commit/: Setup Guide → Behind the Scenes → Hook Creation Guide → Troubleshooting Guide, ~2 hrs) as the named source-of-truth tutorial, with pre-commit.com as reference. Same treatment uv received in CORRECTION 13: docs + one authoritative tutorial, no course, no certificate, no platform badge · 1099-pipeline retro-migration to production standards + pip → uv migration (build-in-public artifact) |
| SQL foundations | Joins, window functions, aggregation fluency | ~79% of Data Engineer postings (the Stage 2 target) and 17% of AI-engineer postings require SQL; top skill across data roles | Mode SQL Tutorial · daily use in the 1099/DataVault work |
| LLM API engineering | Anthropic SDK: structured outputs, tool use, prompt caching; modern prompting | Frontier-model fluency is on the 2026 production-readiness hiring checklist; prompting is now "a prerequisite, not a standalone skill" | Building with the Claude API (Anthropic Academy) · AI Prompting for Everyone · PolicyPulse v1 |
| Evaluation literacy ⭐ | RAGAS/DeepEval, golden datasets, hallucination detection, eval gates in CI | THE 2026 DIFFERENTIATOR: 39.6% of AI-first roles explicitly require evaluation-related skills, yet it is among the rarest skills candidates list (~5.5%) — cited as the single biggest signal of real LLM experience, separating junior from senior | Improving Accuracy of LLM Apps · Building & Evaluating Advanced RAG · blocking eval gates on PolicyPulse v1 |
| RAG fundamentals | Chunking, embeddings, retrieval, the RAG Triad | The default enterprise pattern for grounding LLMs on private data — table stakes for applied-AI roles; RAG architecture adds +10–15% salary at mid-level (KORE1 2026) | Advanced RAG course · IBM GenAI Engineering PC modules · PolicyPulse v1 |
| MCP protocol literacy | MCP concepts, client-server architecture | MCP is the 2026 open standard for connecting AI agents to external tools; MCP integration sits on the 2026 hiring checklist | MCP primer (DL.AI) · groundwork for PolicyPulse's FastMCP server (Stage 3) |
| Containerization & shipping | Dockerfile, Compose, Git/Conventional Commits, diff-review-before-merge, 🆕 branch → PR → review → merge | Deployment skills (Docker/K8s, CI/CD) are what "separate prototype builders from engineers who can own production systems"; Docker/K8s rank in the top demand tier of posting analyses | Docker for Beginners (KodeKloud) · Dockerfile in every flagship per the README standard |
| Employer AI stack (Azure/Copilot) | Copilot Studio, Azure AI fundamentals, Microsoft Agent Framework awareness | Azure appears in 26% of AI-engineer postings (second only to AWS at ~33%); roadmap-internal: the employer already runs M365 Copilot on Azure OpenAI, making this the internal-elevation stack | AI-901 → AB-620 (reimbursed) · ZTM Azure Bootcamp · internal automation wins |
| Domain translation 🏰 | Turning ERISA/retirement-plan operations pain into automation specs with quantified outcomes | Roadmap-internal moat, externally corroborated: financial-services background is explicitly listed as a plus in frontier-lab FDE job specs, and FDE demand concentrates in regulated industries | Two documented internal automation wins (the 450+ tax-code correction pattern) · scope-change conversation evidence |
| Architecture communication 🆕 | C4 model (Context / Container views) + ADRs in docs/adr/ · Structurizr DSL as the single model source, exported to Mermaid for the README | ThoughtWorks Technology Radar places Lightweight Architecture Decision Records in the ADOPT ring — its strongest recommendation — and specifically prescribes storing them in source control rather than a wiki so the record stays in sync with the code. Both clouds on this roadmap's track endorse the practice: AWS publishes an official ADR process guide through Prescriptive Guidance, and the Azure Well-Architected Framework features ADRs. No proctored credential exists for either — this is a discipline, and the artifact is the signal. | Core Course #17 (C4 + ADR source-of-truth pack) · applied on the 1099-pipeline retro-migration pass · carried by every repo per the production standard |
| Order | Course | Platform | Cost | Certificate? | Duration | Why This Course | ✅ Done |
|---|---|---|---|---|---|---|---|
| 1️⃣ | CS50: Introduction to Computer Science 🔄 RESTORED v10.0 | edX/Harvard | FREE | ✅ Yes — free CS50 Certificate; edX verified certificate optional (paid, ~$149 — confirm on edX) · 🆕 C49: was "$90 optional" | 11 weeks | CS FUNDAMENTALS + OMSCS EVIDENCE! Algorithms, data structures, problem-solving.📝 Full rationale — click to expandWith OMSCS retained, CS50 is the most commonly cited CS-background evidence for career-changer applications — and FDE decomposition interviews test exactly these fundamentals. Complete before the OMSCS application window (Stage 2). | 🚧 |
| 2️⃣ | Python for Everybody Specialization | Coursera | Included (Coursera Plus) | ✅ Yes | 8 weeks | Dr. Chuck's legendary course, perfect for beginners, focus on data-relevant Python. | 🚧 |
| 3️⃣ | Mode Analytics SQL Tutorial | Mode | FREE | ❌ No | 2-3 weeks | SQL appears in ~80% of DE/AE postings — the single most load-bearing skill. Table stakes done properly. | 🚧 |
| 3️⃣.5 | Introduction to Git and GitHub (Google) 🆕 NEW | Coursera (Google) | Included (Coursera Plus) | ✅ Yes (shareable — Tier 4/5, never a Certifications line) | ~8 hrs committed⏱️ Timing detail — click to expandGoogle published duration ~20 hrs (4 weeks); committed target ~8 hrs — install, first-repo and account-setup modules skipped as already-evidenced, branching/rebase/conflict modules targeted. Secondary IBM course adds ~10.5 hrs only if taken; combined worst case ~18.5 hrs, of which only the Google ~8 hrs is committed. Optional overflow — never a reason to delay a build milestone. | THE COLLABORATION GAP.📚 Course selection, scoping & secondary option — click to expandGit was previously embedded inside the "Containerization & shipping" skills row with no course of its own; branching, pull requests and conflict resolution appeared nowhere in this file. Solo-repo fluency is already evidenced (7 repos, Conventional Commits, pre-commit); the untested skill is team workflow — branch → PR → review → merge, and recovering from a bad merge. Chosen over the IBM course on syllabus depth: this one covers the staging area, the HEAD alias, rebasing, conflict resolution and the pull-merge-push workflow, which is where a solo developer actually gets stuck, whereas IBM is weighted toward the GitHub web UI, forking and a capstone that asks you to create a public repo — already done seven times over. ⚠️ Scope it, do not complete it: skip the install/first-repo material and target the branching, rebase and conflict modules — ~8 hrs, not 20. ⚠️ Anti-stack note: the IBM course is a component of IBM Applied Software Engineering Fundamentals, already listed as the row-14 secondary option — taking it standalone would double-buy the same hours if that fallback is ever activated.🥈 Secondary (optional, conditional — ): IBM — Getting Started with Git and GitHub (Coursera Plus, ~10.5 hrs, shareable certificate). Genuinely non-overlapping scope, verified against both syllabi: IBM covers cloning and forking (the open-source contribution model) and managing GitHub Projects (Issues, boards) — neither appears in the Google syllabus — and its final project runs dual-track, Part 1 GitHub UI + Part 2 Git CLI. ⭐ The real reason to take it: the final project is peer-reviewed — you submit work and review other learners'. That is the one thing a solo portfolio structurally cannot manufacture, and it is a direct answer to the limitation recorded in CORRECTION 29. ⚠️ Conditional — take it only if IBM Applied Software Engineering Fundamentals (row 14 secondary) is NOT activated, since this course is a component of it and taking both double-buys the hours. ⚠️ Correction to the stated rationale: this course does not add Bash depth. Its desktop module is a reading, and Git Bash is a Windows shell — irrelevant on the Mac Mini M4 / MacBook Air M2 workstations, which ship zsh. The UI half of the rationale is correct; the Bash half is not, and Bash is not a reason to enrol. 🆕 C61 — re-check (Oct 2026): this row already covers the Google course circulating on social media. Live listing: 4.8★ on ~8K reviews, ~365K enrolled, four ~5-hr modules, the fourth on pull requests, code review and CI. Scope unchanged (~8 hrs); the parent Google IT Automation with Python PC is not taken. | 🚧 |
| 4️⃣ | AI Python for Beginners (Andrew Ng) | DeepLearning.AI | FREE (videos) | ⚠️ Pro only | 4-6 hours | PYTHON FOR LLM CONTROL! Variables, lists, loops taught in the context of prompting & API calls — bridges Python basics to SDK work. | ☐ |
| 5️⃣ | IBM Generative AI Engineering Professional Certificate 🔄 RESTORED v10.0 | Coursera | Included (Coursera Plus) | ✅ Yes (Professional Cert) | Months 3–6 (16 courses, compressed) · 🆕 C56: start moved to Month 4, after the soft trigger | THE STAGE 1 SPINE! Build, deploy, and fine-tune AI applications — not "an analyst who prompts ChatGPT." Structured 16-course path (HuggingFace, RAG, LangChain, watsonx, chatbots, capstone).📝 Full rationale — click to expandMid-tier resume credential per the credential hierarchy; its RAG/LangChain modules resurface directly in Stage 3 work.🗒️ Containment note (CORRECTION 43) — do not enrol separately: the IBM Generative AI Engineering with LLMs programme (marketed in Aug-2026 IBM Skills Network email as a Professional Certificate; it lists on Coursera as a Specialization, intermediate, ~12 weeks) is superseded-and-contained here — the same audit-closure treatment given the IBM RAG & Agentic AI PC in Stage 3. Its component courses (Generative AI and LLMs: Architecture and Data Preparation · Gen AI Foundational Models for NLP & Language Understanding · Generative AI Language Modeling with Transformers · Generative AI Engineering and Fine-Tuning Transformers · Generative AI Advanced Fine-Tuning for LLMs · Fundamentals of AI Agents Using RAG and LangChain · Project: Generative AI Applications with RAG and LangChain) are Coursera courses flagged "part of multiple programs" and sit inside this 16-course path. Taking it standalone double-buys the same hours — the identical anti-stack ruling applied to the IBM Git course in Stage 1 row 3️⃣.5. ⚠️ Verify at enrolment: Coursera marks already-completed component courses as ✅ Complete across programmes — confirm the overlap on your own dashboard rather than on this note. Credential effect: none — one Tier-4 Professional Certificate line, not two. 🗒️ Containment note (CORRECTION 61) — two edX listings, do not enrol: ① The edX listing of this same programme re-buys a credential already funded by Coursera Plus — take it on Coursera only. ② The IBM Applied AI Developer PC (edX) — counterpart of the Coursera IBM AI Developer PC (10 courses, ~146 hrs) — has 6 of its 10 courses (~82 hrs) inside this path; the other four (software-engineering intro, HTML/CSS/JS, two career-guide courses) are below the level the repos already evidence. Evaluated, not selected — same anti-stack ruling as CORRECTION 43. | ☐ |
| 6️⃣ | Building with the Claude API (Anthropic Academy) | Anthropic Academy | FREE | ✅ Yes (official) | 8+ hours | PROVIDER SOURCE-OF-TRUTH FOR THE CLAUDE SDK! 84 lessons — structured outputs, tool use, prompt caching. Underwrites both flagships; CCA-F on-ramp. | 🚧 |
| 7️⃣ | Improving Accuracy of LLM Applications | DeepLearning.AI | FREE (videos) | ⚠️ Pro only | 1-2 hours | BUILD AN EVAL FRAMEWORK FROM SCRATCH! Deliberately simulate hallucinations and systematically raise accuracy — the evidence-layer differentiator. | ☐ |
| 8️⃣ | Building & Evaluating Advanced RAG | DeepLearning.AI | FREE (videos) | ⚠️ Pro only | 1 hour | EVALUATION-DRIVEN DEVELOPMENT! The RAG Triad (Context Relevance, Groundedness, Answer Relevance) — applied directly to PolicyPulse. | ☐ |
| 9️⃣ | MCP: Build Rich-Context AI Apps with Anthropic (PRIMER) 🤖 Anthropic Academy alt (first-party): Introduction to Model Context Protocol | DeepLearning.AI · Anthropic Academy (alt) | FREE (videos) | ⚠️ Pro only | 1-2 hours | Protocol literacy BEFORE building PolicyPulse's FastMCP server.📝 Full rationale — click to expandTaught by Anthropic's Elie Schoppik. Retaken as full course in Stage 3. Academy alt builds MCP servers & clients from scratch in Python (tools/resources/prompts) — provider source-of-truth, official Anthropic completion cert. | 🚧 |
| 🔟 | AI Prompting for Everyone (Andrew Ng) 🔄 RESTORED v10.0 | DeepLearning.AI | FREE (videos) | ⚠️ Pro only on DeepLearning.AI — or a shareable certificate via its Coursera listing (confirm Coursera Plus coverage at enrolment) · 🆕 C49 | ~3 hrs (DeepLearning.AI) · ~8 hrs on Coursera · 🆕 C49: was "1-2 hours" · 🆕 C56: flex slot | MODERN PROMPTING (2026 refresh). Replaces the archived 2023 ChatGPT prompt course. Trivial time cost; current cross-model practice. | ☐ |
| 1️⃣1️⃣ | 30 Days of Streamlit Challenge | Streamlit | FREE | ❌ No | 2-3 weeks | BUILD AI UIs FAST! Deployment surface for both flagships and the IBM GenAI capstone. | ☐ |
| 1️⃣1️⃣.5 | 30 Days of AI Challenge (Streamlit) 🆕 NEW | Streamlit | FREE | ❌ No | 2-3 weeks (self-paced) | THE AI SUCCESSOR TO #30DaysOfStreamlit (launched Jan 2026)!📝 Full rationale — click to expandProgresses from first LLM calls, streaming and caching (week 1) → chat interfaces and session state (week 2) → RAG apps (week 3) → advanced techniques, built with Streamlit + Snowflake Cortex AI. Maps directly to the Internal-AI-Builder stage AND previews the Stage 2 Snowflake "one warehouse deep" choice (row 16.5) — synergy, not a detour. Caveat noted honestly: Cortex-flavored examples require a Snowflake trial account; the Streamlit/LLM patterns port to the local-Ollama stack. Take after (or instead of) the original challenge if the classic 30 Days basics feel below level. | ☐ |
| 1️⃣2️⃣ | Docker for Beginners with Hands-on Labs (KodeKloud) 🔄 RESTORED v10.0 | Coursera | Included (Coursera Plus) | ✅ Yes | 6 hours (1 week) | CONTAINERIZATION INTRO! Dockerfile, Compose, in-browser labs. Every flagship ships with a Dockerfile per the README standard — learn it before Stage 2's orchestration layer. | 🚧 |
| 1️⃣3️⃣ | CS50's Introduction to Programming with Python (CS50P) | edX/Harvard | FREE | ✅ Yes (free CS50 cert; verified optional) | ~10 weeks (self-paced) | CREDENTIALED PYTHON SWE-CRAFT ON YOUR STACK!📝 Full rationale — click to expandFunctions, variables, conditionals, loops, exceptions, unit tests & debugging, libraries, file I/O, regular expressions, and OOP/classes — the testing/debugging rigor that CS50x and Python-for-Everybody skim. Recognized Harvard credential, free certificate, pure Python. Chosen over the IBM Applied SWE Fundamentals specialization on brand + rigor + stack fit. Overlaps existing Python intros on the basics — move fast; the marginal value is the testing/debugging layer plus the credential. | ☐ |
| 1️⃣4️⃣ | MITx 6.00.1x: Introduction to Computer Science and Programming Using Python📚 Resources & notes — click to expand🔁 Secondary option (per approval): IBM Applied Software Engineering Fundamentals (Coursera) | edX/MIT · Coursera (alt) | FREE (audit); MITx verified cert paid · IBM alt: Coursera Plus | ✅ Yes (MITx verified cert paid) · IBM alt: ✅ (Specialization cert) | ~9 weeks (self-paced) | MIT-BRANDED CS FOUNDATIONS ON PYTHON.📝 Full rationale — click to expandComputational thinking, problem-solving, simple algorithms & complexity, basic data structures, and testing/debugging (Ana Bell, Eric Grimson, John Guttag); first of the 6.00.1x → 6.00.2x sequence. Note: overlaps CS50x/CS50P on the intro layer — its value is the MIT credential + reinforcement, not new depth. ⚠️ Currency caveat: the course materials still target an older Python version (edX description cites Python 3.5) — the computational-thinking content ages well, but treat modern-Python idiom (type hints, f-strings, match, tooling) as coming from CS50P + uv + the production standard, not from here. Secondary option — IBM Applied Software Engineering Fundamentals (beginner, ~2 months @ 10 hrs/wk, Coursera Plus): Git/GitHub, Linux/Bash, Python, SDLC + design/architecture/deployment foundations, code review; capstone deploys an AI app with IBM Watson + Flask. Recognized brand and "build toward a degree" credit-eligible, but beginner-level and Java/Flask/Watson-flavored — kept as a fallback, not the primary pick. | ☐ |
| 1️⃣5️⃣ | uv — Python Packaging (Astral official docs) + Al Sweigart's uv Quickstart PRODUCTION TOOLING | Astral (docs) · Invent with Python (tutorial) | FREE | ❌ No (docs + tutorial, not a completion cert) | ~2 hours | THE 2026 PACKAGE/ENV MANAGER — NOW THE DEFAULT ACROSS EVERY REPO!📝 Full rationale — click to expanduv (from Astral, makers of Ruff) is a single Rust-based tool that replaces pip + virtualenv + pip-tools + pyenv:uv init → uv add → uv run, with a committed uv.lock for byte-reproducible builds. Astral's own docs are the source-of-truth (matches the vendor-official pattern of Confluent/dbt/HashiCorp); Al Sweigart's quickstart (author of Automate the Boring Stuff, updated 2026) is the terse command reference. Not a framework — this is a docs + one-tutorial afternoon, then use it daily. Underwrites the whole production standard; the pip → uv migration of the live 1099 pipeline doubles as build-in-public content. | 🚧 |
| 1️⃣6️⃣ | Conda Basics (Anaconda Learning) + official conda intro tutorial ⏸️ CONDITIONAL | Anaconda (vendor-official) | FREE (course) · cert paid-gated | ❌ No🎓 Certificate detail — click to expand— course free; the Conda Fundamentals cert is paid-subscription-gated (learning evidence, not a recruiter credential — don't buy the badge) | ~1-2 hours | ⏸️ CONDITIONAL — TAKE ONLY IF CRUCIBLE NEEDS IT.📝 Full rationale — click to expanduv is the default everywhere; Conda earns a place in one project only — Crucible — and only if it grows heavy numerical / CUDA / C++ (BLAS/compiled) backends where Conda's binary channels resolve compiled scientific stacks more cleanly than wheels. Anaconda's own free "Conda Basics" (environments, channels, packages) is the vendor-official source; skip it entirely unless the trigger fires. PolicyPulse + DataVault stay uv-only. Same "take ONE, never stack" discipline as the platform-cert menu. | ☐ |
| 1️⃣7️⃣ | Architecture Documentation: C4 + ADR — source-of-truth pack PRODUCTION STANDARD📚 Resources & notes — click to expand📐 C4: c4model.com (official site, Simon Brown) — read Abstractions → Diagrams → Notation → Review checklist → Interactive example; plus the free "Visualising software architecture with the C4 model" talk.📝 ADR: AWS Prescriptive Guidance — Using ADRs (process · example ADR · FAQ) + adr.github.io (template comparison, MADR, Nygard's original) + Fowler's bliki entry. | c4model.com (CC BY 4.0) · AWS (vendor-official) · ADR GitHub org | FREE | ❌ No🎓 Certificate detail — click to expand— no proctored credential exists for C4 or ADR; the artifact in the repo is the signal (same rule as the Udemy / NVIDIA-DLI completion-cert note) | ~4-5 hours total | THE MISSING LEARNING LINE UNDER THE PRODUCTION STANDARD.📝 Full rationale — click to expandCorrection 8 made ADRs + C4 non-negotiable in every repo and Correction 13 addeduv.lock — but C4/ADR were the only standard items with no corresponding learning row, and the Stage 2 Distribution block already assumes DataVault ships "with its C4 diagram + ADRs." Placed in Stage 1 because the standard applies from S1 and DataVault's S2 ship is the first artifact a hiring manager actually opens. Market weight: ThoughtWorks rates Lightweight ADRs ADOPT (store in source control, not a wiki — exactly the docs/adr/ pattern); AWS and Azure both publish first-party ADR guidance, so the AWS guide doubles as AWS-idiom fluency ahead of DEA-C01. Source-of-truth pattern — matches Confluent / HashiCorp / Astral / dbt Labs. Not a course: docs + one talk, then use it daily. Canonical text if you want depth: Simon Brown's The C4 Model: Visualizing Software Architecture (O'Reilly, published 21 Jul 2026) — see the conditional O'Reilly note in the Stage 3 Loop Reality block. | 🚧 |
| 1️⃣8️⃣ | Pre-Commit Hooks: the Stefanie Molin four-article series addendum — PRODUCTION STANDARD📚 Resources & notes — click to expand🪝 Read in order: Setup Guide → Behind the Scenes → Hook Creation Guide → Troubleshooting Guide.📖 Reference: pre-commit.com (official docs · hook index · stages) + Astral ruff integration. 🎧 Optional companion: Talk Python #482 (~1 hr, passive). ⚠️ Staleness caveat: her examples still show rev: v0.1.5 and the retired bare ruff hook id — read for the reasoning, take the config from CORRECTION 21. | stefaniemolin.com (author-published) · pre-commit.com (official) | FREE | ❌ No🎓 Certificate detail — click to expand— no certification for pre-commit exists anywhere, and no substantive course exists either (searched: Coursera returns nothing despite Coursera Plus being zero marginal cost). The shipped.pre-commit-config.yaml + the two ADRs are the evidence — same rule as the C4/ADR row above. Nothing enters Certifications; the Surviving Nine is untouched | ~2 hours (+1 hr optional podcast) | THE LEARNING LINE UNDER CORRECTION 21.📝 Full rationale — click to expandCorrection 21 made a pinned.pre-commit-config.yaml non-negotiable in all 14 repos — this is its matching learning row, exactly as row 1️⃣7️⃣ is for C4/ADR. Selected on provenance, not popularity: Molin is a Bloomberg engineer who authored hooks that ship in the ecosystem (numpydoc docstring validation; EXIF stripping) and speaks at PyCon/EuroPython — she teaches the tool from the inside. Her setup guide was featured in PyCoder's Weekly #624, Python Bytes #379, Real Python Podcast #220 and Talk Python #482 — four independent editorial endorsements, the nearest thing to peer review this subject has. What each article buys you: Setup Guide — the args:-vs-pyproject.toml decision (config must live in a config file to stay consistent across CI, hooks and editor; this is your version-drift ADR from the other direction). Behind the Scenes — why a repo has exactly one .git/hooks/pre-commit and what pre-commit install actually does; this is the interview answer, not trivia. Hook Creation Guide — writing a custom local hook, needed because an ERISA/PII-specific check has no upstream equivalent. Troubleshooting — the cache/environment errors that otherwise cost hours. ⚠️ Sequencing: read this before writing the first config, not after — otherwise the version-drift ADR becomes a note you wrote once instead of a real mitigation across eleven repos. Rejected alternatives (logged): MLOps Coding Course §5.2 (migrated to lefthook+mise; principles worth reading, config no longer matches the standard) · Hypermodern Python Tooling (Poetry-centric; predates uv-as-default, the ruff-check rename and the uv-lock hook) · Udemy/DataCamp (barred, CORRECTIONS 4 and 7). Distribution hook: "why mypy is not in my pre-commit hooks" is a strong LinkedIn technical-tips post — a real, non-obvious finding with a citable primary source. | 🚧 |
| 1️⃣9️⃣ | Machine Learning Specialization (Andrew Ng) 🆕 CORRECTION 48 · AFC-SCOPED | Coursera (DeepLearning.AI · Stanford Online) | Included (Coursera Plus) | ✅ Yes (shareable — Tier 4, never a Certifications line) | ~3 months @ 5–10 h/wk for all 3 courses (~100 h); Courses 1–2 ≈ two-thirds | THE ML FOUNDATION BEHIND AFC'S AI PREDICTIVE LAYER (CORRECTION 47).📝 Full rationale — click to expandStill the reference ML course in 2026 (5M+ enrollments; revised 2022). Courses 1–2 are required before AFC Stage-1 Phase 2 reaches its ML weeks (build sheet week 13) — supervised learning, logistic regression, decision trees, tree ensembles and XGBoost, and the "advice for applying ML" week (precision/recall on imbalanced data, which is exactly AFC's rare-hit label). Start Course 1 during the backtest weeks (7–12). Course 3 (unsupervised learning, recommenders, reinforcement learning) is optional — taken only if time allows, for a full view of ML. Course 2's TensorFlow neural-network weeks can be skimmed for AFC. Gaps it does not cover, filled at $0: probability calibration → scikit-learn's calibration user guide; purged / embargoed time-series CV → Machine Learning for Algorithmic Trading ch. 6 (owned, see Reading List). Optional free bridge: Kaggle Learn Intermediate Machine Learning (pipelines, XGBoost, leakage). Does not reinstate the retired 14-month ML stage; the Stage 3 ML-literacy module and OMSCS CS 7646 are unchanged. | ☐ |
| ⭐ Elective | Statistics with Python Specialization (U. Michigan) | Coursera | Included (Coursera Plus) | ✅ Yes | 8-10 weeks (module-priority) | ELECTIVE (downgraded from core): prioritize the Inferential Analysis module — hypothesis testing and confidence intervals feed eval statistics. Full completion also supports the OMSCS application's quantitative evidence. | ☐ |
📜 Stage 1 certification exams: Stage 1's course table contains completion certificates only — no proctored exams. The Stage 1 proctored credentials (AI-901 → AB-620, both self-funded) are tracked in the Employer Track section and the master Certifications table.
Archived from Stage 1 (preserved in the Archive): Google Data Analytics Professional Certificate and IBM Data Analyst Professional Certificate (DA-role credentials for a role no longer targeted), Vanderbilt GenAI Data Analyst Specialization (v9.2 itself marked it optional vs. IBM GenAI Engineering), and the 2023-era prompt/OpenAI-SDK courses (already archived in v9.2). Rationale: credential density without evidence is a negative screening signal in 2026.
pip → uv migration) — becomes the seed of the DE flagshipWhy this layer exists. The Thesis already names referrals as a dominant 2026 hiring channel and the Stage 2 apply gate calls cold-applying "a losing channel." That makes distribution the fourth roadmap layer alongside evidence (flagships), credentials (the Surviving Nine), and loop-performance (the practice blocks). Stage 1's job is the lowest-barrier, highest-trust version — local in-person presence + a public build cadence. Both are available today (no gate, no cost), both fit the existing Sunday community/content block, and the public content produced here becomes the application portfolio for AWS Community Builders in Stage 2. All links verified against live July 2026 sources; figures that could not be independently confirmed are flagged, not stated.
① HackGreenville — the Upstate SC tech hub (Slack + in-person). Community run under RefactorGVL, a local 501(c)(3); the Slack is a daily hub and the site aggregates every Upstate tech event.
#introductions / #general, then browse and join the data / AI / jobs channels.② Two local meetups that match your stack — the Python / data / AI rooms, a better fit than a generic dev group:
③ Build-in-public cadence (LinkedIn). One short post per week from the Sunday block, on the three pillars already chosen (frontline building patterns · finance→tech bridge · AI-news commentary). Rule: post artifacts and lessons (a PolicyPulse eval-gate result, a "what I learned" from the 1099 pipeline), never "I'm looking for a job." It compounds a searchable track record and satisfies the 2+ public-content prerequisite for the AWS Community Builders application in Stage 2.
Stage 1 target: in the HackGreenville Slack · 1 local meetup attended/month · one weekly public post. Small, sustainable, and it seeds every later stage.
Goal: first external move at ~M18–20 into a Data Engineer or Analytics Engineer role. Dual-target strategy: one skill investment covers both posting types; many DE roles at smaller companies are functionally AE jobs. DE is the documented FDE feeder background and the deeper moat; AE is the more remote-accessible door and often the faster first offer. Whichever door opens first at good comp is taken — the production-ops layer keeps building either way so the FDE narrative survives.
Why DE remains the stage title: data engineering is the most undersupplied role in enterprise hiring, demand is shifting toward AI-ready infrastructure and governance, and "data engineer with strong production deployment chops" is an explicitly documented FDE background. The AE title is real and well-paid but contested (the role is blurring back into DE/analyst work) and sits closer to the AI-compressed BI layer — it is a door, not the identity.
| Layer | Skills & Tools | DE posting signal | AE posting signal |
|---|---|---|---|
| SQL at scale | Window functions, optimization, warehouse cost awareness (clustering, pruning) | ✅ Core | ✅ Core (the non-negotiable) |
| Transformation | dbt — tested project at real scale (target: 200+ models, sources, tests, docs, CI that actually gates merges) | ✅ Standard tooling | ✅ The core craft |
| Warehouse | Snowflake (the "one deep" — AE-primary, canonical dbt pairing, cloud-agnostic) + BigQuery awareness (retained; dbt adapters port cleanly) + Microsoft Fabric awareness (DP-700 / employer stack) | ✅ | ✅ (dbt + named warehouse = the highest-signal AE line) |
| Semantic / metrics layer | Metric definitions, dbt semantic layer, self-serve enablement, dashboard handoff (Power BI given Microsoft stack) | Useful | ✅ Differentiator |
| Orchestration | Airflow (or Dagster) — DAGs with retries, alerting, monitoring | ✅ Core | Useful |
| Quality & governance | Data contracts, dbt tests / Great Expectations, lineage, access-control awareness (the regulated-finance edge) | ✅ Fast-growing requirement | ✅ "Trusted data" is the job |
| Streaming basics | Kafka fundamentals; batch-vs-streaming judgment | ✅ | Awareness |
| Deployment & ops | Docker → ECS/Fargate (confirmed pattern), Terraform basics, monitoring, incident writeups on own pipelines | ✅ The FDE-feeder layer | Differentiator |
| AI-adjacent data | Embedding pipelines, vector stores, unstructured-data ETL feeding RAG — the "AI-ready infrastructure" demand shift | ✅ Premium signal | ✅ Emerging in postings |
| Order | Course | Platform | Cost | Certificate? | Duration | Why This Course | ✅ Done |
|---|---|---|---|---|---|---|---|
| 1️⃣ | Data Engineering Foundations Specialization (IBM) 🔺 UPGRADED📚 Resources & notes — click to expand(was single-course "Introduction to Data Engineering"; URL previously carried a label/slug mismatch — now corrected) | Coursera (IBM) | Included (Coursera Plus) | ✅ Yes (Specialization cert) | 6-8 weeks (5 courses, compressed; budget updated from 4 weeks) | START HERE — NOW THE FULL FOUNDATION!📝 Full rationale — click to expandUpgraded by approval from the single intro course to IBM's 5-course Specialization: data engineering ecosystem & lifecycle, Python for DE, SQL, and Relational Databases, with hands-on labs on MySQL, PostgreSQL and Db2. The intro course (course 1 of this Specialization, itself recently refreshed with RDBMS/NoSQL/Hadoop-HDFS/Spark coverage) is still the first thing taken — the upgrade adds the Python/SQL/RDBMS reps under the same credential at $0 marginal cost. Move fast through overlap with Stage 1 Python; the marginal value is the DE-framed SQL + relational modeling layer before dbt.🗒️ Parent-programme note (CORRECTION 43): this 5-course Specialization is courses 1–5 of the IBM Data Engineering Professional Certificate (13 courses per the IBM Credly badge; a 2026 practitioner review counts 16 subjects — verify the current course count at enrolment). The Foundations Specialization is the committed scope; the full PC is deliberately not taken. Its remaining tail is Db2 / Hadoop / MongoDB / Cassandra / Cognos-weighted, and that ground is already covered at higher signal by the DeepLearning.AI DE PC (Joe Reis, row 4️⃣), dbt (rows 5️⃣–6️⃣), Snowflake (row 1️⃣6️⃣.5), Astronomer/Airflow (row 7️⃣) and Databricks Academy (row 8️⃣). ⚠️ Cost flag: two independent 2026 reviews state the full IBM DE PC is not bundled into Coursera Plus and is billed separately (~$49/mo) — the Foundations Specialization is Plus-included, so do not assume the family shares one price. Falsifier: revisit the full PC only if a Q1 2027 target employer names Db2, Hadoop or Cognos in a posted JD. | ☐ |
| 2️⃣ | SQL for Data Science (UC Davis) | Coursera | Included (Coursera Plus) | ✅ Yes | 4 weeks | Refresh & deepen SQL — advanced SQL appears in ~95% of DE postings and is THE non-negotiable AE skill. | ☐ |
| 3️⃣ | PostgreSQL for Everybody Specialization + use-the-index-luke.com (internals) 🔁 SWAPPED v10.0 (was PostgreSQL Bootcamp / Udemy — archived) — ⭐ HIGHLY RECOMMENDED | Coursera (U. Michigan) + free web | Included (Coursera Plus) | ✅ Yes (Specialization) | 4-6 weeks | RAW RELATIONAL DEPTH + RECOGNITION! Dr. Chuck's PostgreSQL sequel to your Stage 1 Python for Everybody — rated 4.8 and named a top DE SQL course for 2026, Coursera-Plus-included.📝 Full rationale — click to expandCovers SQL, data modeling, indexing, JSON, and Python integration. Pair it with the free use-the-index-luke.com (Markus Winand) for the query-plan / EXPLAIN / indexing / partitioning internals DE interviews probe — the layer beneath the warehouse. Replaces the Udemy PostgreSQL Bootcamp (preserved in the Archive) with a university-branded credential and $0 marginal cost. | ☐ |
| 4️⃣ | DeepLearning.AI Data Engineering Professional Certificate (with AWS) 🔁 DISAMBIGUATED📚 Resources & notes — click to expand(formerly listed as "AWS Data Engineering Professional Certificate" with theaws-data-engineering slug — two distinct programs exist on Coursera; this row now names the intended one, confirmed by approval) | Coursera (DeepLearning.AI + AWS) | Included (Coursera Plus) | ✅ Yes (Professional Cert) | 3-4 months | THE DE SPINE!📝 Full rationale — click to expandTaught by Joe Reis (co-author, Fundamentals of Data Engineering); 4 courses covering the full DE lifecycle — ingestion, transformation, storage, serving — with hands-on labs built in partnership with AWS and Factored.AI on the AWS Cloud (S3, Glue, Kinesis, Lambda, Redshift; Kimball vs Inmon, star schema, data vault). 2026 reviewer verdict: best fit for "a career changer with some Python and SQL who wants a cloud-native, AWS-backed path into a data engineering role." Learned thoroughly BEFORE the DEA-C01 exam (see exam table below). 🌎 Free Spanish-language onramp available via AWS Entrena (Skill Builder Cloud/AI fundamentals) — useful pre-work given the Azure-native starting stack. | ☐ |
| 5️⃣ | dbt Fundamentals | dbt Labs | FREE | ✅ Yes | 5 hours · 🆕 C56: taken in Stage 1 (plan Weeks 5–6) | MOST IMPORTANT 2026 SKILL! Software engineering applied to data transformation. The core AE craft and standard DE tooling — feeds the tested-project flagship directly. | 🚧 |
| 6️⃣ | dbt Advanced Learning Paths (Analytics Engineering) 🆕 NEW v10.0 — AE FOCUS (link: learn.getdbt.com) | dbt Labs | FREE | ✅ Yes (course badges) | 2-3 weeks cumulative · 🆕 C56: starts in Stage 1 (plan Week 11) | THE AE DIFFERENTIATOR! Advanced materializations, refactoring SQL for modularity, dbt tests at scale, semantic layer & metrics definitions.📝 Full rationale — click to expandPowers the "tested dbt project at real scale" flagship evidence (200+ models, CI-gated) — the profile recruiters call scarce. | ☐ |
| 6️⃣.5 | Dataframe Engine Boundary — Polars-first pipelines · 🥇 Polars User Guide (FREE) · 📖 conditional book 🆕 NEW — CORRECTION 35📚 Sources, the no-certification finding & four declines — click to expand🚨 There is no Polars certification. Verified against the vendor: the Polars Academy is in-company B2B training only (Foundations ½ day · Essentials 1 day · Plugins 1 day, booked by contacting the Academy team), plus a curated list of third-party self-paced courses. No exam, no proctored credential, no badge — so the canon stays at 9 committed + 1 conditional and this row adds no exam.🥇 Primary — the free Polars User Guide + migration pages + API reference. This is the whole committed spend. Work the ingestion layer against the docs first. 📖 Conditional — Python Polars: The Definitive Guide (Janssens & Nieuwdorp, O'Reilly 2025) in the books layer, Tier 5. Bought only if the rewrite stalls on lazy plans, streaming or the expression model. ⚠️ Re-verify the edition — the 1st ed. predates the 1.24 streaming-engine GA. ❌ Four vendor-endorsed self-paced routes, all declined against this file's own rulings: DataCamp ×3 (Polars' named learning partner — the strongest case of the four) declined under CORRECTION 4; Udemy Data Analysis with Polars (Liam Brannigan, Polars contributor, endorsed by Ritchie Vink, current to 1.30.0 — best-provenanced of the four) declined under CORRECTION 7, provenance logged so the falsifier has something to bite on; Coursera Polars from Zero (Pragmatic AI Labs) — Coursera-Plus-included at $0 marginal, and declined anyway because it is a Rust course shipping three Rust CLI binaries, colliding directly with the CORRECTION 22 Rust decline ($0 is not a reason to take the wrong language); Xebia Polars Essentials (€750, in person, Netherlands) declined on cost and geography. ⚠️ Harness friction is the real cost, not the reading. LLM assistants emit pandas signatures against Polars objects — mitigated by the idiom block added to python-core.mdc, not by hoping. | Polars (free docs) | FREE | ❌ No — no certification exists | ~6–8 hrs against the ingestion layer | THE BOUNDARY, NOT THE BENCHMARK.📝 Full rationale — click to expandPolars becomes the default for ingestion, schema enforcement and bulk transforms; pandas is retained deliberately at the openpyxl template-write and plotting/scikit-learn hand-off boundaries; business logic goes to dbt, not to either engine. The reviewable artifact is the ADR recording which engine owns which layer plus a.explain() query plan — not a speed number on a small dataset. ⚠️ Never claimed as a credential: Polars sits near 0.009% of UK postings against pandas at 0.62%, and US postings phrase it as "Pandas, PySpark, or Polars" — an alternative, not a requirement. Learning both is the point; the keyword is worth nothing. | ☐ |
| 7️⃣ | Astronomer Academy — Airflow 101 + DAG Authoring (→ optional Airflow Fundamentals cert) 🔁 SWAPPED v10.0 (was Airflow: The Hands-On Guide / Udemy — archived) | Astronomer | FREE (courses) · certification exam $150 list — free vouchers offered through Astronomer certification workshops and webinars · 🆕 C49 | ✅ Yes (verifiable Astronomer Certification) | 2-3 weeks | ORCHESTRATION — VENDOR-OFFICIAL! Free courses taught by the Astronomer experts behind Apache Airflow — including Marc Lamberti, author of the archived Udemy course.📝 Full rationale — click to expandAirflow 101 (DAGs, scheduling, retries, alerting) → DAG Authoring → advanced (KubernetesPodOperator, deferrable operators, dynamic task mapping, TaskFlow, CI/CD; even a RAG-with-Airflow module that maps to PolicyPulse). Current to Airflow 3 and ends in a recognized, one-click-verifiable Astronomer Certification — unlike a Udemy completion PDF. Orchestration is required in ~75% of DE postings. | ☐ |
| 8️⃣ | Databricks Academy — Data Engineering with Apache Spark (free self-paced) 🔁 SWAPPED v10.0 (was PySpark for Big Data / Udemy — archived) | Databricks Academy | FREE (customer/self-paced) | ✅ Yes (completion; preps DP-750 — Microsoft Certified: Azure Databricks Data Engineer Associate, $165, beta since Mar 2026 — and the Databricks DE certs) · 🆕 C49: exam code verified | 4-6 weeks | BIG DATA ON THE DOMINANT PLATFORM! Production Spark in 2026 runs on Databricks (Azure/AWS/GCP).📝 Full rationale — click to expandFree official self-paced path — Spark DataFrame API (PySpark), Spark SQL, Delta Lake, medallion architecture — that doubles as prep for your preferred DP-750 (Azure Databricks) / Databricks DE Associate conditional cert, collapsing two line-items into one vendor-official track on your Azure stack. PySpark appears in ~70% of DE postings; also the engine behind DP-700's Fabric workloads. | ☐ |
| 9️⃣ | Docker & Kubernetes Masterclass (Packt) | Coursera | Included (Coursera Plus) | ✅ Yes | 4-6 weeks | PRODUCTION DEPLOYMENT! Containerize pipelines, orchestration, scaling, security. Builds on the Stage 1 Docker intro; Docker+K8s appear in 70%+ of DE/ML postings. | ☐ |
| 🔟 | Apache Kafka 101 (Confluent Developer) 🆕 NEW v10.0 — DE FOCUS | Confluent | FREE | ❌ No (badge available) | 1-2 weeks | STREAMING FUNDAMENTALS! Kafka was absent from v9.2 but is now standard in DE postings as demand shifts to real-time, AI-ready data movement.📝 Full rationale — click to expandTopics, partitions, producers/consumers, and the batch-vs-streaming judgment call interviewers probe. Taught by Confluent (Kafka's creators). | ☐ |
| 1️⃣1️⃣ | Terraform Fundamentals (HashiCorp Developer) 🆕 NEW v10.0 — DE FOCUS | HashiCorp | FREE | ❌ No | 1-2 weeks | INFRASTRUCTURE AS CODE! IaC now appears in roughly 1 in 6 DE postings as platform engineering absorbs data engineering.📝 Full rationale — click to expandProvision the flagship's AWS resources (S3, ECS) in Terraform instead of the console — turns "deployed" into "reproducibly deployed." | ☐ |
| 1️⃣2️⃣ | Vector Databases: from Embeddings to Applications | DeepLearning.AI | FREE (videos) | ⚠️ Pro only | 1-2 hours | THE MISSING LINK FOR AI DATA ENGINEERING! Semantic search engines in code, taught by Pinecone & Weaviate engineers — embedding pipelines as data infrastructure. | ☐ |
| 1️⃣3️⃣ | Pre-processing Unstructured Data for LLM Applications | DeepLearning.AI | FREE (videos) | ⚠️ Pro only | 1 hour | 80% OF THE FINANCE-AI JOB! Extracting clean text from messy PDFs, slides, and financial reports — the core skill behind FormSense and PolicyPulse ingestion. | ☐ |
| 1️⃣4️⃣ | Retrieval Augmented Generation (RAG) — Production Ready | DeepLearning.AI | FREE (videos) | ⚠️ Pro only | 1-2 hours | Beyond basic RAG — architecture, deployment, and evaluation for production systems. | ☐ |
| 1️⃣5️⃣ | Retrieval Augmented Generation (RAG) — Full Course | Coursera (DL.AI) | Included (Coursera Plus) | ✅ Yes | ~20 hours | COMPREHENSIVE RAG + EVALUATION! Full lifecycle: retrieval, vector DBs, evaluation with Phoenix/Arize, deployment, observability. | ☐ |
| 1️⃣5️⃣.5 | 🆕 IBM AI-Native Data Engineering Professional Certificate 🆕 NEW — CORRECTION 43📚 All 7 courses, the gap analysis & the scope decision — click to expandProgramme facts (verified Aug 2026): 7 courses · 155 hours · Intermediate level (not beginner — unusual for an IBM PC) · 4 months at 10 hrs/week · Included with Coursera Plus ($0 marginal) · page marked Recently updated — July 2026 · instructors Ruslan Podgaets + Antonio Cangiano (IBM). Stated prerequisites: SQL, basic Python, data pipelines, Git and core software-engineering practice — all already held. ⚠️ Recognition caveat, stated honestly: the programme is new and low-enrolment (the lead instructor's profile showed <500 learners at the time of review). There is no recruiter recognition and no user-experience base yet. Under the credential ladder this is a Tier 4 Professional Certificate — the capstone is the deliverable, not the PDF. Enrol for the skills, not the badge.📋 The full 7-course programme — take all, or take the three flagged 🟢: ① Foundations of AI Native Data Engineering (19 h) — how AI-native differs from traditional pipeline design; LLMs, embeddings, vector DBs and RAG from a data-engineering perspective; a small semantic-search/RAG workflow. ⚪ Overlap: largely covered by rows 1️⃣2️⃣–1️⃣5️⃣ and PolicyPulse S1. Skim. ② AI Systems, Automation, CI/CD and Data Engineering Workflows (19 h) — infrastructure components, Git + CI/CD for AI data projects, using AI tools to generate and validate SQL/code/tests/docs, policy and validation gates. ⚪ Overlap: the production standard (pinned pre-commit, CI-authoritative hook subset, uv sync --frozen, no-vibe-coding diff review) already exceeds this. Skim. 🟢 ③ Vector Databases and Retrieval Data Engineering (22 h) — metadata-rich vector schemas, embedding pipelines, retrieval evaluated on recall, latency and drift, and security + governance controls on vector retrieval. GAP-FILLING. Current coverage is the 1–2 hr DeepLearning.AI short at row 1️⃣2️⃣. The governance/access-control layer is exactly PolicyPulse's S3 access-control-aware retrieval, which has had no course behind it. ④ Lakehouse Architecture for AI-Native Data Platforms (24 h) — open table formats, replay patterns, schema evolution, governed ingestion, data contracts, lineage, access control, CI gates. ⚪ Overlap: the lakehouse slot is already owned by Databricks Academy (row 8️⃣) + DP-750; contracts/tests by dbt. Optional. 🟢 ⑤ Unstructured Data Engineering for AI (24 h) — document/multimodal ingestion, OCR-aware processing, normalization, PII-safe corpus preparation, chunking + metadata enrichment for retrieval/training/citation, and safety/licensing/bias/source-quality gates. GAP-FILLING — the ERISA moat made teachable. Current coverage is the 1-hour short at row 1️⃣3️⃣. PII-safe corpus prep underwrites FormSense and PolicyPulse ingestion; citation-grade chunking underwrites the faithfulness gates. 🟢 ⑥ Reproducible Training Data and ML-Ready Data Pipelines (22 h) — dataset versioning, lineage and release controls; detecting leakage, contamination and point-in-time-correctness failures; feature/label workflows with drift monitoring; CI gates for schema, slice, distribution, bias and reproducibility. GAP-FILLING — the largest single gap found in the whole audit. Point-in-time correctness is precisely what signalcore exists to guarantee for Crucible and AFC (sealed out-of-sample vault + overfitting-budget ledger), and no learning row anywhere in v10.0 covered it.⑦ Capstone: Build and Operate an AI-Native Data Platform (25 h) — define the use case and success criteria, build end-to-end with governance and validation controls, monitoring + incident-response + CI/CD plans, then present a portfolio-ready architecture story with trade-offs and business value. ⚪ Required for the certificate. ⚠️ Two flags: (a) DataVault already is this capstone — the S2 hardening ships ingestion → dbt-tested models (CI-gated) → orchestration → contracts → deploy → monitoring, with ADRs, a C4 view and a written incident/postmortem; (b) the one-system-per-project, never-rebuilt principle breaks if the rubric forces a second architecture. If taken, submit the synthetic public DataVault build so one artifact serves both — and stop if the rubric pulls the design off-course. 🎯 Scope decision — Manuel's call, recorded: the full programme is listed here in its entirety by explicit instruction, so the choice can be made at enrolment with the syllabus in hand rather than from a summary. Two defensible routes: (A) targeted — courses ③⑤⑥ only, 68 hrs, no certificate (fills every identified gap, forfeits the Tier-4 line, consistent with evidence over keywords); (B) full programme — 155 hrs, certificate earned (adds ~87 hrs of mostly-redundant material for one Tier-4 credential with no recruiter recognition yet). ⚠️ Hard constraint either way: this row is subordinate to DataVault S2, which is the CORRECTION 22 evidence gate for the Q1 2027 apply window. It never competes with that ship. 📊 Market evidence on both sides (recorded so the falsifier has something to bite on). For: 2026 posting analyses put SQL and Python in over two-thirds of DE postings with LLM engineering named in ~12%, and describe DEs as increasingly tasked with managing vector databases and embedding pipelines; vector DBs, feature stores and ML-ready data layers appear more frequently in JDs as the role drifts toward infrastructure engineering for AI systems; separate analysis puts vector databases at ~4.5% of AI-engineer postings. Against: practitioners are blunt that employers are renaming existing DE roles, stapling on half an ML engineer's scope, and holding comp flat — treat "AI-focused DE" as a scope premium to negotiate, not a title to chase. Falsifier: drop to route (A), or drop the row entirely, if the Q1 2027 apply list names AI-native platform work in fewer than 3 postings as a requirement rather than a nice-to-have. | Coursera (IBM) | Included (Coursera Plus) | ✅ Yes (Professional Cert — Tier 4, never a Certifications line) | 68 hrs (targeted ③⑤⑥)⏱️ Timing detail — click to expand— or 155 hrs / ~4 months (full programme)⏱️ Subordinate to DataVault S2; scope chosen at enrolment | THE AI-NATIVE DE LAYER — THE STAGE 2 TITLE, MADE TEACHABLE.📝 Full rationale — click to expandStage 2 has been titled AI-Focused Data Engineer / Analytics Engineer since v10.0 and the skill plan already carries the "AI-adjacent data — embedding pipelines, vector stores, unstructured-data ETL feeding RAG" row — but that row's only courses were three shorts totalling ~4 hours. This is the depth behind the title. The three gap-filling courses map one-to-one onto live portfolio work: ③ → PolicyPulse access-control-aware retrieval · ⑤ → FormSense + PolicyPulse PII-safe ingestion · ⑥ →signalcore point-in-time correctness for Crucible/AFC. ⚠️ Never claimed as a credential above its tier — same rule as every Coursera PC in this file. The reviewable artifacts are the ADRs and the eval/drift numbers in the repos, not the certificate. | ☐ |
| 1️⃣6️⃣ | BigQuery for Data Analysts (Google Cloud) 🔁 SWAPPED📚 Resources & notes — click to expand(was "BigQuery Basics for Data Analysts" — verified DISCONTINUED on Coursera July 2026; superseded row preserved verbatim in the v9.2 Archive) | Coursera (Google Cloud) | Included (Coursera Plus) | ✅ Yes | 2 weeks (~12 hrs) | MULTI-CLOUD WAREHOUSE — CURRENT REPLACEMENT COURSE! Covers the "Snowflake OR BigQuery" requirement in many DE/AE postings alongside AWS Redshift skills.📝 Full rationale — click to expandThe retired Qwiklabs-era lab collection is replaced by Google Cloud's current 9-module course: SQL analysis, cleaning & transformation in BigQuery, ingestion, Connected Sheets + Looker Studio visualization, and Dataform for scalable transformation pipelines — Google's dbt-analog, which reinforces the AE frame rather than distracting from it. Snowflake remains the "one warehouse deep" (row 16.5); this stays multi-cloud awareness. | ☐ |
| 1️⃣6️⃣.5 | Snowflake Data Engineering Professional Certificate 🆕 NEW v10.0 — AE-PRIMARY WAREHOUSE | Coursera (Snowflake) | Included (Coursera Plus) | ✅ Yes (Professional Cert) | 4-6 weeks | THE CANONICAL AE STACK — built and delivered by Snowflake's own developer advocates, heavily hands-on with in-product labs: warehouses, databases, ingestion, SQL/Python transformations, Snowpark, pipelines.📝 Full rationale — click to expandPairs directly with dbt to produce the "dbt-on-Snowflake, tested project at real scale with CI" evidence recruiters treat as the highest-signal AE line. This is the "one warehouse deep"; BigQuery Basics (#16) is retained as multi-cloud awareness. Preps for SnowPro Core (see cert table). | ☐ |
| 1️⃣7️⃣ | Knowledge Graphs for RAG (intro to GraphRAG) | DeepLearning.AI (w/ Neo4j) | FREE (videos) | ⚠️ Pro only | 1-2 hours | GRAPHRAG ENTRY POINT — PERFECT DOMAIN FIT! Builds a knowledge graph from SEC filings and adds a vector index for hybrid retrieval; on-ramp to the Stage 3 Neo4j path. | ☐ |
| 1️⃣8️⃣ | TypeScript + MCP Server Sprint — 🥇 HF MCP Course (FREE, ✅ recognized cert) · Total TypeScript + Zod · MCP TS SDK📚 Resources, rulings & row-19 split note — click to expandTypeScript + MCP Server Sprint 🔧 RESOURCES RESTORED + COURSES ADDED🥇 Primary course: Hugging Face MCP Course (FREE, ✅ recognized cert — built in partnership with Anthropic; authors Ben Burtenshaw (HF) + Alex Notov (Anthropic); Python and TypeScript examples; Unit 2 builds an end-to-end MCP app with a HuggingFace.js TS client deployed to Spaces; Unit 3 builds Claude Code workflow servers; fundamentals cert for Unit 1, full cert for shipping a use-case project). 🥈 Secondary (vendor-official, employer's Microsoft stack): Microsoft MCP for Beginners (FREE, MIT; TypeScript track among 6 languages; 11 modules incl. security — OWASP MCP Top 10, Azure Content Safety; study guide updated 5 Feb 2026 to MCP spec 2025-11-25 with a 2 Jul 2026 addendum on the 2026-07-28 spec RC). 📘 Week-1 TS spine (restored from v9.2): Total TypeScript — Beginner's Tutorial (free, 18 exercise-driven lessons, Matt Pocock) + Zod Tutorial (free, 10 exercises — Zod is what the MCP TS SDK uses for tool input validation, so Week 1 feeds Week 2 directly); reference fallback TS Handbook ch. 1-4. 🔨 Week 2: official MCP TypeScript SDK quickstart → build ONE practical TS MCP server exposing a tool from a Python project; deploy locally for Cursor/Claude Desktop; add as a sibling mcp-server-ts/ package.➡️ SPLIT OUT: the Vercel AI SDK / AI-last-mile build target and its learning sources moved to row 19 — different purpose (AI application layer vs. MCP protocol tooling). No net time added: row 19 is carved from this row’s existing 2-week block. ⏸️ Optional overflow: Packt — Ultimate TypeScript Course (Coursera Plus, $0 marginal, ~7 hrs, shareable certificate = Tier 4/5, never a Certifications line). Take only if the free Total TypeScript tutorials leave a gap; Total TypeScript remains the primary Week-1 spine. Partial amendment to the v8.9 ruling (which declined Coursera TS specializations as frontend-heavy — this is a single course covering Node.js alongside browser targets); the v8.9 ruling otherwise stands. | Hugging Face (primary) · Microsoft (secondary) · Total TypeScript · MCP official docs | FREE | ✅ Yes (HF MCP Course cert — free, recognized; Unit-1 fundamentals or full completion) | 2 weeks (shared with row 19 — total unchanged)⏱️ Timing detail — click to expand2 weeks (shared with row 19 —; total unchanged) — 🔄 re-timed: immediately before the compressed Q1 2027 apply window (was ~M14, set against the pre-resignation calendar) so MCP/TS evidence is fresh at interview; subordinate to DataVault S2 — never competes with the evidence gate | Unlocks the MCP-server keyword in TypeScript without adopting TS as primary language.📝 Full rationale — click to expandUnlocks the MCP-server keyword in TypeScript without adopting TS as primary language — retained from v9.2, which carried this full resource set (dropped in the v10.0 restructure; regression fixed here, verified all links live July 2026). The v8.9 ruling stands: Coursera TS specializations evaluated and declined (frontend/framework-heavy, off-target for a backend MCP tool). HF MCP Course chosen as primary because it is the only option ending in a recognized free certificate (same tier as the HF Agents course already in Stage 3) and is Anthropic-partnered; Microsoft's curriculum is the vendor-official reference on the employer's stack with the strongest security module. | ☐ |
| 1️⃣9️⃣ | Vercel AI SDK — AI Last-Mile Build · 🥇 Vercel Academy (FREE, ✅ vendor cert) · 🥈 Scrimba · 📖 AI Hero📚 Build target, learning sources & amendments — click to expandVercel AI SDK — AI Last-Mile Build 🆕 NEW ROW — split out of row 18, which had grown to carry two different purposes: MCP protocol tooling (row 18) vs. the AI application layer (this row). Content below is moved, not new — introduced by CORRECTIONS 22 and 23.🚀 Build target (from v10.0 CORRECTION 22): Vercel AI SDK (FREE, open-source) — build a streaming Claude-powered UI over PolicyPulse’s existing retrieval. Not a course; a deliverable. Chosen on adoption evidence: 62% of TypeScript projects started in 2026 use it, it is the named industry standard for streaming AI UIs, and it is model-agnostic across 25+ providers — matching this file’s provider-agnostic architecture and Anthropic-primary routing. ⚠️ Guardrail: TypeScript is the last mile only — TS frameworks lack the depth for multi-agent collaboration and long-horizon planning, so PolicyPulse, AFC and Crucible stay Python-primary. 🎓 Learning source: Vercel Academy — Builders Guide to the AI SDK (FREE, ✅ vendor-issued certificate, ~12 hrs; starter repo vercel/ai-sdk-fundamentals-starter). PRIMARY on the same logic as the HF MCP Course: free, vendor-official, hands-on, credentialed, and v7-current (Output.object, instructions) where most AI SDK material online is v3-era. Zod carries over directly from Week 1 — no new prerequisite. ⚠️ Privacy-routing amendment: the starter repo ships Vercel AI Gateway; swap for the direct @ai-sdk/anthropic provider (one-line change, ADR-worthy) and hold synthetic data only. ⚠️ Narrow v8.9 exception: Next.js/React content is admitted here because the deliverable is a UI — the frontend layer is the target, not a detour; the v8.9 ruling otherwise stands.🎨 React / Next.js — named outcome, NOT a separate track. The Week-2(b) deliverable is a Next.js/React UI, so this row already produces React evidence; it is named here so it can be claimed on a résumé and in an FDE round rather than sitting unlabelled inside an AI SDK line. No new row, no new course, no net hours, $0. Scoped deliberately to table-stakes competence: components, hooks, state, streaming UI, and calling a typed API. Declined: React as its own learning block, and the wider ecosystem (Redux, React Native, testing libraries, SSR internals). 📦 Ships as a browser page at a URL — Electron/desktop packaging explicitly declined: a reviewer will click a link but will not download an unsigned executable, and code signing plus auto-update is packaging work with zero portfolio signal. ⚠️ Falsifier — two conditions, both required: promote React to a dedicated block only if (a) Stage-3 target JDs name a frontend framework as a requirement rather than a nice-to-have, and (b) the Week-2(b) artifact has actually proved insufficient in a real interview loop. Note the prevailing JD phrasing is "React (or equivalent)" — the requirement is a framework, which Next.js/React satisfies. 🎯 Model-call ownership — Pattern B for the turn, Pattern A for the loop. The single-turn chat runs through the Next.js route handler, which owns the model call and exposes PolicyPulse retrieval as a tool — the pattern Vercel Academy teaches, so the course applies directly. The S3 evaluator-optimizer loop, GraphRAG fusion, access-control retrieval and three-layer eval stay entirely in Python. No agent core crosses the language boundary. ⚠️ This is what makes the privacy amendment load-bearing rather than moot: under Pattern B the route handler sees the full prompt, which is exactly why the Gateway is declined for the direct provider and why the corpus stays synthetic. ⚠️ Falsifier: revisit if a single turn ever needs more than one model round-trip plus tool calls — at that point it has become a loop, and a loop belongs in Python, not in a route handler that has quietly grown one. 🥈 Secondary (optional): Scrimba — Build a Support Agent with Vercel AI SDK (Coursera; RAG + embeddings + tool calling ≈ PolicyPulse in TypeScript; shareable certificate = Tier 4/5, never a Certifications line). ⚠️ Verify Coursera Plus coverage at enrolment — the page shows Free Trial status; if not covered, skip rather than purchase. ⚠️ Evidence flag: the roundup ranking this #1 is published by Scrimba about its own course — syllabus verified independently, ranking claim discounted. 📖 Reference (free): AI Hero — Vercel AI SDK Tutorial (Matt Pocock — same author as the Total TypeScript Week-1 spine; instructor continuity at zero cost). | Vercel Academy (primary) · Coursera/Scrimba (secondary) · AI Hero (reference) · AI SDK official docs | FREE (secondary conditional — verify Coursera Plus) | ⚠️ Certificate not confirmed — the Vercel Academy course is free, but no completion certificate could be verified (Oct 2026 check); confirm at enrolment · 🆕 C49: was "✅ Yes (vendor-issued certificate)" | No net time added — carved from row 18’s 2-week block⏱️ Timing detail — click to expandNo net time added — carved from row 18’s existing 2-week block: Weeks 1–2 MCP/TS core → Week 2(b) onward this row. Same placement as row 18: immediately before the compressed Q1 2027 apply window, subordinate to DataVault S2. | Produces the AI last-mile artifact a Python-only portfolio cannot show.📝 Full rationale — click to expandProduces the AI last-mile artifact a Python-only portfolio cannot show: a streaming Claude-powered UI over PolicyPulse retrieval. Selected on adoption evidence (62% of TypeScript projects started in 2026 use the AI SDK; named industry standard for streaming AI UIs; model-agnostic across 25+ providers, matching this file’s provider-agnostic architecture). Direct FDE-round asset. ⚠️ Guardrail unchanged: TypeScript is the last mile only — PolicyPulse, AFC and Crucible stay Python-primary. | ☐ |
| 2️⃣0️⃣ | ⏸️ WATCHLIST — NOT ENROLLED · Rust for Data Engineering (Pragmatic AI Labs) 🆕 NEW — CORRECTION 36🔭 What it is, why it is parked, and the four triggers that would activate it — click to expandWhat it is: a 31-course series from Pragmatic AI Labs — build production data systems in Rust across ETL, SQL/NoSQL, serverless, GCP and CI/CD. It sits in a catalog that also ships Rust From Zero, Rust for DevOps, a Rust Fundamentals Bootcamp, MLOps, AWS and GenAI tracks. Recommended path: Rust From Zero → terminal/CLI → data stores (SQLite, MySQL, Postgres, DuckDB) → ETL and Polars → serverless/GCP/RAG → shipping and CI/CD. Coursera-Plus-included, so $0 marginal — but 0 hrs committed.🎯 Why this row exists, stated plainly: it is a deliberate forward-looking hedge, not a hot-skill chase. Rust is the language the modern Python data stack is written in — Polars, ruff, uv, pydantic-core, delta-rs — and CORRECTION 35 has just made Polars the default engine. If that substrate ever surfaces into DE posting bars, this is the pre-vetted on-ramp and no re-search is needed. Parking it is the decision; enrolling is not. 🚦 Four triggers — any ONE activates a re-evaluation, none activates enrolment automatically: (1) 🥇 Polars plugins. The strongest and most likely trigger, because it is internal to work already scoped: custom business logic that must run at native expression speed is written in Rust via pyo3-polars, and Polars' own Academy sells a dedicated Plugins course. If a DataVault or PostCheck rule genuinely cannot be expressed in native Polars, this stops being speculative. (2) Rust appears as a required line — not "Python, Go, or Rust" — in ≥3 postings on the actual Q1 2027 apply list. (3) A named target employer lists Rust or PyO3 in a posted JD. (4) Crucible's live-execution path presents a real latency or memory-safety requirement — the CORRECTION 22 falsifier, restated here so both live in one place.⚠️ If a trigger ever fires, this specialization is probably still the wrong entry point. The career-adjacent path for a Python data engineer is PyO3 + maturin — writing Python extensions in Rust — not a general Rust-for-DE curriculum that rebuilds ETL, SQL clients and serverless in a second language he already has. Recorded now so a future trigger does not auto-select the nearest course. ⚠️ Evidence-quality flag (CORRECTION 36 §1): a 31-course series is a fact about the author's production capacity, not the hiring market. This row is parked on substrate logic — Rust is under the Python tools — and explicitly not on catalog size. | Coursera (Pragmatic AI Labs) | Included (Coursera Plus) | ✅ Yes (Specialization cert — Tier 4/5, never a Certifications line) | 0 hrs committed | 🔭 THE FUTURE-PROOFING SLOT — PARKED ON PURPOSE.📝 Full rationale — click to expandRust does not appear in DE posting bars: CORRECTION 22 measured SQL 79.4% · Python 71–73.7% · Spark 41.1% · Java 22.6% · Scala 17.5% · JS 3.4%, and Rust did not clear the threshold to be counted. Where it does co-occur with Python the conjunction is "or", not "and" — the same alternative-in-a-list pattern as "Pandas, PySpark, or Polars". Real growth exists (postings +35% YoY, mid-level ~$130K, 45% of firms running some Rust) but concentrates in systems and infrastructure, and enterprise adopters have more Rust planned than deployed. Meanwhile this portfolio already consumes Rust daily at zero language-learning cost —ruff, uv, polars, pydantic-core. The bet is logged, dated and falsifiable; the hours stay on DataVault S2. | ☐ |
| Credential | Code | Cost | Format | Why It Belongs in Stage 2 | ✅ Passed |
|---|---|---|---|---|---|
| Microsoft Fabric Data Engineer Associate ✅ APPROVED | DP-700 | self-funded | Proctored · free annual online renewal · prep FREE via Microsoft Learn | EMPLOYER-STACK DE CREDENTIAL! SQL/PySpark/KQL on Microsoft Fabric — internal-elevation evidence and the Azure-native counterpart to the AWS cert. | ☐ |
| AWS Certified Data Engineer – Associate ✅ APPROVED | DEA-C01 | $150 personal | Proctored · 3-yr validity · taken AFTER the AWS Professional Cert coursework | PROVE IT! Covers the ~40% AWS posting share for the external DE search — the second half of the dual-cloud, dual-search strategy. | ☐ |
| dbt Analytics Engineering Certification | — | ~$200 | Online proctored · 2-yr validity | ⏸️ CONDITIONAL — the tested dbt project with CI (flagship) is the primary signal recruiters cite; the cert is the tiebreaker, not the unlock. 🆕 CORRECTION 37 — trigger tightened from reactive to observable. The former trigger ("only if AE applications stall") fires during the apply window, and prep runs 4–6 weeks — bad timing. New trigger, either condition: (a) the Q1 2027 apply list names dbt certification in ≥3 postings, or (b) DataVault S2 dbt models ship before the window opens with budget slack remaining. 💲 Price confirmed at ~$200 — 65 questions · 120 min · 65% pass · online proctored via Talview · blueprint targets dbt 1.7. It certifies the role, not the tool: SQL practice, git workflow and modeling patterns sit alongside the dbt-specific material, which is precisely the AE gap. ⚠️ Falsifier — Fivetran and dbt Labs have merged; verify the exam and any community-voucher route still exist at booking. That merger is the most likely explanation for the retired "commonly free" figure this correction removed. | ☐ |
| SnowPro Core Certification 🆕 NEW v10.0 | COF-C03 | $175 personal | Proctored · 100 Q · 110 min · 2-yr validity | ⏸️ CONDITIONAL — the most recruiter-recognized Snowflake credential and the prerequisite gate for all SnowPro Advanced exams. Take as the AE tiebreaker if the apply-list skews to Snowflake shops; the dbt-on-Snowflake flagship is the primary signal. NOT SnowPro Advanced: Data Engineer ($375) — that wants 2+ yrs hands-on Snowflake and is premature for Stage 2. | ☐ |
| Azure Databricks Data Engineer Associate LAKEHOUSE PATH (PREFERRED) | DP-750 | ~$165 · self-funded | Proctored · 120 min · pass 700/1000 · Pearson VUE (GA ~May 2026) | ⏸️ CONDITIONAL (preferred lakehouse option) — same lakehouse/Spark/Delta/Unity Catalog signal as the vendor-neutral Databricks DE, but it is a Microsoft cert on the Azure stack and ~$35 cheaper than the $200 vendor exam. Self-funded, like every credential in the canon. Covers SQL/Python ingestion, production pipelines, Unity Catalog governance, and Git-based SDLC. Take this instead of the vendor-neutral exam when the Months 12–14 apply-list skews Databricks/lakehouse AND the shop runs Azure Databricks. | ☐ |
| Databricks Certified Data Engineer – Associate 🔻NOW FALLBACK | — | $200 personal | Proctored · 45 Q · 90 min · 2-yr validity | ⏸️ CONDITIONAL (fallback only) — retained as the portable, cloud-agnostic lakehouse cert for non-Azure Databricks shops (Databricks on AWS/GCP). Prefer DP-750 above when the target runs Azure Databricks (cheaper of the two). Databricks is ~17% of DE postings (behind Spark and Snowflake); not a core add for the Azure-internal / AWS-external dual-search. The DE flagship pipeline is the primary signal. | ☐ |
⚠️ Platform-cert menu — take ONE, never stack. The conditional certs above (dbt AE, SnowPro Core, and the lakehouse slot — DP-750 preferred / vendor-neutral Databricks DE as the non-Azure fallback, one lakehouse cert max) plus the two approved ones (DP-700, AWS DEA-C01) are not a checklist. 2026 hiring data is consistent: match the cert to your target employer's primary stack; one relevant cert paired with a same-platform project beats a stack of badges (keyword density is a negative signal). DP-700 (employer/Azure) + AWS DEA-C01 (external/AWS) are the two committed certs. Add exactly one conditional platform cert only when a concrete apply-list demands it — the flagship project is what actually clears the interview.
🌎 AWS Entrena Honduras / Centroamérica — evaluated: free AWS onramp, NOT a credential. A legitimate, official AWS program — a partnership of AWS, the Government of Honduras, the Alcaldía Municipal del Distrito Central (AMDC), the U.S. Embassy in Honduras, and Grupo Financiero Atlántida — offering free, Spanish-language AI and cloud training to 15,000 people before 2028 (portal: honduras.awsentrena.com). What it actually delivers: self-paced AWS Skill Builder learning paths — including the "Fundamentos de la nube" plan that preps for, but does not grant, the AWS Certified Cloud Practitioner exam — ending in free completion certificates and Credly digital badges. Per AWS's own framing those badges are AWS-backed recognition but do not equal an official certification (the same credential-hierarchy rule the roadmap applies to Udemy/ZTM/NVIDIA-DLI completion certs). Note that AWS Skill Builder self-paced training is already free worldwide, so the program's real value-add is the Spanish localization, guided structure, and any scholarship perk (paid Skill Builder tier or exam voucher — to be confirmed).
✅ Verdict — enroll, and use it strictly as a free onramp. Because Daybright is an Azure/Microsoft shop, your hands-on cloud is Azure, not AWS — the one real gap before the committed AWS DEA-C01. Run the Cloud-Foundations and AI-fundamentals paths as cheap, structured, Spanish-language pre-work feeding the sequence already in the plan: AWS Data Engineering Professional Certificate (Stage 2 Core Course #4 above) → AWS Certified Data Engineer – Associate (DEA-C01) (cert table above). The completion badges are learning / portfolio evidence only — never list them under Certifications (evidence-over-keywords standard).
⏸️ Cloud Practitioner (CLF-C02) exam — conditional, take ONLY if the scholarship voucher makes it free. 2026 practitioner and hiring data are consistent: CP is a foundational cert whose practical value is "moderate" for a junior new to AWS and drops to "signaling, not learning" for anyone already prepping associate-level exams — the standing advice is to skip straight to the Associate cert. This roadmap already does exactly that (DEA-C01 is committed; CP was never in scope). So take the CP exam only if AWS Entrena bundles a no-cost proctored voucher, as a zero-dollar momentum step before DEA-C01; if it would cost ~$100 out of pocket, skip it and go straight to DEA-C01. ⚠️ Open item to confirm: whether the "Centroamérica / LATAM" banner points to the same Skill Builder catalog as the Honduras portal, and exactly what the scholarship covers beyond the already-free content (paid Skill Builder tier? proctored-exam voucher?) — the voucher answer is the only thing that shifts this verdict.
Why this exists (and why it is Stage 2 only). v10.0 carries an evidence layer (flagships) and a credential layer (the Surviving Nine) but had no loop-performance layer. The portfolio gets the interview; the loop converts it. Published analysis of data-engineering interview loops (Interview Query, 2024) puts SQL in ~85% of loops, Python coding ~70%, system design ~65%, data modeling ~55% — so the apply window at Months 12–14 is gated on live query/coding performance, not on the repo alone. This block is timeboxed to Months 10–14 and deliberately does not run across all stages: the v9.2 archive spread weekly grind targets across every stage, which competes directly with the 25 hrs/week owed to the DataVault flagship. Practice is a pre-apply sprint, not a permanent tax.
⚠️ Badges are not credentials. The same rule that governs Udemy completion PDFs governs practice-platform badges. HackerRank's own hiring research found that fewer than 16% of hiring managers and recruiters rank certifications in their top three resume signals. The v9.2 archive's instruction to "get the SQL certificate for LinkedIn" is superseded — it contradicts the evidence-over-keywords standard. Practice here for fluency; never list these under Certifications.
Take ONE, never stack — the same discipline as the platform-cert menu. Start free; escalate only on evidence that the free bank is exhausted.
| Platform | Cost | When / Target | Purpose & verdict |
|---|---|---|---|
| DataLemur ✅ DEFAULT — start here |
FREE tier | Months 10–13 4–6 problems/week |
FREE-FIRST SQL INTERVIEW BANK. Curated by Nick Singh (Ace the Data Science Interview) with verified company provenance — when a problem is labeled a Meta SQL interview question, there is high confidence it actually was. Substantial free tier; solution videos for video-first learners. Known weakness: no AI tutor or wrong-answer diagnostic — it is a question library, not a learning loop, so pair it with your own EXPLAIN-plan reading from use-the-index-luke.com (already in the Stage 2 course table). This is the default; do not buy anything until this bank is genuinely exhausted. |
| StrataScratch ⏸️ CONDITIONAL — paid upgrade only |
~$39/mo or ~$159/yr | Months 13–14 only (if triggered) |
THE DE-RELEVANT VOLUME PLAY. Largest raw bank reviewed (~500–700+ across SQL and Python combined, real-interview sourced) and the platform most consistently recommended for data-engineering-adjacent practice over general SWE sites. 🚨 ARCHIVE CORRECTION: the v9.2 archive lists this as FREE — that is no longer accurate. The 2026 free tier is roughly 50 questions (enough to evaluate, not to prep) behind an aggressive paywall. Trigger to buy: DataLemur's free bank exhausted AND a live apply-list in hand. Buy monthly, not yearly — the window is 2 months, not 12. |
| HackerRank SQL / Python ➖ OPTIONAL — practice only |
FREE | Months 10–12 warm-up reps only |
MUSCLE MEMORY, NOT SIGNAL. Fine as low-friction warm-up volume; many employers run their screens on the HackerRank platform, so environment familiarity has marginal value. Explicitly retained from the archive with its badge-chasing rationale removed (see the warning above). Skip entirely if DataLemur is holding your attention — this is redundant, not additive. |
| Practical-engineering reps ⭐ HIGHEST ROI — no platform |
FREE | Months 12–14 1 timed rep/week |
WHAT THE LOOP ACTUALLY TESTS. Set a 60-minute timer against your own repos: add a requirement to an existing signalcore or DataVault module and refactor cleanly under time pressure; parse a deliberately messy CSV/JSON with edge cases; build a small CLI with subcommands. This mirrors the real format far better than any question bank, and it doubles as flagship work rather than competing with it. Also rehearse the system-design (~65%) and data-modeling (~55%) rounds by narrating your own medallion layering and Box-7 rules engine out loud. |
❌ Declined for this block — logged as evaluated, not selected: LeetCode (wrong format for both targets — see the Stage 3 loop note; DS&A fundamentals are already covered by CS50 and, if active, OMSCS Computing Systems) · SQLZoo (beginner muscle memory, fully redundant with the Mode SQL Tutorial, PostgreSQL for Everybody, and daily dbt/1099 query work) · Kaggle and FreeCodeCamp (see the changelog rationale) · DataCamp (already declined in CORRECTION 4 — redundant paid subscription). Full rationale for each is in the CORRECTION 7 changelog entry.
🧰 Utility, not practice — logged CORRECTION 61: RunSQL (free, beta, by the dbdiagram / Holistics group) is an in-browser SQL sandbox — DBML schema, grid or CSV data, PostgreSQL / MySQL / SQL Server, shareable links. It has no problem bank and no graded or interview-sourced questions, so it does not replace DataLemur. Use it for shareable reproducible examples in GitHub issues and pull requests, quick dialect checks and schema sketches; real modeling work stays on the local DuckDB / Postgres stack.
Standing rule for this block: nothing here is a committed certification. The Surviving Nine (+1 conditional) is unchanged. These two items exist because the roadmap's regulated-finance background is a domain edge, and a small amount of externally verifiable domain evidence makes that edge legible to someone who has never heard of ERISA. They are optionality, not canon — and neither is required for any Stage 2 or Stage 3 target role.
The prior question, answered first: no finance certification is required for these roles. Practitioners who screen quant and trading-technology CVs are consistent that the CQF "doesn't move me one way or the other" and that a CFA is "close to useless" for quant work, advising programming and mathematics depth plus built projects instead. Live trading-systems postings gate on FIX protocol, KDB+ or another time-series database, low-latency messaging, event-driven architecture, Linux, C/C++, Python, Terraform — a finance credential does not appear as a requirement. The gate is the technical stack plus domain fluency, and the domain fluency is already in hand.
| Item | Cost | What it actually is | Why it earns optional status | ✅ Passed |
|---|---|---|---|---|
| SIE Securities Industry Essentials (FINRA) |
$100 (raised from $80 on 1 Jan 2026) |
A regulator-administered exam, not a completion certificate. Covers securities products, market structure, the regulators, and prohibited practices. 80 questions, 70% to pass, results valid 4 years. Under FINRA Rule 1210 it is the only FINRA qualification exam takeable without employer sponsorship — self-enrol via Form U10. | It travels. RPF is meaningful inside the retirement-plan world; SIE is recognised across brokerages, custodians, wealthtech and fintech generally. Paired with ERISA operations it produces a domain story with no realistic competitor in a DE/AE candidate pool. ⚠️ It does nothing for quant research or trading-systems engineering — its value is the fintech / regulated-engineering lane. | ☐ |
| BMC Bloomberg Market Concepts |
$0 on a Terminal $149 individually |
A certificate of completion — same evidentiary tier as the Udemy/NVIDIA-DLI rule, not a recruiter credential. Four required modules (Economic Indicators, Currencies, Fixed Income, Equities) covering 150+ terminal functions; one year from registration to finish. | Ranked third and honestly: the learning value exceeds the credential value. It is the fastest route to fixed-income/FX/rates vocabulary. Free on a Bloomberg Terminal; $149 through the Bloomberg for Education portal without institutional credentials. | ☐ |
⚠️ Open item — BMC access route unverified. Georgia Tech Library operates a Bloomberg Terminal on the Grove level of Price Gilbert, reservable by current GT faculty, students and staff, and GT's own database note directs students to complete BMC on it for the certificate. Whether OMSCS (online-only) students qualify for that reservation is not confirmed — check with the library before assuming the $149 is avoidable. Do not record this as a settled saving.
Sequencing if elected: Stage 2, after the DP-700 / AWS DEA-C01 committed pair, and never in competition with DataVault's S2 hardening — that ship is the evidence gate for the Months 12–14 apply window and outranks both items. The higher-value finance-lane investment is CS 7646, which costs $0 marginal and carries a graduate transcript line.
Why this layer exists. The Stage 2 Deliverables call for a "referral network activated" — this is the how. With the DE flagship shipping, you now hold a high-signal artifact, so distribution moves from local rooms to the largest online concentration of your exact target audience, plus the concrete referral-geography targets for the M12–14 apply window.
① dbt Community Slack — where analytics engineering lives (~100,000 community members). The densest single room of DE/AE practitioners and hiring managers. Timing matters: join once DataVault ships with its C4 diagram + ADRs, because the culture rewards genuine technical depth and (per a well-known community critique) is wary of the content-marketing spam that clogs #i-made-this. Your artifact is the opposite of spam — that's the edge.
#i-made-this, #advice-dbt-for-beginners, plus tool/warehouse channels (Snowflake, Airflow).#i-made-this — lead with the problem and the eval results, link the repo, ask for feedback. That is how the artifact travels into referral conversations.② AWS Community Builders — apply for the Jan 2027 cohort. ⚠️ Two corrections to the source review: the 2026 window closed 21 Jan 2026, so this is a Stage 2-boundary action, not immediate; and the "$500 credits / 50% re:Invent / free CloudAcademy" specifics are unconfirmed in any 2026 source — what is verified is a 100% certification-exam voucher, AWS promotional credits, and builder-only sessions (the program is free).
③ Referral geography for the apply window. Verified 2026 posting data shows Charlotte, NC (~2 hrs away; a banking hub, so the ERISA/finance background is an on-target edge) saturated with the exact modern stack you're building — dbt + Snowflake + Python + Databricks — including entry-friendly "Associate Data Engineer" roles and financial-data-pipeline roles; Atlanta is the larger secondary hub. Build the target-company list from Built In Charlotte, then work backward to warm intros (dbt Slack local channels, LinkedIn alumni and HackGreenville members at Charlotte shops). A warm referral into a Charlotte fintech beats a cold national application. 🆕 Domain-matched segment (CORRECTION 54): retirement-plan recordkeeping and wealth/retirement fintech is the first list for the soft-trigger search — the one segment where 1099-R, distribution and ERISA operations read as direct experience (e.g., a live 2026 Vestwell Data Engineer posting names dbt and Fivetran). Location-agnostic; remote roles count. 🆕 Bridge tier (CORRECTION 55): inside this first list, technical data roles at recordkeepers / TPAs whose titles may not say "engineer" — data conversion / migration, data operations, implementation data, operations automation / agentic operations — qualify when the posting requires SQL + a warehouse or automation platform + retirement domain (e.g., Vestwell's 2026 client-data-migration analyst role names advanced SQL reconciliations, recordkeeper feeds and Snowflake). Falsifier: dropped if it screens no better than AE / DE applications within the same 25-application window.
Goal: Applied AI Engineer role at ~M30, positioned for Forward Deployed Engineer moves after. This is Job #1 in the three-real-jobs taxonomy — building on top of foundation models — where domain depth + systems sense + shipped evidence wins, and where the finance moat is worth the most.
The 2027 positioning insight: a large share of agentic AI projects are expected to be cancelled by end-2027 for unclear value and weak controls. The engineers who survive are those who shipped something measurable. Eval frameworks as blocking gates — already this roadmap's discipline — are the survival trait, and the interview story: "I ship agents that are measured, not agents that are impressive."
🎯 THE FDE DIFFERENTIATOR — DISCOVERY & DECOMPOSITION (first-class Stage 3 skill)
Across 2026 FDE hiring, the single biggest filter is no longer coding — it is problem decomposition and customer-discovery conversation. Roughly 60% of candidates who clear the technical rounds are cut at the customer-conversation / client-simulation stage, and 73% of frontier-lab FDEs name running discovery conversations as the skill they were least prepared for coming from a traditional engineering background. This is the skill that decides the offer, so it is treated as a first-class Stage 3 deliverable — not an afterthought buried in a practice note.
Why this is your structural edge: your 2 years of ERISA-regulated, client-facing plan-operations work is direct discovery-and-stakeholder experience on exactly the round that eliminates most engineers. Frame it as an advantage, not a gap — and rehearse articulating your own contribution ("I did," not "we did," is the reported trap).
How it is trained & evidenced (cross-refs, no duplication): decomposition-interview reps + discovery / project-deep-dive rehearsal in the Stage 3 Loop Reality note; the ADR set + architecture-defense rehearsal that turns each flagship into an interrogatable "why I chose X over Y and what it cost" script; and the FDE-positioning items in the Focus Areas table below.
| Area | Content |
|---|---|
| Agentic systems (production) | Agentic workflows per the Building Effective Agents taxonomy (orchestrator-workers, sequential), tool use, MCP servers in anger, human-in-the-loop gates for irreversible actions (Crucible pattern), unattended-safe design for read-only/verifiable agents (AFC/FormSense pattern) |
| Evaluation as engineering | RAGAS/DeepEval/GEval as CI-blocking gates; hallucination evals (SelfCheckGPT/FActScore) for financial-grade rigor; eval dashboards as portfolio artifacts |
| ML-literacy module (2–3 months, embedded — replaces the v9.2 14-month stage) | Embeddings in depth, evaluation statistics, inference economics (latency/cost/routing), one small fine-tune done end-to-end as literacy — knowing when NOT to fine-tune (Prompt → RAG → Fine-tune → Distill) is the interview-defensible position. Substituted by OMSCS coursework if the degree track is active. |
| Regulated-AI edge | Privacy-routed architecture (PII local, proprietary via private-endpoint cloud, public scaffolding on free tiers) + per-document access clearance at retrieval time — the RAG-over-fine-tuning argument that is often decisive for ERISA/HIPAA/PCI-adjacent workloads, provable in an audit |
| Certifications | Anthropic CCA-F ($125) ⏸️ conditional on Claude Partner Network access — CCDV-F first if it arrives (C50), AI-103 (Azure AI Apps & Agents Developer — code-first, ~$165), Databricks Certified GenAI Engineer Associate ($200), Neo4j Certified Professional (free) |
| FDE positioning | Decomposition-interview practice (scope → MVP → iterate, thinking out loud), one public talk on a deployed system, deployment stories with business outcomes, apply list weighted to fintech/regulated employers and NY-concentrated FDE postings; routes where remote/low-travel is structurally normal (RSA/PSE-style roles) prioritized |
| Order | Course | Platform | Cost | Certificate? | Duration | Why This Course | ✅ Done |
|---|---|---|---|---|---|---|---|
| 1️⃣ | Agentic AI (Andrew Ng) ⭐ | DeepLearning.AI | FREE (videos) | ⚠️ Pro only | Self-paced (multi-week) | THE #1 AGENTIC COURSE! Vendor-neutral, raw Python — no framework lock-in.📝 Full rationale — click to expandFour design patterns (Reflection, Tool Use, Planning, Multi-Agent) plus the evals/error-analysis discipline that survives the coming agentic-project shakeout. | ☐ |
| 2️⃣ | Evaluating AI Agents | DeepLearning.AI | FREE (videos) | ⚠️ Pro only | 1-2 hours | MEASURE YOUR AGENTS! Code-based vs LLM-as-judge evaluators, metric selection, tracing/observability — powers the Tool Correctness = 1.0 / Task Completion > 0.8 gates. | ☐ |
| 3️⃣ | MCP: Build Rich-Context AI Apps with Anthropic (FULL) 🤖 Anthropic Academy alt (first-party): Model Context Protocol: Advanced Topics | DeepLearning.AI · Anthropic Academy (alt) | FREE (videos) | ⚠️ Pro only | 1-2 hours | THE DEFINITIVE MCP COURSE! Build & deploy MCP servers, client-server architecture — the Stage 1 primer taken to production depth for PolicyPulse.📝 Full rationale — click to expandAcademy alt (Advanced Topics) is a genuinely deeper, distinct course — sampling, notifications, file-system access, transports & scaling for production servers. | ☐ |
| 4️⃣ | AI Agents in LangGraph | DeepLearning.AI | FREE (videos) | ⚠️ Pro only | 2 hours | Stateful workflows with memory, persistence, and human-in-the-loop — built from scratch.📝 Full rationale — click to expandThe HITL pattern behind Crucible's mandatory sign-off gate. ⚠️ Currency note: recorded before LangGraph 1.0 (GA Oct 2025; API stable until 2.0) — notebooks may use pre-1.0 APIs. Treat as conceptual/secondary; LangChain Academy (row 5️⃣.5) is the API-current primary for LangGraph itself, written by the team that builds the current version. | ☐ |
| 5️⃣ | Long-Term Agentic Memory with LangGraph | DeepLearning.AI | FREE (videos) | ⚠️ Pro only | 1-2 hours | AGENTS THAT REMEMBER! Semantic/episodic/procedural memory (maps to the CoALA framework citation on record) — taught by Harrison Chase.📝 Full rationale — click to expand⚠️ Same pre-LangGraph-1.0 currency note as row 4️⃣ — concepts hold; verify API idiom against LangChain Academy / current docs. | ☐ |
| 5️⃣.5 | LangChain Academy (LangGraph + LangSmith) | LangChain | FREE | ✅ Yes (free completion certificates) · 🆕 C49 | Self-paced (notebook-based) | OFFICIAL, CURRENT, FREE — plugs the production-observability gap.📝 Full rationale — click to expandrole elevated: now the API-current PRIMARY for LangGraph learning (LangChain 1.0 + LangGraph 1.0 went GA Oct 2025 with a no-breaking-changes-until-2.0 commitment; the two DeepLearning.AI LangGraph shorts above predate 1.0 and are demoted to conceptual/secondary). Notebook curriculum from the LangChain team on stateful/multi-agent architectures AND evaluation + tracing with LangSmith and production deployment patterns. Directly addresses the agent observability/tracing best-practice flagged in the tri-agent review (LangSmith-style instrumentation), complementing the DeepLearning.AI LangGraph shorts above. Vendor-aligned but broadly applicable given LangChain's ubiquity; use it for the eval/observability layer, not framework lock-in (the roadmap's backbone stays raw-Python + DeepEval/RAGAS). | ☐ |
| 6️⃣ | Agent Skills with Anthropic 🤖 Anthropic Academy alt (first-party): Introduction to agent skills | DeepLearning.AI · Anthropic Academy (alt) | FREE (videos) | ⚠️ Pro only | 1-2 hours | Move workflow logic OUT of prompts into reusable Skills — works across Claude API and Claude Agent SDK; directly applicable to Cadence and the flagship agents.📝 Full rationale — click to expandAcademy alt covers SKILL.md authoring, description-triggering, sharing via repo/plugins, subagent wiring & troubleshooting. | ☐ |
| 7️⃣ | Claude Code: A Highly Agentic Coding Assistant 🤖 Anthropic Academy alt (first-party): Claude Code in Action (on-ramp: Claude Code 101) | DeepLearning.AI · Anthropic Academy (alt) | FREE (videos) | ⚠️ Pro only | 1-2 hours | Agentic coding best practices: context management, MCP integration, parallel instances — while preserving the no-vibe-coding, diff-review-before-merge discipline.📝 Full rationale — click to expandAcademy alt (Claude Code in Action) is the first-party twin for integrating Claude Code into a real dev workflow; Claude Code 101 is the lighter on-ramp. | ☐ |
| 8️⃣ | Document AI: From OCR to Agentic Doc Extraction | DeepLearning.AI | FREE (videos) | ⚠️ Pro only | 1-2 hours | FINANCE-CRITICAL! Agentic workflows over financial PDFs — tables, charts, forms without losing context. FormSense's formal backbone. | ☐ |
| 9️⃣ | Automated Testing for LLMOps | DeepLearning.AI | FREE (videos) | ⚠️ Pro only | 1 hour | THE CIRCLE OF EVALUATION! CI/CD pipelines for LLM apps — evals as blocking gates, automated hallucination/drift catching. (Moved up from v9.2 Stage 5.) | ☐ |
| 🔟 | Generative AI with Large Language Models (AWS + DL.AI) | Coursera | Included (Coursera Plus) | ✅ Yes | 3 weeks (16 hrs) | ML-LITERACY MODULE ANCHOR! The full LLM lifecycle — pre-training → fine-tuning → RLHF → deployment — with the transformer math explained. Substituted by OMSCS coursework if the degree track is active. | ☐ |
| 1️⃣1️⃣ | Finetuning Large Language Models (Sharon Zhou) · 🆕 C49: title corrected — was listed as "Fine-Tuning LLMs with PEFT" | DeepLearning.AI | FREE (videos) | ⚠️ Pro only | 1-2 hours | HANDS-ON FINETUNING — one small fine-tune done properly, AS LITERACY: when to finetune, data preparation, instruction finetuning and evaluation. Knowing when NOT to fine-tune (Prompt → RAG → Fine-tune → Distill) is the interview-defensible position. 🆕 C49: this course does not teach PEFT/LoRA specifically — parameter-efficient methods are covered in row 🔟 (Generative AI with LLMs). | ☐ |
| 1️⃣2️⃣ | Fast & Efficient LLM Inference with vLLM | DeepLearning.AI | FREE (videos) | ⚠️ Pro only | 1-2 hours | INFERENCE ECONOMICS! Serving, batching, KV-cache, quantization — the cost/latency/routing judgment behind the privacy-routed architecture. | ☐ |
| 1️⃣2️⃣.5 | HuggingFace LLM Course (formerly the NLP Course) 🔄 RESTORED TO CORE📚 Resources & notes — click to expand— ⭐ HIGHLY RECOMMENDED · LLM-COURSE TARGETED · 🔁 CONSOLIDATED (fact-check: HF renamed and expanded the NLP Course into the LLM Course — chapters on fine-tuning LLMs and building reasoning models added while classic NLP content is maintained; the two rows were the SAME course, now listed once; a chapter-level certificate is now offered, starting with Chapter 1) | HuggingFace | FREE | ✅ Yes (LLM course chapter certificates) | Self-paced (2-4 weeks) | ECOSYSTEM FLUENCY FOR PRIVACY-ROUTED AI!📝 Full rationale — click to expandNative command of the Hub, datasets, tokenizers, and sentence-transformers — the load-bearing components for deploying LOCAL embeddings and models in the privacy-routed architecture (PII stays local). specifically target HuggingFace's updated open-source LLM Course — the de-facto reference for the open-source stack (modern LLM training, RLHF, fine-tuning, and local deployment). This is the model-layer depth that directly underwrites the local-Ollama routing decision; the NLP course remains the fundamentals on-ramp. Crucial even when never training from scratch. | ☐ |
| 1️⃣3️⃣ | Neo4j GraphAcademy: Knowledge Graphs & GraphRAG path | Neo4j GraphAcademy | FREE | ✅ Yes (→ Neo4j Certified Professional) | Self-paced (multi-week) | DEEPEN GRAPHRAG + RECOGNIZED CREDENTIAL! Knowledge graphs from unstructured data — the formal path behind PolicyPulse's and AFC's Neo4j layer. | ☐ |
| 1️⃣4️⃣ | AI-103 Learning Path — Microsoft Foundry & Azure AI Agents (Microsoft Learn, FREE) 🆕 NEW — CORRECTION 38📚 The three official free sources & exam planning data — click to expand🚨 Correcting a working assumption: AI-103 DOES have official learning. Microsoft publishes it free. Three sources, all $0:① Official study guide — the skills outline, which doubles as the syllabus: connecting an application to a Foundry project, defining agent roles/goals/tool schemas, building agents that integrate retrieval, function-calling and conversation memory, and auditing through trace logging, provenance metadata and approval workflows — that last domain maps directly onto PostCheck. ② Learning path: Get started with AI applications and agents on Azure. ③ Microsoft Foundry training hub — includes developing an agent with Foundry Agent Service + MCP, and built-in tools for optimizing and evaluating models and agents. Microsoft also publishes free preparation paths and an exam sandbox, both linked from the study guide. 📊 Planning data: ~40–60 questions · 100 min · pass 700/1000 · scenario-driven (most items describe a real requirement and ask which service, grounding strategy or agent design fits), with some code-completion items against the Python Foundry SDK. Budget ~60–80 hrs; from AI-901 + Python, roughly 6 weeks. ⚠️ Check before booking: the beta ran ~$99 against the standard $165, and Microsoft frequently issues free or discounted vouchers via Cloud Skills Challenges and virtual training days. ⚠️ AI-103 and AI-200 are two different exams — do not conflate them when searching. ⚠️ Theory-first caveat, stated honestly: the exam is architectural, and you cannot reason about which service fits a scenario if you have never built with any of them. Read the study guide first — then stand up a Foundry project before touching practice tests. | Microsoft Learn | FREE | ❌ No (module assessments only) — the credential is the AI-103 exam | ~60–80 hrs | THE MISSING LEARNING ROW FOR A COMMITTED EXAM. AI-103 sat in the exam table with no course row pointing at how to learn it — a navigation gap, since this table is the guide.📝 Full rationale — click to expandMatches the vendor-official free pattern already used for Confluent, HashiCorp, Astral, dbt Labs and Neo4j. This is the code-first Foundry path; the low-code Copilot Studio path (AB-620) is conditional per CORRECTION 37. | ☐ |
| 1️⃣5️⃣ | Build Custom Engine Agents with the Microsoft 365 Agents SDK (Microsoft Learn, FREE) 🆕 NEW — CORRECTION 38📚 Four modules, the no-tenant unlock & two deprecation warnings — click to expandFour free modules, with assessments: ① Choose a Custom AI Agent Development Path — compares Copilot Studio vs Microsoft Foundry vs M365 Agents SDK vs Teams SDK with trade-offs; take this module first, it resolves the three-layer distinction recorded in CORRECTION 37 §1. ② Understand Microsoft 365 Agents SDK — the copilot stack and custom-engine agents. ③ Utilize an Azure OpenAI model to create an Agent — the load-bearing module for this row. Azure AI Bot Service is the infrastructure backbone (bot registration, channel connectivity, scaling) while the Agents SDK is the framework for your own AI logic — that separation is the architectural point. Covers creating deployments in Microsoft Foundry, adding data sources and search indexes, gathering keys/endpoints, and two retrieval approaches — in-code retrieval via the search SDKs directly, versus the Action Planner with registered tools for AI-driven retrieval decisions (a real ADR-able choice for PostCheck). Ends by deploying to Teams via the M365 Agents Toolkit. ④ Build your custom Agent using the M365 Agents SDK.🔑 The practical unlock — no corporate tenant required. M365 Agents Playground (formerly Teams App Test Tool) lets you chat with your agent and see its messages and Adaptive Cards as they appear in Teams, locally. This matters directly: the Daybright M365 tenant is gone as of 9 Oct 2026, and without the Playground this row would be blocked. ⚠️ Deprecation warning — read before following any tutorial. TeamsFx SDK is deprecated: community-only support until September 2026, new projects must not use it, existing solutions should migrate to the M365 Agents SDK. Many tutorials still teach TeamsFx — check the date on anything you follow. ⚠️ Churn: the Python import root recently moved microsoft.agents → microsoft_agents; pin versions and re-verify signatures.Scope: the SDK extends agents beyond Teams into M365 Chat, Outlook and other M365 hubs. Python is GA and supports 3.10–3.14. | Microsoft Learn | FREE | ❌ No — no certification exists for this SDK | ~8–12 hrs | THE CHANNEL LAYER FOR POSTCHECK — S3 PACKAGING, NOT A BRAIN TRANSPLANT.📝 Full rationale — click to expandADR-009 survives intact: Agent 365 works with agents built on any SDK, naming the Claude Code SDK, OpenAI Agents SDK and LangChain alongside Microsoft's own — so Anthropic SDK stays primary and Ollama stays mandatory for non-synthetic runs. 🏛️ The ERISA-relevant prize is the audit trail, not the chat window: Agent 365 supplies OpenTelemetry observability giving audited, traceable agent interactions, inference events and tool usage, with agents participating in Teams and Outlook like a human participant. An audited, traceable review agent inside a regulated workflow is stronger evidence than the Teams integration itself. 🚫 Synthetic data only — this surface routes through Microsoft cloud and must never touch the regulated path. | ☐ |
| 1️⃣6️⃣ | ⏸️ WATCHLIST — NOT ENROLLED · IBM AI Engineering Professional Certificate 🆕 NEW — CORRECTION 43📚 What it is, why it is parked, and the four triggers to revisit — click to expandWhat it is: IBM's classical ML / deep-learning track — machine learning, deep learning, neural networks and ML algorithms (classification, regression, clustering, dimensionality reduction); supervised and unsupervised models with SciPy and scikit-learn; ML pipelines on Apache Spark; deep-learning models with Keras, PyTorch and TensorFlow. Currently listed as a 6-course programme (reduced from the historical 13), ~3–6 months, Coursera Plus–included. One of the platform's largest AI credentials by enrolment (~174,000+ learners cited in 2026 roundups), so recruiter familiarity is genuinely high — unlike the new AI-Native DE PC.🎯 Why this row exists, stated plainly: it is a parked re-entry point into the ML/deep-learning job family, held open deliberately — not a hedge against v10.0 being wrong. The v10.0 restructure cut the 14-month ML Engineer stage as a career stop: it trained for the job family where PhDs are common and finance-domain depth is worth least, and ML survives here as a compressed literacy module (row 🔟 GenAI with LLMs, row 1️⃣1️⃣ PEFT, row 1️⃣2️⃣ vLLM) under the Prompt → RAG → Fine-tune → Distill sequence. That ruling stands. Parking this is the decision; enrolling is not. If the ML/DL market re-opens in a way that rewards this profile, the on-ramp is pre-vetted and no re-search is needed. 🚦 Four triggers — any ONE activates a re-evaluation; none activates enrolment automatically: (1) 🥇 Posting evidence. ML Engineer or Deep Learning Engineer roles appear as genuine openings on the live apply list — with the domain-and-systems profile this portfolio actually has — rather than as PhD-gated research posts. (2) A named target employer lists Keras/TensorFlow/PyTorch model training (not inference or fine-tuning) as a required line in a posted JD. (3) The Stage 3 ML-literacy module proves insufficient in a real interview loop — i.e. a rejection traced specifically to classical-ML depth, not to agentic/eval/RAG depth. (4) OMSCS Computing Systems free electives are actually spent on ML/DL coursework, at which point this PC is redundant by construction and should be dropped, not taken — the graduate transcript line outranks a Tier-4 certificate. ⚠️ If a trigger fires, check the substitution order first. The accredited route (OMSCS AI/ML free electives, $0 marginal, graduate transcript) outranks this PC under the existing degree-over-credential qualification. This row is the non-degree fallback, and it is Tier 4 — recorded now so a future trigger does not auto-select the nearest course. ⚠️ Anti-stack note: its deep-learning content overlaps the Stage 1 IBM Generative AI Engineering PC (which already carries Keras/PyTorch/SciPy/scikit-learn modules) and the Stage 3 HuggingFace LLM Course (row 1️⃣2️⃣.5). Taking it after those would re-buy hours already spent — the same ruling applied to the IBM RAG & Agentic AI PC above. ⚠️ Evidence-quality flag: enrolment volume is a fact about the course's popularity, not the hiring market for the role it trains. This row is parked on optionality — keeping a cut door openable — and explicitly not on the certificate's learner count. | Coursera (IBM) | Included (Coursera Plus) | ✅ Yes (Professional Cert — Tier 4, never a Certifications line) | 0 hrs committed | 🔭 THE ML / DEEP-LEARNING RE-ENTRY SLOT — PARKED ON PURPOSE, BY APPROVAL.📝 Full rationale — click to expandLogged at Manuel's instruction as a future review point: come back and check whether an opening exists for ML and deep-learning job roles. The v10.0 thesis is that it will not be the right trade — the ML Engineer stage was cut on evidence, and the finance/ERISA moat is worth least in that job family and most in Applied AI / FDE. But the door is now documented, linked, dated and falsifiable instead of closed by silence. The hours stay on PolicyPulse, PostCheck and Crucible. | ☐ |
| 1️⃣7️⃣ | ⏸️ CONDITIONAL — PRE-APPLY REFRESHER · Mastering Algorithms and Data Structures in Python (CodeSignal Learn) 🆕 NEW — CORRECTION 60📚 What it covers, what it misses & the declined edX track — click to expandFive courses · 112 practices · ~16 hrs: ① Hashing, Dictionaries & Sets · ② Sorting & Searching · ③ Linked Lists, Stacks & Queues · ④ Trees — BST, heaps, BFS/DFS · ⑤ Graphs — adjacency list/matrix, BFS/DFS. Python, in-browser, with the Cosmo AI tutor. 4.49★ on ~2,500 ratings, ~29K learners.❌ Not covered: dynamic programming and greedy (CSCA 5414 territory), tries, sliding window, concurrency, and the LRU-style "build, then refactor under changing requirements" round — those stay with the weekly layered-refactor/concurrency reps in the Loop Reality note below. ❌ Declined: the edX version (same content, 5 weeks, $60 verified certificate, via the Sep 2026 2U–CodeSignal partnership). Non-credit, Tier 5, redundant with DTSA 5501/5502 + the CSCA bridge. Take the free CodeSignal path instead. ⚠️ Re-verify before starting: Cosmo free-tier energy limits (launched at 5 bars, recharging every 4 hrs) and Cosmo+ pricing (~$24.99/mo). The path does not require the paid tier. | CodeSignal Learn | FREE (edX $60 track declined) | ✅ Yes (free CodeSignal Certificate of Achievement — Tier 5, never a Certifications line) | ~16 hrs, timeboxed⏱️ Timing detail — click to expandStart 4–6 weeks before the Applied-AI/FDE apply window, or earlier if a target employer sends a CodeSignal online assessment or confirms a DS&A screen. Roughly 3–4 hrs/week over 4–5 weeks, alongside the weekly refactor/concurrency reps. Counts as job search — neither side of the AE/DE ≥ Applied-AI guardrail (CORRECTIONS 58/59). | 🎯 SCREEN-READINESS ON THE PLATFORM THE LOOPS USE — ONLY IF A TARGET ASKS FOR IT.📝 Full rationale & falsifiers — click to expandApplied-AI/FDE loops treat DS&A as table stakes: alongside the applied round (parse logs, build a cache, streaming), prep-vendor reports (directional) describe one classical coding round, with hash maps, heaps, graphs/BFS and caches recurring — and some employers screen through CodeSignal itself. This path is a fast, structured fluency refresher on that exact platform, not new knowledge: the fundamentals are already sourced from CS50 and the CU Boulder bridge (CORRECTION 44). For the AE/DE lane its value is low (most loops weight SQL, modeling and pipeline design), which is why it sits at the Applied-AI apply window, not before.🚦 Falsifiers: (1) Skip if no Applied-AI/FDE target on the live apply list runs a DS&A or CodeSignal round. (2) Skip if CSCA 5454 is completed at B or better and recent own-repo reps already cover these structures. (3) Revisit if loops still fail on DS fundamentals after the sprint — a deeper block from the CSCA bridge, not LeetCode (CORRECTION 7 stands). | ☐ |
Optional depth (kept, links preserved): Neural Networks: Zero to Hero (Karpathy) (FREE, ❌ — GPT from first principles) · AI Engineer Agentic Track (Udemy, $15, ✅) — 8-project capstone bootcamp if extra reps wanted (kept: 5 frameworks / 8 projects, project breadth nothing free matches; its Trading-Floor capstone maps to Crucible) · Hugging Face AI Agents Course (FREE, ✅ recognized cert) 🆕 v10.0 — FREE SECONDARY OPTION to the Udemy track: community-driven, hands-on with smolagents / LlamaIndex / LangGraph, ends in a resume-listable certificate. Framework-agnostic fundamentals (principles over syntax); take it as the free credentialed companion, not a replacement — the two serve different purposes. · IBM RAG and Agentic AI Professional Certificate (Included, ✅ PC) — ⏸️ CONDITIONAL: heavy overlap with the restored IBM GenAI Engineering PC ("replace, not stack"); take only if a second structured program is genuinely needed. audit-closure note: this PC contains "Agentic AI with LangChain and LangGraph" as its 7th course — the v9.2 Stage 2 row #10 ("Agentic AI with LangChain (IBM)") that the v10.0 restructure dropped without a log line is therefore superseded-and-contained here, with its LangGraph content also covered by LangChain Academy + the DeepLearning.AI LangGraph shorts. Gap was documentation, not substance. Ollama and CrewAI are absorbed into project work, not courses is the lane this portfolio does not target, with guides noting teams outgrow it and migrate to LangGraph. Crucible's HITL sign-off + kill-switch and DataVault's ERISA audit posture are the auditability/checkpoint requirement profile the market routes to LangGraph. CrewAI exposure already exists at zero slot cost via the Udemy Agentic Track (5 frameworks) and framework-agnostic HF Agents Course above; the interview-defensible artifact is a PolicyPulse ADR: "Evaluated CrewAI, chose LangGraph" — decomposition evidence, not a course certificate. The DLAI short is also Pro-lab-gated, so taking it would spend Sprint-2 budget on an off-lane framework. Falsifier: revisit only if a Stage 3 target employer names CrewAI in a posted JD.).
| Credential | Code | Cost | Format | Why It Belongs in Stage 3 | ✅ Passed |
|---|---|---|---|---|---|
| ⏸️ CONDITIONAL 🆕 CORRECTION 50 — Anthropic Claude Certified Architect — Foundations Sit only if you join (or your employer joins — free for any organization bringing Claude to market) the Claude Partner Network, or Anthropic opens public registration. If the gate opens, take CCDV-F (Developer – Foundations, $125) first; CCA-F follows — the natural pick when working at an Anthropic partner. | CCA-F (also coded CCAR-F under the 2026 four-track rename) | $125 (was $99) | 60 Q · 120 min · scaled pass 720/1000 | ANTHROPIC-NATIVE AGENTIC CREDENTIAL — blueprint maps 1:1 to the stack: agentic orchestration, Claude Code, structured output, tool design & MCP. Provider source-of-truth for the primary SDK. (July 2026): moved to Pearson VUE (live 30 Jun 2026); fee $99 → $125; retake ladder 14/30/90 days, max 4 attempts / rolling 12 mo; 12-month term with free renewal; exam content unchanged. Now one of a four-exam family (Practitioner/Associate, Developer, Architect-Foundations, Architect-Professional $175). ⚠️ ACCESS RISK — see open question below: registration runs through Anthropic Partner Academy and requires a Claude Partner Network link; the free-for-first-5,000 window has closed and public registration is announced but undated. Confirm Daybright's Partner Network status before scheduling. | ☐ |
| Azure AI Apps & Agents Developer Associate ELEVATED FROM EMPLOYER TRACK | AI-103 | ~$165 · self-funded | ~40–60 Q · 120 min · pass 700/1000 · proctored (Pearson VUE) | CODE-FIRST AZURE COUNTERPART TO CCA-F — successor to the retired AI-102; Python + Microsoft Foundry, generative-AI + agentic solutions (largest domain), RAG grounding, evaluation, Responsible AI. This is the Azure-native mirror of CCA-F's code-first agentic scope: AB-620 is the low-code Copilot Studio maker path, AI-103 is the code-first Foundry developer path (many enterprises run both). Turns the employer track into a genuine on-ramp to the Applied-AI destination rather than stopping at DP-700. Already tracked in the Employer Track; surfaced here so it reads as a Stage 3 Applied-AI credential. | ☐ |
| Databricks Certified Generative AI Engineer Associate | — | $200 | 45 Q · 90 min · 2 yrs | Industry's first production-GenAI engineering credential; maps to RSA-style remote-normal routes. | ☐ |
| NVIDIA-Certified Associate: Generative AI LLMs 🔄 RESTORED v10.0 | NCA-GENL | $125 | 50-60 Q · 60 min · 2 yrs | Erroneously dropped in the initial v10.0 cut — restored. Transformers, prompt engineering, RAG, PEFT verification; the recognized DL credential replacing the discontinued TensorFlow cert. | ☐ |
| Neo4j Certified Professional | — | FREE | Online exam | Graph credential backing the GraphRAG layer in both PolicyPulse and AFC. | ☐ |
❓ OPEN QUESTION — CCA-F access gate. As of the July 2026 Pearson VUE migration, CCA-F registration runs through the Anthropic Partner Academy and requires a Claude Partner Network link; the free-for-first-5,000-employees window has closed, and Anthropic has announced public registration is coming but with no date. This means CCA-F may not currently be sittable as a straightforward "personal" cert. Action items before committing to the Stage 3 CCA-F line: (1) check whether Daybright is (or will join) the Claude Partner Network — any organization can apply for free; (2) if not, watch for Anthropic's public-registration opening; (3) note the Anthropic Developer track (CCDV-F) as the code-first sibling if a role weights builder credibility over solution-architect framing. This mirrors the existing open question on Daybright mid-cycle market adjustments — both are employer-dependency unknowns that change Stage-1/Stage-3 calculus. 🆕 CORRECTION 50 — resolved for now: checked October 2026 — the Developer track is gated the same way (every Claude exam requires a Claude Partner Network work email), so swapping CCA-F for CCDV-F would not remove the gate. Both now sit as one conditional canon line: CCDV-F first, CCA-F after, triggered by Partner Network access (including Daybright joining) or public registration.
🎓 NCA-GENL prep path (NVIDIA DLI) — v10.0 CORRECTION 4 addendum (July 2026, evidence-backed). Research note on the NCA-GENL row above. Recognition reality: the recruiter-verifiable credential is the proctored NCA-GENL exam (Credly badge, one-click verifiable) — NVIDIA DLI courses issue completion/competency certificates, not the credential. Practitioner data is blunt: the badge alone does not unlock the salary bump; it's a credible interview signal that pairs with hands-on RAG/fine-tune portfolio work — most value is in the learning, not the badge (this is the evidence-first thesis). So the prep courses below are chosen to double as portfolio evidence, not just exam cramming. ~70% of NCA-GENL content is platform-agnostic LLM fundamentals; the most credible profile holds ≥1 cloud AI cert + NCA-GENL (already covered — AWS DEA-C01 + Azure track).
Net for the roadmap: ① is the highest-leverage add (free, exam-relevant, doubles as PolicyPulse evidence — the "learning + artifact beats the badge" profile the market rewards). Its unique value over the existing DeepLearning.AI/HuggingFace RAG coverage is the NVIDIA-stack specificity (NeMo / NIM / Triton / RAPIDS terminology) that the exam's ~30% NVIDIA-native content tests. No new spend — all three are free/low-cost DLI self-paced courses.
❌ Declined — logged as evaluated, not selected: the two NVIDIA Professional-tier certifications carried by the v9.2 archive — NCP-AAI (NVIDIA-Certified Professional: Agentic AI, v9.2 Stage 4 row 19) and NCP-GENL (NVIDIA-Certified Professional: Generative AI LLMs, v9.2 Stage 5 row 2) — were silently dropped in the v10.0 restructure with no log line; this entry closes that gap. Decline rationale: the Associate-tier NCA-GENL already occupies the single NVIDIA slot in the Surviving Nine ("replace, not stack" — one NVIDIA credential max); the Professional exams target dedicated ML/GPU-infrastructure practitioners, the job family the v10.0 restructure deliberately cut; and stacking Associate + Professional from one vendor is exactly the credential-density anti-pattern the credential ladder (Tier 3) warns against. Falsifier: revisit NCP-AAI only if a Stage 3 target employer explicitly names it or weights NVIDIA-stack agentic depth (NeMo Agent Toolkit) in a posted JD; revisit NCP-GENL only if NCA-GENL is passed AND an NVIDIA-ecosystem employer is on the live apply-list.
There is no Stage 3 practice-platform row, and that is the finding — not an omission. The Stage 2 block above exists because DE loops are query-and-code heavy. The Applied-AI/FDE loop is a different animal, and no question bank sells what it tests.
What the coding round actually is. Reported Anthropic FDE loops run a practical, multi-stage exercise on a CodeSignal-style platform where each stage adds a requirement that forces you to refactor your earlier code — clean, adaptable implementation carries the round, not a fast brute-force answer. Reported prompts are engineering tasks, not algorithm trivia: implement an LRU cache then extend it as new constraints land (including making it concurrent), transform sampled stack data into execution traces, read a set of files and eliminate duplicates. Practitioner guidance is blunt that FDE coding rounds are realistic engineering problems, not pure DSA puzzles — and this is exactly where most engineers over-prepare on LeetCode and under-prepare on the actual format. Concurrency and multithreading are reported across multiple rounds.
Where candidates actually die. Roughly 60% of candidates who clear the technical programming rounds are filtered out at the customer-conversation / client-simulation round, and recruiters report the values/culture round is the most common failure point overall. The 2026 FDE compensation report found 73% of frontier-lab FDEs say running discovery conversations was the skill they were least prepared for coming from a traditional engineering background. The hiring-manager deep dive screens aggressively for engineers who can articulate their own contribution — "we did" instead of "I did" is the reported trap.
So Stage 3 practice = reps, not a subscription:
⏸️ CONDITIONAL — O'Reilly learning platform, quarterly only. The one paid option that earns consideration, and only because of what it bundles: (1) "Visualizing software architecture with the C4 Model" — a ~3-hour live course taught by Simon Brown himself (static structure, dynamic + deployment diagrams, how to review architecture diagrams, tooling landscape); (2) the C4 Model book (published 21 Jul 2026); (3) Architectural Katas — the moderated live series (Neal Ford / Mark Richards / Sam Newman) where teams answer an RFP under changing requirements, constraints and a deadline, then present and defend to judges, with a session on presenting architecture to stakeholders. Pricing (verified July 2026): $49/mo · $129/quarter · $499/yr. Take the quarter, never the year — same discipline as the StrataScratch conditional. Trigger: the M12–14 apply window opens and both cheaper routes below have been checked and ruled out. ⚠️ Check these first — two possible $0/low-cost routes: (a) ACM professional membership + Skills Bundle add-on (~$75/yr) grants O'Reilly access — but ACM describes its collection as books, video courses, recorded Superstreams and playlists, so live events are NOT confirmed and must be verified before relying on it for the Katas/C4 sessions; (b) O'Reilly for Higher Education is sold to university libraries via ProQuest — check whether Georgia Tech's library carries it once OMSCS enrollment starts (unverified for GT specifically; flagged, not asserted). Note: the free kata bank above delivers the rehearsal at $0 — the paid platform buys the moderated version and the creator-taught C4 session, not the practice itself.
❌ Declined — logged as evaluated, not selected (v10.0 CORRECTION 14, architecture-training audit): Udemy "Modeling Software Architecture: C4, Viewpoints, Perspectives" and "Mastering Software Architecture Patterns" (which does carry a dedicated ADR + C4 + Structurizr lecture) — real content, but they duplicate free first-party material and Udemy completion certs are already rated near-zero weight in this roadmap · Pluralsight "The C4 Model for Software Architecture" — it is sold as instructor-led professional-services training for teams, not a self-serve individual course, so it is not purchasable on this path · Architecture certifications generally — no proctored, US-recruiter-recognized credential for C4 or ADR exists; the nearest options are enterprise-architecture frameworks (TOGAF) or the DACH-weighted iSAQB CPSA, both off-trajectory for Applied-AI/FDE and both unverified here. Revisit only if a target employer names one.
❌ LeetCode — logged as evaluated, not selected. Wrong format for both targets (DE loops want SQL + data modeling; FDE loops want practical refactoring under changing requirements). DS&A fundamentals are already sourced from CS50 and, if the degree track is active, OMSCS Computing Systems — which also covers the concurrency the FDE loop probes, at far greater depth. Revisit only if a target employer is confirmed to run a classical DS&A screen. 🆕 C60: for that case a free, timeboxed platform refresher is now pre-vetted — Stage 3 row 1️⃣7️⃣ (CodeSignal Learn DS&A path, ~16 hrs, 4–6 weeks before the Applied-AI/FDE apply window). LeetCode stays declined.
Why this layer exists. By Stage 3 you have deployed, interrogatable systems and the discovery/decomposition edge. Distribution now shifts from posting to speaking — the highest-authority signal — and from generic networking to the FDE-in-fintech ecosystem where the ERISA moat is worth the most.
① Land the conference/meetup talk (already a Stage 3 deliverable). The rooms joined in Stages 1–2 are the on-ramp:
② Weight the apply list to the FDE-in-fintech ecosystem. Verified 2026 data: FDE postings surged (~800% in 2025) and the role is now delivered not only by frontier labs but through Deloitte, Accenture (APBG), and PwC in financial services — regulated-industry verticals where a finance background is an explicit plus. That consultancy-delivered, financial-services FDE lane is the one aligned to your moat, and it broadens the target list well beyond the frontier labs.
Note on Palantir events: the source review suggested Palantir "AI Engineer Socials." Live checking could not confirm that as a named program, and current Palantir meetups skew defense-tech / veteran — so treat it as lower-priority than the fintech-FDE path above. If a specific Palantir/Foundry role is the target, the higher-signal route is a referral from someone already inside (LinkedIn, the FDE communities), not a general social. Cross-reference the FDE-positioning row in the Focus Areas table.
📌 Flagship decision note: the portfolio is 4 flagships + 2 supporting. PolicyPulse is the Applied-AI flagship (RAG + GraphRAG + MCP + per-document access control — the regulated-finance differentiator). The 1099/DataVault-lineage data platform is the DE flagship (real deployed system, real business outcome — 450+ incorrect tax codes caught before participants received bad documents) and retains scheduling priority, since it feeds the first external move. Crucible is fully restored to Flagship status: an autonomous multi-timeframe (swing → intraday) execution research platform whose human-in-the-loop mandatory sign-off, kill-switch requirement, and "LLM behind the Wall" information barrier are exactly the deployment-safety engineering that FDE interviews in regulated finance probe — and FDE hiring is portfolio- and performance-driven, concentrated in NY fintech. Its live path always retains human sign-off + kill-switch; Phase 2 (paper agent) ships with published eval gates (Tool Correctness = 1.0, Task Completion > 0.8) and a verifier-agent layer before the HITL gate. PostCheck is the dual-target flagship — the only project whose single deliverable produces first-class evidence for both target doors: agentic adjudication with a hard escalation boundary, multimodal reasoning over scanned packets, three-layer eval with a blocking gate, MCP and HITL (Applied AI); and exactly-once event ingestion, deterministic parsing of a ragged block-structured source, an append-only event log with a declared grain, dbt models + contracts, and a metrics layer answering a real operational question (Analytics Engineer / DE). It also carries a real incumbent to beat — a prompt-only reviewer already in use — permitting a genuine before/after rather than an unfalsifiable claim. PostCheck is not FormSense: FormSense is pre-index intake quality (is this form complete and legible enough to file?); PostCheck is post-posting keying verification (does the posted transaction match the request and comply with the SOP?). Different position in the workflow, different source of truth, different escalation target — the two are never merged. Standard budget remains 25 hrs/week: when hours are scarce, priority order is DataVault → PolicyPulse → Crucible; PostCheck S1 is scoped to be independently shippable and independently evidence-bearing, so it never blocks the evidence gate.
| Tier | Project | Role in the portfolio | Stages |
|---|---|---|---|
| 🏁 Flagship 1 | PolicyPulse | Applied-AI flagship: RAG → GraphRAG (Neo4j + ChromaDB), FastMCP server, eval gates (RAGAS/DeepEval), per-document access-control retrieval, privacy-routed providers | S1 → S3 |
| 🏁 Flagship 2 | DataVault / 1099 Data Platform | DE flagship: production financial data platform — ingestion, dbt-tested models with CI, Airflow orchestration, data contracts, Docker/ECS deployment, monitoring + postmortems; semantic/metrics layer for the AE story. S1 is the reconciliation core (Matrix + Relius → canonical model → reconcile → 1099-R Box-7 derivation/validation → corrections by type × week/month), not a "chat with Excel" tool. The retired standalone DataVault Analyst (PandasAI/NL querying) is folded in as the S3 Applied-AI layer over the marts — text-to-SQL against the semantic layer with HITL on every write. One coherent flagship arc; no separate 1099 or Analyst project. Dataframe engine policy (CORRECTION 35): the S2 hardening moves ingestion and bulk transforms to Polars and the reconciliation rules to tested dbt models; pandas is retained deliberately for the openpyxl correction-template write and the plotting hand-off. The shipped S1 pandas pipeline is not rewritten — it is frozen as the "before" and the delta becomes the S2 headline metric. | S1 → S3 |
| 🏁 Flagship 3 | Crucible 🔄 RESTORED | Autonomous multi-timeframe (swing → intraday) execution research platform: backtest engine → paper agent → live micro-sizing; mandatory human sign-off + kill-switch on the live path; "LLM behind the Wall" (in-sample aggregated stats only); verifier agent before the HITL gate; published agentic evals | S1 → S3 |
| 🏁 Flagship 4 | PostCheck | Dual-target flagship (Applied AI and AE/DE in one system): autonomous post-posting QA review agent for regulated distribution operations. Watches an intake folder, claims each packet exactly once (event-as-hint + poll floor + content-hash idempotency + lease TTL), parses the posted-transaction export deterministically (row-type discriminator dispatch — the LLM never sees the workbook), segments and extracts a scanned multi-document packet with a multimodal model, routes on form family, resolves live vs dead payee legs, then adjudicates against a versioned SOP across a fixed 15-item verification surface (PASS / EXCEPTION / CRITICAL / N/A) → IGO / NIGO (needs clarification) / NIGO (do not process). Findings escalate to the human processor with field, form value, export value, SOP citation and fix; clean reviews emit a report artifact; every adjudication appends to an event log feeding a dbt-modelled NIGO quality mart (first-pass IGO rate, reason Pareto, reason-mix drift, agent-vs-human agreement). Safety invariant (binding, tested): read-only and advisory — never keys, posts, reverses or corrects; never contacts a participant, advisor, TPA or sponsor; never edits SSN, name or DOB; an IGO verdict is a recommendation to a human, never an authorization. Headline metric: false-CRITICAL rate versus a flattened-text baseline running the identical rule pack on the identical golden set. Blocking gate is false-NIGO rate, not accuracy (precision blocks, recall reported). The spreadsheet is a rendered export, never the source of truth; fct_document_reviews grain is one row per (packet, review run). Synthetic corpus only — the controlled-NIGO-injection generator is itself a portfolio artifact and the only route to ground-truth labels. Provider-agnostic across three named substrates (Anthropic · Azure OpenAI via Microsoft Foundry · local Ollama), one eval suite, gates run per substrate. | S1 → S3 |
| 🧩 Supporting | FormSense | Agentic workflow (Anthropic taxonomy — interview-defensible vocabulary), multimodal extraction on synthetic ERISA forms, GEval schema adherence. Scope boundary vs PostCheck: FormSense sits pre-index — is the form complete, legible and internally consistent enough to file, alert the submitter, or escalate on low confidence before indexing. It judges the form against itself. PostCheck sits post-posting and judges the form against the posted transaction export. Never merged, never sharing a source of truth. | S1 → S3 |
| 🧩 Supporting | AFC | Read-only GraphRAG financial research; faithfulness ≥ 0.9 eval showcase. its eval-first core is an S1 deliverable — the smallest publishable high-signal artifact (SEC-grounded faithfulness benchmark + controlled-perturbation catalog); GraphRAG research loop is S3. 🆕 (CORRECTION 46) Plus a read-only event-study backtest for trigger decisions — v1 in S1 (insider purchases, volume, dilution state), full trigger matrix by end of S2; reported as lift over a base rate, never as returns. 🆕 (CORRECTION 47) AI-powered predictive layer (ML meta-labeling) from S1 Phase 2 — LLM filing features in S3. | S1 → S3 |
positioning: Crucible and AFC are NOT quant projects, and should never be presented as such. The industry separates quant research (alpha, factor construction, derivatives pricing — stochastic calculus and econometrics, heavily PhD-gated) from quant development / trading-systems engineering (C++/Python, Linux, FIX, time-series stores, event-driven low-latency design). Placing these projects correctly:
Why this line exists: if a reader silently promotes Crucible into a "quant" comparison, it is measured against a PhD-weighted field on a dimension it never claimed. The systems-engineering framing is both true and rarer — deployment-safety engineering for irreversible actions is the differentiated evidence, and it is what FDE-in-fintech interviews actually probe. See the matching entry in the Falsification List.
The model is stage-layered across projects, not project-by-project. You do not finish one project and start the next — you build the S1 layer across the leads, harden to S2, then climb to S3. Skills gate the sequence: each layer teaches what the next project's layer requires. Eval-first blocking gates mean a layer must pass before you climb.
| Order | Build | Skills unlocked (courses / certs) | Why this position |
|---|---|---|---|
| 1 | S1 — PolicyPulse core + DataVault reconciliation core + PostCheck adjudication core | RAG chunk→embed→retrieve, FastMCP, RAGAS/DeepEval eval gates · reconciliation + Box-7 rules engine (🆕 C56: built as tested dbt models) + PII boundary + structured outputs · event-driven intake with exactly-once claiming, deterministic block parsing, multimodal packet extraction, versioned rule engine, blocking precision gates. Courses: IBM GenAI Engineering PC · Building with the Claude API · Building & Evaluating Advanced RAG · Pre-processing Unstructured Data for LLM Applications · MCP primer · Python/SQL foundations · Docker. Certs: AI-901, AB-620 (self-funded) | Cheapest to stand up; teaches the foundations everything reuses. RAG + eval here are prerequisites for AFC's GraphRAG, PolicyPulse S3, and Crucible's "LLM behind the Wall." PostCheck joins this layer because its S1 is independently shippable and independently evidence-bearing — it ships a measurable headline (deterministic parser vs flattened baseline) without waiting on any other project, and its structured-output and eval discipline is the same spine PolicyPulse and DataVault use. |
| 2 | S2 — DataVault leads the DE/AE hardening | dbt + tests, data contracts (Great Expectations), medallion layering, Airflow idempotency, warehouse, semantic/metrics layer, Terraform/ECS · Polars-first ingestion layer with pandas retained at the template/plotting boundaries (CORRECTION 35) · signalcore built here.Courses: PostgreSQL for Everybody · dbt Fundamentals + Advanced · Astronomer Academy (Airflow) · Terraform Fundamentals · Snowflake DE PC · Databricks Academy. Certs: DP-700 ✅ + AWS DEA-C01 ✅ (committed) · take ONE conditional platform cert only if the apply-list demands | DataVault first because its S2 IS the evidence for the Months 12–14 apply window (~Q1 2027). These exact skills then transfer to every other project's S2 (PolicyPulse's embedding pipeline, PostCheck's NIGO quality mart and contracts, AFC's EDGAR lakehouse, Crucible's market-data lakehouse, FormSense's doc-ops pipeline). PostCheck's S2 is the closest sibling to DataVault's — the same dbt + contracts + Airflow + grain-design work applied to review events instead of transactions, which makes it the cheapest second AE proof in the portfolio. |
| 3 | S3 — Applied AI; PostCheck adds the agentic loop; Crucible closes it out | GraphRAG (Neo4j + ChromaDB), agentic loops, deep MCP, HITL, three-layer eval + Arize Phoenix · evaluator-optimizer self-verification with an iteration cap, RAG over a governing standard with clause citation, shadow evaluation before promotion, feedback inheritance from human corrections. Courses: AI Agents in LangGraph · LangChain Academy · Neo4j GraphAcademy · Knowledge Graphs for RAG · Automated Testing for LLMOps · NVIDIA DLI RAG Agents · HuggingFace NLP/LLM. Certs: Neo4j Certified Pro (FREE) · NCA-GENL · Databricks GenAI Assoc · AI-103 · CCA-F ⏸️ conditional on Partner Network access (all self-funded) | PostCheck's S3 is the safest place to learn agentic self-verification — the loop is bounded, the escalation target is a human, and the system is read-only by construction, so a failed iteration costs a false escalation rather than a wrong payment. That is the rehearsal for Crucible. Crucible's live-execution path is built LAST in the entire portfolio — the only genuinely irreversible path (mandatory HITL + tested kill-switch), the hardest stretch, and it reuses skills from all prior work. |
Priority when hours are scarce (25 hrs/week): DataVault → PolicyPulse → Crucible — unchanged. PostCheck slots alongside PolicyPulse at S1 and alongside DataVault at S2, because it shares both spines (structured outputs + eval gates; dbt + contracts + grain design) and because its S1 ships evidence on its own. It never displaces the three leads. AFC slots in after PolicyPulse establishes GraphRAG (shares the eval spine; its eval-first core is publishable early as the smallest high-signal artifact). 🆕 C56: AFC's Phase-1 kickoff is scheduled for plan Day 83 under this clause; AFC's dbt work stays in S2. FormSense where pre-index document-AI is relevant — distinct from PostCheck, which is post-posting. StreamSmart / ODI = backlog.
Relevance ranking (why this order and not another): the first external move targets AI-Focused Data Engineer / Analytics Engineer — so the DE/AE flagship leads. PolicyPulse is second because the Applied-AI flagship is the Stage-3 destination evidence and its S1 is cheap. PostCheck is the hedge across both: it is the only artifact that reads as first-class evidence at either door, so it stays relevant whichever way the apply window breaks. Crucible is a lead flagship but third: highest risk, highest skill prerequisite, and its differentiated value (execution-safety engineering) only reads as credible once the DE and RAG foundations are demonstrably in place.
Backlog (production-grade when built, positioned last): StreamSmart (consumer/personal-finance subscription optimizer) and ODI (internal demand analytics — overlaps the 1099 platform's mart/AI layer; consolidation candidate). Both carry the full production standard if built, but sequence behind the lead trio and the supporting set. Neither is active portfolio.
Standards (unchanged, non-negotiable): no vibe coding — every line understood before merge; eval-first with blocking gates; synthetic data only in public repos; pyproject.toml + uv.lock + src/ layout + py.typed + ruff + mypy; structured logging (structlog over stdlib via ProcessorFormatter, so third-party library logs render through the same chain), a redaction processor as the PII choke point, typed config (pydantic-settings, every credential SecretStr), and capped jittered retries (stamina); Conventional Commits; a pinned .pre-commit-config.yaml in every repo (hooks are a strict subset of the CI gate — CI stays authoritative; ruff-check --fix before ruff-format, uv-lock, gitleaks, detect-private-key, nbstripout where notebooks exist, and conventional-pre-commit on the commit-msg stage so Conventional Commits is enforced, not merely declared; mypy deliberately CI-only); earned-overlay policy (ML components ship only if they beat the baseline). tier ≠ quality: flagship vs supporting denotes size & emphasis, not a quality tier — every project is production-grade and carries the full standard above. Lead flagships receive new tooling first and are updated continuously as skills grow. Each project is ONE system that evolves S1 → S2 → S3, never rebuilt per stage.
Architecture-decision layer added to the production standard. The standard already required a Mermaid architecture diagram; it did not require the decision-and-defense artifacts that Applied-AI / FDE interviews actually probe (decomposition, tradeoff reasoning, stakeholder communication). Both additions below are documentation discipline on work already being built — net-zero cost, high interview signal. They make the difference between "I built X" and "here is why I chose X over Y and what it cost."
| Artifact | Applies to | What it is | Why it earns its place |
|---|---|---|---|
| ADRs — Architecture Decision Records | Every project (flagship + supporting) | A numbered, immutable docs/adr/ log. Each record: context → decision → consequences/tradeoffs (e.g. "GraphRAG hybrid over pure-vector," "HITL on every write in the DataVault Analyst layer," "LLM-behind-the-Wall in Crucible"). Superseded decisions are marked, never deleted — same additive-only discipline as this roadmap. | The single artifact a hiring manager can interrogate line by line. Turns portfolio repos into an interview script; directly feeds the FDE decomposition round and the project-deep-dive rehearsal (see Stage 3 Loop Reality). |
| C4 diagrams | Level 1 (Context) on every project; Level 2 (Container) on the three lead flagships | C4 Context (Level 1): the system as one box with its users and external systems — who/what it talks to. Container (Level 2, leads only): the deployable units (API, worker, vector store, warehouse, MCP server) and how they communicate. Sits alongside the existing Mermaid diagram, which stays as the component/flow view. | C4 is the vendor-neutral standard for exactly the "explain your system to a stakeholder" moment the loop tests. Level 1 forces the boundary-and-dependency clarity FDE work lives on; Level 2 shows you can reason about deployable units, not just code. |
Full production README standard (v10.0, now): Mermaid architecture diagram · C4 Context diagram (+ Container on leads) 🆕 · docs/adr/ ADR set 🆕 · Dockerfile · evaluation-metrics table · 15–30s demo GIF · "What I Learned" · no vibe coding · eval-first blocking gates · synthetic data only in public repos · pyproject.toml + uv.lock 🆕 + src/ + py.typed + ruff + mypy · Conventional Commits · 🆕 .pre-commit-config.yaml (pinned; strict subset of CI) 🆕 · file-by-file review before merge. Rollout: additive and retroactive. Trigger: the Stage-1 1099-pipeline retro-migration pass — the C4 Context view and the first ADRs are written in the same documentation pass as the pip → uv migration, so it is one pass rather than two, and the whole thing becomes build-in-public content per the Stage 1 Distribution cadence. PolicyPulse and Crucible follow at their next hardening pass; supporting projects get Level-1 C4 + ADRs when next touched. Hard gate: DataVault's C4 + ADR set must exist before the Stage 2 dbt-Slack ship post, which already assumes them. No rebuild; no new spend.
how it's learned and tooled (closing the loop). Correction 8 made these artifacts mandatory but named no learning source and no toolchain — the only standard items in the roadmap without either. Both are now fixed:
.dsl file in the repo, version-controlled; on the ThoughtWorks Tech Radar under Diagrams as code), then use structurizr-cli to export the C4 views to Mermaid for the README. This satisfies "C4 diagram alongside the existing Mermaid diagram" from a single source — no two artifacts drifting apart. Direction matters: model in Structurizr, render out to Mermaid (Mermaid's own C4 support is newer and less complete than the dedicated tooling). Structurizr Lite is free and self-hosts in Docker — already a standing requirement, so no new dependency.docs/adr/ in the same repo as the code it describes; immutable once accepted, superseded never deleted.Production / Cost / Architecture adopted as the explicit presentation order. Corrections 8 and 14 defined which artifacts exist in a production repo. They said nothing about the order a reviewer meets them in, or the language layered on top. This correction fixes only that: it adds no artifact and removes none — the Mermaid diagram, C4, ADR set, Dockerfile, eval table, demo GIF, CI and "What I Learned" all stand exactly as specified. Cost: $0. It reorganises what is already being built.
The rule: every flagship README leads with three headings in this order — ① Production · ② Cost · ③ Architecture — and every résumé bullet beneath that project answers one of the three. Anything that answers none of them is cut.
The three-signal framing was first encountered in a 2026 Databricks-focused hiring guide arguing that candidates spend months certifying only to be ignored by managers who value evidence over credentials, naming Production, Cost and Architecture as the signals that generate callbacks. That is a single, partly-paywalled source, so it was corroborated against independent 2026 résumé and hiring guidance before being adopted here:
⚠️ Source-quality flag, per this file's evidence rule: these are résumé-industry and career-content publishers, not peer-reviewed research. What justifies adoption is convergence across independent 2026 sources plus a concrete, checkable mechanism (the Greenhouse/Workday parsing claim) — not the authority of any one of them. Treat as directional. This does not disturb the CORRECTION 7 finding that fewer than 16% of hiring managers rank certifications among their top three résumé signals; it is consistent with it — the structure below is a way of presenting evidence, which is what that finding says actually counts.
One 2026 ATS guide names the recurring failure mode on data-engineering résumés: a pipeline architecture diagram rendered as an image, which the parser skips entirely. This roadmap's standard mandates a Mermaid architecture diagram and C4 diagrams on every project — correctly, for the README, where GitHub renders them natively. Ruling: diagrams live in the repo, never on the résumé. The résumé carries the text of the architecture (named components, deploy path, contracts) and links to the repo where the diagram renders. No change to the artifact standard; a constraint on where it is surfaced.
| Heading | What goes under it | What does not |
|---|---|---|
| ① Production | Where it runs and who depends on it · deploy path (Docker + CI) · monitoring and structured logging (per CORRECTION 16's observability layer) · reliability posture: success rate, freshness/SLA, retry and failure behaviour · blocking eval gates that must pass to merge. | "Built with FastAPI." A stack list is not a production claim. If nothing depends on it and nothing watches it, it is not in production — say so honestly and put it under Architecture instead. |
| ② Cost | What it costs to run and what changed: runtime deltas, warehouse/compute discipline, cost-per-query or per-run, manual hours removed, the mechanism that produced the saving (sizing, caching, partitioning, model routing, batching). | A number with no mechanism, and a saving with no reliability disclosure. Per the senior-reviewer guidance, a speedup or cost cut that hides a reliability regression is the bait-and-switch reviewers watch for — always state the SLA the change held to. |
| ③ Architecture | The existing artifact set, unchanged: Mermaid diagram · C4 Context (+ Container on leads) · docs/adr/ · contracts and tests · the decisions and their rejected alternatives. |
Diagrams presented without the decision behind them. The ADR is what turns a diagram into evidence of judgement. |
Everything else in the standard follows these three — eval-metrics table, 15–30s demo GIF, "What I Learned," Conventional Commit history. Order changes; content does not.
Formula: Action + What + Outcome + Proof, with the three senior components — a named metric against a baseline · the method · the scope. The test, from the same guidance: if a bullet cannot answer "so what?" quickly, it is not doing its job. Cap at 4–6 bullets per project; cut the rest.
Honesty discipline (binding, and it overrides the formula): use numbers only when they can be defended in an interview. Where a metric cannot be shared, substitute scale and reliability outcomes — tables, jobs, refresh cadence, incidents, users — which the guidance explicitly endorses as the alternative. Never invent a figure to fill the shape. A fabricated metric is a failed technical screen with extra steps.
DataVault is the hard case and the rule must be explicit. It is a live system inside an ERISA-regulated environment, and the existing standards already bind: synthetic data only in public repos; financial figures never recorded in public documents; neutral market-evidence language throughout. Correction 18 does not loosen any of that. Therefore, in the public README and on the résumé:
| Project | ① Production | ② Cost | ③ Architecture |
|---|---|---|---|
| DataVault / 1099 Platform lead flagship |
🟢 Strongest of the three projects. Live, depended-upon, regulated; reconciliation success rate, freshness, failure/retry behaviour, on-call reality. | 🟡 Deliberately constrained. Mechanism + non-identifying relative deltas + manual hours removed. No absolute figures — see the ERISA rule above. | 🟢 ADRs on ERISA-driven constraints (retention, auditability, reconciliation guarantees) · C4 L1+L2 · contracts and tests. |
| PolicyPulse | Containerised, deployed, monitored RAG/MCP service; blocking eval gates (RAG Triad, groundedness) as merge conditions. | 🟢 Best Cost story available. Cost-per-query and latency across inference substrates — this is exactly what the CORRECTION 17 substrate benchmark produces. Plus local-vs-cloud routing and token discipline. | GraphRAG design, retrieval-strategy ADRs with rejected alternatives, C4 L1+L2, FastMCP boundary. |
| Crucible | Paper→live execution path, kill switches, monitoring, reconciliation of intended vs filled. | Compute cost per backtest sweep, data-feed cost, sweep efficiency. | Multi-timeframe design, execution and risk-control ADRs. ⚠️ No P&L, no returns, no account figures — methodology and risk control only, per the standing rule. |
| FormSense · AFC supporting |
Lighter — deploy path and eval gates. | ⚪ Optional. Do not manufacture a Cost section where there is nothing to report. | Full ADR + C4 Context as already required. |
index.html, GitHub Profile README) at their next alignment pass, roadmap remaining source of truth.Ground truth, two lines. Since the Pro membership launched (Oct 2025), the DeepLearning.AI free tier is videos only — DeepLearning.AI's own help centre states free members have no access to assessments, certificates or additional tools, and that a Pro subscription is required to fully complete and access an Accomplishment and/or a certificate. Every DeepLearning.AI row in Stages 1–3 previously read FREE + ✅ Yes; all 20 rows are now corrected to FREE (videos) + ⚠️ Pro only. Coursera-hosted DeepLearning.AI rows (marked "Included") are unaffected — Coursera Plus covers those.
The certificate is the minor loss; the labs are the material one. Every row here was chosen for a hands-on outcome ("build an eval framework from scratch", code-alongs, "deploy an MCP server") — on the free tier that degrades to watching someone else build it.
✅ Ruling: Pro is rented monthly for two timeboxed lab sprints, never subscribed and never annual; a short-course Accomplishment stays a completion certificate (Udemy tier, never a Certifications line) and the Surviving Nine (+1 conditional) is unchanged. Cost: $0 committed (~$30 conditional; $0 for both sprints if the optional AMD free month covers Sprint 1). Detail in the four blocks below.
| Tier | Cost | What you get | Status in this roadmap |
|---|---|---|---|
| ① deeplearning.ai — Free | FREE | Course videos only, community forum, newsletters. No labs, no quizzes, no saved progress, no Accomplishment. | Adequate for concept exposure. Not adequate for any row whose "why" column claims a hands-on outcome. |
| ② DeepLearning.AI Pro (learn.deeplearning.ai) |
~$25–30/mo ⚠️ re-verify |
Interactive labs + quizzes in all courses, certificates of completion, save/resume work, hands-on projects, Professional Certificate tracks, 150+ programs. | ⏸️ CONDITIONAL, monthly only — never annual. Bought (or claimed free) as a timeboxed lab sprint, then cancelled. |
| ③ DeepLearning.AI on Coursera | Included | The Specializations and Professional Certificates (Deep Learning Spec, Data Engineering, PyTorch, RAG full course). Separate platform, separate billing from ②. | ✅ Unaffected. Covered by Coursera Plus. Pro does not grant Coursera certificates and Coursera Plus does not grant Pro labs. |
⚠️ Price flag: the $25/mo-annual / $30/mo-monthly figures come from a DeepLearning.AI course page; the help centre deliberately declines to publish a figure and points to the live membership page. Re-verify before paying — do not treat as settled.
A DeepLearning.AI short-course Accomplishment is a completion certificate — the same tier as Udemy and DataCamp under the existing rule, and it never appears under Certifications on a résumé or profile. The Surviving Nine (+1 conditional) is unchanged; nothing here joins it. Consistent with the <16% hiring-manager cert-weighting datapoint already recorded in CORRECTION 7, the reason to ever pay for Pro is the labs, not the badge.
File → Download per notebook, or download the whole workspace; several course notebook sets are also mirrored publicly under the https-deeplearning-ai GitHub organisation with a dependency file.| Stage | Rows whose labs carry the value | What the lab feeds | Verdict |
|---|---|---|---|
| S1 | Improving Accuracy of LLM Applications · Building & Evaluating Advanced RAG · MCP primer · AI Python for Beginners | The eval spine: hand-built accuracy score, deliberate hallucination injection, the RAG Triad (context relevance / groundedness / answer relevance) — these are the blocking eval gates PolicyPulse S1 ships with. MCP labs feed the FastMCP server. | 🔴 Highest lab dependency in the file. Videos alone do not produce a working eval harness. This is where the sprint belongs. 🆕 C58: the sprint runs in Q2 with PolicyPulse's RAG Triad build — the eval-harness build this row names. |
| S2 | Pre-processing Unstructured Data · Knowledge Graphs for RAG · Vector Databases · RAG Production-Ready | Embedding pipeline + vector store as data infrastructure (the AI-adjacent DE evidence in the S2 deliverables); messy-PDF extraction for FormSense and PolicyPulse ingestion; the Neo4j entry point ahead of GraphAcademy. | 🔴 High. All four are code-along by nature. Same sprint as S1 — the two stages' labs total roughly 12–15 hours. |
| S3 | Agentic AI (Ng) · Evaluating AI Agents · LangGraph ×2 · Document AI · Automated Testing for LLMOps · Fine-Tuning PEFT · vLLM | Agent design patterns and evaluator selection; CI/CD for LLM apps (CircleCI); PEFT/LoRA reps; serving, batching, KV-cache and quantisation behind the local-first inference claim. | 🟠 Medium — a second, separate month. Agentic AI is multi-week and the most lab-heavy single row in the roadmap. Logged as ~$30 conditional, one month, timed to the S3 build — not a rolling subscription. |
| S3 | MCP: Advanced Topics · Agent Skills · Claude Code (the Anthropic-origin rows) | Same material, first-party. | ✅ No Pro needed — route through Anthropic Academy, already present in these rows per CORRECTION 10: free, hands-on, and an official Anthropic completion certificate. Four rows drop out of the Pro dependency entirely. |
| — | AI Prompting for Everyone | Nothing load-bearing. | ⚪ Videos are sufficient. The row already records that prompt-engineering certs carry low hiring weight — do not spend a lab slot here. |
Status: ⏸️ OPTIONAL. Free tier only. Nothing here joins the Surviving Nine.
AMD's AI Developer Program is free and open-enrolment — anyone can join, nobody is selected. That is the decisive difference from AWS Community Builders, where selection is the credential: AMD membership carries no résumé signal and must not be listed as one. It is joined, if at all, for two perks:
Also available and deliberately not taken: AI Academy courses, a private Discord with AMD engineers, monthly office hours, GPU sweepstakes (no career weight), and ROCm Blogs external submission via GitHub under AMD editorial discretion — logged as a conditional S3 publication on-ramp only if AMD-specific results ever exist.
🚫 Declined — logged as evaluated, not selected: the AMD ROCm Certification Program (Associate launched 24 Jul 2026; Professional later 2026; Expert early 2027). Four reasons: (1) wrong layer — it tests ROCm/HIP kernel and memory optimisation, RCCL multi-GPU, vLLM/SGLang serving, Kubernetes + AMD AI Studio, i.e. GPU-infrastructure engineering, a neighbouring profession to this roadmap's DE/AE → Applied-AI → FDE arc; (2) no local practice loop — ROCm does not and will not run on Apple Silicon (Metal/MLX is a different architecture), so every hour is metered rented cloud, versus Ollama on the Mac Mini at $0 and unlimited; (3) no track record — days old at time of review, with no hiring, salary or posting-frequency data, which fails this file's own evidence rule; (4) no slot — adding it breaks "replace, not stack" with five exams already committed in S3. Market context: NVIDIA still holds ~86% of data-centre GPU revenue in 2026 and CUDA's ecosystem lock-in is unbroken, so ROCm depth is a bet on ecosystem growth, not a near-term hiring signal. Falsifier: revisit only if a target employer names ROCm or AMD Instinct in a posting.
Cost: $0 committed (~$30 conditional if Sprint 2 fires; $0 for both sprints if the AMD free month covers Sprint 1). Net effect on the cert canon: none.
Principle: replace, not stack. Keyword density is a negative signal in 2026; each credential below serves a specific, named purpose. Everything else from v9.2's 24+ list is archived.
| Cert | Cost | Track | Stage | Purpose | ✅ Passed |
|---|---|---|---|---|---|
| Azure AI Fundamentals (AI-901) | $99 🆕 C52 — was ~$165; Microsoft Fundamentals tier (US price; varies by region) | Personal | S1 | Cheapest first certification and the Stage 1 credential anchor — self-funded, like every credential in this plan. 🆕 C52 addendum — was "Cheapest first approval; proves the reimbursement path". AI-901 (replacing AI-900, retired 30 Jun 2026) now includes Microsoft Foundry model deployment / single-agent solutions and reading Python code that calls AI services — more hands-on than the old fundamentals exam. | ☐ |
| ⏸️ CONDITIONAL — AI Agent Builder Associate (AB-620) 🆕 CORRECTION 37 | ~$165 | Personal | S1–S2 (deferred) | MOVED FROM COMMITTED TO CONDITIONAL. AB-620 is the low-code Copilot Studio maker path; this portfolio's evidence standard is production Python — typed, tested, eval-gated, ADR-documented. A low-code credential does not evidence that, and PostCheck must never be rebuilt on a Copilot Studio canvas (that is an evidence downgrade, not enterprise realism). 🚦 Single activation trigger: a deliberate decision to specialize in the Microsoft ecosystem — e.g. the Q1 2027 apply list skews to Microsoft shops, or a target employer runs M365 Copilot / Power Platform as its primary agent surface. Until then the Azure-native credential is AI-103 (code-first Foundry), which remains committed. ⚠️ Note the original rationale — "strongest employer alignment" — was written against Daybright Financial's stack; that employment ended 9 Oct 2026, so the alignment argument no longer holds automatically. | ☐ |
| Fabric Data Engineer (DP-700) | ~$165 | Personal | S2 | ✅ Approved — employer-stack DE credential; internal evidence | ☐ |
| AWS Certified Data Engineer – Associate | $150 | Personal | S2 | ✅ Approved — external search coverage (AWS ~40% posting share) | ☐ |
| NVIDIA-Certified Associate: Generative AI LLMs (NCA-GENL) 🔄 RESTORED | $125 | Personal | S3 | ✅ Restored — recognized DL/GenAI verification (replaces discontinued TF cert); was erroneously dropped in the initial v10.0 cut | ☐ |
| Databricks Certified GenAI Engineer Associate | $200 | Personal | S3 | First production-GenAI cert; maps to RSA-style remote-normal routes. also reads as a DE cert — 2026 DE postings increasingly require RAG pipelines / vector DBs / LLM integration, so this doubles as a bridge credential for the "AI-focused DE" framing (kept in S3 for the Databricks hands-on requirement). | ☐ |
| Neo4j Certified Professional | FREE | Personal | S3 | GraphRAG credential backing PolicyPulse | ☐ |
| Azure AI Apps & Agents Developer Associate (AI-103) | ~$165 | Personal | S3 | Code-first Azure counterpart to CCA-F (Python + Foundry, agentic/RAG); on-ramp from the Azure stack to the Applied-AI target | ☐ |
| ⏸️ CONDITIONAL — Anthropic Claude certification: CCDV-F first, then CCA-F 🆕 CORRECTION 50 | $125 each | Personal | S3 (when the gate opens) | MOVED FROM COMMITTED TO CONDITIONAL. All four Claude exams — Associate, Developer, Architect-Foundations, Architect-Professional — require a work email from a Claude Partner Network organization, so none can be sat as a personal certification today. Trigger: you join (or your employer joins — free for any organization bringing Claude to market) the Claude Partner Network, or Anthropic opens public registration. Then: ① CCDV-F (Claude Certified Developer – Foundations — code-first: Claude API, tools, MCP; 53 Q · 120 min) as the builder credential; ② CCA-F / CCAR-F (Architect – Foundations, ~6 months of hands-on Claude experience recommended) after it — the natural pick when working at an Anthropic partner. Meanwhile the free Anthropic Academy course certificates are the Tier-4 evidence. Provider source-of-truth for the primary SDK; CCA-F $99 → $125 (Pearson VUE, 30 Jun 2026). | ☐ |
| dbt Analytics Engineering Certification | ~$200 | Personal | S2 | ⏸️ Conditional — take only if AE applications stall; the tested dbt project is the primary signal | ☐ |
Why this exists. The ranking below was already the operating logic of this file, but it was only ever stated in fragments — the mid-tier ruling in one note, "keyword density is a negative signal" in the preamble above, the <16% datapoint in Stage 2, the DataCamp and Udemy ratings in the stage tables, the Accomplishment ruling in CORRECTION 17. This table is an index over those rulings, not a replacement for them; every one of them stands where it is. Nothing is promoted, demoted, added or removed by this correction.
| Tier | What it is | Instances in this roadmap | What it is for | Evidence |
|---|---|---|---|---|
| 1 | Production evidence | DataVault / 1099 Platform · PolicyPulse · Crucible · PostCheck (+ FormSense, AFC), presented per Production / Cost / Architecture. | Winning the offer. This is what passes the technical screen. | 76% of hiring managers say portfolio work can outweigh formal education; a Fortune 500 manager reports hiring bootcamp grads who had built streaming platforms over certified candidates who could not write a basic SQL window function. |
| 2 | Accredited degree | Georgia Tech OMSCS — MSCS, Computing Systems. | Durability and portability. The only credential here that cannot be earned in a weekend — and the one immigration systems and foreign employers recognise, which matters to the Spain path. | The same MSCS as the on-campus degree ("O" is the delivery method, not the title); acceptance under 50% for Spring 2025 and tightening; 72% say degree level still matters, 65% say a master's justifies higher pay for the same role. |
| 3 | Proctored vendor exams | The Surviving Nine — now 7 committed + 3 conditional (CORRECTION 50) — the table above. | Clearing the filter, not winning. Gets the repo opened. Per the preamble: one relevant cert beats a stack of badges. | The engineers who move fastest show a recognised cert plus a portfolio with real pipeline code; certifications matter most for career changers proving baseline competence, after which portfolios and domain expertise outweigh them. |
| 4 | Coursera Professional Certificates & Specializations | IBM Generative AI Engineering (S1) · AWS Data Engineering (S2) · the Coursera-hosted DeepLearning.AI programs. Covered by Coursera Plus. | Structured curriculum + brand. The capstone is the deliverable; the PDF is not. | Explicitly: the capstone project provides portfolio material, which matters more than the certificate itself. Matches the existing mid-tier ruling recorded below this table. |
| 5 | Completion certificates | Udemy · DataCamp · DeepLearning.AI Accomplishments (per CORRECTION 17) · Anthropic Academy. | Skills / portfolio evidence only. Never a Certifications line on a résumé or profile. | Fewer than 16% of hiring managers or recruiters rank certifications among their top three résumé signals (HackerRank, recorded in CORRECTION 7). |
⚠️ Source-quality flag, per this file's evidence rule: the percentage figures above come from résumé-industry and career-content publishers, not peer-reviewed research — directional only. The load-bearing evidence is the practitioner material (hiring-manager accounts, the OMSCS admissions and workload reports) and the HackerRank datapoint already recorded in CORRECTION 7.
The operative consequence, stated once: Tiers 3–5 are filter-clearing instruments and nothing more. Only Tier 1 and Tier 2 are differentiators — and the scarcest asset in this file appears in neither column, because it is the regulated-finance domain edge sitting on the separate axis above.
Credential-hierarchy note: the IBM Generative AI Engineering Professional Certificate (Stage 1) and AWS Data Engineering Professional Certificate (Stage 2) are Coursera Professional Certificates — mid-tier resume credentials earned through coursework, tracked in the stage course tables above rather than this proctored-exam list.
Conditional platform-cert menu note (v10.0 Correction 3): beyond the committed set above, three employer-matched data-platform certs — dbt Analytics Engineering, SnowPro Core (COF-C03, $175), and Databricks DE Associate ($200) — sit in the Stage 2 certification table as a conditional menu: take at most ONE, and only when a concrete apply-list runs that stack. They are deliberately kept out of this committed canon to preserve "replace, not stack." GCP Professional Data Engineer (PDE) was evaluated and not selected — off-stack for the Azure-internal / AWS-external / fintech-FDE trajectory (GCP ≈ 1.2% of data postings; salary edge is a scarcity premium behind a longer, off-path search).
The ruling, stated once: books are Tier 5 on the credential ladder — skills evidence only, never a Certifications line. They earn their place only where a production-standard item has no learning source, which is the same test Core Course #17 (C4 + ADR) and #18 (pre-commit) already pass. Buy at stage entry, never upfront — the v9.2 archive committed to Designing Data-Intensive Applications at 1st edition (2017) and the 2nd shipped March 2026; a book bought ahead of when it is read is a book that goes stale before it is opened. Re-verify the edition at every purchase.
The aging principle governing every selection and every decline below: books split into three groups that age at different rates — foundations age best, system design ages moderately, framework and vendor books age fastest — and there is no agentic-AI canon yet, because the field moves faster than the publishing cycle. This is the book-layer analogue of this file's own badges ≠ credentials rule, and it is why every framework title in the declines is declined. ⚠️ Evidence-quality flag: much of the 2026 "best AI books" literature is affiliate-monetised roundup content. Selections below rest on convergence across independent sources plus a checkable mechanism (a named chapter, a named practitioner adoption, a primary vendor page) — never on a roundup alone. Total committed: six purchases across ~32 months. Fluent Python is already owned — $0. 🆕 CORRECTION 57: now eight committed titles (CORRECTION 51 added Jansen 3e; CORRECTION 57 adds Data Engineering Design Patterns). The Data Warehouse Toolkit is bought (Oct 2026). One upcoming-titles watchlist below — no spend.
| Tier | Book | Author / Edition | Why it earns a slot | ✅ Read |
|---|---|---|---|---|
| 🥇 PRIMARY | Robust Python | Patrick Viafore O'Reilly, 2021 |
The only book mapping 1:1 to the non-negotiable production standard. Typed Python, a dedicated chapter on customizing your typechecker (mypy configuration, inline vs. config file, CI integration), user-defined types via Enums/dataclasses/Protocols, extensibility, and a comprehensive testing strategy as a safety net. It fills a gap this file already documented: uv, structlog, stamina, pydantic-settings and pre-commit all carry "no course exists — docs only" rulings (CORRECTIONS 13, 16, 21). Selected on a checkable mechanism, not a roundup: the ZenML engineering team publicly credits it as the basis for adopting mypy across their codebase, and specifically names its chapter on introducing type hints to a legacy codebase — which is the 1099-pipeline retro-migration. Also Talk Python #332, the same editorial-vetting standard applied to the Molin pre-commit series. ⚠️ Currency caveat: 2021, so it predates PEP 695 generics and modern union syntax. Read it for the type-system reasoning; take syntax from the Python 3.14 docs. Same treatment as the Molin caveat in the CORRECTION 21 addendum — and the staleness is itself instructive. |
☐ |
| 🥇 PRIMARY | AI Engineering Building Applications with Foundation Models |
Chip Huyen O'Reilly, 2025 |
The eval spine — and the only v9.2 survivor, promoted. 🔄 Moved from the v9.2 Stage-4 slot to Stage 1 by ruling: this file makes evaluation literacy ⭐ the Stage 1 differentiator (39.6% of AI-first roles require it; ~5.5% of candidates list it) and PolicyPulse v1 ships with eval gates in Stage 1. A book that improves those gates in month 3 is worth more than the same book read in month 25, and it is foundations-tier, so it ages slowly enough to still serve S3. Consensus #1 across four independent 2026 shortlists and the most-read book on the O'Reilly platform since release. Decisive for this roadmap specifically: it is evaluation-first (open-ended evaluation, AI-as-a-judge) and framework-neutral — mental models that hold across providers — which matches both the eval-gate thesis and the no-framework-lock-in ruling. Carries forward as the S2 AI-adjacent reference and the S3 agentic reference; not re-bought at either stage. | ☐ |
| 🥈 SECONDARY | Python Testing with pytest | Brian Okken Pragmatic Bookshelf 2nd ed., 2022 |
Testing is load-bearing everywhere in v10.0 and had no learning source at all. The production standard runs on pytest: CI as the authoritative gate (CORRECTION 21), eval-first blocking gates, PostCheck's frozen 200-packet golden set, and the structlog.testing.capture_logs field assertions named in CORRECTION 16 §7. Robust Python has a testing section; this is the craft treatment — fixtures, parametrization, plugin design. Provenance is consistent with the existing standard: Okken hosts Test & Code and co-hosts Python Bytes — the same publication the CORRECTION 21 addendum already cites as one of four editorial vettings behind the Molin series. Reviewers who had used pytest for years report finding features they did not know. ⚠️ Two honest caveats: current edition is 2022 (pytest 7) — verify plugin and CLI details against current docs; and reviewers note it is close to "a more entertaining version of the pytest documentation" and not ambitious on test-driven design. It also does not cover property-based testing (Hypothesis). Read it for fixtures, parametrization and plugin design; take TDD philosophy elsewhere. |
☐ |
| 📖 REFERENCE OWNED — $0 |
Fluent Python | Luciano Ramalho O'Reilly, 2nd ed., 2022 |
Already in hand — enters as reference tier, consuming no purchase and no slot. Idiomatic Python depth (data model, protocols, concurrency, type hints in practice); 4.62 average across ~1,695 Goodreads ratings. Recorded explicitly so it is visible in the plan rather than invisible on a shelf. Because it is already owned there is no replace-not-stack conflict with the pytest secondary — nothing is being bought twice. Use it as a lookup reference against Robust Python's prescriptions, not as a cover-to-cover read; the 25 hrs/week budget belongs to the flagships. | ☐ |
| 🥇 PRIMARY — AFC-SCOPED 🆕 CORRECTION 51 |
Machine Learning for Trading (3rd ed. — retitled from Machine Learning for Algorithmic Trading) |
Stefan Jansen Packt, 3rd ed., 2026 |
The ML-for-trading reference for AFC's AI predictive layer — promoted from the CORRECTION 48 conditional upgrade to a committed buy. A ground-up rebuild (2026) organized as one research-to-live workflow, with nine case studies running through the book: leak-proof cross-validation, gradient boosting through transformers, RAG and causal inference, and MLOps with model monitoring — the closest match in print to AFC §5.7 and its Stage 3 LLM features. Free concept primers and MIT-licensed companion code (ml4trading.io, GitHub). Buy at AFC Stage-1 Phase 2 entry (buy-at-stage-entry rule, CORRECTION 34); the edition must be the 3rd; price re-verified at purchase — no figure asserted. Read for methodology, not marketing: the publisher's "alpha factory" framing does not change AFC's positioning — results stay lift over a base rate, never returns. Caveat: new release — few independent reader reviews yet; the 2nd edition's reputation is the evidence so far. Skip the RL/GNN chapters unless a project needs them. | ☐ |
| 📖 REFERENCE OWNED — $0 🆕 CORRECTION 48 |
Machine Learning for Algorithmic Trading | Stefan Jansen Packt, 2nd ed., 2020 |
🆕 CORRECTION 51: now the backup to the 3rd edition above (useful for the same chapters until the 3rd edition is bought). Already in hand — the finance-specific ML reference for AFC's AI predictive layer (CORRECTION 47), consuming no purchase and no slot. Read for AFC Stage-1 Phase 2: ch. 6 (the ML workflow; cross-validation challenges in finance — purging, embargoing and combinatorial CV), ch. 7 (logistic regression for classification), ch. 12 (gradient boosting with LightGBM/CatBoost, out-of-sample predictions, SHAP interpretation). Read for concepts; implement in AFC's own Python 3.14 stack — the 2020 code environment is dated. Edition note: a 3rd edition, retitled Machine Learning for Trading (Packt, 2026), is closer still to AFC (point-in-time SEC EDGAR pipelines, triple-barrier labels, BH-FDR, Polars, RAG over SEC filings, knowledge graphs) — ⏸️ conditional upgrade, not bought by this correction; its companion code (MIT) and free primers at ml4trading.io are usable without buying. Buy only if the 2nd edition plus the free primers leave a gap during AFC Phase 2 or Crucible S2. Evaluated and not selected: López de Prado, Advances in Financial Machine Learning (2018) — the owned Jansen ch. 6 covers purged CV; AFC §5.7 still cites it as the origin of meta-labeling. | ☐ |
| Tier | Book | Author / Edition | Why it earns a slot | ✅ Read |
|---|---|---|---|---|
| 🥇 PRIMARY | The Data Warehouse Toolkit The Definitive Guide to Dimensional Modeling |
Ralph Kimball & Margy Ross Wiley, 3rd ed., 2013 |
The AE core craft, and the highest-signal line in analytics-engineering JDs made teachable. Star schemas, conformed dimensions, slowly changing dimensions, and above all declaring the grain. Decisive evidence — dbt Labs' own dimensional-modeling guide teaches Kimball's four-step design process: select a business process → declare the grain → identify the dimensions → identify the facts. That is literally the ruling PostCheck already operates under (CORRECTION 33 §7: fct_document_reviews grain is one row per (packet, review run)), and the discipline DataVault's S2 marts depend on. No OMSCS overlap — Computing Systems does not teach dimensional modeling, so this is additive rather than substituted. Age is not a defect here: dimensional modeling is the closest thing data engineering has to a timeless skill, and it remains the pragmatic default precisely because it pairs naturally with dbt. ⚠️ Known critique (accept it, do not fight it): the book is organised by industry use case, so the core principles are spread across many chapters — a structural criticism raised repeatedly by reviewers. Read the early principles chapters plus the SCD material; do not read cover to cover. 🆕 CORRECTION 57 — ✅ OWNED (bought Oct 2026). Already in hand, so the buy-at-stage-entry rule no longer binds: read it alongside DataVault's dbt build (the CORRECTION 56 Stage-1 slice). Reading map, tied to the flagships: Ch 1–2 (primer + the technique catalog — keep as the lookup reference) · Ch 3 (the four-step process — declare the grain of DataVault's distributions fact) · Ch 4 (fact-table types: a periodic snapshot is the weekly corrections mart; an accumulating snapshot fits a distribution's lifecycle — received → IGO/NIGO → processed → 1099 issued — which is PostCheck's core) · Ch 7 + Ch 10 (Accounting; Financial Services — the industry chapters closest to recordkeeping) · Ch 19 (the 34 ETL subsystems — map each to a dbt test, snapshot or macro). Skip the telecom, transportation, education and healthcare chapters. |
☐ |
| ⏸️ CONDITIONAL | Designing Data-Intensive Applications (DDIA) | Martin Kleppmann & Chris Riccomini O'Reilly, 2nd ed., March 2026 |
🔴 Edition correction — the v9.2 archive committed to the 1st edition (2017). The 2nd edition shipped March 2026, with Chris Riccomini joining as coauthor. Any purchase must be 2e; the 1st edition is nine years old. Distributed systems, storage engines, consistency, batch vs. stream — and the standard system-design-interview reference. ⏸️ Held conditional on an anti-stack falsifier: OMSCS Computing Systems covers distributed systems directly, and this file's own rule is that OMSCS substitutes overlapping self-study ("replace, not stack" applies to study hours too). Buying it and then taking a graduate distributed-systems course pays twice for the same material. Triggers — buy on either: (a) the OMSCS distributed-systems course is not taken, or (b) the Q1 2027 apply window opens with a target employer's loop carrying a system-design round. Its value peaks at the apply window, not in Stage 2 study time. | ☐ |
| ⏸️ CONDITIONAL | Vector Databases | Nitin Borwankar O'Reilly, 2026 |
The AI-focused-DE half of this stage was audited and found already covered — this is the only credible book-layer addition, and it is deliberately not committed. The Stage 2 "AI-adjacent data" row (embedding pipelines, vector stores, unstructured-data ETL feeding RAG) is already served by three committed DeepLearning.AI rows flagged 🔴 S2-high in the CORRECTION 17 lab-dependency map — Pre-processing Unstructured Data · Knowledge Graphs for RAG · Vector Databases — plus AI Engineering carried forward from S1. A book here would stack on paid labs already budgeted, not fill a gap. This title runs from embedding theory through converting SQLite3 and PostgreSQL into vector databases and integrating them into RAG, which matches the pgvector-on-Postgres direction of the stack. ⚠️ Declined for now on this file's own evidence rule: published 2026 with no review history — the identical objection recorded against the AMD ROCm certification in CORRECTION 17 ("no track record; fails the evidence rule"). Trigger: only if the DL.AI Vector Databases lab leaves a demonstrated gap. | ☐ |
| ⏸️ CONDITIONAL | Python Polars: The Definitive Guide Transforming, Analyzing, and Visualizing Data |
Jeroen Janssens & Thijs Nieuwdorp O'Reilly, 1st ed., 2025 |
The learning slot for the CORRECTION 35 dataframe engine policy — and it lands here rather than in the course table because no Polars certification exists. Verified against the vendor: the Polars Academy is in-company B2B training only, and all four self-paced routes it endorses fail this file's own rulings (DataCamp → CORRECTION 4 · Udemy → CORRECTION 7 · Coursera Polars from Zero → a Rust course colliding with CORRECTION 22 · Xebia → €750, in person, NL). Passes the CORRECTION 34 test on a checkable mechanism, not a roundup: it is the title the vendor's own Academy names as the definitive guide, its foreword is by Ritchie Vink, the creator of Polars, both authors wrote it as colleagues at Xomnia — the company where Polars was created, and every example and dataset ships in a public GitHub repo, so the exercises are runnable rather than readable. Covers the eager, lazy and streaming APIs and is built around unlearning pandas habits, which is the actual failure mode. ⏸️ Why conditional: the free Polars User Guide is the primary source and the whole committed spend — buy the book only if the DataVault ingestion rewrite stalls on lazy plans, streaming or the expression model. ⚠️ Edition caveat (CORRECTION 34 §3): the 2025 1st edition predates the 1.24 streaming-engine GA — re-verify at purchase; a 2nd edition supersedes this row. ❌ Effective Polars (Matt Harrison) evaluated, not selected — self-published with no independent review history, the identical objection recorded against Vector Databases above. | ☐ |
| 🥈 SECONDARY 🆕 CORRECTION 57 |
Data Engineering Design Patterns Recipes for Solving the Most Common Data Engineering Problems |
Bartosz Konieczny O'Reilly, 2025 |
The production-reliability layer between the tool courses and the S2 gate — the one Stage 2 gap no committed source fills. Stage 2's courses teach tools (dbt, Airflow, Terraform, Snowflake); none gives a book-length, tool-agnostic treatment of why pipelines fail and the reusable fixes. This book's chapters are that layer: ingestion, error management, idempotency, data value, data flow, security, storage, data quality (Audit-Write-Audit-Publish, Constraints Enforcer, Schema Compatibility Enforcer) and observability (flow-interruption, lag and SLA-miss detectors, lineage). Checkable mechanism, not a roundup: those chapters map onto this file's own S2 standards — idempotent Airflow DAGs, data contracts, monitoring with a written postmortem — and onto DataVault's existing quarantine path (error management). They are also the vocabulary DE interview loops probe ("how do you make a backfill idempotent?"). No anti-stack conflict: DDIA (conditional, above) covers system internals, not pipeline patterns; the DE Professional Certificate covers the lifecycle, not a pattern catalog. ⚠️ Honest caveats: reader reviews are mixed (~3.4 on Goodreads — one practitioner review calls it the de facto reference handbook for the craft; another reader found it hard to tell who needs it); the author's own preface says it is not a good resource without commercial DE experience (he suggests about six months) — which is why it is timed to S2, after DataVault S1 and the live 1099 pipeline; and its examples lean on Spark / Kafka / Delta Lake, so read for the pattern and implement it in this stack (DuckDB + dbt now, Snowflake + Airflow in S2). Buy at Stage 2 entry (DataVault S2 hardening start, after the CORRECTION 54 soft trigger); price re-verified at purchase — no figure asserted. Read as a reference, not cover to cover: the idempotency, data-quality and observability chapters first. Falsifier: if DataVault's S2 orchestration and contract work reaches its midpoint without the book being opened, it was stacking — log it and add no further pattern books. | ☐ |
| ⏸️ CONDITIONAL 🆕 CORRECTION 57 |
Financial Data Engineering Design and Build Data-Driven Financial Products |
Tamer Khraisha O'Reilly, 2024 |
The domain-matched DE title — held conditional on the evidence rule. About 500 pages on the financial data domain: its structure and players, financial identifier and entity systems, financial data governance, the financial DE lifecycle, and pipelines built with open-source tools and APIs — written by a senior data engineer with more than a decade in the financial sector. It fits every finance-facing target in this file: Tier-1 retirement recordkeepers, the CORRECTION 55 bridge tier, Tier-3 capital-markets fintech, and the security-master / reference-data work under AFC and Crucible S2. No anti-stack conflict with Kimball: Kimball's Financial Services chapter is dimensional modeling; this is the domain data ecosystem around it. ⏸️ Why conditional, not committed: public review history is thin (a handful of Goodreads ratings) — the same evidence objection recorded against Vector Databases above. Triggers — buy on either: (a) bridge-tier or capital-markets screens probe identifiers, reference data or financial data governance; or (b) AFC / Crucible S2 security-master work stalls on identifier mapping. Read the publisher's sample chapter before buying. | ☐ |
| Tier | Book | Author / Edition | Why it earns a slot | ✅ Read |
|---|---|---|---|---|
| 🥇 PRIMARY | Fundamentals of Software Architecture A Modern Engineering Approach |
Mark Richards & Neal Ford O'Reilly, 2nd ed., 2025 |
This is the argument-hardest pick, and it is not the obvious one. CORRECTIONS 8 and 14 made ADRs and C4 non-negotiable in every repo — then sourced them from free web pages only, with no book-length treatment anywhere in the plan. This book closes that exactly: a dedicated ADR chapter (basic structure, worked example, storing ADRs, ADRs as documentation, ADRs for standards, ADRs on existing systems) and a diagramming chapter naming C4 explicitly alongside UML and ArchiMate. Provenance link that settles it: Neal Ford is also the author of the Architectural Katas series already named in CORRECTION 14 §5 as the architecture-defense rehearsal mechanism — so the book and the rehearsal method come from the same source. Its First Law — "everything in software architecture is a trade-off" — is precisely the script the FDE decomposition round tests, and the risk-storming and trade-off-analysis chapters are the decomposition drill in written form. 2nd edition (2025) is the one to buy; it also adds material on leveraging generative AI in architectural decisions. | ☐ |
| 🥈 SECONDARY | Hands-On Large Language Models | Jay Alammar & Maarten Grootendorst O'Reilly, 2024 |
The model-layer intuition behind the ML-literacy module. Embeddings, semantic search, text classification and generation, with Alammar's visual clarity. Selected because it is described by independent 2026 shortlists as the most approachable first technical book on how LLMs actually work, and — the operative reason here — one of the best ways to build a genuine mental model of how language models behave under different conditions, which matters when designing agents that must reason, plan and use tools consistently. That maps directly onto the module's "embeddings in depth" line and onto agent debugging on PolicyPulse and PostCheck. It is literacy-tier by design, which is the correct depth — the 14-month ML-Engineer stage was cut in v10.0 and is not being reintroduced through a book. | ☐ |
| ⏸️ OPTIONAL — AFC S3 🆕 CORRECTION 51 |
Generative AI for Trading and Asset Management | Ernest P. Chan & Hamlet Jesse Medina Ruiz Wiley, 2025 |
Domain companion for AFC's Stage 3 LLM-extracted filing features — how generative AI applies to trading and asset management, from a long-time ML-in-trading practitioner (Chan: Quantitative Trading, Machine Trading). Narrower than Jansen and complementary to it: Jansen covers the discriminative-ML workflow end to end; this covers the generative side. Optional: buy only when AFC Stage 3 begins and only if the LLM-feature work needs it; price re-verified at purchase. Not the empty agentic-AI slot below — it is a finance-domain book, so that slot and its M21 falsifier are unchanged. | ☐ |
| ⏸️ CONDITIONAL — AGENTIC SLOT 🆕 CORRECTION 53 |
Designing Multi-Agent Systems Principles, Patterns, and Implementation for AI Agents |
Victor Dibia Self-published, 2025 |
The first title found that passes this slot's own test — framework neutrality and independent review history. Framework-neutral by construction: it builds a complete agent library from scratch (picoagents) on the same ideas behind AutoGen, LangGraph and CrewAI, so the lessons survive framework churn. Maps directly onto Stage 3: orchestration patterns from deterministic workflows to autonomous coordination (Crucible's workflow-vs-agent line), trajectory-based evaluation (the Tool Correctness gate), MCP and A2A, and patterns for observability, interruptibility and trust (HITL). Author: Principal Research Software Engineer at Microsoft Research and core AutoGen maintainer. Reception: 4.89 average on Goodreads (19 ratings, 15 reviews); praised by Valliappa Lakshmanan (Generative AI Design Patterns, O'Reilly). Caveats: small review base; self-published after a Manning deal fell through; the author's own reading list ranks it first. ⏸️ Conditional — confirm at M21 (the slot's revisit point): re-check the review base, then buy at Stage 3 entry; price re-verified at purchase. Falsifier: if by M21 the review base has not grown, independent reviewers report material errors, or the companion code is abandoned, leave the slot empty. Evaluated, not selected: Albada, Building Applications with AI Agents (O'Reilly, 2025 — LangGraph/LangChain/AutoGen implementations; 3.63 average across 30 ratings); Gulli, Agentic Design Patterns (Springer, 2025 — LangChain/CrewAI/Google ADK code); Lakshmanan, Generative AI Design Patterns (broad GenAI patterns, overlapping Chip Huyen's AI Engineering already in Stage 1). | ☐ |
🚫 The Stage 3 slot beyond these two is deliberately left empty, with a falsifier. There is no agentic-AI canon — the field moves faster than the publishing cycle, and the honest 2026 position is that adjacent foundations and system-design titles outperform anything marketed as an agent book. Revisit at M21, and only if a title emerges with independent review history and framework neutrality. 🆕 CORRECTION 53: a candidate has emerged — Dibia, Designing Multi-Agent Systems (2025), is now held in the table above as ⏸️ conditional; the M21 revisit becomes a confirmation check rather than a search. The rule itself is unchanged.
The v9.2 archive carried book tables in all five retired stages. The archive itself is untouched and byte-identical — this is the disposition record, not an edit to it. Fourteen of fifteen entries do not survive the v10.0 restructure; one does, and is promoted above.
| v9.2 entry | Verdict | Reasoning |
|---|---|---|
| Python for Data Analysis (McKinney, 3rd ed.) | ⚠️ DEMOTED | Written for the Data Analyst target v10.0 cut. Teaches pandas — now table stakes — not the typed/production standard that is the actual differentiator. Useful as a pandas lookup on DataVault work; not a committed purchase. |
| Data Smart | ❌ RETIRED | Excel → analytics is the retired DA on-ramp, and the roadmap now runs Python-first from Stage 1. 🚨 Factual error in the archived row, recorded here for accuracy: v9.2 credits "Jordan Goldmeier, 1st Edition (2014)." The 1st edition is John W. Foreman (October 2013); Goldmeier authored the 2nd edition (2023). The row conflated the second-edition author with the first-edition year. Archive preserved verbatim; the correction lives here. |
| Python Crash Course (Matthes) | ❌ RETIRED | Beginner Python, fully redundant with CS50P + Python for Everybody + MITx 6.00.1x already committed in Stage 1. Textbook "replace, not stack." |
| Fundamentals of Data Engineering (Reis & Housley) | ⚠️ DEMOTED | 🚨 Anti-stack finding: Joe Reis is the instructor of the DeepLearning.AI Data Engineering Professional Certificate already committed as Stage 2 Core Course #4 (named and disambiguated in CORRECTION 20 §3). Same author, same lifecycle framework — buying the book pays twice for one body of work. No 2nd edition exists. Optional only. |
| Designing Data-Intensive Applications (Kleppmann) | 🔴 EDITION ERROR | v9.2 lists 1st ed. (2017). The 2nd edition shipped March 2026 (Kleppmann + Riccomini). Retained above as a ⏸️ conditional with an OMSCS anti-stack falsifier. This entry is the reason the buy-at-stage-entry rule exists. |
| Data Pipelines Pocket Reference (Densmore, 2021) | ❌ RETIRED | Pre-dbt-era and pre-Airflow-3. Superseded by the vendor-official Astronomer and dbt Learn tracks already in Stage 2. |
| Hands-On ML (Géron) · Intro to ML with Python (Müller & Guido) · The Hundred-Page ML Book (Burkov) | ❌ RETIRED | Correctly dead with the 14-month ML Engineer stage cut in v10.0. Not reintroduced; the ML-literacy module is served by Hands-On LLMs plus OMSCS electives. |
| Build a Large Language Model (From Scratch) (Raschka) | ⏸️ OPTIONAL DEPTH | Excellent and deeper than anything else on the model layer — it walks planning and coding every part of an LLM, dataset preparation and pretraining. That is deeper than literacy, and rebuilds the ML-Engineer depth v10.0 deliberately cut. Falsifier: a target employer requiring pretraining or model-development work. |
| AI Engineering (Huyen) | ✅ PROMOTED | The single survivor — moved from the v9.2 Stage-4 slot to Stage 1 as the eval spine. See the Stage 1 block above. |
| Generative AI with LangChain, 2nd ed. | ❌ RETIRED | Framework tier — ages fastest. Conflicts directly with the no-framework-lock-in ruling and with the CORRECTION 20 addendum's LangGraph-primary decision. |
| NLP with Transformers (Tunstall et al., 2022) | ⚠️ SUPERSEDED | Superseded by the Hugging Face LLM Course already consolidated into the active tables in CORRECTION 20 §5 — free, current, and carrying a chapter-level certificate. |
| Designing Machine Learning Systems (Huyen, 2022) | ⚠️ SUPERSEDED | Superseded for this trajectory by the same author's AI Engineering, which is the foundation-model-era successor. Do not buy both. |
| Staff Engineer (Larson) · The Staff Engineer's Path (Reilly) | ❌ RETIRED | Stage 5 was cut. Both are written for staff-level ICs operating inside an organisation — not for a career-changer's first external move. Falsifier: revisit only after landing and holding a senior IC role. |
❌ Evaluated during this pass and NOT selected — logged so the decision is re-checkable rather than silently absent:
ruff-check rename and the uv-lock hook). Recorded again here only so a future reader does not re-open it as a Stage 1 candidate. Decline stands.🔭 BOOK WATCHLIST — upcoming titles (🆕 CORRECTION 57) — not committed, no slot, no spend. Each is re-checked when it publishes and enters this list only through a future correction, after independent reviews exist (the evidence rule above).
Decision (July 2026, updated by Correction 2): OMSCS is retained, with the intended specialization switched from Machine Learning to Computing Systems — distributed systems, databases, operating systems, networks, and software architecture. Rationale: the roadmap's destination is Applied AI Engineer → FDE, which is a production engineering path, not a model-development path; deep model-training coursework duplicated a focus this roadmap deliberately cut, while Computing Systems coursework is precisely the "bridge AI modeling and production engineering" layer. Georgia Tech permits AI and Machine Learning electives inside the OMSCS program regardless of specialization — so 1–2 applied AI/ML courses are planned as free electives, keeping the applied-AI layer without re-adopting a model-training identity. The result: an accredited US Master of Science in Computer Science (≈$9.2K–$10.5K all-in for this profile — figure corrected at CORRECTION 44; OMSCS moved to residency-tiered pricing for students matriculating Fall 2025 or later, so an out-of-state South Carolina student pays $236/credit-hour (Fall 2026 rate) + $212 per term below 4 credits, not the flat ~$7K quoted in most write-ups) whose title clears engineer-role HR filters, at roughly one-seventh the cost of the closest content-fit alternative.
The problem this solves. OMSCS states no credit-hour prerequisite. What the committee asks of a non-CS applicant is objectively documented capability in programming, object-oriented design, data structures and algorithms — an Industrial Engineering degree from Honduras plus self-study does not, on its own, clear that bar. The cheapest instrument that produces graded US graduate transcript evidence is CU Boulder's own admission pathway, which simultaneously admits Manuel to a second accredited MS-CS. One spend, three outputs: admission evidence · a fallback degree already in progress · algorithms preparation for CS 6515.
| Course | Credits / Cost | Why this one | ✅ Done |
|---|---|---|---|
| CSCA 5414 — Dynamic Programming, Greedy Algorithms | 1 cr · $525 | DP and greedy are the exact core of CS 6515 (Graduate Algorithms), the hardest gate inside Computing Systems. Listed ~4 weeks @ 10 hrs/wk; 4.7★ / 277 reviews, 87% liked. | ☐ |
| CSCA 5424 — Approximation Algorithms & Linear Programming | 1 cr · $525 | LP + approximation — also CS 6515 syllabus material, and directly reusable in Crucible optimisation work. | ☐ |
| CSCA 5454 — Advanced Data Structures, RSA & Quantum Algorithms | 1 cr · $525 | Closes the "data structures" half of the OMSCS evidence bar with a graded transcript line. | ☐ |
Rules that make this work: a B or better in each of the three + a 3.00 cumulative GPA = automatic admission to the CU Boulder MS-CS, with no application, no transcripts, no recommendation letters, no TOEFL and no application fee; the credits count toward that degree's 15 required Breadth credits, so nothing is wasted if the fallback is taken. Courses can be previewed in the non-credit experience under the existing Coursera subscription before any tuition is paid; progress carries over on upgrade. Prep (not for credit, $0 under Coursera Plus): DTSA 5501 Algorithms for Searching, Sorting and Indexing and DTSA 5502 Trees and Graphs: Basics — reviewers consistently report the pathway assumes solid data-structures fluency. Finish CS50 weeks 7–10 first.
💳 How paying for credit actually works — and why it is NOT the ASU Universal Learner model (CORRECTION 44 addendum, September 2026)
At ASU ULC the grade comes first and the credit is bought afterwards. At CU Boulder the order is reversed: a course is not credit-bearing until CU tuition is paid in Buff Portal, and paying is what unlocks the restricted content — the honor-code / password quiz, the final exam or project and any proctored assessment — which is where the grade is produced. There is no "see the score, then buy the credit" option.
🧭 Standing procedure for every bridge course — non-credit first:
1. Run the course in non-credit mode under Coursera Plus ($0 marginal) through all ungraded lectures, quizzes and programming assignments; retry freely.
2. Upgrade only when the work reads as a B or better. Upgrading is allowed at any point in the enrollment window, including after the non-credit material is finished; auto-graded work carries over (discussion posts and peer-graded items may not).
3. If it does not read as a B, do not upgrade — repeat in a later session. Cost of a miss: subscription time only.
⏱️ Hard mechanics to plan around: six 8-week sessions per year · the enrollment window opens 2 weeks before classes start and closes 2 weeks before coursework is due · all for-credit work is due on the session's last day, with no extensions · tuition never rolls over to a later session · once paid, no Coursera subscription is needed for that course and proctoring is included.
↩️ Refund rule: full refund only if the drop is within 14 days of the class start or enrollment date (whichever is later) and no restricted content has been opened and no grade received — a clean drop leaves no transcript record. ⚠️ Opening the password quiz / honor-code verification ends refund and drop eligibility; a later withdrawal is a W with no refund. Do not open it until you intend to finish.
ℹ️ Admin note: creating the CU student account without enrolling for credit that term sets the status to discontinued. It is harmless and reversible (register and pay in a later session) — it is not a rejection.
⚠️ Object-oriented design is deliberately NOT bought here. The CU OOAD specialization (CSCA 5428/5438/5448) would add 3 credits / $1,575 for the OOD half of the evidence bar. Declined — CS50P (Stage 1 row 1️⃣3️⃣, free, Harvard) plus the live repos already evidence OOP, and the $1,575 belongs on flagship infrastructure. Falsifier: adopt it only if an OMSCS admissions reply names object-oriented design specifically as the missing item.
Effective with Fall 2027 admission, citizenship alone no longer satisfies Georgia Tech's English-language requirement — this rule is live for the 15 Aug 2027 application. It is satisfied by one of: a degree from an approved country · a degree where English was the language of instruction · an approved test score. A Spanish-medium Honduran degree clears none of the first two, so plan on TOEFL iBT ≥ 4.5 (new 1–6 scale) or IELTS Academic ≥ 7.0, official scores sent from the testing service (institution code 5248), valid within two years of the term start. Book it by ~May 2027. Note: a completed US post-secondary degree exempts permanently — CU pathway credits do not; only the finished CU degree would.
Computing Systems = 9 core + 9 specialization electives + 12 free electives. The plan below front-loads the Stage 2 job family (AE/DE) and back-loads the Stage 3 job family (Applied AI / FDE), matching the career sequence rather than the course catalog.
| Block | Course | Serves | ✅ Done |
|---|---|---|---|
| Core (9 cr) | CS 6400 — Database Systems Concepts & Design | 🅰️ AE/DE — dimensional + relational modeling behind DataVault; pairs with Kimball (CORRECTION 34 books layer). | ☐ |
| CS 6300 — Software Development Process | 🅰️ AE/DE — the production-engineering discipline the flagships already run on; also the AI-specialization escape hatch (see falsifier below). | ☐ | |
| CS 6515 — Introduction to Graduate Algorithms ⚠️ | Required by Computing Systems. The single highest-risk course in the degree — reviewers report retakes at 2–3 attempts and 12–25 hrs/week. The CU bridge exists partly to de-risk it; CS 8001 OLP (1-credit prep seminar) is the on-ramp. Take it alone in its term. | ☐ | |
| Specialization electives (9 cr) | CS 7210 — Distributed Computing | 🅰️ AE/DE — consistency, replication, failure modes; the layer that makes "production-grade" defensible in an architecture round. | ☐ |
| CS 6211 — System Design for Cloud Computing | 🅰️ AE/DE — cloud-native system design behind the Docker/ECS + orchestration layer. | ☐ | |
| CS 6310 — Software Architecture & Design (or CS 6422 — Database System Implementation) | 🅰️ AE/DE — ADR/C4 discipline formalised; CS 6422 swaps in if the DE lane wants storage-engine internals instead. | ☐ | |
| Free electives (12 cr) | CS 7643 — Deep Learning | 🅱️ Applied AI — the model-layer depth the Stage 3 ML-literacy module only skims. | ☐ |
| CS 7650 — Natural Language Processing | 🅱️ Applied AI — retrieval/eval foundations under PolicyPulse. | ☐ | |
| CS 7646 — Machine Learning for Trading | 🅱️ Applied AI / finance lane — already designated above; $0 marginal, lighter workload, pairs with a heavy systems course. | ☐ | |
| CS 6601 — Artificial Intelligence (or CS 6422 if not taken above) | 🅱️ Applied AI — search, planning, probabilistic reasoning; the classical-AI floor under agentic work. | ☐ |
Two OMSCS rules that constrain the sequence: admission is conditional until two designated foundational courses are passed with a B or better within 12 months of matriculation (confirm the asterisked list at registration — CS 6400 and CS 6300 are the natural pair here), and a B or better is required in every specialization course (C is only tolerated in free electives). Load: one course per term, three terms a year → Spring 2028 → ~2030–31. This sits beyond the Stage 3 horizon by design; the degree is Tier 2 (durability and portability, incl. the Spain path), never the thing that wins the Q1 2027 offer.
| Program | Cost | Format | Assessment |
|---|---|---|---|
| Duke MEng in AI for Product Innovation (AIPI) | ~$63K–$74K | 24-month part-time online for working professionals | Best curriculum fit of the three — applied AI with real engineering pipelines, an ML Engineer track covering MLOps and production deployment with data engineering/cloud electives, corporate-partner capstone, and reported 100% placement within 6 months at a $118K median. Disqualified on cost at current compensation: ~7x the OMS programs for content the roadmap largely builds anyway (target roles are portfolio-driven). Revisit only with substantial employer funding or scholarship. |
| Georgia Tech OMS Analytics (OMSA) | <$10K | Fully online, 2–3 years part-time, 36 credits | Respected and affordable; the 6-credit applied practicum can be executed as a project at the current employer (attractive for the Stage 1 elevation). Not selected because it is an analytics/data-science credential — the lane this roadmap deliberately exited — and ~half the interdisciplinary core (business analytics, visual analytics, OR) overlaps 15 years of existing business-data experience. Remains an analytics-lane fallback, but is displaced as the primary fallback by CU Boulder MS-CS (CORRECTION 44), which is CS-titled and needs no admissions committee. |
| CU Boulder MS-CS on Coursera 🆕 ADOPTED — bridge + fallback (CORRECTION 44) | $525/cr · $15,750 full degree · bridge alone $1,575 | 100% online, 8-week sessions ×6/yr, pay-as-you-go, take a session off without penalty; ~2.5 yrs at 2 courses/session | Not a competitor to OMSCS — an instrument in front of it. Performance-based admission (3 pathway courses at B or better) supplies the graded US transcript evidence OMSCS asks of non-CS applicants, and admits Manuel to a real MS-CS as a hedge. Recognised: HLC-accredited, identical diploma and transcript to the on-campus degree with no "online"/"Coursera" designation; U.S. News 2026 places CU Boulder CS at #30 nationally (#14 among publics). Honest limits: brand is a clear tier below Georgia Tech outside Colorado; DE depth is thin — Software Architecture for Big Data was demoted from Breadth/pathway to elective in the 2024-25 catalog (the older "big-data breadth track" advice is stale), Big Data Challenges & NoSQL is still "in development", and 15 of 30 credits are fixed Breadth (both pathways + ML + Ethics + Autonomous Systems), ~6 of which serve neither target role. If the fallback is taken, the elective 15 go to: Software Architecture for Big Data · Data Mining · Generative AI · Object-Oriented Analysis & Design · NLP (or up to 6 credits of outside electives from the MS-DS/MS-EE catalogs). |
| CU Boulder MS-AI on Coursera | $525/cr · $15,750 | Same platform, cadence and PBA model; pathways are ML: Theory & Hands-On Practice or Foundations of Probability & Statistics | Evaluated, not selected. It optimises for the job family this roadmap reaches second (Stage 3) and under-serves the one it reaches first (AE/DE, Stage 2), and its AI content is reachable as electives from inside the MS-CS anyway. Falsifier: revisit only if the Stage 2 external move is skipped entirely and the first external role is Applied AI. |
this track is no longer an employer benefit. Every exam on it is paid personally. The section below is preserved verbatim for changelog integrity; read every "reimbursed" and "reimbursable" in it as superseded — self-funded. Verified list prices (USD, exam fee only): AI-901 $99 · AB-620 $165 · DP-700 $165 · AI-103 $165 · DP-750 $165 (optional lakehouse slot). Microsoft prices on two tiers — $99 Fundamentals, $165 Associate/Expert/Specialty. The sequencing rationale in the section below still holds; only the funding assumption is retired. The internal-elevation rationale in the closing sentence is superseded by CORRECTION 22.
Carried forward from v9.x as an official section. Sequence: AI-901 → AB-620 → DP-700, all reimbursable through the Financial Industry Professional Education Program. Anchor study course: ZTM Azure Bootcamp (Foundry workflows & agents). Microsoft Agent Framework (MAF) remains flagged for employer-ecosystem integrations — addendum (flag upgraded on verified July-2026 research): Microsoft merged AutoGen and Semantic Kernel into MAF, which reached v1.0 general availability in April 2026 and is now positioned as the default agent framework for.NET/Azure-native enterprises — i.e., Daybright's exact stack. Ruling: ⏸️ WATCHLIST, not a course — AI-103 already carries the Azure agentic credential, the roadmap's framework primary stays LangGraph (regulated-industry default) with the Anthropic-native SDK backbone (which itself passed AutoGen on enterprise production-deployment count in early-2026 telemetry), and MAF is docs-learnable in days if needed. Trigger: adopt MAF (official Microsoft Learn docs, no paid course) only if a Stage 1 internal build is explicitly requested on the Microsoft-idiomatic path, or the scope-change conversation with Jen lands on.NET/Azure-native agent work. Same one-framework discipline as the platform-cert menu. This track is the engine of the Stage 1 internal-elevation strategy: every cert doubles as evidence in the scope-change conversation.
Maps the employer's Financial Industry Professional Education Program (effective 1 July 2026) onto this roadmap. The program reimburses exam fees and study materials for approved certifications (first two attempts) and pays a credentialing bonus on completion, subject to written manager pre-approval in advance of any spend.
The governing judgement: this program is designed to deepen retirement, benefits and advisory expertise. Nearly every credential on its schedule reinforces the lane this roadmap is deliberately exiting, and several of the largest bonuses sit on the least relevant credentials. Bonus size is not a strategy. The discipline below is the same "replace, not stack" rule applied everywhere else: take the one credential that makes an existing strength externally verifiable, and decline the rest on the record.
| Credential | Status | Rationale | ✅ Done |
|---|---|---|---|
| RPF Retirement Plan Fundamentals (ASPPA) |
✅ ADOPTED — the single employer-funded domain credential | Six online modules; the course and assessments are open-book, untimed, with unlimited attempts; approximately 30–50 hours of study; refreshed by ASPPA in April 2026. Near-zero failure risk and a bounded time cost. Its value here is not the credential itself but what it converts: the ERISA claim moves from "I worked in this domain" to a verifiable foundational credential in it — strengthening precisely the discovery-and-decomposition story the FDE track is built on. It is also the vocabulary layer beneath PolicyPulse's corpus, FormSense's forms, and DataVault's Box-7 derivation logic — material already being modelled in software. Finally, it is the prerequisite gate for the rest of the ASPPA ladder, so it preserves optionality without committing to any of it. | ☐ |
| SIE Securities Industry Essentials (FINRA) |
🟡 Case-by-case reimbursement ask | Not on the approved schedule, but the program provides a review route for unlisted certifications. The argument is structural: SIE is the mandatory foundational half of the Series 7, which is on the approved schedule — a Series 7 is SIE plus a specialised "top-off" exam. Cost is $100, so the ask is low-stakes either way. Cross-referenced in the Finance-Domain Optionality block. ⚠️ Unverified: whether the employer or an affiliate is a FINRA member firm able to sponsor Series 6/7 at all — those exams require a member firm to file a Form U4. SIE itself requires no sponsorship, so it remains available regardless. | ☐ |
| QKA Qualified 401(k) Administrator (ASPPA) |
⏸️ DEFERRED — revisit only post-M8 | The bonus value is real, but so is the cost: 18 topical courses divided into two packages of nine, each with a practice test and a proctored final exam, against an ~11-week suggested study schedule; the QKA-1 package alone is $835. Two reasons to defer. First, it lands squarely in the window when DataVault's S2 must ship — the evidence gate for the Months 12–14 apply window — and 25 hrs/week does not absorb both. Second, QKA signals "career TPA administrator," which works against the transition narrative rather than for it. Eligibility also runs through RPF regardless: the credential requires either three years of plan-administration experience or the RPF certificate. Revisit only if the Month-8 internal elevation succeeds and the tenure horizon extends. | ☐ |
| 🆕 CEBS Certified Employee Benefit Specialist (IFEBP · Wharton) — and its RPA sub-designation |
⏸️ CONDITIONAL — Month-8 decision point Reclassified out of the declined set |
Why this is not in the row below. CFA, CAIA and CIMA are gated behind work-experience requirements that this background plausibly cannot satisfy. CEBS has no work experience requirement at all — it is coursework and exams only. The employer's $1,000 bonus is therefore genuinely reachable, which is a material difference from every other "upon attaining designation" line on the schedule. Structure: five self-paced courses, no electives, each with a 100-question exam requiring 70% to pass (pass/fail only, no score reported); four computer-based testing windows per year. The curriculum is developed by the Wharton School of the University of Pennsylvania and administered by IFEBP — a partnership spanning over 45 years, which is the only line on this schedule besides the actuarial track that clears the roadmap's "university credentials win on rigor" test. Designed for completion within three years, with no time limit and no cap on courses per year. 🆕 The recommended form is RPA, not full CEBS. The five courses split into a health track (GBA 1, GBA 2), a retirement track (RPA 1, RPA 2) and a bridge (GBA/RPA 3, Strategic Benefits Management). RPA 1 and RPA 2 are the working domain directly — retirement plan qualification requirements, DC/DB plans, ESOPs, IRAs, small-employer plans, SECURE 2.0 — the same material DataVault, PolicyPulse and FormSense already model in software. GBA 1 and GBA 2 are group health, dental, disability and the U.S. health care system: not this domain, and roughly 60% of the full program. Taking RPA alone (3 courses) yields a real, listable designation at ~85% domain relevance instead of ~40%, at roughly $2,235+ instead of ~$3,725+, over ~1–1.5 years instead of ~3 — and every course still counts toward CEBS if it is ever completed later. Zero waste, and the option stays open. Cost basis (U.S., per course): exam $495 (includes two attempts, 120-day access window) · study guide $250 (print + online) · textbook varies · optional instructor-led online study group $240. Third-party estimates put full CEBS at roughly $4,000 all-in including materials and testing. ⚠️ IFEBP states pricing may change at any time and the final figure depends on supplementary materials — treat these as planning numbers, not quotes. ⚠️ Reimbursement gap: the employer schedule lists CEBS but not RPA. RPA would be a case-by-case ask — with a strong argument, since the three RPA courses are a literal subset of the five-course CEBS curriculum already approved. Put it in writing. Decision rule: not now. Revisit at Month 8 alongside QKA, and only if the internal elevation succeeds and the tenure horizon extends. Full CEBS is justified only in the scenario this roadmap is explicitly designed to avoid — benefits becoming the permanent domain. |
☐ |
| CFA · CFP · CAIA · CIMA · actuarial track (EA1/EA2/A4/MSPA/FSPA) | ❌ DECLINED — evaluated, not selected | 🆕 Corrected figure: an earlier draft of this row stated CFA was "three levels at roughly 900 hours each." That was wrong by roughly 3×. CFA Institute recommends approximately 300 hours per level — so ~900–1,000 total, and realistically 1,000–1,150 for a career-changer from a non-finance background (Level II candidates typically report 350–400 hours). The conclusion is unchanged; the number is now accurate. 🆕 The decisive objection is structural, not the hours. Read the employer schedule's payout language: RPF, QKA and the actuarial exams pay "per exam passed"; the Series exams and AIF/CRC/CPFA pay "upon passing." CFA, CAIA and CIMA pay only "upon attaining designation" — and each gates that designation behind a work-experience requirement. CFA's is the hardest: qualified hours must be directly related to the investment decision-making process, or produce a work product that informs it. Retirement plan administration is operations and compliance — compliance testing, distributions and recordkeeping do not inform anyone's investment decisions, and neither does a data-engineering role. The realistic outcome is ~1,000 hours and several thousand dollars spent, followed by an unreachable charter and a bonus that never pays. CAIA (professional experience + membership) and CIMA (executive education at a Registered Education Provider, two background checks, and three years of verified relevant experience, at a total cost of roughly $5,000–$9,000) carry the same structural risk. Practitioner evidence: asked directly by a CS graduate working at a hedge fund, respondents were blunt — one hiring-side reply stated they never check whether a candidate holds a CFA because they are a hedge fund rather than an investment bank, and that mathematics, statistics, algorithms and track record are what matter; a charterholder told the same person to spend the time learning to code better instead. CFP, CAIA and CIMA are advisory, alternatives and investment-management credentials respectively — none intersects an engineering trajectory. The actuarial track is a multi-year mathematics path toward a different profession entirely. ⚠️ Falsifier to watch: large asset managers do weight the CFA culturally — one practitioner noted that large asset managers look for it while proprietary trading shops do not. If the Stage 3 apply list ever shifts toward asset managers (BlackRock / Fidelity / Vanguard, all of which hire data engineers at scale), CFA Level I alone becomes worth reconsidering. It earns $0 from the employer schedule, since that bonus requires the full charter. Logged so the decision is on the record rather than silently re-litigated each time the bonus schedule is read. |
— |
| Series 65 (and Series 63) | ➖ Noted, not pursued | Recorded only because they share SIE's sponsorship-free property and carry a bonus. They are state securities-law and investment-adviser-law exams; the engineering-relevance is low. Documented so the option is visible if a target employer ever names one. | — |
⚠️ Open item — resolve in writing before enrolling in anything. The employer's schedule lists "Retirement Plan Fundamentals (RPF-1, RPF-2)" with a bonus stated per exam passed. That is the superseded two-exam structure; the current ASPPA course is a single six-module certificate. The bonus mapping onto the current structure is therefore unconfirmed, and the spread between plausible readings is material. Obtain a written determination from the program administrator before enrolment — the program's own pre-approval requirement makes this the natural moment to ask, and pre-approval is mandatory for reimbursement in any case.
🆕 The ladder fork — pick one, they do not stack with each other. The two domain credentials above come from different bodies running different ladders, and the employer funds both. Choosing one is choosing a ladder:
| Ladder | Path | Reads best to | Signal |
|---|---|---|---|
| ASPPA | RPF → QKA → QKC → QPA → CPC | TPAs, recordkeepers, plan administrators | Industry-native depth. QKA is the standard credential for the work being done now — precise for the current seat |
| IFEBP / Wharton | RPA (or GBA) → CEBS | Consultancies, brokers, insurers, enterprise benefits buyers | Breadth plus a recognised academic brand. More portable outside the TPA world |
The wrinkle worth noticing: the Stage 3 apply list is weighted toward consultancy-delivered FDE-in-fintech — Deloitte, Accenture, PwC financial services. That audience recognises Wharton/CEBS more readily than ASPPA/QKA. So the IFEBP ladder arguably has better external portability toward where this roadmap is actually heading, even though the ASPPA ladder is more precise for where the seat is today. Neither is free; both cost hours that DataVault S2 has a prior claim on.
✅ Sequencing decision — unchanged: RPF first, and only RPF. At roughly 30–50 hours, open-book, untimed and with unlimited attempts, it is an order of magnitude cheaper in hours than anything else on this page, it sits on the bonus schedule, and it is the prerequisite gate for the ASPPA ladder regardless. It front-loads the verifiable-domain benefit at close to zero cost and commits to nothing. The ladder itself is not chosen until Month 8, when the outcome of the internal elevation is known: if elevation succeeds and tenure extends, RPA is the better second move than QKA because it points outward; if the fallback trigger fires, stop at RPF and route every remaining hour into DataVault S2.
Relationship to the cert canon: nothing in this section joins the Surviving Nine (+1 conditional). This is a separate, employer-funded domain lane running parallel to the technical canon — it does not expand it, and the "take ONE, never stack" discipline applies here as strictly as anywhere else.
| Milestone | Approx. timing | Market band (base unless noted) |
|---|---|---|
| Internal AI Builder (current employer) | M8 | Current comp maintained; scope change + reimbursed certs (no reset) |
| Data Engineer (first external move) | M18–20 | $95K–$130K entry (starting-salary surveys run $127K+ mid-market) |
| Analytics Engineer (alternate first move) | M18–20 | $90K–$130K entry; $125K–$195K mid-band (median ~$158K); more remote-accessible |
| Applied AI Engineer | ~M30 | $130K–$200K TC; medians ~$185K+ |
| FDE track | M32+ | Posted bands cluster $150K–$217K base; frontier-lab TC far higher (equity-weighted ceiling, not floor) |
Note: all figures are market bands from the companion analysis and July 2026 re-verification — no personal compensation data is recorded in this document. Salary data lags; re-check bands before negotiating.
Everything below this line is ARCHIVED v9.2 content, preserved unmodified for reference and changelog integrity. It is not the official plan. Superseded elements include: the 5-stage structure, the external Data Analyst exit, the 14-month ML Engineer stage, the "Remote Global Track" framing, the 24+ certification target, the 8-flagship portfolio, the Upwork income bridge, ROI/marketing projections, and the local-first-only thesis (corrected to privacy-routed). Where archived month numbers, salary claims, or market assertions conflict with the v10.0 sections above, v10.0 governs.
Source: Cross-checked against 365 Data Science 2026 AI Engineer postings analysis, StackOne 120+ Agentic Tools 2026 report, MCP 2026 ecosystem (97M+ monthly SDK downloads), and DeepLearning.AI evaluation guidance. All v8.2 standards remain intact — these are additive enhancements.
Role Brand Decision (confirmed May 2026): Dual positioning preserved — "GenAI-Powered Data Analyst OR Junior AI Engineer." Skill development leans engineering-first within the dual frame.
This roadmap positions you as an AI Engineer from DAY 1—not a traditional Data Analyst who learns AI "later":
Market Reality 2026: While 90%+ of candidates learn "prompt engineering," YOU'LL BUILD production AI systems, deploy local LLMs, and architect agentic workflows. Finance companies desperately need professionals who can implement AI without cloud dependencies—that's YOU.
| Total Timeline | Weekly Hours | Investment | Freelance Revenue | Net ROI |
|---|---|---|---|---|
| 37 months (5 stages) |
25 hours/week (M-F: 4:30-6am + 8-10pm | Sat: 5-8:30am + 8-10pm | Sun: 7:30-9:30pm) |
$1,400-1,900 (Coursera + Platforms + Books) |
$8K-20K | 15,000%+ |
| Stage | Timeline | Role | Key AI Focus |
|---|---|---|---|
| Stage 1 | Months 1-5 | GenAI-First Data Analyst & AI Engineer | IBM GenAI Engineering: Build, deploy, fine-tune LLMs! |
| Stage 2 | Months 6-15 | GenAI Data Engineer + AI Systems Architect | Vector DBs, RAG infrastructure, embedding pipelines for AI |
| Stage 3 | Months 16-29 | ML Engineer + Local LLM Specialist | Ollama, QLoRA fine-tuning, on-premise AI for finance |
| Stage 4 | Months 30-34 | Agentic AI Engineer & LLM Specialist | LangGraph, multi-agent systems, autonomous workflows |
| Stage 5 | Months 35-37 | Senior LLM Engineer | Job Search + System Design + Portfolio Optimization |
| Day | Time Blocks | Daily Hours | Focus |
|---|---|---|---|
| Monday - Friday | 4:30 AM - 6:00 AM 8:00 PM - 10:00 PM |
3.5 hrs/day (1.5 + 2) |
Morning: Courses/Videos Evening: Practice + Projects |
| Saturday | 5:00 AM - 8:30 AM 8:00 PM - 10:00 PM |
5.5 hrs | Deep work: Projects, Portfolio, Trading practice |
| Sunday | 7:30 PM - 9:30 PM | 2 hrs | Week review, Community engagement, Planning next week |
| TOTAL | - | 25 hrs/week | M-F: 17.5 hrs | Sat: 5.5 hrs | Sun: 2 hrs |
💡 Pro Tips:
🎯 The thesis: a deliberate hybrid stack — frontier cloud capability for scale, paired with a private, on-device local-first layer for privacy, cost, and control. The local-first group is the differentiator most candidates don't have; the cloud group keeps me current with frontier models. Together they mirror real production LLM-Ops: provider-agnostic, privacy-routed, no vendor lock-in.
Badge legend: S1–S5 = stages where the tool is actively used; S? = not emphasized in that stage. Deep-dive rationale lives in each stage's tools section (full breakdown in Stage 1).
| Tool | Cost | Role in the Journey | Active Stages |
|---|---|---|---|
| OpenCode Agentic coding agent (in Cursor) |
FREE | Spec-driven, gated agentic development with provider-agnostic model-routing | S1S2S3S4S5 |
| Ollama Local inference engine |
FREE | Private, zero-cost on-device LLM runtime (Qwen3.5); peaks at the Stage 3 Local-LLM-Specialist phase | S1S2S3S4S5 |
| LM Studio GUI runtime + MLX engine |
FREE | Interactive local chat & model benchmarking (Apple MLX) — heaviest while establishing/tuning local inference | S1S2S3S4S5 |
| AnythingLLM Self-hosted AI workspace |
FREE | Private RAG + project/workspace management; routes to local (Ollama) or pay-as-you-go (OpenRouter) | S1S2S3S4S5 |
| Tool | Cost | Role in the Journey | Active Stages |
|---|---|---|---|
| Cursor AI IDE ⭐ Primary editor |
$20/mo | Primary editor for all coding; Agentic harness to produce codebase while allowing human-gate revision, and hosts the OpenCode agents | S1S2S3S4S5 |
| VS Code Secondary editor · portable baseline |
FREE | Industry-standard editor and the base Cursor is built on — VS Code skills transfer directly. Jupyter/.ipynb work, integrated debugger, Git, Dev Containers; the vendor-neutral, interview-relevant editor competency (plain VS Code + Copilot is the common shop standard) |
S1S2S3S4S5 |
| Claude Pro + Anthropic SDK Daily AI pair + primary build SDK |
$20/mo (+ PAYG API) |
Primary reasoning/pair-programming partner and agentic coding; building with the Anthropic SDK (anthropic) as the projects' primary provider and the anchor of the model-routing fallback chain |
S1S2S3S4S5 |
| OpenRouter Multi-model gateway |
Pay-as-you-go | One key to many frontier models (MiniMax M3, GLM-5.2, …) for heavy builds and fallbacks — no per-vendor lock-in | S1S2S3S4S5 |
| OpenAI (ChatGPT + Codex + SDK) Secondary cloud chat, coding agent + build SDK |
$20/mo (+ PAYG API) |
General-purpose chat (ChatGPT), the Codex coding agent, and building with the OpenAI SDK (openai) in projects — used on select projects; ChatGPT is also required for the Stage 1 Vanderbilt GenAI course. Adds OpenAI to the model-routing fallback chain. |
S1S2S3S4S5 |
| Google AI Studio + Gemini SDK Prototyping playground + build SDK |
FREE TIER (PAYG above) |
Rapid prompt prototyping in AI Studio; building with the Gemini SDK (google-genai) in projects — reinforces provider-agnostic, multi-SDK fluency and adds Gemini to the model-routing fallback chain |
S1S2S3S4S5 |
🛠️ Editor skill note: Cursor is the daily driver, but VS Code fluency is an explicit, portable skill — debugging, extensions, the .ipynb/notebook workflow, Git integration, and Dev Containers. Because Cursor is a VS Code fork, this competency transfers to any team (many standardize on plain VS Code + Copilot) and is the interview-safe baseline.
Major Strategic Shift (2026): Instead of learning AI "later", you're becoming an AI-FIRST Data Analyst from Month 1!
The Game-Changing Move: IBM Generative AI Engineering (Months 3-5)
Moving the **IBM GenAI Engineering Professional Certificate** from Stage 2 → Stage 1 transforms your career trajectory from *"Analyst who learns AI later"* to *"AI Engineer who knows Analytics."*
Why This Positioning Wins in 2026:
Your Interview Story: "I'm a Data Analyst who builds AI-powered solutions. I can do everything a standard DA does—SQL queries, Python analysis, visualizations—PLUS I build chatbot interfaces using LLM SDKs (Gemini, OpenAI, Claude) and LangChain. I've also fine-tuned LLMs for financial analysis using RAG architecture. This combination of traditional DA skills and production AI engineering makes me uniquely valuable."
Key Insight: You're not "just learning to prompt AI"—you're learning to BUILD AI TOOLS. The IBM cert teaches RAG, fine-tuning, LangChain, deployment. You'll be a BUILDER, not just a USER.
| Order | Course Name | Platform | Cost | Certificate? | Duration | Why This Course |
|---|---|---|---|---|---|---|
| 1️⃣ | CS50: Introduction to Computer Science | edX/Harvard | FREE | ✅ Yes ($90 optional) | 11 weeks | CS fundamentals you already started! Algorithms, data structures, problem-solving - strong foundation before specializing in data |
| 2️⃣ | Python for Everybody Specialization | Coursera | Included | ✅ Yes | 8 weeks | Dr. Chuck's legendary course, perfect for beginners, focus on data-relevant Python |
| 3️⃣ | Google Data Analytics Professional Certificate | Coursera | Included | ✅ Yes | 6 months (self-paced) | Industry-recognized, covers SQL, R, Tableau, data cleaning - CRITICAL for analyst roles |
| 4️⃣ | IBM Data Analyst Professional Certificate | Coursera | Included | ✅ Yes | 3-4 months (11 courses) | COMPREHENSIVE DA TRAINING! 11 courses: Excel, Python, SQL, Pandas, Data Viz, Capstone Project + Interview Prep. Python-focused depth to complement Google's broad coverage. Professional Certificate = strong resume credential! |
| 5️⃣ | Mode Analytics SQL Tutorial | Mode | FREE | ❌ No | 2-3 weeks | Most important skill for analyst - SQL is in 80% of job postings! |
| 6️⃣ | Statistics with Python Specialization (University of Michigan) | Coursera | Included | ✅ Yes | 3 months (8-10 weeks focused) | PYTHON-BASED STATISTICS! 3 courses: (1) Understanding & Visualizing Data, (2) Inferential Analysis, (3) Fitting Statistical Models. Hypothesis testing, confidence intervals, regression - all with Python. University of Michigan certificate! |
| 7️⃣ | 🆕🤖 AI Python for Beginners (Andrew Ng) | DeepLearning.AI | FREE | ✅ Yes | 4-6 hours | PYTHON FOR LLM CONTROL! Taught by Andrew Ng (2024). Unlike generic Python courses, this teaches you Python SPECIFICALLY to control LLMs—variables, lists, loops taught in the context of prompting & API calls. Perfect bridge between Python basics and GenAI engineering. Take alongside Python for Everybody! |
| 8️⃣ | 🆕🤖 30 Days of Streamlit Challenge | Streamlit | FREE | ❌ No | 2-3 weeks (self-paced) | BUILD AI UIs FAST! Official Streamlit challenge. Master the #1 framework for deploying GenAI apps with web interfaces. You'll need this for IBM GenAI cert capstone AND every future AI project. Complements IBM cert's dry theory with hands-on UI skills! |
| 9️⃣ | 🆕🤖 Building with the Claude API (Anthropic Academy) | Anthropic Academy | FREE | ✅ Yes (official) | 8+ hours | PROVIDER SOURCE-OF-TRUTH FOR THE CLAUDE SDK! 84 lessons on integrating Claude into production apps — structured outputs, tool use, prompt caching. Underwrites every Anthropic-SDK project (DataVault, PolicyPulse, ODI, AFC, Crucible). Official LinkedIn certificate from the model-maker. Replaces the dated OpenAI-only SDK courses (archived below). |
| 🔟 | 🆕🤖 Improving Accuracy of LLM Applications (DeepLearning.AI) | DeepLearning.AI | FREE | ✅ Yes | 1-2 hours | BUILD AN EVAL FRAMEWORK FROM SCRATCH! Develop an evaluation score, deliberately simulate hallucinations, and systematically raise accuracy. Mirrors the AFC eval-first perturbation methodology — sits alongside Building & Evaluating Advanced RAG as your evaluation backbone. |
| 1️⃣1️⃣ | 🆕🤖 AI Prompting for Everyone (Andrew Ng) | DeepLearning.AI | FREE | ✅ Yes | 1-2 hours | MODERN PROMPTING (2026 REFRESH). Replaces the 2023 ChatGPT Prompt Engineering course (archived below). Current prompting across today's models — finding info, thought-partnering, working with code. Note: prompt-engineering certs carry low hiring weight — treat as a quick refresh, not a priority. |
| 1️⃣2️⃣ | 🆕🤖 Building & Evaluating Advanced RAG (DeepLearning.AI) | DeepLearning.AI | FREE | ✅ Yes | 1 hour | EVALUATION-DRIVEN DEVELOPMENT! Learn the RAG Triad: Context Relevance, Groundedness, Answer Relevance. Apply directly to PolicyPulse project using TruLens/DeepEval. Shows recruiters you MEASURE AI quality, not just build it. THE #1 differentiator for 2026 AI portfolios! |
| 1️⃣3️⃣ | 🆕🤖🔌 MCP: Build Rich-Context AI Apps with Anthropic (PRIMER) | DeepLearning.AI | FREE | ✅ Yes | 1-2 hours | 🆕 v8.9 — PULLED FORWARD AS A PRIMER. Taught by Anthropic's Elie Schoppik. Take this before building PolicyPulse's FastMCP server (you learn the protocol before you first build against it, rather than after). Covers MCP client-server architecture, building/deploying servers, and connecting to local files / GitHub / Google Docs. This is the lightweight first pass — the full Stage 4 deep-dive (same course, expanded use in the agentic capstone) remains in place. Also primes the Month 14 TypeScript + MCP server sprint. 🆕 v9.0: also the on-ramp for the Anthropic Claude Certified Architect (CCA-F) — start the free Anthropic Academy prep courses now; the exam itself is deferred to Stage 4. |
| 1️⃣4️⃣ | 🆕 Docker for Beginners with Hands-on Labs (KodeKloud) | Coursera | Included | ✅ Yes | 6 hours (1 week) | CONTAINERIZATION INTRO! Learn Dockerfile, Docker Compose, container basics with in-browser labs. Add a Dockerfile to at least 1 portfolio project. 60%+ of AI/ML job postings require Docker — quick win for Junior AI Engineer applications! |
| 1️⃣5️⃣ | 🤖 Generative AI Data Analyst Specialization (Vanderbilt) | Coursera | Included | ✅ Yes | 4-6 weeks | OPTIONAL - Analyst-Focused AI Workflows: Dr. Jules White teaches ChatGPT+SQL integration, AI-guided data exploration. Good for analyst workflows. HOWEVER: The IBM GenAI Engineering cert below is MORE IMPORTANT for building AI systems. Do Vanderbilt only if you have extra time after IBM cert. Requires ChatGPT Plus ($20/mo) |
These were active Stage 1 courses, now superseded by newer material (added above). Retained here for the record — not part of the active plan.
| Course Name (archived) | Platform | Why archived | Replaced by |
|---|---|---|---|
| ChatGPT Prompt Engineering for Developers | DeepLearning.AI | 2023 / GPT-3.5, OpenAI-only — dated | AI Prompting for Everyone (active above) |
| Building Systems with the ChatGPT API | DeepLearning.AI | 2023, OpenAI-only — dated | IBM GenAI Engineering cert + Building with the Claude API (active above) |
| LangChain for LLM Application Development | DeepLearning.AI | LangChain API churn — superseded | Newer LangGraph / agent courses already in Stage 4 |
🔗 OFFICIAL PROGRAM: IBM Generative AI Engineering Professional Certificate on Coursera
📊 Program Overview: 16 courses | ~6 months (self-paced, compress to 3 months) | 111,000+ enrolled | 4.7★ rating (3,615 reviews)
💰 Cost: Included with Coursera Plus ($59/month) or individual course pricing
Traditional Path: Learn basic DA skills → Wait 6-10 months → Learn AI in Stage 2 → Competitive for entry DA roles
NEW "AI-First" Path: Learn DA basics (2 months) → BUILD AI SYSTEMS (3 months) → Competitive for JUNIOR AI ENGINEER roles immediately!
The Difference: Moving IBM GenAI Engineering to Stage 1 means you're not "an analyst who prompts ChatGPT"—you're someone who can BUILD, DEPLOY, and FINE-TUNE AI applications. Only 5-10% of DA candidates can do this!
🎯 Foundation Block (Courses 1-6):
📊 Data & ML Block (Courses 7-9):
🤖 Advanced LLM Block (Courses 10-14):
🏗️ RAG & Capstone Block (Courses 15-16):
💡 Accelerated Learning Strategy (Compress 6 months → 3 months):
IBM Official Capstone (Course 16):
Your Enhanced Version: "FinanceGPT Assistant"
💡 Why This Combination Wins: IBM cert proves you can build production AI systems with RAG + LangChain. Your trading background + finance domain = unique expertise. Only 5-10% of candidates have Finance + AI Engineering + Trading knowledge!
| Course Name | Platform | Cost | Certificate? | Duration | Why This Course |
|---|
| Platform | Cost | Weekly Target | Purpose |
|---|---|---|---|
| HackerRank SQL | FREE | 5-7 challenges/week | SQL practice - MOST IMPORTANT! Get SQL certificate for LinkedIn |
| HackerRank Python | FREE | 3-4 challenges/week | Python practice, get certificate for LinkedIn/Upwork |
| Kaggle Learn | FREE | 1 micro-course/week | Python, Pandas, Data Viz courses + get certificates to showcase |
| SQLZoo | FREE | 2-3 exercises/day | Interactive SQL practice, builds muscle memory |
| StrataScratch | FREE | 2 problems/week | Real data analyst interview questions from FAANG companies |
💡 Why AI Tools Matter: These tools accelerate your learning by 2x and position you as a GenAI-powered analyst. They're investments that pay for themselves in productivity!
| Tool | Cost | When to Start | Why Essential |
|---|---|---|---|
| Cursor AI IDE ⭐ PRIMARY EDITOR |
$20/month | Month 1 (Day 1!) |
GAME-CHANGER FOR LEARNING! • Composer mode: Build entire Streamlit apps from description • Multi-file understanding: See how projects connect • @Docs: Learn correct syntax as you code • 150ms latency vs VS Code 300ms For 25 hrs/week learner, 2x speed = $20 well spent! |
| VS Code Secondary for Notebooks |
FREE | Month 1 (Keep installed) |
JUPYTER NOTEBOOK WORK: • Better for data exploration notebooks • Industry standard (important for interviews) • Use for quick Pandas exploration sessions • Hybrid: Cursor for projects, VS Code for notebooks |
| ChatGPT Plus ⭐ Required for Vanderbilt Course |
$20/month | Month 2 (When starting Vanderbilt) |
PROFESSIONAL AI TOOL: • Required for Vanderbilt GenAI DA course • Advanced Data Analysis (Code Interpreter) • Upload datasets, get instant visualizations • Daily tool for GenAI-powered analysis work Cancel after course OR keep for productivity! |
Total AI Tools Cost: $160 for Stage 1
ROI: These tools make you 2x faster AND position you as GenAI-powered analyst = higher starting salary!
💡 Why This Impresses Recruiters: The paid cloud tools above accelerate learning; this stack proves you can architect and run AI systems without cloud dependency — on-device inference, private data handling, and explicit model-routing. For regulated finance employers (where participant data cannot leave the building), an engineer who already runs a local, privacy-first LLM stack is a rare, high-signal hire. This is the practical proof behind the roadmap's "deploy AI without cloud dependencies" thesis — not a slogan, a running system.
| Tool | Role in My Stack | Cost | Why It's a Differentiator |
|---|---|---|---|
| OpenCode ⭐ Agentic coding agent (in Cursor + terminal) OPEN SOURCE |
Spec-driven, gated agentic development — runs inside Cursor IDE | FREE (pay only for chosen API) |
PRODUCTION AGENTIC WORKFLOW. Custom agents (plan / build / docs-sync / eval-guardian / security-auditor), slash-commands, and a provider-agnostic model-routing layer: local Qwen3.5 (Ollama) for private planning, cloud (MiniMax M3 / GLM-5.2 via OpenRouter) for heavy builds. Permission gates enforce manual-commit discipline and additive-only edits — recruiter-visible proof of disciplined, no-"vibe-coding" engineering. |
| Ollama Local inference engine ON-DEVICE |
Private, zero-cost LLM runtime (Qwen3.5 9B, custom 16K-context Modelfile) | FREE | DATA NEVER LEAVES THE MACHINE. Apple-Silicon Metal acceleration; powers OpenCode's private planning and any finance/proprietary work. Demonstrates the privacy-routing principle the roadmap is built on — sensitive data → local, public research → cloud. Directly underpins the Crucible & AFC local-first AI analysts. |
| LM Studio GUI runtime + MLX engine ON-DEVICE |
Interactive local chat & model benchmarking (Apple MLX) | FREE | APPLE-SILICON-NATIVE INFERENCE. Runs MLX-optimized models (e.g. Qwen3.5 9B 4-bit) for faster on-device chat, with an OpenAI-compatible server and per-model tuning. Used as a benchmarking bench to A/B local engines (MLX vs GGUF) — evidence of measured, evaluation-first tooling decisions rather than hype-following. |
| AnythingLLM Self-hosted AI workspace SELF-HOSTED |
Private RAG + project/workspace management; routes to local or pay-as-you-go models | FREE (self-hosted) |
OWN THE INTERFACE AND THE DATA. A self-hosted workspace that unifies local (Ollama) and pay-as-you-go (OpenRouter) models under one private app — chat, document RAG, and project management without handing documents to a vendor's cloud UI. Shows end-to-end ownership of a private knowledge stack, not just API consumption. |
| oMLX ⏸️ OPTIONAL — benchmark only (C61) OPEN SOURCE |
MLX inference server (macOS menu bar) with an SSD-tiered KV cache — candidate backend for long agentic-coding sessions | FREE (~2 hrs, timeboxed) |
MEASURE BEFORE ADOPTING. Ollama's MLX engine needs 32 GB+ and falls back to llama.cpp Metal on 16 GB, so on this hardware oMLX and LM Studio are the only MLX paths. Its one unique feature is a prompt cache that survives restarts (a vendor benchmark on an 18 GB M3 Pro: ~0.6 s vs ~77 s first-turn latency after restart; ~28 vs ~23 tok/s). Against it: an independent test saw memory climb and one freeze, ~8 GB of usable model memory on 16 GB, Mac-only (not a Docker/CI runtime).📝 Benchmark protocol & falsifier — click to expandRun oMLX vs Ollama vs LM Studio on Qwen3.5-9B 4-bit with one long, repeated Claude Code session; record tok/s, peak memory and post-restart first-token latency; write it up as a README note. Adopt as the agentic-coding backend only if it wins on post-restart latency with no memory-pressure or freeze event; otherwise log the result and stop. Ollama stays the primary runtime (cross-platform, Docker/CI, what the flagships and employers use); LM Studio stays the MLX bench. Re-check if Ollama lowers its MLX memory floor below 32 GB. |
Cloud / paid services remain in the stack (Claude Pro, OpenRouter credits, Cursor, course-required ChatGPT) — this local-first toolchain complements them, giving a defensible hybrid: cloud for scale and frontier capability, local for privacy, cost, and control.
💡 Strategy: Use these platforms to REINFORCE Coursera learning with hands-on practice and build portfolio-quality projects that get you hired!
| Platform | Cost | When to Use | Specific Activities & Goals |
|---|---|---|---|
| FreeCodeCamp | FREE | Weeks 3-20 (After Python/SQL basics) |
COMPLETE: • "JavaScript Algorithms and Data Structures" - Critical for technical interviews! (100 hrs) • "Data Visualization" - Python D3.js projects for portfolio (300 hrs) • Build 5 certification projects for GitHub Time: 4-6 hrs/week (evenings 9-10pm) Output: FreeCodeCamp certificates + 5 polished portfolio projects |
| DataCamp ⭐ Highest Value Here |
$25/month ($125 total for 5 months) |
Day 1 - Month 5 (Parallel with Coursera) |
COMPLETE TRACKS: • "Data Analyst with Python" track (41 hrs) • "SQL Fundamentals" track (21 hrs) • "Data Manipulation with pandas" course (16 hrs) • "Data Visualization with Python" (7 hrs) How to Use: • Mornings (4:30-6am): Coursera videos • Evenings (8-9pm): DataCamp interactive exercises Time: 8-10 hrs/week Why: Interactive coding environment accelerates Python/SQL fluency faster than videos alone! Cancel After: Month 5 (once job-ready) |
| Zero to Mastery | $39/month or $279/year |
Month 4-5 (Interview prep phase) |
START COURSES: • "Complete Machine Learning & Data Science Bootcamp" - Modern portfolio projects (40 hrs) • "Master the Coding Interview: Data Structures + Algorithms" - Start DS&A prep for future (20 hrs in Stage 1) Time: 6-8 hrs/week (Saturday deep work) Output: 1 capstone project that feels "hirable" Why: ZTM projects are more modern/professional than typical Coursera projects - employers notice! |
💰 Stage 1 Platform Investment: DataCamp $125 (5 months) + ZTM $78 (2 months) = $203 total
📌 Credential note (ZTM = evidence, not credential): Zero to Mastery here is skills & project evidence — hands-on practice and portfolio material — not a resume credential. ZTM issues certificates of completion (non-accredited), which carry no recruiter/ATS recognition. Your verifiable credentials come from Coursera (IBM/Google), DeepLearning.AI, and proctored certification exams. On your resume/LinkedIn, list ZTM as skills demonstrated / projects built — never under certifications.
💡 Strategy: Each project introduces new capabilities that build on the previous — creating a clear skills progression narrative that recruiters can follow. 5 projects (PolicyPulse, FormSense, StreamSmart, AFC, Crucible) evolve through the career stages! The portfolio carries two flagships: AFC (read-only small-cap swing research) and Crucible (autonomous intraday execution, the chosen first build).
| # | Project Name | Timeline | Skills Demonstrated | New Skills Introduced | Where to Showcase |
|---|---|---|---|---|---|
| 1 | 1099 Reconciliation ETL Pipeline ✅ LIVE PRODUCTION 🛠️ v8.2 RETRO-MIGRATION |
Deployed | Python, pandas, openpyxl, Matplotlib, data cleaning, ETL pipeline design, synthetic data generation | ETL pipelines, pytest, CI/CD (GitHub Actions), production deployment 🆕 v8.3 Migration Task: Retrofit to v8.2 standards — replace requirements.txt with pyproject.toml ([project.optional-dependencies] dev), add py.typed PEP 561 marker, add Dockerfile, update README install instructions. ~4-6 hour task. Recruiters often click the deployed-production repo first; consistency with v8.2 across all repos is the signal. |
• GitHub w/ README • LinkedIn featured • $15K/yr savings |
| 2 | DataVault Analyst ⭐ First AI Project |
4 weeks | Natural language analytics for retirement plan data with PII protection, AI guardrails, and code transparency | + LLM SDK (Gemini/OpenAI/Claude), PandasAI, Streamlit, Pydantic structured outputs, PII handling, AI observability | • GitHub w/ GIF demo • Streamlit Cloud • LinkedIn post |
| 3 | PolicyPulse 🧠 RAG Foundation 🔄 EVOLVES 5 STAGES 🔌 MCP SERVER |
4 weeks | RAG chatbot answering HR policy questions with cited sources, confidence scoring, and auto-escalation to HR. Exposes retrieval as a FastMCP server — Cursor and Claude Desktop can query the HR knowledge base directly via MCP. | + Embeddings, ChromaDB vector store, RAG pipeline, semantic search, ticket escalation system, Anthropic SDK as primary provider (Claude excels at RAG synthesis with prompt caching), FastMCP server (~50 LOC) exposing retrieval tools 🆕 Stage 2/3 upgrade path: evolve to a GraphRAG hybrid (Neo4j knowledge graph + ChromaDB vectors) for multi-hop policy questions where vector-only retrieval stitches the wrong chunks together — a documented fix for multi-hop hallucination that strengthens groundedness. |
• GitHub w/ GIF demo • Streamlit Cloud • Blog post • MCP server demo |
| 4 | FormSense 📄 Document Intelligence 🔄 EVOLVES 5 STAGES |
5 weeks | Multimodal AI reading handwritten distribution forms, validating against ERISA business rules, routing complete → ticket / incomplete → email | + Multimodal AI (Gemini Vision), form extraction, business rule validation, email automation | • GitHub w/ GIF demo • Streamlit Cloud • Demo video |
| 5 | Operations-Demand-Intelligence 📊 Enterprise Analytics |
6 weeks | Analyzing 8+ months of real OnBase workflow data for staffing decisions, capacity planning, and demand patterns | + Enterprise real data integration, advanced analytics, stakeholder reporting, Plotly | • GitHub w/ README • Streamlit Cloud • Case study |
| 6 | StreamSmart Optimizer 📺 Consumer AI App 🔄 EVOLVES 5 STAGES |
6 weeks | AI-powered streaming subscription rotation advisor with cost-per-view analytics, content search via live APIs, and savings tracking | + External API integration (Watchmode/TMDB), httpx async, consumer UX, optimization algorithms | • GitHub w/ GIF demo • Streamlit Cloud • Product Hunt |
| 7 | Attention-Flow Catalyst 🚀 FLAGSHIP — Research System 🔄 EVOLVES 5 STAGES 🤖 ANTHROPIC PRIMARY |
10 weeks (Phase 1A + 1B) |
Defensible research system: walk-forward backtesting, survivorship bias controls, SEC Form 4 + Wikipedia + news triggers (incl. T6 squeeze-context: short-interest / float / days-to-cover), Parquet lakehouse, AI-powered dashboard. Anthropic SDK as primary provider — Claude's reasoning quality matters most for financial analysis (elevated faithfulness threshold of 0.9). | + DuckDB lakehouse, Parquet, httpx async, edgartools (SEC), multi-source alternative data, statistical methodology, bootstrap CI, Anthropic SDK (Claude) as primary; Gemini fallback | • GitHub w/ GIF demo • Streamlit Cloud • Blog series • Demo video |
| 8 | Crucible 🔥 FLAGSHIP — Autonomous Intraday Trading Research Platform 🔄 EVOLVES via PHASES 🦙 LOCAL-FIRST (Qwen3/Ollama) ▶️ STARTED FIRST |
Phase 1 (~10-14 weeks) |
Strategy-agnostic intraday research-to-execution platform: an AI-assisted research loop where an LLM proposes strategy improvements that are proved by deterministic backtests behind a sealed out-of-sample vault. Strategies are plugins (IT-1 ORB + VWAP Reclaim ship first to prove the abstraction). Phase 1 (backtest engine) begins now in Stage 1; the autonomous paper-trading and live agentic phases mature across Stages 3–4. Distinct from AFC: AFC = illiquid sub-$5 swing research (read-only); Crucible = liquid intraday execution (autonomous). Local-first AI (Qwen3 via Ollama; Gemini → Anthropic → OpenAI fallback). | + Own event-driven backtest harness, deterministic strategy plugins (Protocol+ABC+registry), walk-forward CV + sealed OOS vault + overfitting budget ledger, Optuna optimization, local LLM (Qwen3/Ollama), NautilusTrader (Phase 2–3), Alpaca + Schwab/TOS execution adapters, LangGraph multi-agent oversight | • GitHub w/ GIF demo • Architecture docs • Engine-parity report • Blog series |
🔥 Two Flagships, Two Different Hard Problems: The portfolio now carries two flagship-tier systems, deliberately distinct so they demonstrate range rather than redundancy. Attention-Flow Catalyst (AFC) is a read-only research system hunting predictive triggers in illiquid small-caps on a swing (multi-day) timeframe. Crucible is an autonomous execution platform that takes liquid intraday strategies from backtest → paper → live through validation gates. Shared ~70% engineering spine (point-in-time data, lakehouse, walk-forward backtest, bias controls, evaluation, Docker/CI, agents) — different universes, different timeframes, different purposes. Crucible is the chosen first build because its Phase 1 backtest engine is squarely Stage 1–2 skill and produces the highest-rigor portfolio artifact.
💡 Why This Matters: These projects aren't "done and forgotten" — they evolve with your skills through the career stages. This demonstrates architectural thinking, long-term system design, and the ability to progressively enhance production systems. Recruiters see a candidate who can grow systems, not just build throw-away demos. Note: Crucible evolves through its own build phases (backtest → paper → live) which map onto the career stages — Phase 1 in Stage 1, the agentic paper/live phases maturing across Stages 3–4.
| Project | Stage 1 Data Analyst |
Stage 2 Data Engineer |
Stage 3 ML Engineer |
Stage 4 LLM Specialist |
Stage 5 Senior LLM |
|---|---|---|---|---|---|
| 🧠 PolicyPulse | RAG chatbot + ChromaDB + Streamlit + ticket escalation | AWS S3 doc storage, PostgreSQL ticket tracking, scheduled re-ingestion | Fine-tuned embedding model for HR domain, re-ranking model | LangGraph orchestration, Pinecone vector DB, multi-agent, voice interface | Production SaaS: multi-tenant, RBAC, Slack/Teams, LLMOps evaluation |
| 📄 FormSense | Multimodal extraction + validation + email/ticket routing | AWS S3 form storage, SQS queue, PostgreSQL, batch processing | Custom extraction model, form classification (distribution vs loan vs rollover) | Multi-agent (Extractor + Validator + Router), MCP integration, form history RAG | OnBase integration, real-time processing, multi-form-type, LLMOps benchmarks |
| 📺 StreamSmart | Advisory dashboard + AI rotation planner + content search | AWS deployment, PostgreSQL, Airflow price monitoring, vector DB for content | ML viewing prediction, churn models, collaborative filtering recommendations | LangGraph agents for cancel/resubscribe, MCP tool integration, full automation | Production SaaS, LLMOps evaluation, monetization, mobile app, user accounts |
| 🚀 AFC (Flagship) | Backtest engine + AI dashboard (Phase 1A + 1B) | AWS S3, Airflow orchestration, 500+ tickers at scale | XGBoost, LSTM, MLflow model tracking | RAG + multi-agent trading system, voice interface | Production deployment, monetization ($2-50K/mo potential) |
| 🔥 Crucible (Flagship) autonomous intraday |
Phase 1: own backtest harness + AI research loop + sealed OOS vault (IT-1 ORB + VWAP Reclaim plugins) | Migrate to NautilusTrader; engine-parity gate; more strategy plugins; data lakehouse at scale | Phase 2: autonomous paper-trading agent crew (LangGraph); local LLM (Qwen3/Ollama) analyst; paper-vs-backtest parity | Phase 3 begins: live micro-sizing on Alpaca + Schwab/TOS; multi-agent oversight (regime → risk → journalist → fund-manager) | Hardened autonomous live execution, full observability, reconciliation, monetization potential |
⚡ Stage 1 Projects at a Glance:
| Month | Learning Focus | Building/Doing | Career Actions |
|---|---|---|---|
| Month 1 | • Python basics (10 hrs/week) • SQL fundamentals (10 hrs/week) • Excel advanced (5 hrs/week) |
• HackerRank SQL daily • Small Python scripts • Anonymize bookkeeping data for projects |
• Set up GitHub • Draft LinkedIn data analyst profile • Research 20 target companies |
| Month 2 | • Pandas deep dive (8 hrs/week) • Data visualization (5 hrs/week) • Statistics basics (6 hrs/week) • Tableau/Power BI (6 hrs/week) |
• Build Project #1 • Launch Upwork profile • Start Kaggle competitions |
• Complete Google Data Analytics cert • Add certificates to LinkedIn • Apply to 2-3 Upwork gigs • Network with 10 analysts on LinkedIn |
| Month 3 | • Advanced SQL (joins, CTEs, window functions) • Time series analysis • Data cleaning techniques • Business metrics & KPIs |
• Build Project #2 • Get first Upwork client • Practice mock interviews |
• START APPLYING TO JOBS! • Target: 15-20 applications/week • Roles: Junior Analyst, Data Analyst, Business Analyst • Tailor resume for each |
| Month 4 | • Tableau/Power BI advanced • A/B testing concepts • Data storytelling • Interview prep (SQL + Python) |
• Build Project #3 • Complete 2-3 Kaggle notebooks • Create case study presentations |
• Apply: 20-25/week • Practice interviews • Get Upwork testimonials • Network aggressively |
| Month 5 | • Interview prep intensive • Fill knowledge gaps • Polish storytelling • Learn about target companies |
• Build Project #4 • Polish all GitHub projects • Create portfolio website • Record project demos |
• GOAL: SECURE OFFER! • Continue applications • Follow up on interviews • Accept analyst role OR • Build Upwork to $3K+/month |
| Timeline | Services to Offer | Pricing | Goal |
|---|---|---|---|
| Month 2-3 | • Data entry & cleaning • Excel automation • Simple Python scripts • Financial data organization |
$15-25/hr (entry pricing) |
Get 3-5 projects Build reputation |
| Month 4-5 | • Data analysis reports • Tableau/Power BI dashboards • SQL queries & reports • Financial analysis |
$25-40/hr (with testimonials) |
$2-5K total revenue 5-star ratings |
🎯 Goal: Build a STANDOUT project combining your trading knowledge + data skills + AI = rare profile that kills in interviews!
Why This Project: 77.4% of organizations are experimenting with AI, but few data analysts can build GenAI-powered dashboards. This positions you at the intersection of two highest-demand skills!
| Component | Features | Tech Stack | Skills Demonstrated |
|---|---|---|---|
| Traditional Analysis (Month 2-3) |
• Technical indicators (RSI, MACD, Bollinger Bands) • Historical price analyzer • Volume analysis • Trend detection |
• Python (Pandas, NumPy) • Matplotlib/Plotly • Yahoo Finance API • SQL for data storage |
• Data wrangling • Visualization • Financial domain |
| 🤖 GenAI/LLM Layer (Month 4-5) |
• Natural language queries: "What was revenue in March?" → auto-chart • AI market commentary: Auto-generated insights • Anomaly explanations: AI describes unusual patterns • Chat interface: Ask questions about your data |
• Streamlit (web app framework) • LLM SDK (Gemini primary, OpenAI/Claude supported) • PandasAI (supplementary chat with data) • Deploy to Streamlit Cloud (FREE) |
• AI integration • Prompt engineering • Full-stack deployment • Production skills |
What You'll Build:
💡 Why This Stands Out: Combines trading knowledge + data skills + AI integration. Only ~5% of junior analysts can build this. Shows you're ready for the GenAI-powered future!
🔎 Portfolio: GitHub repo + Live demo on Streamlit Cloud + YouTube walkthrough
⏰ Time Allocation: 11 hours/week out of 25 total study hours
🎯 Priority: GET HIRED FAST! Focus on recruiter-heavy platforms, not endless learning communities.
| Platform | Time/Week | Recruiter Exposure | What To Do |
|---|---|---|---|
| 30 min/day (3.5 hrs/week) |
⭐⭐⭐⭐⭐ MAXIMUM |
NON-NEGOTIABLE! #1 Priority: • Connect with 5-10 data analysts daily • Post weekly updates (projects, learnings) • Comment on 2-3 posts daily • Turn on #OpenToWork badge • Message analysts for informational interviews • Follow target companies |
|
| GitHub | 1 hr, 3x/week (3 hrs/week) |
⭐⭐⭐⭐⭐ HIGH |
Your Portfolio Showcase: • Push projects with excellent READMEs • Profile README with contact info • Star trending repos (stay current) • Small open source contributions • Make repos public and polished |
| Kaggle | 2 hrs, 2x/week (4 hrs/week) |
⭐⭐⭐⭐ MEDIUM-HIGH |
Already in your roadmap! • Complete micro-courses (Python, Pandas, Data Viz) • Join beginner competitions • Comment on notebooks • Share your work • Some recruiters scout here! |
| Reddit: r/dataanalysis r/datascience |
30 min/week (Sunday review) |
⭐⭐⭐ LOW-MEDIUM |
Quick Updates Only: • Lurk mostly, ask specific questions • Check job postings • Stay updated on tools/trends • Don't get sucked into discussions • Time-box strictly! |
Why Wait? You're on a TIGHT timeline (6-8 months!).
Focus: Courses → Projects → Job Applications
LinkedIn + GitHub + Kaggle = Enough for Stage 1!
| Metric | Target by Month 5 | Why It Matters |
|---|---|---|
| LinkedIn Connections | 100+ data analysts | Network = job opportunities |
| LinkedIn Posts | 2 per week (40 total) | Visibility to recruiters |
| GitHub Projects | 7+ production-grade repos | Portfolio for interviews |
| Kaggle Certificates | 3+ micro-courses | Shows continuous learning |
| Informational Interviews | 5+ conversations | Insider insights + referrals |
| Milestone | Target | Done? | Date |
|---|---|---|---|
| CS50: Introduction to Computer Science Certificate | Month 3 | ||
| Python for Everybody Certificate | Week 8 | ||
| Data Analysis with Python (IBM) Certificate | Month 3 | ||
| Google Data Analytics Certificate | Month 3 | ||
| SQL HackerRank Gold Badge | Month 2 | ||
| Python HackerRank Gold Badge | Month 3 | ||
| Kaggle Learn Certificates (Python, Pandas, Data Viz) | Month 2-3 | ||
| 🏆 Project #1 — 1099 ETL Pipeline DEPLOYED | ✅ Complete | ||
| 🏆 Project #2 — DataVault Analyst (First AI Project) | 4 weeks | ||
| 🏆 Project #3 — PolicyPulse (RAG Foundation) | 4 weeks | ||
| 🏆 Project #4 — FormSense (Multimodal AI) | 5 weeks | ||
| 🏆 Project #5 — Operations-Demand-Intelligence (Enterprise) | 6 weeks | ||
| 🏆 Project #6 — StreamSmart Optimizer (Consumer AI) | 6 weeks | ||
| 🏆 Project #7 — Attention-Flow Catalyst Phase 1A + 1B (Flagship) | 10 weeks | ||
| 🔥 Project #8 — Crucible Phase 1 (Flagship, started first): backtest harness + AI research loop, IT-1 ORB + VWAP Reclaim | 10-14 weeks | ||
| GitHub Profile (8+ production-grade repos with READMEs + GIF demos) | Month 5 | ||
| Upwork Profile Launched | Month 2 | ||
| First Upwork Project | Month 3 | ||
| 3+ Upwork Testimonials | Month 5 | ||
| Job Applications Submitted | 50+ by Month 5 | ||
| Informational Interviews | 5+ by Month 5 | ||
| LinkedIn Connections (Data Analysts) | 100+ by Month 5 | ||
| DATA ANALYST JOB SECURED! | Month 4-5 | ||
| OR Upwork Income $3K+/month | Month 5 | ||
| 📈 TRADING: Attention-Flow Catalyst Phase 1A Complete (Backtest Engine) | Month 4 | ||
| 📈 TRADING: AFC Phase 1B Complete (AI Dashboard) | Month 5 | ||
| 🔥 TRADING: Crucible Phase 1 — backtest harness + AI research loop + sealed OOS vault (IT-1 ORB + VWAP Reclaim plugins, local Qwen3/Ollama) | Stage 1 (started first) | ||
| 📈 TRADING: Read Chapters 1-3 (Book) | Month 5 |
Don't wait until you feel "ready" - you'll never feel 100% ready. Companies hire for potential and domain expertise.
You're ready to apply when you have:
Target job titles: GenAI-Powered Data Analyst, Data Analyst (with AI/LLM), Junior Data Analyst, Associate Analyst, Business Analyst, Financial Analyst, AI/ML Analyst
| Priority | Book Title | Author | Edition/Year | Why Important |
|---|---|---|---|---|
| ⭐ MUST BUY | Python for Data Analysis | Wes McKinney (Pandas creator) | 3rd Edition (2022) ~$60 |
THE definitive Python for data book. Covers Pandas, NumPy, data cleaning, visualization, and real-world datasets. Written by the creator of Pandas. This is your Bible for Stage 1. Non-negotiable purchase. |
| ⭐ MUST BUY | Data Smart | Jordan Goldmeier | 1st Edition (2014) ~$35 |
Perfect for Excel → Python transition. Bridges your bookkeeping/Excel background to Python analytics. Covers data cleaning, modeling, and analytics concepts in accessible way. Ideal for your background. |
| Optional | Python Crash Course | Eric Matthes | 3rd Edition (2023) ~$40 |
Comprehensive Python basics. Only buy if you need fundamental Python reinforcement before diving into data-specific work. Skip if you pick up Python quickly from online courses. |
💰 Stage 1 Book Investment: $95-135 (2 must-buy books, 1 optional)
📖 When to Buy: Get both must-buy books in Month 1. Use "Python for Data Analysis" as your main reference throughout Stage 1. Read "Data Smart" first (2 weeks) to bridge Excel knowledge to Python.
🚫 Skip These: "Automate the Boring Stuff" (wrong focus - scripting not data), "Beyond the Basic Stuff" (intermediate Python not data-focused), generic beginner books (waste of money).
You're now employed! Time to upgrade from Analyst to Engineer—but with an AI-first twist.
2026 Market Reality: Data Engineering Is Changing
| Feature | Standard Data Engineer | AI-First Data Engineer (YOU) |
|---|---|---|
| Data Type | Structured (SQL Tables) | Unstructured (PDFs, Audio, News) |
| Storage | Data Warehouse (Redshift) | Vector Database (Pinecone/Weaviate/Qdrant) |
| Transformation | Cleaning numbers | Chunking & Embedding text for RAG |
| End User | Business analysts | AI/LLM systems |
Why This Transition Wins:
Your Unique Positioning: "I build data pipelines that feed AI systems. While traditional DEs move data between SQL tables, I extract text from financial PDFs, chunk it, embed it into vector databases, and serve it to LLMs via RAG architecture. My finance background means I understand WHAT data matters for financial AI."
These are NEW requirements for AI-focused Data Engineers:
Your Stage 2 Capstone: Build "Financial Knowledge Graph + Vector DB" that ingests SEC filings (PDFs), extracts data, and serves an AI-powered financial-analysis chatbot via a hybrid retriever — embeddings in a vector DB (Pinecone/Qdrant) for semantic breadth + a real knowledge graph in Neo4j (entities: companies, filings, officers, holdings, dates → typed relationships) for multi-hop, explainable reasoning. This makes the "knowledge graph" in the title real (not just PostgreSQL tables) and directly targets multi-hop hallucination — reinforcing your eval-first faithfulness standard.
| Order | Course Name | Platform | Cost | Certificate? | Duration | Why This Course & Why Now |
|---|---|---|---|---|---|---|
| 1️⃣ | Introduction to Data Engineering | Coursera | Included | ✅ Yes | 4 weeks | START HERE! Learn ETL, ELT, data warehousing, data lakes concepts before diving into tools |
| 2️⃣ | SQL for Data Science | Coursera | Included | ✅ Yes | 4 weeks | Refresh & deepen your SQL - UC Davis quality, essential for DE roles (95% of jobs require advanced SQL) |
| 3️⃣ | PostgreSQL Bootcamp | Udemy | $15 | ✅ Yes | 6 weeks | Production database skills - PostgreSQL is industry standard, learn indexing, optimization, real-world usage |
| 4️⃣ | AWS Data Engineering Professional Certificate | Coursera | Included | ✅ Yes | 3-4 months | DEEP LEARNING! Comprehensive AWS: S3, Redshift, Glue, EMR, Kinesis - learn it thoroughly BEFORE certification |
| 5️⃣ | AWS Certified Data Engineer - Associate | AWS | $150 | ✅ Certification | Exam prep | PROVE IT! Take exam AFTER Professional Cert - you'll pass easily with proper preparation. Industry gold standard! |
| 6️⃣ | PySpark for Big Data | Udemy | $15 | ✅ Yes | 6 weeks | Big data processing at scale - PySpark appears in 70% of DE jobs. Now you can handle massive datasets! |
| 7️⃣ | Apache Airflow: The Hands-On Guide | Udemy | $15 | ✅ Yes | 4 weeks | ORCHESTRATION! Tie everything together - schedule pipelines, monitor jobs. 75% of DE roles require Airflow! |
| 7️⃣.5 | 🆕 Docker & Kubernetes Masterclass (Packt) | Coursera | Included | ✅ Yes | 4-6 weeks | PRODUCTION DEPLOYMENT! Containerize your pipelines, deploy to GKE. Docker+K8s appear in 70%+ of DE/ML job postings. Builds on Stage 1 Docker intro with orchestration, scaling, security, and multi-container apps! |
| 8️⃣ | 🆕 dbt Fundamentals (CRITICAL!) | dbt Labs | FREE | ✅ Yes | 5 hours | MOST IMPORTANT 2026 SKILL! Data build tool brings software engineering to data transformation. SQL-based, accessible with your DA background. "Learning dbt significantly improves odds of landing DE job" |
| 9️⃣ | 🤖 IBM Generative AI Engineering Professional Certificate (CRITICAL!) | Coursera | Included | ✅ Yes | 3 months (3-4 hrs/week, Months 6-8) | REINFORCE & APPLY Stage 1 GenAI Skills! If you completed this cert in Stage 1, SKIP and focus on the RAG + LangChain modules you haven't applied to DE projects yet. If you deferred it, take it now — 3 courses covering GenAI Fundamentals, LangChain, and RAG. Apply directly to your Stage 2 data pipeline projects! |
| 🔟 | 🆕 Agentic AI with LangChain (IBM) | Coursera | Included | ✅ Yes | 3 weeks | GenAI-ENHANCED DATA ENGINEERING! Learn LangChain basics for building AI-assisted data pipelines, agents for data quality checks. Prepares you for LLM engineering in Stage 4! |
| 1️⃣1️⃣ | 🆕🤖 Vector Databases: from Embeddings to Applications | DeepLearning.AI | FREE | ✅ Yes | 1-2 hours | THE MISSING LINK FOR AI DATA ENGINEERING! Taught by Pinecone & Weaviate engineers. Cuts through fluff—shows you HOW to build semantic search engines in code. Use directly for your Streaming Pipeline project to store financial news headlines. SHORT but CRITICAL! |
| 1️⃣2️⃣ | 🆕🤖 Pre-processing Unstructured Data for LLM Applications | DeepLearning.AI | FREE | ✅ Yes | 1 hour | 80% OF YOUR FINANCE AI JOB! Standard DE courses teach SQL. This teaches extracting clean text from messy PDFs (SEC 10-K filings), PowerPoint slides, and financial reports. This is the CORE skill that separates AI-First DEs from traditional DEs. FREE and SHORT! |
| 1️⃣3️⃣ | 🆕🤖 Retrieval Augmented Generation (RAG) - Production Ready | DeepLearning.AI | FREE | ✅ Yes | 1-2 hours | PRODUCTION-READY RAG! Go beyond basic RAG—learn architecture, deployment, and evaluation for production systems. Builds on your IBM GenAI cert RAG knowledge with deployment best practices. Apply directly to your Financial Knowledge Graph capstone! |
| 1️⃣4️⃣ | 🆕🤖 Retrieval Augmented Generation (RAG) — Full Course (DeepLearning.AI) | Coursera | Included | ✅ Yes | ~20 hours (multi-week) | COMPREHENSIVE RAG + EVALUATION! Covers the FULL RAG lifecycle: retrieval, vector DBs (Weaviate), evaluation with Phoenix/Arize, deployment, observability. Builds on Stage 1 RAG intro with production depth. Highly rated (4.7★). Certificate included! |
| 1️⃣5️⃣ | 🆕 BigQuery Basics for Data Analysts (Google Cloud) | Coursera | Included | ✅ Yes | 2 weeks | MULTI-CLOUD DATA WAREHOUSE! Quick exposure to BigQuery alongside your AWS Redshift skills. Shows multi-cloud awareness on resume. Many DE jobs require Snowflake OR BigQuery — this covers the gap! |
| 1️⃣6️⃣ | 🆕🤖🕸️ Knowledge Graphs for RAG (intro to GraphRAG) | DeepLearning.AI (w/ Neo4j) | FREE | ✅ Yes | 1-2 hours | 🆕 GRAPHRAG ENTRY POINT — PERFECT DOMAIN FIT! Taught by Neo4j's developer evangelist; builds a knowledge graph from SEC filings (your exact AFC domain) and adds a vector index for a hybrid retriever using Cypher + LangChain. The direct on-ramp to your upgraded Stage 2 capstone. Vector for breadth, graph for connected reasoning. |
| Learning Phase | Courses | What You Gain |
|---|---|---|
| Phase 1: Foundation (Months 6-7) |
• Intro to DE • SQL for Data Science • PostgreSQL |
Understand DE concepts + master SQL + production database skills |
| Phase 2: Cloud Mastery (Months 8-11) |
• AWS DE Professional Cert • AWS Certified DE - Associate |
Deep AWS knowledge + official certification - this combination is POWERFUL for resumes! |
| Phase 3: Scale, Deploy & Orchestration (Months 12-15) |
• PySpark • Apache Airflow • 🆕 Docker & Kubernetes • 🆕 BigQuery Basics |
Handle big data + automate everything + containerize deployments + multi-cloud awareness! |
| Platform | Cost | Weekly Target | Purpose |
|---|---|---|---|
| AWS Free Tier | FREE | 3-4 hrs hands-on | Build real data pipelines: S3 → Lambda → Redshift (practice what you learn in courses!) |
| HackerRank SQL (Advanced) | FREE | 5 advanced problems/week | Complex queries, window functions, query optimization - master advanced SQL |
| GitHub | FREE | Push code daily | Version control practice, build DE portfolio with each project |
| DataCamp | $25/mo | 1-2 exercises/day | Optional: Spark, Scala, advanced SQL - interactive practice (cancel after 2-3 months) |
💡 Strategy: Focus on DS&A interview prep + modern DE tools while building production-quality projects!
| Platform | Cost | When to Use | Specific Activities & Goals |
|---|---|---|---|
| FreeCodeCamp | FREE | Months 6-15 (Throughout DE stage) |
COMPLETE: • "Back End Development and APIs" - Perfect for pipeline APIs (300 hrs) • "Relational Database" - Advanced PostgreSQL practice (300 hrs) • Build 2-3 production-level DE projects Time: 3-4 hrs/week Output: 2-3 API + database projects for GitHub Focus: Real-world data engineering patterns |
| DataCamp | $25/month ($125 for Months 6-10) |
Months 6-10 ONLY (Then cancel) |
SPECIFIC COURSES: • "Introduction to Data Engineering" - DE concepts (4 hrs) • "Introduction to Airflow" - Workflow orchestration (4 hrs) • "Streaming Data with AWS Kinesis and Lambda" - Real-time processing (4 hrs) Time: 3-4 hrs/week Cancel After: Month 10 (Coursera goes deeper after this) Why: Quick hands-on practice with Airflow and AWS streaming |
| Zero to Mastery ⭐ CRITICAL for Interviews |
Already subscribed (from Stage 1) |
Months 8-12 (Parallel with DE courses) |
INTENSIVE INTERVIEW PREP: • "Master the Coding Interview: Data Structures + Algorithms" - COMPLETE THE ENTIRE COURSE (40+ hrs) • "Complete SQL & Databases Bootcamp" - Modern SQL practices vs academic Coursera (20 hrs) Time: 5-7 hrs/week Output: Interview-ready, production-quality code Why: ZTM's DS&A course is THE BEST for interview prep - this is your secret weapon for senior DE roles! |
💰 Stage 2 Platform Investment: DataCamp $125 (5 months) + ZTM $0 (already subscribed) = $125 total
🎯 Key Focus: By end of Stage 2, you should ACE technical interviews for mid-level DE roles thanks to ZTM DS&A!
📌 Credential note (ZTM = evidence, not credential): Zero to Mastery here is skills & project evidence — hands-on practice and portfolio material — not a resume credential. ZTM issues certificates of completion (non-accredited), which carry no recruiter/ATS recognition. Your verifiable credentials come from Coursera (IBM/Google), DeepLearning.AI, and proctored certification exams. On your resume/LinkedIn, list ZTM as skills demonstrated / projects built — never under certifications.
💡 Strategy: Evolve 4 Stage 1 projects with DE infrastructure + build 1 new DE-specific project. This shows you can scale existing systems — not just build from scratch!
| Month | Project Name | Skills Demonstrated | Where to Showcase |
|---|---|---|---|
| Month 7-8 | 🧠 PolicyPulse — Stage 2 Cloud Document Infrastructure |
AWS S3 document storage, PostgreSQL ticket tracking database, scheduled re-ingestion pipeline, data versioning for policy documents | • GitHub (same repo, new branch) • Architecture diagram • Blog post walkthrough |
| Month 9-10 | 📄 FormSense — Stage 2 Batch Processing Pipeline |
AWS S3 form storage, SQS queue for async processing, PostgreSQL ticket tracking, scheduled batch processing for high-volume form intake | • GitHub (same repo, new branch) • Architecture diagram • Demo video |
| Month 11-12 | 📺 StreamSmart — Stage 2 Production Data Platform |
AWS deployment, PostgreSQL user/subscription data, Airflow for automated price monitoring, vector DB for content similarity search | • GitHub (same repo, new branch) • Technical blog • Live deployment |
| Month 13-14 | 🚀 AFC (Flagship) — Stage 2 Scalable Trading Infrastructure |
AWS S3 market data lake, Airflow orchestration for daily data collection, scale from 50 → 500+ tickers, PySpark for historical data processing | • GitHub (same repo, new branch) • Architecture diagram • Case study |
| Month 14-15 | Complete Data Pipeline with Airflow 🆕 New DE Project |
Apache Airflow, DAGs, scheduling, data quality checks, error handling, monitoring, alerts — SHOWCASE ALL DE SKILLS! | • GitHub • Live demo • Case study • Video walkthrough |
| Month | Learning Focus (Evenings) | Building (Weekends) | Career Actions |
|---|---|---|---|
| Month 6-7 | FOUNDATION PHASE • Intro to Data Engineering • SQL for Data Science • PostgreSQL Bootcamp START |
• Set up AWS account • Practice SQL on HackerRank • Start Project #1 (ETL basics) • Learn PostgreSQL locally |
• Excel at analyst job • Build relationships at work • Research DE roles at company • Join DE communities |
| Month 8-9 | AWS LEARNING BEGINS • PostgreSQL Bootcamp FINISH • AWS DE Professional Cert START • S3, Glue basics |
• Complete Project #1 • Start Project #2 (AWS Data Lake) • Practice with AWS Free Tier • Build S3 + Lambda demos |
• Ask for DE tasks at work • Volunteer for pipeline projects • Network with DEs on LinkedIn • Update LinkedIn profile |
| Month 10-11 | AWS DEEP DIVE • AWS DE Professional Cert • Redshift, EMR, Kinesis • Data warehousing concepts • Prep for certification exam |
• Complete Project #2 • Start Project #3 (Streaming) • Practice AWS exam questions • Build complex AWS architectures |
• Update resume with AWS projects • Add AWS Professional Cert to LinkedIn • Apply to internal DE roles • 5-10 external applications/week |
| Month 12 | CERTIFICATION TIME! • AWS DE Professional Cert FINISH • Take AWS Certified DE - Associate EXAM • Review weak areas |
• Complete Project #3 • Polish AWS projects • Create architecture diagrams • Document everything |
• GET AWS CERTIFIED! • Add certification badge to LinkedIn • Update resume: "AWS Certified" • Apply: 10-15 DE roles/week |
| Month 13-14 | BIG DATA PHASE • PySpark for Big Data • Distributed computing • Performance optimization • Airflow course START |
• Start Project #4 (PySpark) • Kaggle big data competitions • Practice Spark on large datasets • Learn Docker basics |
• Apply: 15-20 DE roles/week • Practice DE interviews • System design practice • Mock interviews with peers |
| Month 15 | ORCHESTRATION FINALE • Apache Airflow FINISH • Interview prep • System design for DE • Fill knowledge gaps |
• Project #5: Complete Pipeline • Polish ALL 5 projects • Record demos • Create portfolio website • Practice explaining projects |
• GOAL: DE OFFER! • Continue applications (20+/week) • Interview extensively • Negotiate salary (+30%) • TRANSITION TO DE ROLE! |
Why: Many MCP servers ship TypeScript-first (FastMCP-TS, Vercel AI SDK is TS-only). MCP server experience is becoming a 2026 hiring keyword — per the official MCP 2026 ecosystem report, 97M+ monthly SDK downloads and 200+ server implementations across GitHub, Slack, Postgres, Notion, Jira, Salesforce. Manuel's stack stays Python-primary; this sprint is targeted skill acquisition.
The Sprint (1.5 hours/day x 2 weeks):
mcp-server-ts/ package. ~15 hours.Output: One TS MCP server in your portfolio, "TypeScript (basics)" + "MCP server development" on LinkedIn skills, demonstrable cross-language ability without committing to TS as a primary language.
Why Month 14, not 15: Month 15 is goal-deadline month for DE offer. Month 14 already has Docker basics — TS/MCP fits the "production tooling" theme. Adjust to Month 13 if AWS cert prep is going faster than expected.
🔗 Implementation: The Attention-Flow Catalyst (AFC) project serves as the primary implementation for your algorithmic trading system, evolving through all 5 stages. See AFC Stage 2 in the Portfolio Projects section above.
🎯 Goal: Build production-grade data pipelines for real-time market data and create scalable trading infrastructure!
Why Now: Apply your Data Engineering skills to handle high-frequency trading data at scale!
| Book Chapters | Topics Covered | What You'll Build | Skills Applied |
|---|---|---|---|
| Chapters 4-6 (Months 6-10) |
• Alternative data sources • Real-time data pipelines • Feature engineering • Data storage optimization • Cloud architecture for trading |
• AWS-based market data lake • Real-time price streaming (Kinesis) • Historical data warehouse (Redshift) • Feature store for trading signals • Automated data quality checks |
• AWS (S3, Glue, Redshift) • Apache Airflow • PostgreSQL • PySpark • API integrations |
| Chapters 7-8 (Months 11-15) |
• Time series data at scale • Market microstructure • Order book analysis • Sentiment data pipelines • Backtesting infrastructure |
• High-frequency data pipeline • Order book analyzer • News sentiment aggregator • Scalable backtesting system • Performance monitoring dashboard |
• Big data processing • Distributed systems • Real-time analytics • AWS certification • System design |
Build: "Production Trading Data Platform"
💡 Portfolio Impact: This shows you can handle REAL production systems - a huge advantage for senior DE roles at fintech companies!
⏰ Time Allocation: 10.5 hours/week out of 25 total study hours
🎯 Priority: Excel at your DA job + build DE network + transition to DE role!
| Platform | Time/Week | Recruiter Exposure | What To Do |
|---|---|---|---|
| 30 min/day (3.5 hrs/week) |
⭐⭐⭐⭐⭐ MAXIMUM |
Update to "Data Engineer": • Connect with Data Engineers (not just analysts now) • Post about DE projects, AWS learning • Share certification journey • Join DE-focused groups • Target fintech companies • Engage with DE content daily |
|
| GitHub | 1 hr, 3x/week (3 hrs/week) |
⭐⭐⭐⭐⭐ HIGH |
Showcase DE Architecture: • Push AWS/DE projects • Architecture diagrams in READMEs • Contribute to DE tools (Airflow, etc.) • Star trending DE repos • Show production-grade code |
| AWS re:Post + r/aws |
1 hr/week | ⭐⭐⭐⭐ MEDIUM-HIGH |
AWS Community: • Ask AWS-specific questions • Share your architectures • Learn certification tips • Connect with AWS experts • AWS recruiters browse here! |
| DataTalks.Club (Slack) |
2 hrs/week | ⭐⭐⭐ MEDIUM |
NOW You Can Join DE Community: • Ask DE-specific questions • Share AWS projects • Learn about Airflow, Spark • Network with practicing DEs • Time-box strictly! |
| Local Meetups (In-Person!) |
4 hrs/month (1 hr/week avg) |
⭐⭐⭐⭐⭐ MAXIMUM |
CRITICAL! Best for Jobs: • Attend Data Engineering meetups • AWS user groups • Practice elevator pitch • Collect business cards • Recruiters attend these! |
| Metric | Target by Month 15 | Why It Matters |
|---|---|---|
| LinkedIn Connections | 250+ (150 DEs) | DE network for job opportunities |
| LinkedIn Posts | 2 per week (80 total) | Build DE reputation |
| GitHub DE Projects | 5 production-grade | Show architecture skills |
| In-Person Meetups | 10+ attended | Real networking = best results |
| AWS Community Posts | 10+ questions/answers | Show AWS expertise |
| Milestone | Target | Done? | Date |
|---|---|---|---|
| 1️⃣ Introduction to Data Engineering | Month 6 | ||
| 2️⃣ SQL for Data Science | Month 7 | ||
| 3️⃣ PostgreSQL Bootcamp | Month 8 | ||
| 4️⃣ AWS Data Engineering Professional Certificate | Month 11 | ||
| 5️⃣ AWS Certified Data Engineer - Associate ✅ | Month 12 | ||
| 6️⃣ PySpark for Big Data | Month 13 | ||
| 7️⃣ Apache Airflow Course | Month 15 | ||
| 🏆 PolicyPulse — Stage 2 (AWS S3 + PostgreSQL) | Month 8 | ||
| 🏆 FormSense — Stage 2 (S3 + SQS + Batch Processing) | Month 10 | ||
| 🏆 StreamSmart — Stage 2 (AWS + Airflow + Vector DB) | Month 12 | ||
| 🏆 AFC (Flagship) — Stage 2 (S3 + Airflow + 500+ Tickers) | Month 14 | ||
| 🏆 Complete Data Pipeline with Airflow (New DE Project) | Month 15 | ||
| GitHub Portfolio (12+ repos: 7 Stage 1 + 5 Stage 2 evolutions) | Month 15 | ||
| Technical Blog Posts (DE topics) | 5+ by Month 15 | ||
| HackerRank SQL Advanced Badge | Month 10 | ||
| DE Job Applications | 75+ by Month 15 | ||
| LinkedIn Connections (Data Engineers) | 250+ total | ||
| DATA ENGINEER JOB SECURED! | Month 15 | ||
| Salary Upgrade to $80-100K | Month 15 | ||
| 📈 TRADING: AWS Trading Data Platform Complete | Month 15 | ||
| 📈 TRADING: Read Chapters 4-8 (Book) | Month 15 | ||
| 📈 TRADING: Real-time Data Pipeline (Kinesis) | Month 12 | ||
| 📈 TRADING: Backtesting Infrastructure Built | Month 14 |
Skills Mastered (In Order):
| Skill Category | What You'll Know |
|---|---|
| Concepts | ETL, ELT, data warehousing, data lakes, dimensional modeling |
| SQL Mastery | Advanced queries, optimization, indexing, window functions, CTEs |
| Databases | PostgreSQL production skills - the industry standard |
| Cloud (AWS) | S3, Redshift, Glue, EMR, Kinesis, Lambda, Athena + CERTIFIED! |
| Big Data | PySpark, distributed computing, handling massive datasets |
| Orchestration | Apache Airflow, DAGs, scheduling, monitoring, production pipelines |
Resume Power:
| Priority | Book Title | Author | Edition/Year | Why Important |
|---|---|---|---|---|
| ⭐ MUST BUY | Fundamentals of Data Engineering | Joe Reis & Matt Housley | 1st Edition (2022) ~$60 |
THE modern data engineering bible. Covers data pipelines, cloud platforms (AWS/Azure/GCP), data modeling, warehousing, ETL/ELT, DataOps, and best practices. This book will guide your entire Stage 2 learning and transition from DA to DE. |
| ⭐ MUST BUY | Designing Data-Intensive Applications | Martin Kleppmann | 1st Edition (2017) ~$60 |
The classic DE architecture book. Deep dive into data systems fundamentals, distributed systems, database internals, scalability, and reliability. Dense but essential for understanding how data systems work at scale. Senior engineers reference this book constantly. |
| Optional | Data Pipelines Pocket Reference | James Densmore | 1st Edition (2021) ~$30 |
Quick reference guide for building pipelines with Airflow, Spark, and cloud tools. Good supplementary resource if you want a compact handbook alongside the comprehensive books above. |
💰 Stage 2 Book Investment: $120-150 (2 must-buy books, 1 optional)
📖 When to Buy: Purchase both books at the start of Month 6 (when you transition to DE). Read "Fundamentals of Data Engineering" cover-to-cover in Months 6-7. Use "Designing Data-Intensive Applications" as deep-dive reference throughout Stage 2.
💡 Pro Tip: These books are dense. Don't rush through them. Take notes, code along with examples, and apply concepts to your AWS and pipeline projects. They're investments you'll reference for years.
You're now a Data Engineer with GenAI skills! Time to master LOCAL LLMs and fine-tuning.
2026 Market Reality: Local LLMs Are the Future for Finance
| Challenge | Cloud LLMs (OpenAI/Anthropic) | Local LLMs (YOUR Expertise) |
|---|---|---|
| Data Privacy | ❌ Send sensitive data externally | ✅ All data stays on-premise |
| Cost at Scale | ❌ $$$$ per 1M tokens | ✅ One-time GPU cost |
| Customization | ❌ Limited fine-tuning options | ✅ Full model control via LoRA/QLoRA |
| Compliance | ❌ Complex regulatory checks | ✅ No third-party sharing |
Why This Makes You Top 2-3% of Candidates:
🎓 CRITICAL: Math Foundation FIRST! Learn Linear Algebra & Calculus (Months 16-17) RIGHT before ML courses. This makes deep learning concepts actually make SENSE, not just API calls you memorize.
Master these tools that 95%+ of AI engineers don't know:
Your Stage 3 Capstone: "Fine-Tuned Financial LLM"
Why This Differentiates You: Generic GPT-4 doesn't understand specialized financial/trading language. YOUR model does. This proves you can customize AI for specific domains—the #1 skill finance companies desperately need!
| Order | Course Name | Platform | Cost | Certificate? | Duration | Why This Course |
|---|---|---|---|---|---|---|
| 1️⃣ | Mathematics for Machine Learning Specialization | Coursera | Included | ✅ Yes | 8-10 weeks | START HERE! Linear algebra, calculus, PCA - essential ML math. Makes everything else click! |
| 2️⃣ | Machine Learning Specialization (Andrew Ng) | Coursera | Included | ✅ Yes | 3 months | THE foundational ML course - supervised, unsupervised, neural networks (AFTER math!) |
| 3️⃣ | Deep Learning Specialization (Andrew Ng) | Coursera | Included | ✅ Yes | 3-4 months | CNNs, RNNs, attention, transformers - essential for modern ML/LLM work |
| 4️⃣ | 🆕 NVIDIA DLI: Fundamentals of Deep Learning | NVIDIA DLI | FREE / $30 | ✅ Yes | 1-2 days | REPLACES DISCONTINUED TF CERT! NVIDIA certifications are the new gold standard for deep learning verification in 2026. GPU-accelerated deep learning, model training, deployment. Industry-recognized credential. TensorFlow Developer Certificate was discontinued May 2024. |
| 5️⃣ | MLOps Specialization | Coursera | Included | ✅ Yes | 2 months | Production ML: CI/CD for ML, model serving, monitoring - critical for ML engineers |
| 6️⃣ | Fast.ai Practical Deep Learning | Fast.ai | FREE | ❌ No | 2 months | Top-down approach, build models quickly, excellent for practitioners |
| 7️⃣ | 🆕🤖 Generative AI with Large Language Models (AWS + DeepLearning.AI) | Coursera | Included | ✅ Yes | 3 weeks (16 hrs) | THE "BIBLE" OF LLM THEORY! The ONLY comprehensive course covering the FULL LLM lifecycle: pre-training → fine-tuning → RLHF → deployment. Explains transformer architecture MATH, Chinchilla scaling laws, quantization, PEFT (LoRA/QLoRA). Taught by AWS AI practitioners with hands-on labs. Take AFTER Deep Learning Specialization—this bridges ML theory to LLM engineering! 4.7★, 600K+ enrolled. |
| 8️⃣ | 🆕🤖 Fine-Tuning LLMs with PEFT (DeepLearning.AI) | DeepLearning.AI | FREE | ✅ Yes | 1-2 hours | HANDS-ON LoRA & QLoRA! Practical code-along where you take a generic model and retrain it on a specific dataset. Learn WHEN to fine-tune vs. prompt engineer, evaluation strategies, and parameter-efficient methods. Pairs perfectly with AWS GenAI course above. Apply directly to your "Fine-Tuned Financial LLM" capstone project! |
| 9️⃣ | 🆕🤖 Fast & Efficient LLM Inference with vLLM (DeepLearning.AI) | DeepLearning.AI | FREE | ✅ Yes | 1-2 hours | LOCAL-FIRST INFERENCE & QUANTIZATION! Serving, batching, KV-cache, and quantization for efficient local LLM inference. Closest formal course to Crucible's Ollama/Qwen3 local-first analyst — the nearest credential for the Local-LLM Specialist skill (Ollama itself is hands-on, no cert exists). |
| 🔟 | 🆕🤖🕸️ Neo4j GraphAcademy: Knowledge Graphs & GraphRAG path → Neo4j Certified Professional | Neo4j GraphAcademy | FREE | ✅ Yes (Neo4j Certified Professional) | Self-paced (multi-week) | 🆕 DEEPEN GRAPHRAG + RECOGNIZED GRAPH CREDENTIAL! Official Neo4j path: build knowledge graphs from unstructured data, fuse vector + graph retrieval, and assemble end-to-end GraphRAG pipelines with Neo4j's GenAI tools — earning the recruiter-recognized Neo4j Certified Professional badge. Builds directly on the Stage 2 "Knowledge Graphs for RAG" intro. Complement: DeepLearning.AI "Agentic Knowledge Graph Construction" (multi-agent KG building) for the advanced edge. |
Roadmap-track credentials (vendor-agnostic, portfolio-facing). The NVIDIA exam completes the "NVIDIA is the gold standard" note above — you already have the DLI course; this adds the exam.
| Certification | Code | Cost | Format | Why It Belongs in Stage 3 |
|---|---|---|---|---|
| NVIDIA-Certified Associate: Generative AI LLMs | NCA-GENL | $125 | 50–60 Q · 60 min · valid 2 yrs | The exam behind the NVIDIA DLI course above — transformers, prompt engineering, RAG, PEFT, deployment. Recruiter-recognized credential that stands in for the discontinued TensorFlow Developer Certificate. |
| Databricks Certified Generative AI Engineer Associate | — | $200 | 45 Q · 90 min · 2 yrs · Python | Industry's first production-GenAI engineering cert. Production RAG, LLM chains, MLflow, Vector Search, Unity Catalog governance, evaluation/monitoring — reinforces your DeepEval eval-first discipline at the Stage 2→3 production boundary. |
| Platform | Cost | Weekly Target | Purpose |
|---|---|---|---|
| Kaggle Competitions | FREE | Work on 1 active competition | Real ML problems, learn from others' notebooks, build reputation |
| Papers with Code 🚨 DEFUNCT — see footnote below |
FREE | Read 1 paper/week | Stay current with ML research, implement algorithms |
| HuggingFace | FREE | Try 2-3 models/week | Learn transformer models, practice fine-tuning, prepare for LLM stage |
| Google Colab | FREE | Daily practice | Free GPU for training, experiment without cloud costs |
🚨 ARCHIVE FOOTNOTE (added by v10.0 CORRECTION 7, July 2026 — the table above is preserved verbatim per the additive-only policy). Papers with Code is defunct. Meta sunsetted it on 24–25 July 2025 without prior notice — users hit 502 errors and garbled text, GitHub issues went unanswered, and the domain now redirects to Hugging Face Trending Papers. The ~9,300 benchmark leaderboards, ~79,800 paper-to-code linkages, and ~5,600 tracked datasets are no longer served from the canonical URL; the site had been acquired by Meta in December 2019 under a public commitment that it would stay neutral, open, and free. Live successors: Hugging Face Trending Papers (the official Meta/HF-announced replacement) and paperswithcode.co, a community revival launched by Niels Rogge of Hugging Face's open-source team that restores SOTA leaderboards. Historical data survives as community JSON dumps and the pwc-archive on Hugging Face. No active-roadmap impact — v10.0 cut the ML-Engineer stage that this table served, and paper-tracking is not a v10.0 practice line. Flagged so the archive is not mistaken for a live link.
💡 Strategy: Build competition-winning ML projects and master modern frameworks for impressive portfolio!
| Platform | Cost | When to Use | Specific Activities & Goals |
|---|---|---|---|
| FreeCodeCamp | FREE | Months 16-29 (Throughout ML stage) |
COMPLETE: • "Machine Learning with Python" - Project-based ML certification (300 hrs) • "Data Analysis with Python" - Reinforce analytics skills (300 hrs) • Build 3-4 ML certification projects Time: 3-5 hrs/week Output: FreeCodeCamp ML certificates + 3-4 production ML projects Why: Projects are BETTER quality than typical Coursera ML projects! |
| DataCamp | NOT USED | SKIP in Stage 3 | NO SUBSCRIPTION NEEDED: DataCamp's ML content doesn't add enough value vs. Coursera + FreeCodeCamp Better to invest time in: Kaggle competitions + hands-on projects 💰 Savings: $350 by skipping DataCamp in ML stage! |
| Zero to Mastery ⭐ BEST for Modern ML |
Already subscribed ($279/year) |
Months 20-24 (After Coursera ML foundations) |
HANDS-ON MODERN FRAMEWORKS: • "TensorFlow Developer Certificate" (ZTM version) - Industry-focused TF training (30 hrs) • "PyTorch for Deep Learning" - Modern deep learning workflows (40 hrs) Time: 6-8 hrs/week Output: 2-3 modern ML apps using latest frameworks Why: More hands-on than Coursera, uses current best practices, portfolio projects look "production-ready"! |
| Kaggle Competitions 🏆 Essential for ML Engineers |
FREE | Months 20-29 (After fundamentals) |
COMPETE & LEARN: • Join 3-5 competitions (aim for top 25%) • Study winning solutions • Build ensemble models • Network with ML community Time: 5-8 hrs/week Output: Kaggle medals/badges + competition experience Why: Kaggle experience = instant credibility with ML hiring managers! |
💰 Stage 3 Platform Investment: ZTM $0 (already subscribed) + Kaggle FREE = $0 additional!
🎯 Key Focus: Build competition-worthy portfolio that screams "I can build production ML systems!"
📌 Credential note (ZTM = evidence, not credential): Zero to Mastery here is skills & project evidence — hands-on practice and portfolio material — not a resume credential. ZTM issues certificates of completion (non-accredited), which carry no recruiter/ATS recognition. Your verifiable credentials come from Coursera (IBM/Google), DeepLearning.AI, and proctored certification exams. On your resume/LinkedIn, list ZTM as skills demonstrated / projects built — never under certifications.
💡 Strategy: Evolve 4 Stage 1 projects with ML capabilities + build 2 new ML-specific projects. This shows you can add ML intelligence to existing systems AND build standalone ML applications!
| Month | Project Name | Skills Demonstrated | Where to Showcase |
|---|---|---|---|
| Month 19-20 | Predictive Model (Tabular Data) 🆕 New ML Project |
Scikit-learn, feature engineering, model selection, hyperparameter tuning, evaluation metrics | • GitHub • Kaggle notebook • Blog post |
| Month 21-22 | 🧠 PolicyPulse — Stage 3 Fine-Tuned HR Retrieval |
Fine-tuned embedding model for HR domain, re-ranking model for better retrieval accuracy, evaluation benchmarks | • GitHub (same repo) • HuggingFace model • Technical article |
| Month 23-24 | 📄 FormSense — Stage 3 Custom Extraction Model |
Custom fine-tuned extraction model, form classification (distribution vs loan vs rollover), accuracy improvement benchmarks, transfer learning | • GitHub (same repo) • HuggingFace Space • Demo video |
| Month 25-26 | 📺 StreamSmart — Stage 3 ML Prediction Engine |
ML-based viewing prediction, churn models, personalized recommendations with collaborative filtering, MLflow tracking | • GitHub (same repo) • Architecture diagram • Case study |
| Month 27-29 | 🚀 AFC (Flagship) — Stage 3 ML Trading Models |
XGBoost signal prediction, LSTM time series, MLflow model tracking, ensemble strategies, walk-forward ML validation | • GitHub (same repo) • Live demo • Blog series • HuggingFace models |
| Month 27-29 | NLP Sentiment Analysis 🆕 New ML Project |
BERT/RoBERTa fine-tuning, text preprocessing, transformers, evaluation, API deployment (FastAPI + Docker) | • GitHub • HuggingFace Space • Technical article |
| Month | Learning Focus (Evenings) | Building (Weekends) | Career Actions |
|---|---|---|---|
| Month 16-17 | • Mathematics for ML (START HERE!) • Linear Algebra • Multivariate Calculus • PCA & dimensionality reduction |
• Practice math problems • Implement algorithms from scratch • Visualize concepts • Build intuition |
• Excel at DE job • Take on ML-related tasks • Research ML roles • Network with ML engineers |
| Month 18-20 | • ML fundamentals (Andrew Ng) • Regression, classification • Model evaluation • Scikit-learn • Math now makes sense! |
• Kaggle beginner competitions • Project #1: Tabular data • Practice feature engineering • Apply math concepts |
• Update LinkedIn with ML learning • Start building ML portfolio • Network with ML community |
| Month 21-23 | • Deep Learning (Andrew Ng) • Neural networks • CNNs for vision • TensorFlow/Keras • Backprop (understand the math!) |
• Project #2: Computer vision • Kaggle image competitions • Build Streamlit demos • Implement NN from scratch |
• Apply to ML-adjacent roles at company • Start ML job applications • Practice ML coding interviews |
| Month 24-26 | • NLP & Transformers • BERT, GPT architecture • HuggingFace ecosystem • MLOps fundamentals • TensorFlow cert prep |
• Project #3: NLP sentiment • Project #4: ML pipeline • Take TensorFlow cert exam • Build production demos |
• Apply to ML Engineer roles • 10-15 applications/week • Practice ML system design • Get TensorFlow certified! |
| Month 27-29 | • Advanced topics: - Model optimization - Scalable ML - System design for ML - Advanced math applications • Interview prep |
• Project #5: RecSys • Polish all projects • Create portfolio website • Record project videos • Open source contributions |
• GOAL: ML ENGINEER OFFER! • Apply: 20+ roles/week • Interview extensively • Negotiate $120-150K • Transition to ML role |
🔗 Implementation: The Attention-Flow Catalyst (AFC) project serves as the primary implementation for your algorithmic trading system. See AFC Stage 3 in the Portfolio Projects section above (XGBoost, LSTM, MLflow).
🔥 Crucible (second flagship) here: Phase 2 matures in Stage 3 — migrate from the Phase 1 own-harness to NautilusTrader (with an engine-parity gate proving both agree on a fixed window), then build the autonomous paper-trading agent crew (LangGraph) with a local Qwen3/Ollama research analyst. This stage's local-LLM skills (Ollama, quantization) are exactly what Crucible Phase 2 needs — the project and the curriculum reinforce each other. Gate: paper-vs-backtest parity before any live consideration.
🎯 Goal: Apply Machine Learning to trading! Build predictive models for price movements and develop intelligent trading strategies.
Why Now: You have the MATH foundation + ML skills to understand WHY models work, not just HOW to use them!
| Book Chapters | Topics Covered | What You'll Build | Skills Applied |
|---|---|---|---|
| Chapters 9-12 (Months 18-23) |
• Linear models for trading • Tree-based models (XGBoost) • Feature engineering for alpha • Time series forecasting • Model evaluation for trading |
• Price prediction models (regression) • Direction classifier (up/down) • Volatility forecasting • XGBoost strategy optimizer • Feature importance analyzer |
• Scikit-learn • Math foundation! • Statistical modeling • Cross-validation • Backtesting |
| Chapters 13-15 (Months 24-26) |
• Deep learning for trading • LSTMs for time series • CNNs for chart patterns • Sentiment analysis with NLP • Ensemble methods |
• LSTM price predictor • CNN chart pattern recognizer • News sentiment model (BERT) • Multi-model ensemble strategy • Risk management system |
• TensorFlow/Keras • Neural networks • NLP transformers • Deep learning math • MLOps |
| Chapter 16 (Months 27-29) |
• Portfolio optimization • Risk-adjusted returns • Sharpe ratio optimization • Walk-forward analysis • Production ML for trading |
• Portfolio optimizer • Risk analyzer • Walk-forward backtester • Real-time model serving • Performance monitoring |
• Advanced ML • System design • Production deployment • Financial metrics • TensorFlow Certified! |
Build: "ML-Powered Trading Strategy Suite"
💡 Career Impact: This demonstrates ADVANCED ML skills applied to finance - perfect for quant trader, ML engineer at hedge funds, or fintech ML roles!
⏰ Time Allocation: 16.5 hours/week out of 25 total study hours
🎯 Priority: Build ML reputation + network with ML engineers + position for ML roles!
| Platform | Time/Week | Recruiter Exposure | What To Do |
|---|---|---|---|
| 30 min/day (3.5 hrs/week) |
⭐⭐⭐⭐⭐ MAXIMUM |
Update to "ML Engineer": • Connect with ML engineers, researchers • Post ML projects + trading models • Share math learning journey (unique!) • Engage with ML content • Target hedge funds, fintech ML teams • #MachineLearning #MLOps hashtags |
|
| GitHub | 1 hr, 4x/week (4 hrs/week) |
⭐⭐⭐⭐⭐ HIGH |
Showcase ML Systems: • Push ML trading models • Jupyter notebooks with analysis • Contribute to ML libraries (scikit-learn, etc.) • Model cards, experiment logs • Production ML code (not just notebooks!) |
| Kaggle Competitions | 2 hrs, 2x/week (4 hrs/week) |
⭐⭐⭐⭐⭐ HIGH |
CRITICAL! ML Recruiters Scout Here: • Join intermediate competitions • Aim for top 10% in 2-3 • Share notebooks publicly • Comment & learn from winners • Top performers get contacted! |
| Reddit: r/MachineLearning r/learnmachinelearning |
1 hr/week | ⭐⭐⭐ MEDIUM |
Stay Current on Research: • Read paper discussions • Share your ML projects • Learn new techniques • Job postings occasionally • Time-box strictly! |
| Papers with Code | 2 hrs/week | ⭐⭐⭐⭐ MEDIUM-HIGH |
Implement SOTA Models: • Read trending papers • Implement for trading project • Push implementations to GitHub • Shows you can read papers! • Some research labs recruit here |
| MLOps Community (Slack/Discord) |
2 hrs/week | ⭐⭐⭐ MEDIUM |
Production ML Skills: • Learn deployment patterns • Share pipeline architectures • Ask about monitoring, scaling • Network with MLOps engineers |
| ML/AI Conferences (In-Person/Virtual) |
2-3 days total (1-2/year) |
⭐⭐⭐⭐⭐ MAXIMUM |
HUGE Career Impact: • Attend local AI summits • NeurIPS/ICML (if accessible) • Network with companies • Learn cutting-edge research • Companies recruit at conferences! |
| Metric | Target by Month 29 | Why It Matters |
|---|---|---|
| LinkedIn Connections | 400+ (200 ML focused) | ML network for opportunities |
| Kaggle Rank | Top 10% in 2-3 competitions | Recruiters actively scout |
| GitHub ML Projects | 8+ production ML systems | Show depth and breadth |
| Paper Implementations | 3+ on GitHub | Shows research understanding |
| Conferences Attended | 2+ events | Network with companies |
| Milestone | Target | Done? | Date |
|---|---|---|---|
| Mathematics for ML Specialization | Month 17 | ||
| ML Specialization Certificate (Andrew Ng) | Month 21 | ||
| Deep Learning Specialization | Month 24 | ||
| TensorFlow Developer Certificate | Month 26 | ||
| MLOps Specialization | Month 27 | ||
| Fast.ai Course Complete | Month 25 | ||
| Kaggle Competitions (3+ submitted) | Month 29 | ||
| 🏆 Predictive Model — Tabular Data (New ML Project) | Month 20 | ||
| 🏆 PolicyPulse — Stage 3 (Fine-Tuned HR Embeddings) | Month 22 | ||
| 🏆 FormSense — Stage 3 (Custom Extraction Model) | Month 24 | ||
| 🏆 StreamSmart — Stage 3 (ML Prediction Engine) | Month 26 | ||
| 🏆 AFC (Flagship) — Stage 3 (XGBoost + LSTM + MLflow) | Month 29 | ||
| 🏆 NLP Sentiment Analysis (New ML Project) | Month 29 | ||
| HuggingFace Models Published | 2+ by Month 29 | ||
| ML Blog Posts | 5+ by Month 29 | ||
| GitHub ML Portfolio (18+ repos total: 7 S1 + 5 S2 + 6 S3) | Month 29 | ||
| ML Job Applications | 60+ by Month 29 | ||
| ML ENGINEER JOB SECURED! | Month 28-29 | ||
| Salary Upgrade to $120-150K | Month 29 | ||
| 📈 TRADING: ML Trading Strategy Suite Complete | Month 29 | ||
| 📈 TRADING: Read Chapters 9-16 (Book) | Month 29 | ||
| 📈 TRADING: 5+ ML Models Trained & Backtested | Month 26 | ||
| 📈 TRADING: LSTM + News Sentiment Models | Month 28 | ||
| 📈 TRADING: Portfolio Optimizer Built | Month 29 |
Why starting with Mathematics for ML is brilliant:
| Benefit | Impact |
|---|---|
| Better Understanding | You'll actually understand what gradient descent, backprop, and matrix operations DO |
| Interview Performance | Stand out by explaining the math behind algorithms, not just using APIs |
| Faster Learning | Andrew Ng's courses make WAY more sense when you know the math |
| Better Intuition | Debug models more effectively, choose right algorithms, tune hyperparameters |
| Research Papers | Actually understand ML/LLM papers instead of just skimming |
| Career Longevity | Fundamentals don't change - frameworks do. You'll adapt to any new tool |
| Priority | Book Title | Author | Edition/Year | Why Important |
|---|---|---|---|---|
| ⭐ MUST BUY | Hands-On Machine Learning with Scikit-Learn, Keras, and TensorFlow | Aurélien Géron | 3rd Edition (2022) ~$65 |
THE best practical ML book, period. Covers end-to-end ML projects, scikit-learn (classical ML), TensorFlow & Keras (deep learning), neural networks, CNNs, RNNs, transformers, and production ML. Hands-on code examples throughout. This single book can take you from ML beginner to engineer. Absolutely essential. |
| Recommended | Introduction to Machine Learning with Python | Andreas Müller & Sarah Guido | 1st Edition (2016) ~$50 |
Gentler introduction to ML with focus on scikit-learn. More accessible than Géron if you want an easier on-ramp. Practical approach with clear explanations. Buy if Géron's book feels too intense initially. |
| Optional | The Hundred-Page Machine Learning Book | Andriy Burkov | 1st Edition (2019) ~$40 |
Concise ML theory overview in just 100 pages. Perfect for quick reference and interview prep. Covers all essential ML concepts without fluff. Great to have on hand for rapid review. |
💰 Stage 3 Book Investment: $65-155 (1 must-buy, 2 optional)
📖 When to Buy: Purchase "Hands-On Machine Learning" at Month 16 when starting Stage 3. Work through it chapter by chapter alongside your ML courses. Code along with every example - don't just read passively.
💡 Study Strategy: This is a hands-on stage. Open Jupyter notebook, work through Géron's examples with your own datasets (use your trading data!). Build projects based on each chapter. The book has 800+ pages - take your time and master each concept before moving forward.
🚫 Skip These: "Deep Learning" by Goodfellow (too theoretical, use online resources instead), "Pattern Recognition and Machine Learning" by Bishop (academic textbook, not practical for your path).
You're now an ML Engineer with Local LLM expertise! Time to build AGENTIC systems, not just chatbots.
2026 Reality: Simple RAG Is Commodity, Agents Are Cutting Edge
| Capability | Simple Chatbot (Everyone) | Agentic AI (Top 5%) |
|---|---|---|
| Workflow | Linear: Query → Search → Answer | ✅ Loops: Plan → Act → Check → Retry |
| Tool | LangChain (sequential chains) | ✅ LangGraph (graph-based, stateful) |
| Error Handling | Fails and stops | ✅ Retries, backtracking, adaptation |
| Complexity | "Chat with PDF" | ✅ Multi-agent systems, web browsing, tool calling |
What it is: the June-2026 successor to prompt → context → harness engineering. Instead of prompting an agent by hand each step, you design the system that prompts it: trigger → act → observe → verify → repeat until a stop condition. Popularized by Addy Osmani and Boris Cherny ("I don't prompt Claude anymore — I have loops that prompt it").
Why this is mostly a re-frame for you, not a new skill: Stage 4 already teaches "Plan → Act → Check → Retry," LangGraph stateful loops, and evaluator-optimizer. The literature is unanimous that the verifier is the bottleneck — defining measurable "done" is the hard part — which is exactly your eval-first discipline (DeepEval ≥0.9 gates, "behind the Wall"). You are ahead of most here.
The 5 production-loop components to add (the genuine gaps — none are in the roadmap yet):
⚠️ Autonomy is a per-project decision, not a blanket default:
📚 Best course (no dedicated "loop engineering" course exists yet — the term is weeks old; these teach the real substance):
Why LangGraph > LangChain (2026 Evolution):
Your Stage 4 Mission: Build production agentic systems using LangGraph. Master multi-agent orchestration, tool calling, web browsing integration. Create "AI Trading Assistant" that can research stocks, verify data from multiple sources, and adapt strategies based on feedback—not just answer questions!
Focus heavily on these frameworks that define 2026's cutting edge:
Your Stage 4 Capstone: "Agentic Trading Assistant" (AFC)
Why This Differentiates You: Most candidates can build "Chat with PDF" (simple RAG). You can build systems that REASON, VERIFY, and ADAPT — the skills needed for production AI agents in 2026. Naming the patterns explicitly (orchestrator-workers, sequential, evaluator-optimizer) signals senior-track pattern literacy. This is what finance companies desperately need: AI that can audit its own work!
| Order | Course Name | Platform | Cost | Certificate? | Duration | Why This Course |
|---|---|---|---|---|---|---|
| 1️⃣ | LangChain & Vector Databases | Udemy | $15 | ✅ Yes | 3 weeks | Build LLM applications: RAG, agents, chains, memory - practical hands-on |
| 2️⃣ | HuggingFace NLP Course | HuggingFace | FREE | ❌ No | 1 month | Transformers library deep dive, fine-tuning techniques, model deployment |
| 3️⃣ | Neural Networks: Zero to Hero (Karpathy) | YouTube | FREE | ❌ No | 2 months | Build GPT from scratch - understand LLMs from first principles |
| 4️⃣ | 🆕 Ollama (Local LLMs) | Ollama | FREE | ❌ No | 1 week | RUN LLMS LOCALLY! Deploy Llama 3, Mistral, other models on your machine. No API costs for experimentation. Great for privacy-sensitive financial data! |
| 5️⃣ | 🆕🤖 Agentic AI (Andrew Ng) | DeepLearning.AI | FREE | ✅ Yes | Self-paced (multi-week) | ⭐ THE #1 AGENTIC AI COURSE OF 2026! Taught by Andrew Ng himself. Vendor-neutral, raw Python—no framework lock-in. Master 4 design patterns: Reflection, Tool Use, Planning, Multi-Agent. KEY DIFFERENTIATOR: Includes evaluation-driven development + MCP tool integration. Builds a Deep Research Agent capstone. "The single biggest predictor of success is disciplined evals"—Ng. Take this FIRST before framework-specific courses! |
| 6️⃣ | 🆕🤖 Evaluating AI Agents (DeepLearning.AI) | DeepLearning.AI | FREE | ✅ Yes | 1-2 hours | MEASURE YOUR AGENTS! Code-based vs LLM-as-a-Judge evaluators, choosing the right metrics, and tracing/observability for agent runs. Pairs with Agentic AI above ("disciplined evals" — Ng) and powers StreamSmart's "Circle of Evaluation" + Crucible's agent oversight. |
| 7️⃣ | 🆕🤖 MCP: Build Rich-Context AI Apps with Anthropic | DeepLearning.AI | FREE | ✅ Yes | 1-2 hours | THE DEFINITIVE MCP COURSE! Taught by Anthropic's Elie Schoppik (Head of Technical Education). Build & deploy MCP servers, connect to GitHub/Google Docs/local files, learn client-server architecture. Covers future roadmap: multi-agent architecture, MCP registry API, server discovery, auth. Replaces reading docs alone—this is the OFFICIAL Anthropic training! |
| 8️⃣ | 🆕 AI Agents in LangGraph | DeepLearning.AI | FREE | ✅ Yes | 2 hours | LANGGRAPH > LANGCHAIN! Stateful workflows with memory, iteration, conditional logic. ReAct, Reflection, Reflexion architectures. Critical for production agents! |
| 9️⃣ | 🆕🤖 Long-Term Agentic Memory with LangGraph | DeepLearning.AI | FREE | ✅ Yes | 1-2 hours | AGENTS THAT REMEMBER! Taught by Harrison Chase (LangChain CEO). Master 3 memory types: Semantic (facts), Episodic (experiences), Procedural (skills). Build email agent with LangMem for persistent memory across sessions. CRITICAL for your Trading Assistant—it needs to remember past analyses & learn from feedback! |
| 🔟 | 🆕🤖 Multi-AI Agent Systems with crewAI (DeepLearning.AI) | DeepLearning.AI | FREE | ✅ Yes | 1-2 hours | MAKE AI AGENTS TALK TO EACH OTHER! For your Trading Team project: one AI researches, another analyzes, another executes. Learn role-based collaboration, personality tuning, real-time orchestration. Pairs with CrewAI docs study above. Recommended by Google Doc as essential for Stage 4! |
| 1️⃣1️⃣ | 🆕 CrewAI Multi-Agent Framework | CrewAI Docs | FREE | ❌ No | 2 weeks | MULTI-AGENT ORCHESTRATION! Build teams of AI agents that collaborate. Role-based agents, task delegation, real-world automation. Hot framework for 2026! |
| 1️⃣2️⃣ | 🆕🤖 Agent Skills with Anthropic | DeepLearning.AI | FREE | ✅ Yes | 1-2 hours | BRAND NEW (Feb 2026)! Latest DeepLearning.AI course. Move workflow logic OUT of prompts into reusable "Skills" (structured folders). Works across Claude.ai, Claude Code, Claude API, and Claude Agent SDK. Combine skills with MCP + subagents. This is the PRODUCTION pattern for reliable agents—stop putting everything in prompts! |
| 1️⃣3️⃣ | 🆕🤖 Claude Code: A Highly Agentic Coding Assistant | DeepLearning.AI | FREE | ✅ Yes | 1-2 hours | SUPERCHARGE YOUR WORKFLOW! Taught by Anthropic. Best practices for agentic coding: context management, MCP server integration (Playwright, Figma), multi-instance parallel work. Apply to RAG chatbot, data analysis, web apps. Directly upgrades YOUR Cursor AI workflow with production patterns! |
| 1️⃣4️⃣ | 🆕🤖 Document AI: From OCR to Agentic Doc Extraction | DeepLearning.AI | FREE | ✅ Yes | 1-2 hours | FINANCE-CRITICAL! Build agentic workflows that process SEC filings, invoices, financial PDFs. Extract tables, charts, forms without losing context. Deploy serverless RAG on AWS with event-driven processing. This is YOUR competitive edge: Finance + AI document processing = top 1% of candidates! |
| 1️⃣5️⃣ | 🆕 Model Context Protocol (MCP) | Anthropic | FREE | ❌ No | 1 week | NEW INDUSTRY STANDARD! Anthropic's protocol for AI tool integration. Connect LLMs to databases, APIs, file systems. "USB-C for AI" - learn early! |
| 1️⃣6️⃣ | 🆕 IBM RAG and Agentic AI Professional Certificate | Coursera | Included | ✅ Yes | 3 months | COMPREHENSIVE AGENTIC AI! Build RAG, multimodal, agentic AI applications. LangChain, LangGraph, CrewAI, AG2 frameworks. Hands-on labs with cloud environments! |
| 1️⃣7️⃣ | 🆕🤖 AI Engineer Agentic Track: Complete Agent & MCP Course (Udemy) | Udemy | $15 | ✅ Yes | 6 weeks (17+ hrs) | ⭐ COMPREHENSIVE CAPSTONE BOOTCAMP! 175K+ enrolled, 4.7★. Build 8 REAL projects: Career Digital Twin, SDR Agent, Deep Research, Stock Picker, 4-Agent Engineering Team, Browser Operator, Agent Creator, and TRADING FLOOR CAPSTONE (4 agents, 6 MCP servers, 44 tools!). Covers ALL frameworks: OpenAI Agents SDK, CrewAI, LangGraph, AutoGen, MCP. Your FLAGSHIP portfolio project! |
| 1️⃣8️⃣ | 🆕📜 Anthropic Claude Certified Architect — Foundations (CCA-F) | Anthropic | $99* | ✅ Yes (CCA-F) | 60 Q · 120 min | 🆕 v9.0 — ANTHROPIC-NATIVE AGENTIC CREDENTIAL. Blueprint maps 1:1 to your stack: agentic orchestration (27%), Claude Code (20%), prompt/structured output (20%), tool design & MCP integration (18%), context/reliability (15%). Prep starts in Stage 1 (free Anthropic Academy); sit the exam here. * free for the first 5,000 Claude Partner Network employees; public registration signaled. |
| 1️⃣9️⃣ | 🆕📜 NVIDIA-Certified Professional: Agentic AI LLMs (NCP-AAI) | NVIDIA | Verify | ✅ Yes (NCP-AAI) | Self-paced prep | 🆕 v9.0 — PLANNED, PROFESSIONAL-TIER AGENTIC CAPSTONE. Agent architecture, multi-agent design, RAG, and AI safety — the bullseye credential for your Agentic AI Engineer capstone. Verify current fee/exam code on the NVIDIA Certification Center. |
📝 Side note — review the DeepLearning.AI catalog: The specific DeepLearning.AI courses you need are already listed individually across Stages 1, 3, and 4. DeepLearning.AI ships new short courses frequently, so periodically check the DeepLearning.AI course catalog for new agentic / eval / LLM-inference courses worth adding — rather than tracking a generic "series."
💡 Strategy: Short DeepLearning.AI courses (1-2 hrs each, FREE) build your knowledge rapidly. Then the Udemy bootcamp ties everything together with 8 production projects. The IBM cert runs in parallel for resume credibility. Total new investment: ~$15 (Udemy sale)!
| Platform | Cost | Weekly Target | Purpose |
|---|---|---|---|
| HuggingFace Hub | FREE | Fine-tune 1 model/week | Practice with LLMs, publish models, build reputation |
| Claude API | $5 credits | Build 1 demo/week | Learn prompt engineering, RAG, function calling |
| OpenAI API | $5 credits | Experiment daily | Learn GPT-4 capabilities, embeddings, fine-tuning |
| Pinecone | FREE tier | Build RAG apps | Vector database for semantic search, RAG systems |
| ArXiv | FREE | Read 2 papers/week | Stay current with LLM research: GPT-5, Llama 4, Gemini, etc. |
💡 Strategy: Master modern LLM tools and frameworks - ZTM updates faster than Coursera for bleeding-edge AI!
| Platform | Cost | When to Use | Specific Activities & Goals |
|---|---|---|---|
| FreeCodeCamp | FREE | Limited use (FCC weak on LLMs) |
OCCASIONAL USE: • Use for algorithm optimization for inference speed • System design patterns for LLM apps Time: 1-2 hrs/week (low priority) Why: FreeCodeCamp doesn't have deep LLM content yet - focus on ZTM instead! |
| DataCamp | NOT USED | SKIP in Stage 4 | NO SUBSCRIPTION: DataCamp's LLM content lags behind ZTM and Coursera Better alternatives: ZTM + Hugging Face docs + hands-on projects 💰 Focus budget on: Cloud credits for LLM deployment instead! |
| Zero to Mastery ⭐ CRITICAL FOR MODERN LLMs |
Already subscribed ($279/year) |
Months 30-34 (Entire LLM stage!) |
CUTTING-EDGE LLM TRAINING: • "ChatGPT Complete Guide" - Prompt engineering mastery (20 hrs) • "LangChain and OpenAI with Python" - Build production LLM apps (25 hrs) • "Vector Databases & RAG Systems" - Modern LLM architecture (15 hrs) Time: 8-10 hrs/week Output: Modern LLM applications using latest tools & patterns Why: ZTM updates FAST for AI/LLM - more current than Coursera! Their LLM courses use 2025-2026 best practices! |
| Hugging Face 🤗 Essential LLM Platform |
FREE | Months 30-34 (Throughout stage) |
COMMUNITY & PRACTICE: • Deploy 3-5 models to Hugging Face Spaces • Fine-tune open-source LLMs • Contribute to discussions • Build reputation in LLM community Time: 4-6 hrs/week Output: Public LLM demos + community credibility Why: Hugging Face profile = resume for LLM engineers! |
💰 Stage 4 Platform Investment: ZTM $0 (already subscribed) + Hugging Face FREE = $0 additional!
🎯 Key Focus: Build production LLM apps with 2025-2026 tools - your portfolio should look cutting-edge!
📌 Credential note (ZTM = evidence, not credential): Zero to Mastery here is skills & project evidence — hands-on practice and portfolio material — not a resume credential. ZTM issues certificates of completion (non-accredited), which carry no recruiter/ATS recognition. Your verifiable credentials come from Coursera (IBM/Google), DeepLearning.AI, and proctored certification exams. On your resume/LinkedIn, list ZTM as skills demonstrated / projects built — never under certifications.
💡 Strategy: Evolve 4 Stage 1 projects into agentic AI systems + build 1 new LLM evaluation project. This is where your projects become autonomous, multi-agent systems — the pinnacle of 2026 AI engineering!
| Month | Project Name | Skills Demonstrated | Where to Showcase |
|---|---|---|---|
| Month 30 | 🧠 PolicyPulse — Stage 4 Agentic HR Assistant |
LangChain/LangGraph orchestration, Pinecone vector DB migration, multi-agent (retriever + verifier + responder), voice interface | • GitHub (same repo) • HuggingFace Space • Demo video |
| Month 31 | 📄 FormSense — Stage 4 Multi-Agent Document Processor |
Multi-agent system (Extractor + Validator + Router agents), MCP integration for email sending, form history RAG for cross-referencing | • GitHub (same repo) • Live demo • Conference talk proposal |
| Month 32 | 📺 StreamSmart — Stage 4 Full Automation Agents |
LangGraph agents for cancel/resubscribe automation, MCP tool integration, multi-agent orchestration — "Tell me what to do" → "Do it for me" | • GitHub (same repo) • Live deployment • Case study |
| Month 33 | 🚀 AFC (Flagship) — Stage 4 Agentic Trading Assistant |
Multi-agent architecture (named patterns): Researcher → Analyst → Risk Manager → Executor — implements orchestrator-workers + sequential patterns from Anthropic's "Building Effective Agents." Each worker calls tools via MCP servers (SEC, Yahoo, news APIs). Evaluator-optimizer loop for self-correction. Web browsing, human checkpoints, memory. | • GitHub (same repo) • Live demo • Blog series • Conference talk |
| Month 34 | LLM Evaluation Framework 🆕 New LLM Project 🧪 ADVANCED HALLUCINATION DETECTION |
Custom benchmarks, LLM-as-judge, performance metrics, safety testing — applies to ALL portfolio projects. Advanced hallucination detection: SelfCheckGPT (consistency-based — sample N responses, score divergence as hallucination signal — works without external knowledge bases) + FActScore (atomic-fact decomposition + retrieval verification — gold standard for fact-grounded financial analysis). Critical for AFC's elevated 0.9 faithfulness threshold. | • GitHub • Open source contribution • Blog series • Apply to AFC + PolicyPulse |
| Month | Learning Focus (Evenings) | Building (Weekends) | Career Actions |
|---|---|---|---|
| Month 30 | • LLM fundamentals • Prompt engineering • RAG architecture • Vector databases |
• Project #1: RAG system • Experiment with APIs • Try different LLMs |
• Take on LLM projects at work • Start LLM-focused blog • Network in AI communities |
| Month 31 | • Fine-tuning techniques • LoRA, QLoRA • Model evaluation • Deployment strategies |
• Project #2: Fine-tuned LLM • Publish to HuggingFace • Create demo apps |
• Update LinkedIn: "LLM Engineer" • Speak at local meetups • Contribute to LLM projects |
| Month 32 | • LLM agents • LangGraph/CrewAI • Tool use & function calling • Multi-step reasoning |
• Project #3: Multi-agent system • Build advanced demos • Write technical articles |
• Apply to LLM roles: 15-20/week • Target: OpenAI, Anthropic, startups • Practice LLM interviews |
| Month 33 | • Production LLM systems • Monitoring & observability • Cost optimization • Safety & alignment |
• Project #4: Production app • Deploy at scale • Monitor performance |
• Apply: 20-25 LLM roles/week • Interview actively • Build reputation in LLM space |
| Month 34 | • Advanced topics: - Constitutional AI - RLHF - Red teaming • Interview prep |
• Project #5: Evaluation framework • Open source contributions • Polish portfolio |
• GOAL: LLM ENGINEER OFFER! • Negotiate $150-200K • Transition to LLM role • Celebrate your journey! 🎉 |
🔗 Implementation: The Attention-Flow Catalyst (AFC) project serves as the primary implementation. See AFC Stage 4 in the Portfolio Projects section above (multi-agent Researcher → Analyst → Risk Manager → Executor).
🔥 Crucible (second flagship) here: Phase 3 begins in Stage 4 — autonomous live execution at micro-sizing on Alpaca and/or your Schwab/TOS account, with a deterministic execution core wrapped by multi-agent oversight (regime-selector → risk-manager → trade-journalist → fund-manager review). The same LangGraph/agent-pattern skills built for AFC apply directly. Hard, code-enforced guardrails (daily max loss, two-loss rule, kill switch) and live-vs-modeled reconciliation. Note: real capital; treated as research validation, not income — no positive-expectancy claim.
🎯 Goal: BUILD YOUR AI TRADING ASSISTANT! Use LLMs to create an intelligent system that analyzes markets, generates insights, and executes trades based on your signals!
Why This is PERFECT Timing: You now have ML models (Stage 3) + LLM skills (Stage 4) = AI assistant that UNDERSTANDS trading!
| Book Chapters | Topics Covered | What You'll Build | Skills Applied |
|---|---|---|---|
| Chapters 17-19 (Months 30-32) |
• Reinforcement Learning for trading • Q-learning & DQN • Policy optimization • Multi-agent systems • LLMs for market analysis |
• RL trading agent (DQN) • LLM market analyst (RAG + news) • Multi-agent trading system • Sentiment-driven strategies • AI risk manager |
• LLM prompt engineering • RAG architecture • Agent orchestration • Fine-tuning LLMs • Vector databases |
| Chapter 20 (Months 33-34) |
• Production trading systems • Execution algorithms • Risk management with AI • Real-time monitoring • Regulatory compliance |
• COMPLETE AI TRADING ASSISTANT: - Natural language interface - Analyzes market conditions - Generates trading signals - Executes trades automatically - Risk monitoring & alerts |
• LangChain/LangGraph • Function calling • Production LLM systems • API integration • Real-time processing |
🤖 Build: "GenAI-Powered Trading Assistant" - Your CAPSTONE Project!
💰 This is a GAME-CHANGER:
| Component | Technologies Used |
|---|---|
| Data Layer | AWS data platform (Stage 2) + real-time feeds + alternative data |
| ML Models | Your Stage 3 models (XGBoost, LSTM, sentiment) + RL agent |
| LLM Brain | Claude/GPT-4 with RAG + fine-tuned model + prompt engineering |
| Agent System | LangGraph multi-agent: Analyst, Risk Manager, Executor |
| Interface | Chat UI (Streamlit/FastAPI) + mobile app + Telegram bot |
| Execution | Broker APIs (Alpaca, IBKR) + order management system |
| Monitoring | Real-time dashboards, alerts, performance tracking, cost optimization |
⏰ Time Allocation: 16 hours/week out of 25 total study hours
🎯 Priority: Position as LLM expert + build AI community presence + land LLM engineer role!
| Platform | Time/Week | Recruiter Exposure | What To Do |
|---|---|---|---|
| 30 min/day (3.5 hrs/week) |
⭐⭐⭐⭐⭐ MAXIMUM |
Update to "LLM Engineer": • Connect with LLM researchers, engineers • Post about AI Trading Assistant progress • Share LLM projects & learnings • Use #LLM #GenerativeAI #AI hashtags • Target: OpenAI, Anthropic, AI startups • Engage with AI thought leaders |
|
| Twitter/X (NEW!) |
20 min/day (2.5 hrs/week) |
⭐⭐⭐⭐⭐ CRITICAL |
LLM Community is HERE: • Follow: Karpathy, Sam Altman, researchers • Share LLM projects (#BuildInPublic) • Engage with AI threads • Post AI Trading Assistant updates • Many LLM companies recruit via Twitter! |
| GitHub | 1 hr, 4x/week (4 hrs/week) |
⭐⭐⭐⭐⭐ HIGH |
Showcase LLM Systems: • AI Trading Assistant repo • RAG implementations • Fine-tuned models • Multi-agent systems • Contribute to LangChain, LlamaIndex |
| HuggingFace Forums + Discord |
2 hrs/week | ⭐⭐⭐⭐ HIGH |
Center of LLM Community: • Share your fine-tuned models • Ask technical questions • Contribute to discussions • Network with researchers • Some companies recruit here! |
| LangChain Discord | 2 hrs/week | ⭐⭐⭐⭐ MEDIUM-HIGH |
Agent Development Hub: • Learn advanced patterns • Share AI Trading Assistant architecture • Get help with multi-agent systems • Network with LangChain users |
| Reddit: r/LocalLLaMA r/ChatGPT r/artificial |
1 hr/week | ⭐⭐⭐ MEDIUM |
Stay Current: • Learn about new models • Discover tools for LLM dev • Share your projects • Job postings occasionally |
| AI Engineer Community (Discord) |
2 hrs/week | ⭐⭐⭐⭐ MEDIUM-HIGH |
Practical AI Engineering: • Learn production LLM patterns • Share your architecture • Network with AI engineers • Job opportunities posted! |
| AI Summit + LLM Meetups |
Monthly (4 hrs/month avg) |
⭐⭐⭐⭐⭐ MAXIMUM |
In-Person Networking: • Local LLM/AI meetups • Virtual AI conferences • Practice explaining your project • Companies actively recruit! |
| Metric | Target by Month 34 | Why It Matters |
|---|---|---|
| LinkedIn Connections | 600+ (300 LLM/AI focused) | LLM network for opportunities |
| Twitter Followers | 200+ engaged followers | LLM companies recruit via Twitter |
| HuggingFace Models | 3+ published models | Shows LLM expertise publicly |
| LLM Blog Posts | 8+ technical articles | Position as LLM expert |
| Conference/Meetup Talks | 1+ presentation given | HUGE visibility boost! |
| GitHub AI Trading Assistant | Complete, documented, promoted | Flagship project showcases everything! |
Month 32-34: Submit talk proposals to:
Why This Matters:
| Milestone | Target | Done? | Date |
|---|---|---|---|
| HuggingFace NLP Course Complete | Month 32 | ||
| Karpathy Neural Networks Complete | Month 33 | ||
| 🏆 PolicyPulse — Stage 4 (LangGraph + Pinecone + Multi-Agent) | Month 30 | ||
| 🏆 FormSense — Stage 4 (Multi-Agent Document Processor) | Month 31 | ||
| 🏆 StreamSmart — Stage 4 (LangGraph Cancel/Resubscribe Agents) | Month 32 | ||
| 🏆 AFC (Flagship) — Stage 4 (Agentic Trading Assistant) | Month 33 | ||
| 🏆 LLM Evaluation Framework (New LLM Project) | Month 34 | ||
| HuggingFace Models Published | 3+ by Month 34 | ||
| LLM Blog Posts/Tutorials | 8+ by Month 34 | ||
| Open Source Contributions (LLM projects) | 5+ PRs | ||
| Conference Talk or Meetup Presentation | 1+ by Month 34 | ||
| LLM Job Applications | 50+ by Month 34 | ||
| LLM ENGINEER JOB SECURED! | Month 33-34 | ||
| Salary Upgrade to $150-200K | Month 34 | ||
| 🤖 TRADING: AI TRADING ASSISTANT COMPLETE! | Month 34 | ||
| 📈 TRADING: Read Chapters 17-20 (Book) | Month 34 | ||
| 📈 TRADING: RL Trading Agent (DQN) | Month 32 | ||
| 📈 TRADING: LLM Market Analyst with RAG | Month 31 | ||
| 📈 TRADING: Multi-Agent System Built | Month 33 | ||
| 📈 TRADING: Auto-Execution via Broker API | Month 34 |
| Priority | Book Title | Author | Edition/Year | Why Important |
|---|---|---|---|---|
| ⭐ MUST BUY | Build a Large Language Model (From Scratch) | Sebastian Raschka | 1st Edition (2024) ~$60 |
Brand new book (2024!) specifically for LLM implementation. Covers LLM architecture from ground up, training and fine-tuning, GPT-style models, and production deployment. Written by renowned ML educator Sebastian Raschka. Perfect timing for your Stage 4 LLM specialization. This is THE book for understanding how LLMs actually work under the hood. |
| ⭐ MUST BUY | AI Engineering | Chip Huyen | 1st Edition (2025) ~$60 |
2025 EDITION! Production-ready AI systems roadmap. Covers the full lifecycle of AI applications: from prototyping to production. LLM evaluation, RAG systems, fine-tuning decisions, and scaling. Written by the industry expert on ML systems. Essential for building real-world AI applications! |
| ⭐ MUST BUY | Generative AI with LangChain (2nd Edition) | Ben Auffarth & Leonid Kuligin | 2nd Edition (2025) ~$60 |
UPDATED FOR LANGGRAPH! LLMs with external tools/databases/APIs, RAG implementations, multi-agent workflows, production deployment patterns. Covers LangGraph (beyond just LangChain). Perfect companion for your agentic AI projects! |
| Recommended | Natural Language Processing with Transformers | Lewis Tunstall, Leandro von Werra, Thomas Wolf | 1st Edition (2022) ~$60 |
Official book from the Hugging Face team. Comprehensive coverage of transformers library, BERT, GPT, fine-tuning, and deployment. Practical approach with code examples. Excellent for learning to work with pre-trained models and the Hugging Face ecosystem you'll use daily. |
| Optional | Designing Machine Learning Systems | Chip Huyen | 1st Edition (2022) ~$55 |
Production ML systems design. Covers MLOps, deployment, monitoring, and scaling. Useful for understanding how to deploy LLM systems in production. Good bridge between ML engineering and LLM production work. |
💰 Stage 4 Book Investment: $180-295 (1 must-buy, 2 optional)
📖 When to Buy: Purchase "Build a Large Language Model" at Month 30. Work through it systematically while building your LLM projects. The book teaches you to build LLMs from scratch - perfect complement to your courses.
⚙️ Important Note: LLM field moves VERY FAST. Beyond these core books, rely heavily on: Hugging Face documentation (always updated), arXiv papers (latest research), GitHub repos (cutting-edge implementations), and online tutorials. Physical books for foundations, online resources for latest techniques.
💡 Study Strategy: Implement everything from Raschka's book from scratch. Don't just copy code - understand each component. Then use Hugging Face book to learn production-ready implementations. Build your AI Trading Assistant using both approaches.
37 Months Ago: Bookkeeper in financial services
TODAY: Senior LLM Engineer earning $180-250K+ with advanced expertise and global opportunities!
Before you stop taking courses, there's ONE more that separates Senior Engineers from everyone else:
| Order | Course Name | Platform | Cost | Certificate? | Duration | Why This Course |
|---|---|---|---|---|---|---|
| 1️⃣ | 🆕🤖 Automated Testing for LLMOps (DeepLearning.AI) | DeepLearning.AI | FREE | ✅ Yes | 1 hour | ⭐ THE "CIRCLE OF EVALUATION"! Write an AI that GRADES your other AI. Build CI/CD pipelines for LLM apps using CircleCI. Catch hallucinations, data drift, harmful output automatically. Endorsed by Andrew Ng: "addresses a key issue—how to quickly evaluate and build trust in LLM outputs." THIS is the Senior Engineer skill that separates you from hobbyists. $200K+ roles REQUIRE this! |
| 2️⃣ | 🆕📜 NVIDIA-Certified Professional: Generative AI LLMs (NCP-GENL) | NVIDIA | Verify | ✅ Yes (NCP-GENL) | Self-paced prep | 🆕 v9.0 — STAGE 5 CAPSTONE CREDENTIAL (first cert in this stage). Professional-tier: design, train, and fine-tune LLMs with distributed-training and optimization strategies. Recommended 2–3 yrs hands-on — a natural Senior-LLM-Engineer capstone. Verify fee on the NVIDIA Certification Center. |
| Focus Area | Activities | Goal |
|---|---|---|
| Research & Innovation | • Read cutting-edge papers • Experiment with latest models • Contribute to research • Publish findings |
Become thought leader in LLM space |
| Leadership | • Mentor junior engineers • Lead LLM projects • Present at conferences • Technical decision-making |
Position for senior/staff roles |
| Specialization | • Deep dive into specific area (e.g., multimodal LLMs, alignment, agents) • Build reputation in niche • Open source leadership |
Become go-to expert in specialty |
| Network & Community | • Speak at conferences • Write influential blog posts • Build Twitter/LinkedIn presence • Organize meetups |
Expand opportunities, build brand |
💡 Strategy: Focus on BUILDING and NETWORKING, not courses. Use platforms for community engagement, not learning!
| Platform | Cost | Focus | Activities & Goals |
|---|---|---|---|
| FreeCodeCamp | FREE | Minimal use | GIVE BACK: • Write technical articles/tutorials • Help beginners in forums • Contribute to open source curriculum Time: 1-2 hrs/week Why: Build reputation by teaching others! |
| DataCamp | NOT USED | SKIP | NO VALUE AT THIS STAGE: You're beyond DataCamp's level - focus on building, not courses! Better use of time: Build consulting clients + trading system deployment |
| Zero to Mastery | Keep subscription ($279/year) |
Community networking | USE THE COMMUNITY, NOT COURSES: • Network in ZTM Discord • Share your projects/wins • Help other students • Stay updated on latest AI tools Time: 2-3 hrs/week (community only) Why: ZTM community = networking opportunities + job leads! Note: Cancel if budget tight - you're done with learning, focus on DOING! |
| Twitter/X 🔥 Critical for LLM Engineers |
FREE | Thought leadership | BUILD YOUR BRAND: • Share LLM insights & learnings • Engage with AI community • Live-tweet experiments • Connect with founders/VCs Time: 3-5 hrs/week Output: 1,000+ followers in AI community Why: Twitter = where LLM opportunities happen! Senior roles come from network! |
| Hugging Face | FREE | Public presence | SHOWCASE EXPERTISE: • Deploy production-grade models • Create popular Spaces • Write model cards • Get stars/downloads on models Time: 4-6 hrs/week Why: Your Hugging Face = your resume. Top models = consulting clients! |
💰 Stage 5 Platform Investment: ZTM $70 (optional 3 months) = $0-70 total
🎯 Reality Check: At this stage, your "learning" happens by building and shipping, not taking courses!
| Project/Activity | Impact |
|---|---|
| Open Source LLM Tool/Library | Create widely-used tool in LLM ecosystem (e.g., evaluation framework, RAG library) |
| Research Paper Implementation | Reproduce SOTA results, create accessible implementation, educate community |
| Conference Presentation | Present at major AI conference (NeurIPS, ICML, ACL) or industry event (AI Summit) |
| Technical Blog Series | In-depth tutorial series that becomes go-to resource (like Karpathy-style) |
| Consulting/Advisory | Advise startups on LLM strategy, side income $5-15K/month |
💡 Strategy: All 4 multi-stage projects reach their final production form. This is where demo projects become production SaaS, integrated enterprise systems, and revenue-generating platforms.
| Month | Project Name | Skills Demonstrated | Where to Showcase |
|---|---|---|---|
| Month 35 | 🧠 PolicyPulse — Stage 5 (FINAL) Production SaaS |
Multi-tenant architecture, RBAC, Slack/Teams integration, LLMOps evaluation pipeline, A/B testing retrieval strategies | • GitHub (same repo) • Live SaaS demo • Case study |
| Month 35 | 📄 FormSense — Stage 5 (FINAL) Enterprise Integration |
OnBase integration, real-time processing, multi-form-type support, LLMOps evaluation pipeline with extraction accuracy benchmarks | • GitHub (same repo) • Enterprise demo • Technical whitepaper |
| Month 36 | 📺 StreamSmart — Stage 5 (FINAL) Consumer Product |
Production SaaS, LLMOps evaluation, monetization model, mobile app, user accounts, payment integration | • GitHub (same repo) • Product Hunt launch • Revenue metrics |
| Month 36-37 | 🚀 AFC (Flagship) — Stage 5 (FINAL) Production AI Trading System |
Production deployment, LLMOps evaluation, AI trading system monetization ($2-50K/mo potential), performance dashboards | • GitHub (same repo) • Live trading demo • Revenue tracking • Conference keynote |
🔗 Implementation: The Attention-Flow Catalyst (AFC) project reaches its final production form here. See AFC Stage 5 in the Portfolio Projects section above (production deployment, monetization, LLMOps evaluation).
🎯 Goal: Scale your AI Trading Assistant to production, monetize it, and establish yourself as a leader in GenAI-powered finance!
Why This Matters: Transform your capstone project into a revenue-generating business or consulting offering!
| Focus Area | What You'll Do | Outcome |
|---|---|---|
| Production at Scale (Month 35) |
• Deploy AI assistant to production • Handle 100+ concurrent users • Sub-100ms response times • 99.9% uptime • Cost optimization (<$500/month) |
Production-grade system ready for real users/clients |
| Advanced Features (Month 36) |
• Multi-asset support (stocks, forex, crypto, commodities) • Social trading features • Mobile app (iOS/Android) • Advanced risk management • Compliance & reporting |
Feature-complete platform competitive with commercial products |
| Monetization (Month 37) |
• Option 1: SaaS product ($49-199/month tiers) • Option 2: Consulting ($150-300/hr) • Option 3: Manage capital for clients (2&20 fees) • Option 4: Open source + consulting/support |
$2-10K/month passive income OR $20-50K/month consulting! |
Your Complete Journey - Data to Dollars:
| Stage | What You Built | Portfolio Value |
|---|---|---|
| Stage 1 | Market data dashboard with technical indicators | Shows data analysis skills + domain knowledge |
| Stage 2 | Production data platform (AWS-based) | Demonstrates cloud architecture + DE skills at scale |
| Stage 3 | ML trading models (5+ models + ensemble) | Proves ML expertise with real-world financial application |
| Stage 4 | AI Trading Assistant (complete system) | FLAGSHIP PROJECT - combines everything you learned! |
| Stage 5 | Production SaaS / Consulting Business | MONETIZED PROJECT - actual revenue generator! |
Choose Your Path (or combine them!):
| Path | What You Offer | Revenue Potential | Time Investment |
|---|---|---|---|
| SaaS Product | AI Trading Assistant as subscription service | $2-10K/mo (passive) | High upfront, low ongoing |
| Consulting | Build custom AI trading systems for clients | $20-50K/mo | Active (hourly billing) |
| Fund Management | Manage client capital using your AI system | $50K-500K/yr (2&20 fees) | Medium (requires compliance) |
| Education | Courses, workshops on AI trading systems | $5-20K/mo | Medium (content creation) |
| Hybrid | Open source tool + premium support + consulting | $10-30K/mo | Flexible - best of all worlds! |
This Project Makes You Attractive For:
💎 The Unique Advantage: You're one of the FEW people who can:
This combination is EXTREMELY rare and HIGHLY valuable! 🏆
⏰ Time Allocation: 15-20 hours/week out of 25 total
🎯 Priority: Thought leadership + consulting clients + revenue generation + community building!
| Platform | Time/Week | Impact | What To Do |
|---|---|---|---|
| LinkedIn (Leader Position) |
30 min/day (3.5 hrs/week) |
⭐⭐⭐⭐⭐ CONSULTING CLIENTS |
Position as Expert: • Post thought leadership content • Share AI trading system insights • Engage with industry leaders • Open to consulting inquiries • Mentor junior engineers publicly • Clients will reach out! |
| Twitter/X (Build Following) |
30 min/day (3.5 hrs/week) |
⭐⭐⭐⭐⭐ MASSIVE REACH |
Grow Your Audience: • Daily AI/trading insights • Thread your learnings • Engage with AI community • #BuildInPublic your business • Target: 1000+ followers by Month 37 |
| Your Blog/ Newsletter (NEW!) |
4 hrs/week | ⭐⭐⭐⭐⭐ SEO + AUTHORITY |
Content Creation: • Weekly newsletter: "AI Trading Systems" • Technical tutorials • Case studies from your system • Substack or Medium • Clients + job offers will come! |
| YouTube Channel (Optional) |
6 hrs/week (if you do it) |
⭐⭐⭐⭐⭐ HUGE VISIBILITY |
Video Content: • AI trading system tutorials • LLM development walkthroughs • Project deep dives • Can generate consulting leads • Monetization via ads + sponsorships |
| GitHub (Open Source Leader) |
3 hrs/week | ⭐⭐⭐⭐⭐ CREDIBILITY |
Lead Projects: • Maintain popular repos • Accept PRs, mentor contributors • Create reusable tools/libraries • GitHub sponsors potential • Showcase expertise |
| Organize Meetups (Leadership!) |
8 hrs/month (2 hrs/week avg) |
⭐⭐⭐⭐⭐ COMMUNITY LEADER |
HUGE Career Boost: • Organize local LLM/AI meetup • Invite speakers, companies • Build your network exponentially • Known as "the LLM person" • Consulting opportunities flow! |
| Podcast Guest Appearances |
2 hrs/month (as opportunities arise) |
⭐⭐⭐⭐ CREDIBILITY |
Share Your Journey: • Pitch yourself to AI/trading podcasts • "From Bookkeeper to LLM Engineer" • Unique story = interesting guest • Exposure to new audiences |
| Conference Speaking (Expert Position) |
1-2 talks/year (prep time varies) |
⭐⭐⭐⭐⭐ EXPERT STATUS |
Ultimate Positioning: • Major conference talks • "Building Production AI Trading Systems" • Companies approach you directly • Consulting at premium rates • You're now a recognized expert! |
| Revenue Stream | How Community Helps | Time to Revenue | Potential |
|---|---|---|---|
| SaaS Product | Your audience becomes users. Twitter/blog for marketing. | Month 36-37 | $2-10K/mo |
| Consulting | LinkedIn + talks = inbound leads. No cold outreach needed! | Month 35+ | $20-50K/mo |
| Courses/Workshops | Newsletter audience + YouTube subscribers = ready buyers. | Month 36+ | $5-20K/mo |
| Sponsorships | Blog/YouTube/newsletter audience = sponsor opportunities. | Month 37+ | $2-5K/mo |
| Advisory Roles | Conference talks + expertise = startups approach you. | Month 36+ | $5-15K/mo |
| Metric | Target by Month 37 | Business Impact |
|---|---|---|
| LinkedIn Connections | 1,000+ (AI/finance leaders) | Consulting network |
| Twitter Followers | 1,000+ engaged | Audience for products/services |
| Newsletter Subscribers | 500+ engaged readers | Direct marketing channel |
| YouTube Subscribers | 1,000+ (if you do it) | Video content monetization |
| Conference Talks | 2+ major talks given | Expert positioning |
| Meetup Organization | Host 6+ events | Local network leadership |
| Inbound Opportunities | 5+ consulting inquiries/month | Revenue generation! |
| Revenue from Content/Community | $2-30K/month | Beyond salary income! |
Why Stage 5 Community Work is CRITICAL:
By Month 37:
Total Potential Income by Month 37:
Base Salary: $180-250K + Consulting: $20-50K/mo + Content: $2-10K/mo
= $400-700K+ per year! 🚀💰
| Milestone | Target | Done? | Date |
|---|---|---|---|
| 🏆 PolicyPulse — Stage 5 FINAL (Production SaaS + LLMOps) | Month 35 | ||
| 🏆 FormSense — Stage 5 FINAL (OnBase Integration + LLMOps) | Month 35 | ||
| 🏆 StreamSmart — Stage 5 FINAL (Consumer SaaS + Monetization) | Month 36 | ||
| 🏆 AFC — Stage 5 FINAL (Production AI Trading System) | Month 37 | ||
| Published Open Source LLM Project | Month 35 | ||
| Conference Talk Accepted | Month 36 | ||
| Technical Blog Series (10+ posts) | Month 37 | ||
| Mentored Junior Engineers | 2+ by Month 37 | ||
| Led Major LLM Project at Work | Month 36 | ||
| LinkedIn Followers (AI/LLM focused) | 1,000+ by Month 37 | ||
| Research Paper Reproduced | 1+ by Month 37 | ||
| Consulting Clients | 2-3 by Month 37 | ||
| SENIOR LLM ENGINEER STATUS | Month 37 | ||
| Salary: $180-250K+ | ACHIEVED ✅ | ||
| 🚀 TRADING: PRODUCTION SYSTEM DEPLOYED! | Month 37 | ||
| 📈 TRADING: All Book Chapters Complete (1-20) | Month 37 | ||
| 📈 TRADING: Multi-Asset Support (Stocks/Forex/Crypto) | Month 36 | ||
| 📈 TRADING: Mobile App Deployed | Month 37 | ||
| 💰 TRADING: MONETIZATION ACTIVE ($2-50K/mo) | Month 37 |
Why this is a separate section: this pathway is employer-focused, not part of the vendor-agnostic career roadmap above. Daybright is a confirmed Microsoft/Azure + Entra shop (Intune-managed devices, AzureAdJoined: YES; Microsoft 365 Copilot runs on Azure OpenAI), so these Azure/Copilot credentials are reimbursable via the Financial Industry Professional Education Program and grow you toward an internal AI-builder role.
Reimbursement mechanics: none of these are on Daybright's pre-approved schedule, so each goes through the case-by-case path — email learning@daybright.com with manager sign-off before incurring cost, framed as professional development. Exam fee + required study materials are reimbursed for the first two attempts. No completion bonus (bonuses attach only to the finance/actuarial/securities certs).
| Roadmap Timing | Credential | Code | Cost | Purpose |
|---|---|---|---|---|
| Stage 1 (now) | Azure AI Fundamentals | AI-901 | $99 | Foundation; cheapest and easiest first approval; proves the reimbursement path works. (Refreshed exam expects some hands-on Foundry/Python.) |
| Stage 1 (parallel) | Applied Skills: Declarative Agents in VS Code | — | Free | Hands-on, code-first (VS Code + M365 Agents Toolkit + TypeSpec); MCP-capable. Closest to your "no vibe coding" principle. Nothing to reimburse — do it now. |
| Stage 2 (optional) | Fabric Data Engineer Associate | DP-700 | $165 | Azure-native counterpart to your AWS DE cert — SQL/PySpark/KQL on Microsoft Fabric, running on Daybright's stack. |
| Stage 3 | AI Agent Builder Associate | AB-620 | $165 | Building agents on Copilot Studio — Daybright's actual AI tool. Covers RAG, MCP servers, A2A, multi-agent, Foundry. Ties to your Month-14 MCP sprint + PolicyPulse FastMCP server. |
| Stage 4 | Azure AI Apps & Agents Developer Associate | AI-103 | ~$165 | Portable Azure AI-developer capstone (successor to the retired AI-102): Foundry + Python + generative-AI apps + agents. In beta — verify code/price on Microsoft Learn. |
Recommended order: AI-901 first (prove the benefit path) → free Applied Skills lab in parallel → AB-620 as the flagship reimbursed exam → AI-103. Employer-reimbursed, so $0 net to you (gross ~$594 tracked in the investment table).
⚠️ Timing: AI-102 and AI-900 retired June 30, 2026 — use the AI-103 / AI-901 successors. AI-103 is in beta (delayed scoring, ~2–3 months to results).
All courses below sit under one ZTM membership (the $299/yr annual plan in the pre-approval email — also the on-ramp to ZTM's free-lifetime challenge: 1 new lecture/month for 30 months → lifetime access). The Azure Bootcamp is the anchor (Daybright's exact Azure/Foundry stack); the rest build the AI-engineering and automation skills behind the Microsoft Agent Framework + Copilot work. All bundled in ZTM's "Become an AI Engineer" career path.
| ZTM Course | What it builds (for Daybright automation) | Ties to |
|---|---|---|
| ⭐ Azure Bootcamp: Build AI Workflows & Agents with Microsoft Foundry | Foundry fundamentals → enterprise AI workflows, agents & human-in-the-loop automations on Azure — Daybright's exact stack. The anchor course. | AI-901 + AI-103 · MAF |
| The AI Agents Bootcamp | Multi-agent automation with CrewAI / LangGraph / MCP; gates agent actions behind human approval (matches your human-in-the-loop safety rule). | AB-620 · Crucible |
| AI Engineering: Building AI Apps with LangChain | LLM apps, RAG, embeddings, LangGraph agents — core AI-engineering build skills. | PolicyPulse · AFC |
| Prompt Engineering Bootcamp | Structured prompting & autonomous-agent basics — foundational across all the above. | All stages |
Also on ZTM (search the course catalog): an MCP course + a FastAPI → MCP-server course (feed your PolicyPulse FastMCP server and the Microsoft Agent Framework), plus Claude Code for DevOps and Self-Hosted AI with Ollama — aligned to your model-routing lanes (finance data local on Ollama; Anthropic/cloud for public work), both usable as providers inside the Microsoft Agent Framework.
| Metric | Month 0 (TODAY) | Month 37 (GOAL) |
|---|---|---|
| Role | Bookkeeper | 🎯 Senior LLM/AI Engineer |
| Salary Progression | ~$90K bookkeeper | Month 5: $65K (Analyst) Month 15: $90K (DE) Month 29: $135K (ML) Month 37: $200K+ (LLM) ✅ |
| Location | US | Remote Global (full flexibility!) |
| Skills | Bookkeeping, Excel, basic business | Expert: SQL, Python, Cloud (AWS Certified), ML Math, DL, LLMs, RAG, Fine-tuning, MLOps |
| Portfolio | None | 20+ projects: 4 DA + 5 DE + 5 ML + 5 LLM + open source contributions |
| Certifications | None | 24+ (Google DA, AWS DE Certified, Neo4j Certified Professional, NVIDIA NCA-GENL / NCP-AAI / NCP-GENL, Databricks GenAI Engineer Associate, Anthropic CCA-F, TensorFlow, Math for ML, Coursera certs) — plus separate Employer Track (Azure AI-901, AB-620, AI-103, DP-700) |
| Network | Limited | 1,000+ AI/ML professionals, conference speaker, thought leader |
| Freelance Income | $0 | $15K-30K total from Upwork + consulting |
| Job Security | Limited (single employer) | EXTREMELY HIGH - Top 1% in-demand skill globally |
| Math Foundation | None | SOLID - Linear algebra, calculus, understand ML from first principles |
| Life Stability | Stagnant, seeking growth | Stable, thriving, fully established! |
| Category | Amount |
|---|---|
| Coursera Plus (already owned) | $0 |
| Stage 1: Certifications | $80 |
| Stage 2: PostgreSQL, PySpark, Airflow courses | $45 |
| Stage 2: AWS Certified Data Engineer - Associate | $150 |
| Stage 3: TensorFlow Certificate | $100 |
| Stage 4: LangChain course | $15 |
| 🆕 v9.0 Roadmap Certs (Section B — personal): | |
| Stage 3: NVIDIA NCA-GENL (Generative AI LLMs) | $125 |
| Stage 3: Databricks GenAI Engineer Associate | $200 |
| Stage 4: Anthropic Claude Certified Architect (CCA-F) | $99* |
| Stage 4: NVIDIA NCP-AAI (Agentic AI — planned) | Verify |
| Stage 5: NVIDIA NCP-GENL (Generative AI LLMs — planned) | Verify |
| 🏢 Employer Track (Section A — reimbursed): AI-901 $99 · AB-620 $165 · AI-103 ~$165 · DP-700 $165 (opt) · Applied Skills free | $0 net (~$594 gross, reimbursed) |
| Books & Resources | $90 |
| Misc (conferences, networking) | $50 |
| TOTAL INVESTMENT | $954+ personal · Employer track $0 net (~$594 reimbursed) |
| Salary Increase (annual) | +$90K-160K/year |
| Freelance Revenue (total) | $15K-30K |
| NET ROI | 20,000-30,000% |
| Priority | Book Title | Author | Edition/Year | Why Important |
|---|---|---|---|---|
| Reference | Staff Engineer: Leadership Beyond the Management Track | Will Larson | 1st Edition (2021) ~$40 |
Essential for senior/staff engineer transition. Covers technical leadership, influence without authority, architectural decision-making, and career progression. You're becoming a SENIOR engineer - this teaches you how to operate at that level. |
| Optional | The Staff Engineer's Path | Tanya Reilly | 1st Edition (2022) ~$45 |
Another excellent senior engineering book. Covers technical leadership, navigating complex organizations, and driving large-scale projects. Good complement to Larson's book with different perspective. |
| Optional | AI Engineering | Chip Huyen | 1st Edition (2025) ~$60 |
Brand new AI engineering book (released 2025). Covers building and deploying AI systems at scale. Excellent for understanding production AI architecture. |
💰 Stage 5 Book Investment: $0-145 (All optional - focus on doing, not reading)
📖 When to Buy: Stage 5 is about DOING, not learning from books. The leadership books are optional but valuable for senior role transition. Buy only if you want guidance on technical leadership.
⚙️ Critical Point: At this stage, you should be learning from: Production work experience, conference talks, research papers (arXiv), open-source contributions, building your own systems, and mentoring others. Books are supplementary. Your real education comes from shipping production LLM systems.
💡 Focus Strategy: Spend your time building, not reading. Your AI Trading Assistant should be in production. Focus on: System architecture, performance optimization, cost management, monitoring, and scaling. Lead technical discussions at work. Contribute to open source. Write blog posts. Speak at meetups. Build your reputation as a senior LLM engineer through DOING.
🎯 Better Investments Than Books: Conference tickets ($500-1000), online courses on specific advanced topics ($50-200), GPU cloud credits for experimentation ($100-500), domain name + hosting for portfolio ($50/year).
| Advantage | Why It Matters |
|---|---|
| Income Security | Employed from Month 5 - never unemployed throughout 37-month journey |
| Progressive Learning | Each role builds on previous - natural skill progression without gaps |
| Optimized DE Courses | Sequenced learning + AWS deep prep BEFORE certification = higher pass rate & retention |
| Math Foundation | Learned at optimal time (Month 16) - makes ALL ML/LLM work clearer and deeper |
| AWS Certification | Official AWS Certified Data Engineer badge = massive resume boost! |
| Risk Mitigation | Career foothold established fast (Month 5), then steady climb with income safety net |
| Domain Expertise | Bookkeeping background gives you edge for data analyst roles |
| Real Experience | Learn by doing in real jobs, not just courses - better than bootcamps |
| Network Building | Build professional network at each stage - valuable connections |
| Market Positioning | By Month 37, you're senior engineer with 2+ years experience at each level + AWS Certified |
🎯 Purpose: Reinforce Coursera learning with hands-on practice, build portfolio-quality projects, and master interview skills!
| Stage | FreeCodeCamp | DataCamp | Zero to Mastery | Stage Total |
|---|---|---|---|---|
| Stage 1: DA (Months 1-5) | FREE DS&A + Data Viz |
$25/mo × 5 $125 |
$39/mo × 2 $78 |
$203 |
| Stage 2: DE (Months 6-15) | FREE APIs + Databases |
$25/mo × 5 $125 |
Included $0 |
$125 |
| Stage 3: ML (Months 16-29) | FREE ML Projects |
SKIP | Included $0 |
$0 |
| Stage 4: LLM (Months 30-34) | Minimal | SKIP | Included $0 |
$0 |
| Stage 5: Senior (Months 35-37) | Give Back | SKIP | Optional $0-70 |
$0-70 |
| TOTAL | FREE | $250 (10 months) |
$279-349 (1-2 year sub) |
$528-598 |
💡 Platform Strategy by Stage:
🎯 Why These Platforms Are Worth It:
📌 Credential note (ZTM = evidence, not credential): Zero to Mastery here is skills & project evidence — hands-on practice and portfolio material — not a resume credential. ZTM issues certificates of completion (non-accredited), which carry no recruiter/ATS recognition. Your verifiable credentials come from Coursera (IBM/Google), DeepLearning.AI, and proctored certification exams. On your resume/LinkedIn, list ZTM as skills demonstrated / projects built — never under certifications.
| Stage | Must-Buy Books | Optional Books | Total Investment |
|---|---|---|---|
| Stage 1: DA (Months 1-5) | • Python for Data Analysis ($60) • Data Smart ($35) |
• Python Crash Course ($40) | $95-135 |
| Stage 2: DE (Months 6-15) | • Fundamentals of Data Engineering ($60) • Designing Data-Intensive Applications ($60) |
• Data Pipelines Pocket Reference ($30) | $120-150 |
| Stage 3: ML (Months 16-29) | • Hands-On Machine Learning ($65) | • Intro to ML with Python ($50) • Hundred-Page ML Book ($40) |
$65-155 |
| Stage 4: LLM (Months 30-34) | • Build a Large Language Model ($60) | • NLP with Transformers ($60) • Designing ML Systems ($55) |
$60-175 |
| Stage 5: Senior (Months 35-37) | None (focus on doing!) | • Staff Engineer ($40) • Staff Engineer's Path ($45) • AI Engineering ($60) |
$0-145 |
| TOTAL | 6 must-buy books across 4 stages | $340-760 | |
💡 Smart Buying Strategy:
📊 Total Learning Investment (37 Months):
| Coursera Plus | $530 | (all online courses) |
| Supplemental Platforms | $528-598 | (DataCamp 10 months + Zero to Mastery + FreeCodeCamp FREE) |
| Books (must-buy) | $340 | (6 essential books) |
| Books (optional) | $0-420 | (if you want all optional books) |
| TOTAL INVESTMENT | $1,398-1,888 | 37 months to $200K salary! |
| ROI | 10,000-14,000%+ return on investment! | |
🎯 Why These Books Matter:
These aren't just textbooks - they're career investments. Each book was chosen because it's THE definitive reference for that stage. Written by industry leaders and practitioners. You'll reference them for years. The $340 in must-buy books will save you hundreds of hours of searching for information and prevent costly mistakes. Physical books also force you to slow down, take notes, and deeply understand concepts - something online courses alone can't provide.
You have the COMPLETE roadmap.
You have ALL 5 stages mapped out.
You have the timeline (37 months with income security!).
You have the resources (Coursera Plus + optimized courses).
You have the strategy (analyst → DE → ML → LLM).
You have the PROPER COURSE ORDER (learn→certify→succeed!).
You have the MATH foundation (learned at optimal time!).
You have AWS CERTIFICATION strategy (deep learning THEN certification!).
You have the support (this guide!).
All you need is ACTION.
Start with Month 1: SQL + Python basics
Build your first project by Month 2
Launch Upwork by Month 2
Start applying by Month 3
Get hired by Month 5
Learn DE in perfect sequence (Months 6-15)
Get AWS Certified (Month 12)
Learn math in Month 16 (perfect timing!)
Build your AI Trading Assistant!
Let's make you a Senior LLM Engineer! 🚀
Document Version: ROADMAP v9.2 (Course Alignment) - GenAI/LLM-Enhanced Path + Production Portfolio
Created: November 17, 2025 | Updated: July 7, 2026
Structure: 5 Stages | 37 Months | Beginner → Data Analyst → DE → ML → LLM
Investment: $954+ personal (Employer track $0 net, ~$594 reimbursed) | ROI: 20,000%+
* CCA-F is free for the first 5,000 Claude Partner Network employees.
Key Optimizations:
• NEW v9.2: 🛡️ PERSONAL-STATUS LANGUAGE NEUTRALIZED — removed/reworded 8 mentions of uncertain visa/immigration status across the doc (Stage 1 timeline note, "37 Months Ago" line, and the Month 0 vs Month 37 transformation table: Role, Location, Job Security, Risk Mitigation, and Life Stability rows). Before-state framing kept intact and neutral (e.g., "Limited (single employer)", "Stagnant, seeking growth"); no immigration/visa/citizenship references remain. Content/wording change only; no course rows, certs, or structure changed. ✅
• NEW v9.1: 📌 ZTM = EVIDENCE, NOT CREDENTIAL — added a reusable credential note to each stage's Platform Usage Strategy box (Stages 1-4) and to the Supplemental Platforms Investment Summary. Clarifies that Zero to Mastery is skills & project evidence (non-accredited certificate of completion, no recruiter/ATS recognition), while verifiable credentials come from Coursera (IBM/Google), DeepLearning.AI, and proctored certification exams. Additive-only; no course rows or tables changed. ✅
• NEW v9.0: 🎓 CERTIFICATION EXPANSION (Section B — roadmap-integrated) — recruiter-recognized exams added to the stages where they belong: Stage 3 → NVIDIA NCA-GENL ($125) + Databricks GenAI Engineer Associate ($200); Stage 4 → Anthropic Claude Certified Architect CCA-F ($99; blueprint maps 1:1 to the agentic/MCP stack) + NVIDIA NCP-AAI (Agentic, planned); Stage 5 → NVIDIA NCP-GENL (first Stage-5 cert, planned). CCA-F prep on-ramp noted in Stage 1. Stage 4 certs placed canonically in the main Core Courses table (rows 18-19), mirrored as one-line timing pointers in the recommended-order list — matching the existing IBM-cert convention. TensorFlow references left in place for change-tracking — NVIDIA added alongside, not replacing. ✅
• NEW v9.0: 🏢 EMPLOYER TRACK section added after Stage 5 — a separate, parallel Daybright Azure/Copilot pathway (AI-901, Applied Skills declarative agents, DP-700, AB-620, AI-103), reimbursable via the Financial Industry Professional Education Program under the professional-development clause. Kept separate from the vendor-agnostic roadmap by design; $0 net (employer-reimbursed, ~$594 gross). ✅
• NEW v9.0: 📚 STUDY PATH added inside the Employer Track — a curated Zero to Mastery course path (Azure Bootcamp / Microsoft Foundry anchor, AI Agents Bootcamp, AI Engineering with LangChain, Prompt Engineering, plus MCP / FastAPI and Claude Code / Ollama lane courses) mapping ZTM training to the Azure/Copilot certs (AI-901, AB-620, AI-103) and the Microsoft Agent Framework automation work. One membership ($299/yr, on-ramp to ZTM's free-lifetime challenge). ✅
• NEW v8.9: 🔌 MCP PRIMER pulled forward to Stage 1 — DeepLearning.AI "MCP: Build Rich-Context AI Apps with Anthropic" (Elie Schoppik, FREE, 1-2 hrs) added before the PolicyPulse FastMCP build so the protocol is learned before it's first built against; full Stage 4 deep-dive left in place (resequencing, not a duplicate) ✅
• NEW v8.9: 📘 TYPESCRIPT sprint resource upgraded (Month 14) — primary swapped from bare TS Handbook ch 1-4 to Total TypeScript Beginner's Tutorial + Zod Tutorial (free, Matt Pocock, exercise-driven); Zod maps directly to the MCP TS SDK's input validation. Handbook retained as reference fallback. Coursera evaluated and not used here (TS specializations are frontend/framework-heavy, off-target for a backend MCP tool) ✅
• NEW v8.8: 🔁 LOOP ENGINEERING added (Stage 4) — named the June-2026 prompt→context→harness→loop progression; added the 5 production-loop components (triggers/scheduling, layered exits, state persistence, cost caps, human-in-the-loop gates), a per-project autonomy map (AFC/FormSense unattended; Crucible keeps a human sign-off on live trades), and a best-course pick (Vanderbilt "AI Agents and Agentic AI in Python") ✅
• NEW v8.7: 🔗 AFC REVERSE-SYNC — T6 Squeeze-Context trigger (short-interest / float / days-to-cover, sourced from signalcore) + the signalcore shared-primitives library (the AFC↔Crucible boundary: parameterized, point-in-time-safe primitives both flagships import; neither imports the other) now reflected in the roadmap, matching the project scopes ✅
• NEW v8.7: 🛠️ VS Code promoted to a first-class Tools-table entry (S1–S5) with an editor-skill note — the portable, interview-relevant editor baseline Cursor is built on ✅
• NEW v8.6: 🕸️ GRAPHRAG / KNOWLEDGE-GRAPH ARCHITECTURE added — Stage 2 capstone upgraded to a real Neo4j hybrid (vector + graph) retriever; GraphRAG skill line added with honest cost caveat (vector stays the backbone) ✅
• NEW v8.6: 🎓 GraphRAG courses added — Stage 2 intro: DeepLearning.AI "Knowledge Graphs for RAG" (SEC-filings demo); Stage 3 deepen: Neo4j GraphAcademy → Neo4j Certified Professional (+ Agentic KG Construction) ✅
• NEW v8.6: 🔗 PolicyPulse tagged with a Stage 2/3 GraphRAG hybrid upgrade path (multi-hop policy questions / groundedness) ✅
• NEW v8.5: 🧰 CORE TOOLCHAIN overview section added near the top (all-stages hybrid stack with per-stage badges) — prominent recruiter-facing index of local-first + cloud tools ✅
• NEW v8.5: 🦙 SELF-HOSTED & LOCAL-FIRST AI TOOLCHAIN section added to Stage 1 — OpenCode (agentic coding in Cursor), Ollama + LM Studio (on-device LLMs), AnythingLLM (self-hosted RAG workspace) ✅
• NEW v8.5: 🔀 PROVIDER-AGNOSTIC MODEL-ROUTING documented — local Qwen3.5 (Ollama) for private planning, cloud (MiniMax M3 / GLM-5.2 via OpenRouter) for heavy builds ✅
• NEW v8.5: 🔒 PRIVACY-FIRST ARCHITECTURE framed as a recruiter differentiator (finance/proprietary → on-device; public research → cloud) ✅
• NEW v8.4: 🤖 Building with the Claude API (Anthropic Academy) added to Stage 1 — provider source-of-truth for the Claude SDK (official cert) ✅
• NEW v8.4: 🧪 Improving Accuracy of LLM Applications added to Stage 1 (build eval framework + simulate hallucinations) ✅
• NEW v8.4: ✍️ AI Prompting for Everyone added to Stage 1 (2026 refresh of dated ChatGPT PE course) ✅
• NEW v8.4: ⚡ Fast & Efficient LLM Inference with vLLM added to Stage 3 (local inference + quantization — nearest formal cert for the Ollama/Qwen3 local-LLM skill) ✅
• NEW v8.4: 🧭 Evaluating AI Agents added to Stage 4 (agent observability + LLM-as-judge) ✅
• NEW v8.4: 🗄️ Dated 2023 OpenAI-era courses (ChatGPT PE, Building Systems, LangChain for LLM App Dev) moved to a new Stage 1 "Archived / Superseded" table — kept for documentation ✅
• NEW v8.4: 🧹 Removed 5 duplicate course listings from Stage 4 Core Courses (canonical entries retained in Stages 1–3) ✅
• NEW v8.4: 🧹 Removed dated cert rows (ChatGPT PE, Building Systems, LangChain) from the Stage 4 Progress Tracker (already in Stage 1 Archived table) ✅
• NEW v8.4: 🧹 Removed duplicate course-milestone rows (Vector DBs, Finetuning, Generative AI with LLMs, generic "DeepLearning.AI LLM Courses 5+") from the Stage 4 Progress Tracker — these courses are tracked in their canonical Stages 2–3 ✅
• NEW v8.4: 🔗 Replaced generic "LLM Series by DeepLearning.AI" catalog link in Stage 4 with a catalog-review side note (specific DLAI courses already listed across stages) ✅
• NEW v8.3: 🛠️ 1099 PIPELINE flagged for v8.2 retro-migration (pyproject.toml + py.typed + Docker) ✅
• NEW v8.3: 🔌 MCP SERVER added to PolicyPulse Stage 1 (FastMCP exposing retrieval tools) ✅
• NEW v8.3: 🤖 ANTHROPIC SDK as primary provider for PolicyPulse + AFC (provider-agnostic preserved) ✅
• NEW v8.3: 🧩 AFC Stage 4 named with "Building Effective Agents" patterns (orchestrator-workers + sequential + evaluator-optimizer) ✅
• NEW v8.3: 📜 TYPESCRIPT + MCP SERVER SPRINT added to Stage 2 Month 14 (2 weeks, ~30 hours) ✅
• NEW v8.3: 🔗 A2A PROTOCOL detail expanded in Stage 4 (Linux Foundation Agentic AI Foundation, Dec 2025) ✅
• NEW v8.3: 🧪 SELFCHECKGPT + FACTSCORE added to Stage 4 LLM Evaluation Framework (financial-grade rigor) ✅
• v8.2: 🧪 DEEPEVAL EVALUATION FRAMEWORK added to all 7 project scopes (evaluation-driven development) ✅
• v8.2: 🐳 DOCKER SUPPORT added to all 7 project scopes (Dockerfile + containerization) ✅
• v8.2: 📦 Docker for Beginners course added to Stage 1 (Month 5) ✅
• v8.2: 🔍 Building & Evaluating Advanced RAG course added to Stage 1 (FREE) ✅
• v8.2: ☸️ Docker & Kubernetes Masterclass added to Stage 2 (Months 12-13) ✅
• v8.2: 📊 BigQuery Basics + Coursera RAG course added to Stage 2 ✅
• v8.2: ❌ TensorFlow Developer Certificate REMOVED (discontinued May 2024) → replaced with NVIDIA DLI ✅
• v8.2: 🔄 IBM GenAI cert clarified as Stage 1 primary, Stage 2 reinforcement ✅
• 🏆 7 PRODUCTION-GRADE PORTFOLIO PROJECTS with scoped architecture documents ✅
• 🔄 4 MULTI-STAGE PROJECT EVOLUTIONS (PolicyPulse, FormSense, StreamSmart, AFC) spanning all 5 stages ✅
• 🚀 ATTENTION-FLOW CATALYST integrated as primary algorithmic trading implementation across all stages ✅
• Start with Data Analyst (4-5 months) instead of Data Engineer (9 months) ✅
• CS50 Computer Science fundamentals in Stage 1 ✅
• Statistics with Python Specialization (University of Michigan) ✅
• IBM Data Analyst Professional Certificate (11 courses!) ✅
• 4 critical LLM courses added to Stage 4 ✅
• 📈 ALGORITHMIC TRADING PROJECT integrated across all 5 stages ✅
• 🌍 COMMUNITIES ENGAGEMENT & RECRUITER EXPOSURE sections for each stage ✅
• 📅 CUSTOM STUDY SCHEDULE - 25 hrs/week with specific time blocks ✅
• 💻 SUPPLEMENTAL PLATFORMS (FreeCodeCamp + DataCamp + Zero to Mastery) ✅
• Stage 2: Optimized course order (concepts → SQL → databases → AWS → cert → big data → orchestration)
• AWS Professional Certificate BEFORE certification exam ✅
• PostgreSQL, PySpark, Airflow added for complete DE skillset ✅
• Mathematics for ML in Stage 3 (Months 16-17) for solid foundation ✅
• Total timeline: 37 months
Result: 8 production-grade repos (1 deployed), 5 multi-stage project evolutions, IBM + Google + AWS certifications, comprehensive LLM training, PLUS two complete AI trading systems (AFC + Crucible) AND strategic community presence!
🏆 Portfolio Architecture:
• Stage 1: 8 production-grade repos (ETL → AI analytics → RAG → Multimodal → Enterprise → Consumer → AFC Flagship → Crucible Flagship)
• Stage 2: 4 evolved DE repos + 1 new Airflow project
• Stage 3: 4 evolved ML repos + 2 new ML projects (tabular + NLP)
• Stage 4: 4 evolved agentic repos + 1 LLM Evaluation Framework
• Stage 5: 4 production SaaS/enterprise deployments + monetization
📈 Algorithmic Trading Journey (via Attention-Flow Catalyst):
• Stage 1: Walk-forward backtest engine + AI dashboard (Phase 1A + 1B)
• Stage 2: AWS S3, Airflow orchestration, 500+ tickers at scale
• Stage 3: XGBoost, LSTM, MLflow model tracking
• Stage 4: Multi-agent trading system (Researcher → Analyst → Risk Manager → Executor)
• Stage 5: Production deployment & monetization ($2-50K/mo potential!)
🔥 Autonomous Intraday Journey (via Crucible — second flagship, started first):
• Stage 1 (Phase 1): Own event-driven backtest harness + AI research loop + sealed OOS vault; IT-1 ORB + VWAP Reclaim strategy plugins; local-first LLM (Qwen3/Ollama)
• Stages 2–3 (Phase 2): Migrate to NautilusTrader (engine-parity gate); autonomous paper-trading agent crew (LangGraph); paper-vs-backtest parity validation
• Stages 3–4 (Phase 3): Live micro-sizing on Alpaca + Schwab/TOS; deterministic execution core with multi-agent oversight (regime → risk → journalist → fund-manager)
• Distinct from AFC: liquid intraday execution vs. illiquid small-cap swing research; ~70% shared engineering spine — the shared layer is signalcore (parameterized, point-in-time-safe primitives: volume/accumulation, dilution, short-interest, relative-strength, validation; both flagships import it, neither imports the other)
🌍 Community Strategy:
• Stage 1: LinkedIn + GitHub + Kaggle (job focus)
• Stage 2: Add AWS community + DE meetups
• Stage 3: Kaggle competitions + ML conferences
• Stage 4: Twitter/X + HuggingFace + conference talks
• Stage 5: Thought leadership + consulting clients + revenue!
Your future self will thank you for starting today! 💚🚀
"The best time to plant a tree was 20 years ago. The second best time is now."
You're not just learning tech - you're building a transformative career with the BEST preparation. Let's go! 🚀
End of document. Official plan: v10.0 sections above the Archive. Back to top ↑