Lesson 17Proof of Work — Brand, Projects, Products, and the Door into Silicon Valley

Welcome to Module 12 (Bonus): The Career Layer — personal brand, portfolio, products, and the path into YC/a16z/Silicon Valley startups as an LLM engineer. Fair warning: this module is blunter than the others, because career advice that hedges is worthless. Everything here assumes you've done (or are doing) the course's build exercises — this module is about converting that work into leverage.

Topic 85: Proof-of-Work — what "personal brand" actually means for engineers

Delete the influencer image. For engineers, personal brand = discoverable evidence of ability. When a YC founder or an a16z-portfolio CTO considers you, they do one thing before any interview: they look you up. Your brand is literally what they find in those ninety seconds — and the hierarchy of what counts is brutal and consistent:

Read the bottom row honestly: certificates and course completions — including this course — are approximately noise in startup hiring. Nobody at a 12-person company cares what you studied; they care what you made, whether it worked, and whether you can prove it. That's not cynicism, it's the good news: the currency is artifacts, and artifacts can be manufactured by anyone with a laptop and discipline, from anywhere on Earth — including Lahore. Geography gates offices; it does not gate proof-of-work.

Two design decisions turn scattered work into a brand:

1. Positioning — become legibly "the person who X." Generic ("AI engineer passionate about LLMs") is invisible; specific is memorable. Strong positionings sound like: "fine-tunes small models that beat frontier models on narrow tasks, and publishes the evals" — or "builds and benchmarks local-AI inference" — or "makes rigorous evals for underserved languages." Note the shape: a T — broad across this course's twelve modules (you can converse anywhere), spiked deep in one or two (you're known for something). Pick the spike deliberately; Topic 86 gives you the menu.

2. Public by default. Every project ships with a README that sells (what it does, the numbers, a GIF, how to run it), a writeup, and where possible a live demo (HF Spaces makes this free). The private repo where your best work sleeps is a brand asset earning 0%. And note what the hierarchy's top four rows share: they all contain measurements. The Module 10 discipline — publish the evals, the benchmarks, the cost math — is precisely what separates engineer-brand from AI-influencer slop, because almost nobody posting about AI brings numbers. Your differentiation is rigor made public.

---

Topic 86: The Advanced Project Portfolio — what to actually build

The heart of your request. The rule before the list: one flagship done to completion beats ten half-projects — and "completion" means the four-part ship: repo + evals/numbers + writeup + live demo. Here's the tier list, each project mapped to the course modules it proves:

Tier S — flagships. Pick ONE and go deep:

1. "My 8B beats [frontier model] on X" — the full specialist pipeline (Modules 2–3–10): build a dataset with your Topic 17 synthetic pipeline + Topic 18 curation, QLoRA + DPO it, then rigorously evaluate against a frontier model on a firewalled golden set — and publish model, dataset, eval harness, and the writeup with the numbers. Task choice is strategic: pick something underserved where beating the giant is achievable — Urdu/Roman-Urdu tasks (your unfair advantage: frontier models are genuinely weak there and you can judge quality natively), SQL generation for a schema family, domain-specific structured extraction. This project is the single strongest "LLM engineer" credential that exists below actual lab experience, because it proves the entire stack.

2. An inference-optimization project with published benchmarks (Module 4 spike): implement speculative decoding or a KV-cache/quantization technique from scratch (or contribute one to llama.cpp/vLLM), or build a "quantization quality atlas" — Q8→Q2 across 5 models × 4 task types, with a public results table. The systems-engineering audience for this is exactly the audience that hires at infra startups.

3. An agent scored on a public benchmark (Modules 7/10): a SWE-bench-lite or τ-bench submission with a serious trajectory-analysis writeup — where it failed, why, what fixed it. A middling score with brilliant failure analysis signals more engineering maturity than a demo that "usually works."

