Zero to Software Engineer
A 6-month job-ready program with an optional 12-month Mastery extension. Project-first: one flagship application (an LMS) is built incrementally across every module, so students carry one real system from a to-do app to a deployed, cached, search-enabled, horizontally-scalable platform.
Prerequisites
Laptop, 8GB+ RAM, stable internet.
Basic logic and arithmetic only.
20–25 hrs/week — 3+ months minimum to see Phase 1 through.
Comfortable debugging and researching independently by Month 3.
Open to BCA, MCA, B.Tech, diploma students, and career switchers — no prior coding experience required.
Milestone ladder
Frontend Mastery
Months 1 through 3. The goal is to take you from zero to React developer.
| Month | Core topics | Refinements added | Projects | Milestone |
|---|---|---|---|---|
| Month 1Fundamentals | Variables, loops, functions, arrays, objects, problem-solving, Git. | Reading error stack traces, console debugging workflow, VS Code debugger basics, not just print-debugging. | Calculator, Quiz App, Student Management System, Expense Tracker. | Can write and debug a small program from a blank file. |
| Month 2Web Dev | Semantic HTML, CSS Flexbox/Grid, DOM, Fetch API, async JS. | Accessibility basics (semantic tags, alt text, keyboard nav), Chrome DevTools network/performance tabs, a basic Lighthouse audit. | Portfolio Website, E-Commerce UI, Admin Dashboard, Movie App. | Can ship a responsive, accessible static site. |
| Month 3React + TS | Components, state, hooks, routing, Context API, TypeScript fundamentals. | React Query / TanStack Query for server state, which separates "UI state" from "server state" early, a common junior-dev confusion. Basic component testing with Vitest + React Testing Library. | LMS Frontend, E-Commerce App, Analytics Dashboard. | Can build a professional, tested frontend application. |
Weekly rhythm inside each month: weeks 1–2 are concept + guided build, week 3 is an independent build on a fresh spec, week 4 is code review + a refactor pass — introducing review culture early instead of saving it for Month 11.
Backend & Production
Months 4 through 6. The goal is to take you from React developer to production developer.
| Month | Core topics | Refinements added | Projects | Milestone |
|---|---|---|---|---|
| Month 4Node.js | Express, REST APIs, JWT auth, middleware, API design. | Input validation with Zod, structured logging (pino/winston), rate limiting on auth routes. | Authentication API, User Management API, Course Management API. | A hardened, documented REST API. |
| Month 5PostgreSQL | SQL, joins, normalization, indexing, transactions. | Connection pooling, seed/migration tooling (Prisma or Knex), EXPLAIN ANALYZE reading practice on the LMS’s own slow queries. | LMS Database, Complete LMS Backend, Progress Tracking System. | Can design a normalized schema and diagnose a slow query. |
| Month 6Docker + AWS | Docker, Docker Compose, Nginx, AWS EC2/S3/RDS/IAM, CI/CD. | Secrets management (never commit .env), a minimal GitHub Actions pipeline (lint, test, build, deploy), basic uptime/error monitoring (UptimeRobot or free-tier Sentry). | Deploy the complete LMS, Dockerized Full-Stack App, Cloud Deployment Pipeline. | Can build and deploy a complete full-stack application, and know when it’s on fire. |
The original brochure lists Docker, AWS, Nginx, and CI/CD together in one month; CI/CD is scoped down to one working GitHub Actions pipeline the student can point to, not a general DevOps deep-dive — that returns properly in Months 10–11.
System Thinking
Months 7 through 9. The goal is to take you from application developer to system designer.
| Month | Core topics | Refinements added | Challenge |
|---|---|---|---|
| Month 7Software Engineering | Clean Code, SOLID, design patterns, refactoring, testing, code reviews. | A fixed test-coverage bar on the refactor (e.g. 70%+ on core modules) so "refactor" has a checkable definition of done. | Refactor the LMS using professional engineering practices. |
| Month 8Advanced Backend | Redis caching, rate limiting, background jobs, RabbitMQ, WebSockets, Elasticsearch. | A cache-invalidation strategy write-up (the actual hard part of caching), idempotency keys for background jobs. | Add caching, async processing, and search to the LMS. |
| Month 9System Design | Scalability, availability, load balancing, caching, replication, sharding, CAP theorem, CDN, event-driven architecture. | A written design doc per case study, not just a diagram, which forces students to argue tradeoffs rather than just draw boxes. | Design systems inspired by YouTube, Netflix, Amazon, Uber, WhatsApp. |
System design case studies now each produce a 1–2 page design doc — context, constraints, tradeoffs, what you'd change at 10x scale — mirroring what real system-design interviews actually ask for.
High-Scale & Career
Months 10 through 12. This is where mastery and career readiness come together.
| Month | Core topics | Refinements added | Challenge |
|---|---|---|---|
| Month 10High-Scale Engineering | Distributed systems, microservices, API gateways, distributed caching, database scaling, fault tolerance, monitoring/logging/metrics, high availability, disaster recovery. | Prometheus + Grafana as the concrete monitoring stack, plus a deliberate chaos test: kill a service, verify the system degrades gracefully. | Design a platform capable of handling 1 million users. |
| Month 11Team Workflow | Agile, Scrum, Jira, Git branching, PRs, code reviews, testing, bug tracking, documentation, team communication. | Weekly peer PR review starts in practice back in Month 4; this month formalizes it into sprint ceremonies. | Build a production-style product in teams. |
| Month 12Mastery + Career | Advanced system design, architecture discussions, performance optimization, production debugging, security, resume, GitHub portfolio, mock interviews, machine coding, behavioral interviews. | An OWASP Top 10 walkthrough against the LMS itself (SQLi, auth bypass, XSS) as the security module’s hands-on project, not just a lecture. | Present, defend, and explain the final system like a software engineer. |
Capstone: the LMS built since Month 1 is the spine of the final portfolio piece — by graduation it is tested, cached, searchable, containerized, monitored, and has survived a security review, which is a stronger story than a fresh capstone project built from scratch in Month 12.
What changed from the original brochure, and why
- Testing and code review moved earlier. A light version starts Month 3 (component tests, weekly PR reviews) instead of Month 7, so it becomes a habit rather than a Month 7 lecture.
- Every month has a named toolchain, not a category. "CI/CD fundamentals" becomes "one working GitHub Actions pipeline"; "monitoring" becomes "Prometheus + Grafana."
- System design case studies now require a written design doc, not just a whiteboard diagram, so the skill transfers directly to interview performance.
- Security gets a hands-on project: OWASP Top 10 against the students’ own LMS, instead of living only in the Month 12 topic list.
- One flagship project (the LMS) threads the entire 12 months instead of a fresh capstone in Month 12.
- A weekly rhythm was added inside each month (build, independent build, review) so pacing is explicit rather than left to the instructor.
Everything else in the original brochure — module order, project list, milestone language, phase structure — is preserved as-is. These are additions and sharpenings, not a restructure.
Ready for Software Engineering?
No prior experience required — just the time commitment and a working laptop.