12-Hour Crash
Junior AI Systems Engineer • Remote BD • US Hours

Portfolio projects that prove this exact job.

Build one project that demonstrates APIs + LLM + data + documentation together.

12-hour crash planBDT 50k-70k / monthRemote BD • US hoursDiagrams + quiz per module
Fast-learner loop (use for every module): 1) Look at the diagram first — get the shape. 2) Read once, fast. 3) Say it out loud in 30 seconds. 4) Take the quiz. Anything you miss, re-read only that part.

Build ONE of these well (better than three half-done)

Project A • Best fit

AI Ticket Classifier Pipeline

Webhook/API ingest → queue → LLM classify to JSON → store in SQLite/Postgres → simple report page. Golden-set eval script included.

APIs LLM DB Webhooks

Project B

Invoice / Document Extractor

Upload text/PDF text → structured JSON extraction with validation → CSV export. Shows prompt engineering + schema discipline.

Prompting JSON schema

Project C

n8n + Code Automation

n8n workflow (form → AI classify → Google Sheet/DB → Slack/email) + one step done in code. Shows low-code + code judgement.

n8n Integrations

Project D

RAG FAQ Assistant

Embed a small docs set → retrieve → answer with citations. Even 20 documents is enough to demo chunking & retrieval clearly.

RAG Embeddings

48-hour build plan (Project A)

BlockDeliverable
Hours 0–4Repo, README skeleton, API endpoint + webhook receiver, .env.example
Hours 4–10LLM classify with JSON schema + validation + retry
Hours 10–16DB storage, dedupe by event id, queue/background processing
Hours 16–24Golden set (30 examples) + eval script printing accuracy
Day 2Report page, error handling, SOP doc, demo video/GIF, polish README

README that gets you shortlisted

Hands-on labs (90 min each)

  1. Webhook lab: Receive, verify signature (HMAC), dedupe, return 200 fast, process async.
  2. Rate-limit lab: Call a public API in a loop; implement backoff + caching.
  3. Prompt lab: Same task, 3 prompt versions; score all on 20 examples.
  4. AI-coding lab: Add a feature with Claude Code/Codex; keep the diff + tests to show in the interview.
flowchart TD IN["Input: ticket text
via API / webhook"] --> API["API endpoint
validate + dedupe"] API --> Q["Queue"] Q --> LLM["LLM classify
temperature 0, JSON schema"] LLM --> VAL{"Valid +
confident?"} VAL -->|Yes| DB[(SQLite / Postgres)] VAL -->|No| HQ["Human queue /
retry once"] HQ --> DB DB --> REP["Report page
counts by category"] LLM -.-> EV["Eval script
golden set accuracy"]
Figure 11 — Project A architecture. If you can draw and explain this, you can answer half the technical interview.

Test yourself

Module 5 Test — Projects & Labs (self-check)

Tap an answer — explanation appears instantly. Pass mark: 70%. Retake until you pass.

One strong portfolio project beats three half-done because…

Why: Depth + documentation + eval results is what gets you shortlisted.

Your README must contain…

Why: A senior-readable README is a hiring signal for this documentation-heavy role.

Golden set is for…

Why: Evals for model behaviour; unit tests for code. You need both.

0 / 3 correct