4. A rigorous eval suite for an underserved domain (Module 10 spike): e.g., a contamination-resistant Urdu benchmark, or a domain eval (regional legal/medical/financial tasks) with meta-evaluated LLM judges (Topic 75's full rigor). Evals are the most supply-constrained skill in the industry right now — labs and startups alike hire eval-obsessed people on sight, and almost nobody's portfolio demonstrates it.

5. A production-grade RAG system with ablations (Module 6): hybrid + reranker + golden set — and the part that makes it advanced: the ablation study (chunk-size sweep, reranker on/off, recall@k for each) published as a table. "I built RAG" is Tier B; "here's what each pipeline stage is worth, measured" is Tier S.

Tier A — strong supporting pieces (2–3 of these around your flagship): an MCP server for a real tool (early on a spreading standard = discoverable); a multi-tenant LoRA serving demo (one base, hot-swapped per-customer adapters — Topic 22's wardrobe, which very few people have actually built); your synthetic-data pipeline extracted as a reusable OSS tool (generation + the filtering stack); a local AI app shipped to real users (hardware-tiered, Topic 68's playbook); and the sleeper: a from-scratch reimplementation with a writeup — DPO or GRPO in 300 lines, Flash-Attention tiling in Triton, a tiny inference engine. "I built X from scratch and here's what I learned" is beloved by exactly the engineers who do hiring.

Tier B — commoditized; never flagships: generic chatbots, chat-with-your-PDF, framework-wrapper demos, prompt collections. Fine as learning exercises (you did several in this course); invisible as portfolio.

The meta-rule tying it together: choose projects that generate writing material and numbers — because Topic 88's content engine feeds on them, and Module 10's discipline is your watermark on every one.

---

Topic 87: Open-Source Strategy — becoming a known name

You already understand OSS as a contributor; this topic is OSS as career architecture. Two ladders, climb both:

Ladder 1 — contribute to the repos your future employers read. In this field, that list is specific: vLLM, llama.cpp, SGLang, TRL/PEFT/transformers, Unsloth, Axolotl, Ollama, LiteLLM, MLX-examples. Contributions here are qualitatively different from generic OSS: the maintainers and heavy users of these exact repos are the AI-infra hiring pool, and a merged PR is a work sample they've already reviewed. The realistic on-ramp (you know this ladder from your own history — it transfers directly): reproduce and triage issues → fix docs and error messages → small bugfixes → and then aim for one substantive contribution in your spike area (a kernel, a sampler feature, a quant format, an eval integration). Crucial strategic note: depth in one repo's community beats scattered PRs across ten. "Regular contributor to vLLM's quantization code" is a positioning; "47 PRs across 20 repos" is a statistic.

Ladder 2 — maintain your own. The best personal OSS is extracted from real work — the filtering pipeline you built for your flagship, the eval harness, the MCP server — because tools born from real need have real users. And here's the signal hierarchy insiders use: stars are vanity; usage is sanity; maintenance is character. Downloads, dependents, and — above all — answered issues and steady releases over months are what a senior engineer checks. A 90-star tool with 40 closed issues and 12 releases outsignals a 3,000-star flash that died in six weeks, because maintenance predicts what you'll be like as a colleague.

The compounding mechanism to understand explicitly: OSS is a distributed trust network. Every review exchange with a maintainer, every user you help, is a weak tie with someone in the industry — and startup hiring runs disproportionately on exactly these ties ("we hired her because she'd been fixing our bugs for six months"). You are not contributing code; you are accumulating witnesses.

---

Topic 88: Building Products as an Engineer — the second résumé

Module 11 taught product shapes; this topic is why an engineer chasing SV jobs should ship products anyway — and how. The core claim: a shipped product with even 50 real users is a different résumé category, because it proves the exact bundle startups hire for — you can scope, build, deploy, measure, support, and iterate end-to-end without supervision. That bundle is the founding-engineer job description; founders hiring engineer #1–5 overweight "has shipped a real product" above almost everything, including pedigree.

The playbook, compressed from Module 11: go vertical and boring (Topic 80's lesson — document automation for one niche, not another general chatbot; boring niches have paying customers and no competition from every other portfolio); run the concierge → productize sequence (Topic 81 — do it manually for five users first; you're gathering your golden set and edge cases as market research); wire unit economics from day one (Topic 77's metering — even at toy scale, practicing margin math is the point); and charge money early. The first dollar of internet revenue matters wildly out of proportion to its amount: "built and monetized an AI product" moves you into a category most engineers never enter, and gives every future interview its best story.

The portfolio-of-small-bets frame: treat products as 2–6-week builds, launched publicly (Topic 89's mechanics), then killed or doubled-down based on signal. Three honest launches a year — including the "failures" — beat one precious idea polished privately forever, because the failures are also assets: a product with 200 users, a churn problem, and a postmortem writeup demonstrates (and teaches) more real judgment than any successful tutorial-follow. Startups know their own life is exactly this loop; evidence you've run it is evidence you'll survive there.

And note the beautiful convergence: your products feed everything else in this module — they generate the writing material (89), the eval sets and data flywheels (81), the OSS extractions (87), and the proof-of-work artifacts for outreach (90). The product isn't a detour from the career path; it's the engine of it.

---

Topic 89: Distribution — writing and launching like an engineer

Artifacts that no one sees don't exist. Distribution is the multiplier on everything above — and engineers systematically underinvest in it because it feels like marketing. Reframe: it's documentation with reach, and the engineer's version has a formula:

The content engine: every project from Topics 86–88 ships as a pipeline of derivatives — the README (the salespage), the deep-dive post ("how I built it / what I measured" — write the post you needed before starting), the launch thread/post, and eventually the talk. One unit of work, four units of distribution. What performs for LLM engineers specifically — notice these are exactly your Module 10 muscles: benchmark posts with tables ("I quantized 5 models to 6 levels; here's the quality atlas"), from-scratch explainers ("DPO in 300 lines, annotated"), cost breakdowns ("what fine-tuning actually costs: $1.87, receipts attached"), failure postmortems, and measured contrarian takes ("the reranker mattered more than the embedding model: ablations inside"). The common denominator is numbers — the one ingredient the ocean of AI content lacks, and therefore your entire differentiation.

The platforms, by function: X/Twitter is the AI industry's town square — the founders, researchers, and infra engineers you want to reach are actually there, and the underrated mechanic isn't broadcasting, it's substantive replies: consistently adding measured, technical value under posts by people in your spike area builds recognition faster than shouting into your own timeline. A personal blog is the canonical, permanent, searchable home (platforms decay; your domain doesn't). Hacker News / Show HN for launches — brutal, honest, and one good thread can matter more than a year of tweets. r/LocalLLaMA and the HF community for local-AI and model work — genuinely kind, high-density audiences for exactly Tier-S projects #1, #2, and #4. LinkedIn for recruiter surface area (repost your blog; don't create for it). And talks — meetups first, conferences after; community organizing, which you already do at scale, is literally this infrastructure pre-built.

The cadence truth: one genuinely deep post per month plus consistent smaller presence, sustained for twelve months, beats any burst — because almost nobody sustains it. Consistency is the moat precisely because it's boring. And the compounding is real: post #1 gets 40 readers; post #14 gets quoted by someone whose reply-guys include three founders. The curve is flat then steep; most people quit in the flat part, which is why the steep part is uncrowded.

---

Topic 90: Landing the YC / a16z / Silicon Valley Job — the mechanics

Now the target itself. First, understand how these companies actually hire, because it's structurally different from big tech: teams of 5–50, hiring decided by founders/senior engineers in days not months, work-sample culture (they'd rather watch you build than watch you LeetCode — though some still do DSA rounds, so don't be helpless there), and referrals + inbound proof-of-work massively outperform cold applications. The role names you're hunting: AI engineer, LLM engineer, founding engineer, member of technical staff, forward-deployed engineer (FDE — engineer embedded with customers building on the product; currently one of the hottest and most accessible AI-startup roles, and a natural fit for anyone with community/DevRel DNA), and DevRel engineer.

Where the jobs physically are: YC's Work at a Startup (workatastartup.com — applications land in founders' inboxes, not ATS purgatory), the a16z portfolio job board and each portfolio company's careers page, Wellfound, the monthly HN "Who is hiring?" thread, and — underrated channel — founders announcing hires on X, where a reply with an artifact beats a hundred queued résumés.

The playbook that actually converts — proof-of-work outreach, and it's the entire module compressed into a motion:

This converts at rates that make spray-applying look broken, because you've pre-performed the work sample and demonstrated the exact behavior startups hire for: initiative on their actual product. It's also simply the same motion as Topic 87's OSS ladder and Topic 89's substantive replies — proof-of-work, aimed.

The interview loop, mapped to your curriculum: expect (a) a practical build — take-home or pairing: "build a RAG service over these docs," "get this fine-tune working," "add a tool to this agent" — Modules 3/6/7 live; (b) LLM system design — "design a support bot for 1M users: models, serving, costs, failure modes" — literally your Topics 38/70/77 capstone documents recited; (c) the project deep-dive — they will drill into your flagship to verify you built it and probe what you measured ("how did you know it improved?" — Module 10 is the separator here; candidates who answer with eval methodology are rare and get offers); (d) increasingly, eval-thinking questions outright; and (e) product sense (Topic 84 — "should this feature use AI at all?"). Notice: this course is the interview prep; the gap is only reps.

The international path — the honest sequence (for building from Pakistan toward SF): (1) Remote-first roles and contract work at these same startups exist and are won by exactly the playbook above — expect global competition and signal flexibility on timezone overlap explicitly. (2) Prove yourself remotely → relocation + sponsorship becomes a conversation with an employer who already wants you, which is the only version of the visa conversation that goes well. (3) Know the O-1 visa exists — the "extraordinary ability" route — and internalize the beautiful alignment: its evidence criteria (original contributions, press/writing, judging others' work, critical roles in distinguished organizations) are literally this module's outputs. Your OSS maintainership, published benchmarks, community leadership, and launched products are a visa case assembling itself; build with that dossier consciously in mind. (4) The founder path runs in parallel — YC accepts applications from anywhere and relocates accepted companies. And the overriding principle: don't wait for geography. The network, the repos, the launches, and half the jobs are on the internet; the flywheel spins from anywhere:

One pragmatic footnote before the ritual: when offers come, understand startup equity before signing — ask for the numbers that make options mean something (total shares outstanding, strike price, latest valuation, vesting cliff), because "0.3%" is not information without them. Founders respect the question; it signals you've been around the block you're trying to enter.

---

The 12-Month Arc — everything in this module, sequenced

Q1 — Foundation: choose your positioning (85) and flagship (86); begin the target-repo apprenticeship (87); publish two deep-dives from course work you've already done (89). Q2 — The flagship ships: all four artifacts (repo, numbers, writeup, demo); launch properly (HN + communities); land the first substantive OSS contribution. Q3 — Product + aim: the two-week concierge product, monetized (88); two more deep-dives; build the 10-startup list and run the outreach playbook on the first three (90). Q4 — Compound: second Tier-A project or double down on whatever got signal; a talk; outreach round two — now with a portfolio that speaks before you do, and an O-1-shaped paper trail accumulating quietly underneath.

Twelve months of this loop, run honestly, puts you in roughly the top percentile of candidates these companies see — not because the work is superhuman, but because the loop's power is consistency and almost nobody sustains it past month two. The models in this course were trained by gradient descent: small correct updates, relentlessly repeated, compounding into capability nobody could have hand-coded. Your career runs on the same optimizer. Same math. Start the loop.

That closes Module 12 — and now truly the full curriculum, engineering and career both. If you want, we can go one level deeper on any piece of this: drafting your actual positioning sentence, spec'ing your flagship in detail, or writing the first proof-of-work outreach note together.