Your résumé opens the door; your portfolio proves the interview is worth scheduling
Remote .NET hiring in 2025 is global: recruiters in UK, US, and EU time zones skim hundreds of profiles weekly. They will not clone your repo during the first pass. They click one live link, glance at README structure, and check whether you sound like someone who has shipped. Tutorial ToDo apps and "Contoso University" forks signal tutorial completion—not production habits. This guide lists portfolio projects that consistently earn callbacks for ASP.NET Core developers, especially from India applying internationally.
What recruiters scan in ninety seconds
- Live URL — Swagger or Blazor UI on Azure/AWS free tier; SSL working.
- README hero — Problem, stack, architecture diagram thumbnail, how to run locally in five commands.
- Commit history — Not one giant "initial commit"; sensible messages over weeks.
- Tests folder — Even ten integration tests imply discipline.
- No secrets — If .env was committed once, trust drops.
Archetype 1: Multi-tenant SaaS API (LMS or billing lite)
Build a minimal learning or subscription API: tenants, JWT auth, EF Core global filters, Stripe test mode webhook, admin metrics endpoint. Why it works: mirrors real B2B remote job work. Highlight: tenant isolation test, OpenAPI, Docker compose with SQL + Redis. Mention AI only if you added a bounded feature—e.g., quiz generation behind approval—not a chatbot glued on for buzzwords.
// README highlight — architecture
[React Admin] -> [ASP.NET Core BFF] -> [SQL + Redis]
-> [Stripe webhooks]
-> [Background worker: email]Archetype 2: Reliability story project
Take archetype 1 or a catalog API and add: health checks, structured Serilog, OpenTelemetry trace to Jaeger or Azure Monitor, GitHub Actions CI, load test screenshot (k6 or NBomber) with brief analysis. Remote employers fear offshore devs who disappear when production breaks—this project says you have operated like on-call.
Archetype 3: Integration-heavy micro-demo
Not fifteen services—two is enough. Example: Order API + Inventory API communicating via RabbitMQ or Azure Service Bus with outbox pattern documented in README. Shows distributed thinking without resume-driven Kubernetes unless you operate it live.
What to remove from portfolios in 2025
- Unmodified Udemy course clones.
- Desktop WinForms unless applying legacy maintenance roles.
- Repositories with no README and random language mix.
- Blockchain certificates with no user problem solved.
GitHub profile optimization
Pin three repos maximum. Profile README: one line value prop, links to LinkedIn and blog if any, timezone (IST) and remote preference explicit. Add CONTRIBUTING.md and issue templates to one flagship repo—signals collaboration norms remote teams expect.
Deploy cheaply but credibly
Azure Container Apps or App Service free tier, Railway, or Fly.io for API; Vercel for static admin. Custom subdomain (yourname.dev) costs little and looks intentional. Include smoke test badge from GitHub Actions in README.
Write the case study paragraph recruiters forward
Template: "Built X for Y users/problem. Stack: .NET 8, EF, Redis. Shipped Z metric: p95 200ms at 500 RPS in k6 test. Learned W when webhook idempotency failed in staging." Numbers beat adjectives.
Cover letter and application hooks
Reference their product stack if public. Link one repo anchor deep link: live demo + specific file (auth middleware). For AI-heavy companies, show a feature with evaluation notes (latency, cost per request)—not "used OpenAI."
Interview bridge from portfolio
Prepare to whiteboard the same architecture you shipped. Explain one trade-off you regret and one you would repeat. Remote screens often include take-home—your public repo quality predicts trust for small take-homes.
Time-box for employed developers
Eight weeks, six hours/week: weeks 1–2 domain model and auth; 3–4 core API; 5 deploy + CI; 6 tests + load smoke; 7 README + diagram; 8 polish and LinkedIn post. Consistency beats another unfinished repo.
Legal and ethics
Do not expose real employer code. Synthetic data only. If you open-source work paid by a client, get written permission.
Remote .NET jobs go to candidates who prove delivery online. A multi-tenant API with live deploy, tests, and a short reliability story beats ten tutorial badges—optimize for the recruiter's ninety-second click, then back it up in the interview.