{
  "url": "https://job.help/en/hack/backend-90day-bootcamp",
  "title": "Backend in 90 Days — A Non-CS Hacker's Bootcamp (2026 Edition)",
  "summary": "A focused 90-day route to one deployed backend project, using AI tools for repetition and feedback without treating them as a substitute for fundamentals.",
  "pillar": "hack",
  "locale": "en",
  "datePublished": "2026-05-05",
  "dateModified": "2026-05-05",
  "author": "Learn Desk",
  "sources": [],
  "body_markdown": "## Why 90 days\n\nNinety days is not a promise to replace a full academy or bootcamp, master the fundamentals, or secure a job. It is a deliberately narrow sprint: one language, one framework, and **one deployed project you can explain without the AI beside you**. Use copilots for repetitive work and fast feedback, but prioritize review, tests, and a written record of failures. Continue filling foundational gaps after the sprint.\n\n## The 90 days, in 4 phases\n\n| Phase | Window | Deliverable |\n|---|---|---|\n| Phase 1 — Environment | Week 1~2 | Local + cloud + Git wired, AI copilot loop habituated |\n| Phase 2 — Language & Framework | Week 3~6 | One language + one framework feel native to your fingers |\n| Phase 3 — Real project | Week 7~11 | One service an outside user can run |\n| Phase 4 — Resume & apply | Week 12~13 | Resume, portfolio, and an application-response log |\n\n## Phase 1 — Environment\n\n- VS Code + Cursor + GitHub Copilot or Claude Code\n- WSL2 (Windows) or macOS as a baseline\n- A 3-minute mental model of HTTP, DNS, and TLS — depth comes later\n- The AI pair-programming loop: **you choose the structure, AI scaffolds, you review.**\n\nIf you stall in week 1, the 90 days collapse. Force yourself to complete one full cycle — `git clone → run locally → push → deploy` — before the first week ends.\n\n## Phase 2 — Language & Framework\n\nThree tracks. Pick one, then 4 weeks of total commitment.\n\n| Track | Best fit | Core stack |\n|---|---|---|\n| **Node.js** | Broad server ecosystem; verify against target listings | TypeScript + NestJS or Hono |\n| **Python** | AI/data adjacency | FastAPI + Pydantic |\n| **Go** | Infra & high-perf | Gin + sqlc |\n\n**Decision-paralysis rule**: 2 hours of debate; if undecided, choose Node.js. Move.\n\nWeekly artifacts:\n- Week 3: single-route API with one DB table CRUD\n- Week 4: auth + middleware + error handling\n- Week 5: external API + queue (OpenWeather, Telegram, etc.)\n- Week 6: tests + Docker + GitHub Actions CI\n\n## Phase 3 — Real project\n\nThis is the inflection. Build for **one defined user and one recurring workflow**, then recruit a small number of testers. Avoid arbitrary user or revenue targets and do not treat a to-do clone as proof by itself.\n\nReasonable categories:\n- A career×AI tool (a niche workflow automated for one profession)\n- A small SaaS that processes payments end-to-end\n- An open-source library shipped on npm or PyPI\n\nProject checklist:\n- Auth (email + OAuth)\n- DB schema + migrations\n- API surface (REST or tRPC)\n- Payments (Stripe or Toss)\n- Deploy + custom domain + HTTPS\n- README + usage docs + 60-second demo\n\n**Decision rule**: add payments only when the chosen problem needs them. Implement test-mode failures and refunds, then document the trade-off. Payments do not guarantee stronger hiring outcomes; observability, security, or tests may be the more useful depth signal.\n\n## Phase 4 — Apply\n\n- Compare resume and job-description language → [/resume](/resume)\n- GitHub contribution graph + pinned repos cleaned up\n- English LinkedIn profile (apply globally too)\n- A sustainable weekly application cap, with job, resume version, and response logged\n\nThe week before interviews, record and review your own answers, then use the interview guides in [/match](/match) to check evidence, length, and structure.\n\n## Common traps\n\n| Trap | Fix |\n|---|---|\n| 10 courses, 0 projects | Force one project per course — uncompleted projects = zero value |\n| Urge to switch language mid-track | Track chosen in week 3 is locked through week 11 |\n| Interview answers stuck at \"I studied X\" | Lead with project trade-offs and decisions you made |\n| Resume = certs + courses list | Rewrite around quantitative results (users, revenue, perf) |\n\n## What JOB.HELP gives you along the way\n\nThe tools learners hit most during these 90 days:\n\n- **[/match](/match)** — interview and cover-letter guides (Phase 4)\n- **[/resume](/resume)** — local resume/job-description phrase comparison; not an official ATS score or hiring prediction\n- **[/tools](/tools)** — AI playbooks per profession (developer edition)\n- **[/agents](/agents)** — review/test/CI agent catalog\n\nNinety days is short. Reduce scope and leave a working artifact every week. The final test is not whether you can call yourself a developer, but whether you can explain your design choices and failure record in your own words.\n\n## Evidence and reference material\n\n- [Stack Overflow Developer Survey 2025 — reported AI-tool use and sentiment](https://survey.stackoverflow.co/2025/ai)\n- [GitHub research — a bounded Copilot task-completion experiment and its method](https://github.blog/news-insights/research/research-quantifying-github-copilots-impact-on-developer-productivity-and-happiness/)",
  "citation": {
    "publisher": "JOB.help",
    "suggested": "JOB.help, \"Backend in 90 Days — A Non-CS Hacker's Bootcamp (2026 Edition)\" (2026-05-05), https://job.help/en/hack/backend-90day-bootcamp"
  }
}