← Learn · Roadmap · 1 August 2026 · 7 min

25 Projects To Build To Get Hired in 2026

25 portfolio projects reverse-engineered from what YC and Accel are funding in 2026 — MCP servers, eval harnesses, agent infrastructure, and physical-world data. Ranked beginner to hard, with the hiring signal each one sends.

Reverse-engineered from what YC (Fall/Summer 2026 RFS) and Accel are funding — because that's what the companies hiring you are building.

Why this list looks different: models are commoditised. The moat moved to harnesses, evals, agent-native infrastructure, and physical-world data. Hiring managers in 2026 scan for production signals — how you handle failure, what you measured, what you deleted. A repo with a published eval score beats a demo video.

Instant reject pile: wrapper chatbots, chat-with-your-PDF, to-do app with a GPT button, sentiment analysis on tweets.

Beginner (8)

Weekend to two weeks. Each one teaches a 2026-relevant primitive, not a tutorial.

1. MCP server for a tool nobody has wrapped yet

Expose a niche API (your gym's booking system, a transit feed, a university portal) over Model Context Protocol. MCP went to the Linux Foundation in Dec 2025 and is now the default integration layer.

→ Signal: you can design an API for agents, not humans. Almost every AI team is doing this right now.

2. Eval harness for your own prompts

A CLI that runs prompts against a fixed test set on every commit and fails the build on regression.

→ Signal: the single biggest gap in the industry — 89% of teams with production agents have observability, only 52% have evals. Say that number in an interview.

3. Deepfake-aware "prove you're human" widget

Liveness challenge + device attestation + a signed proof, drop-in. A finance worker recently wired $25M to a video call where every other participant was a deepfake.

→ Signal: security thinking + cryptographic primitives. Rare in junior portfolios.

4. Semantic diff tool for changelogs

Watches an API's OpenAPI spec, detects breaking changes, posts a plain-English summary to Slack.

→ Signal: structured extraction from noisy text, and that you understand what actually breaks production.

5. Local-first voice interface for one specific task

Not an assistant. One job — logging medication, capturing site notes, stock counts — on-device.

→ Signal: latency budgets and offline inference. Everyone can call an API; few can hit a latency target.

6. Sensor → dataset pipeline

Put a cheap sensor somewhere nobody measures (air quality on your street, soil moisture, noise) and publish a clean, versioned, public dataset with an API.

→ Signal: real data engineering, not Kaggle. And you now own data nobody else has.

7. Agent-readable version of a website

Take a site built for human eyes, generate the machine-native surface: structured endpoints, llms.txt, a CLI. YC's line: "Machines do not require GUIs."

→ Signal: you understand why browser-clicking agents are a hack.

8. One-command deploy for single-user apps

Auth, DB, domain, done. YC's A Cloud for Small Software RFS: small software is now trivial to build and still painful to ship.

→ Signal: DevOps and the boring 80% of software. Interviewers probe this and most candidates fold.

Medium (9)

Two to six weeks. This is the tier that actually converts to offers — big enough to have hard tradeoffs, small enough to finish.

9. Multiplayer agent session

Multiple people watch, redirect and hand off the same long-running agent, Figma-style. YC's Multiplayer AI RFS: AI hasn't had its Google Docs moment.

→ Signal: realtime systems (CRDTs, streaming) + product taste. A very strong senior-track project.

10. Vertical AI operating system for one trade

HVAC, tree surgery, marine repair — quoting, scheduling, invoicing, routing work between a human and an agent. YC funded Kebra (S26) for exactly this.

→ Signal: full-stack shipping against a real workflow. Best project if you're targeting vertical-AI startups (there are hundreds hiring).

11. Agent-native compliance monitor

Watch a regulator's filings, diff them, map changes to obligations, generate the audit trail. YC's AI-Native Compliance Infrastructure.

→ Signal: you can build something auditable and explainable, not vibes-based. Fintech and regtech hire on this.

12. Dependabot for APIs

Vendor ships a breaking change → agent scans the codebase, finds affected usages, opens the PR. From YC's Self-Maintaining APIs (30%+ of AWS service downtime traced to unnoticed external changes).

→ Signal: AST parsing, codegen, safe automated changes. Dev-tools companies will interview you on sight.

13. Agent memory with actual forgetting

Most "memory" is a vector store that only grows. Build decay, contradiction resolution, and provenance on every fact.

→ Signal: context engineering — which has replaced prompt engineering as the core AI-engineer skill.

14. Adaptive tutor for one skill, taught properly

Not flashcards. Model what the learner misunderstands, generate the next task from that. YC's The Primer RFS.

→ Signal: you can define and measure a success metric (learning gain) instead of shipping a feature.

15. Robot/human job router

Mixed fleet of agents, robots and people with wearables — decide who does what, and prove the routing beats a naive baseline.

→ Signal: optimisation + simulation. Strong for robotics and ops-heavy companies.

16. Stablecoin rails for agent-to-agent payments

Escrow, spend limits, revocable delegated authority. YC calls agentic commerce inevitable now regulatory clarity landed. Testnet only.

→ Signal: you can reason about trust boundaries when the actor isn't a person.

17. Inference cost profiler

Trace an agent run, attribute tokens/latency/dollars per step, flag where a smaller model would do.

→ Signal: you think about unit economics. Instantly separates you from candidates who've never seen a bill.

18. Nowcast from your own sensor data

Assimilate your sensor network into a short-horizon forecast and score it against the official one. Sorcerer (YC) does this with weather balloons; the US government buys the output.

→ Signal: honest backtesting and a real ML pipeline end to end.

Hard (8)

Months. One of these done well is a standout thesis, a research role, or a company.

19. Agent harness with deterministic replay

Any agent run replayable exactly — same tool results, same branch points — for debugging and regression.

→ Signal: distributed systems, event sourcing, sandboxing. This is the missing layer in production AI. Infra teams will fight over you.

20. Self-improving research agent

Hypothesise → design experiment → run → interpret → update, in one narrow domain where experiments are cheap. rekursiv.ai (YC S26) is building this.

→ Signal: RL and credit assignment. Research-engineer track.

21. RL environment for a real industrial process

High-fidelity simulator + reward spec a frontier lab could train against. Maingen (YC S26) does this for factories. Value is in fidelity, not the RL.

→ Signal: domain modelling and sim-to-real. Frontier labs are actively hiring for exactly this.

22. Inference scheduler for agent workloads

Agent traffic is bursty and branchy — nothing like chat. Speculative branch execution, KV-cache reuse across sibling agents, preemption.

→ Signal: memory management and systems performance. Highest-paid niche in the industry.

23. Dynamic interface generator

UI that assembles itself per user and task at runtime. YC's Dynamic Software Interfaces. Hard part isn't generation — it's stability, accessibility, and not confusing the user every session.

→ Signal: program synthesis + HCI rigour. Very few people can do both.

24. Verifiable AI output for a regulated domain

Medicine, law or finance: every claim traceable to a source, unsupported claims structurally blocked. Measure hallucination rate honestly and publish it.

→ Signal: evaluation rigour and red-teaming. Publishing your own failure rate is the strongest credibility move available to you.

25. Edge autonomy for a denied environment

Perception + decision stack with no cloud, degraded GPS, tight power. The constraint set behind YC's defense RFS and Accel's defense-tech allocation. Build the civilian version: search and rescue, agriculture, disaster response.

→ Signal: embedded systems, sensor fusion, model compression. Defense and robotics money is enormous in 2026.

How to actually convert these into a job

  • One hard project properly beats five mediums. Recruiters don't want many projects; they want a few strong, well-explained ones.
  • Publish a number. An eval score, a latency budget you hit, a cost-per-run. Numbers survive the six seconds a recruiter gives your repo.
  • Write the "what didn't work" section. A paragraph on the approach you abandoned and why signals more seniority than the feature list does.
  • Deploy it. A live URL converts. A screenshot doesn't.

Pattern across all 25: each produces proprietary data, a hard systems artifact, or a real workflow — the things models can't commoditise, and therefore the things companies still need to hire humans for.

Sources

If you want to see prompts for shipping some of these fast, there is a single-file sticky-notes app, a frosted-glass refraction cube in raw WebGL, and a drivable 3D car game.