Contents
Part 2: The road to your first job in Bengaluru

Week 1: fix the proof

Don’t start outreach until every link works. During this week, apply only to postings under 24 hours old.

DayTasksDone when
Day 1Rebuild your resume with the builder. Fix everything in the audit. Make every linked repo public. Archive the junk repos.A friend clicks every resume link from a logged-out browser and all of them load.
Day 2Deploy every flagship project with seeded demo accounts, one per role. Put the demo logins in each README.A friend logs in as each role on each app without help.
Day 3Write real READMEs for your 3 flagships (template below). Add a data model diagram (dbdiagram.io works).A stranger understands each project in 60 seconds.
Day 4Deploy a one-page portfolio: pitch, 3 project cards, resume PDF, contact. Update GitHub bio and pins. Rewrite LinkedIn. Build or refresh your Naukri profile.Everything matches the resume.
Day 5Record a 2 to 3 minute Loom per flagship: demo, then code, then one hard decision you made.Three videos, linked in each README and on the portfolio.
Day 6Take the defend-the-code test with a friend or mentor.You pass on your main project at least.
Day 7Build a list of 80 Bengaluru companies in a sheet (tracker on the weekly review page). Set job alerts. Take half the day off.80 rows, with a contact name for at least 40.

README template

README.md
# Project name
One sentence: what it does and for whom.

Live: <url>   |   Demo logins: admin@demo / user@demo (password: demo1234)
Walkthrough video: <loom link>

## Screenshots (3)
## Features (by role)
## Tech stack and why each piece was chosen
## Architecture (browser -> Next.js server components/actions -> ORM -> PostgreSQL)
## Data model (ER diagram + 3 lines on the key relations)
## Auth and authorization (how sessions work, where role checks happen)
## Hard problems I solved (problem, options, what I chose, why)
## What I'd do next (tests, caching, pagination...)
## Run locally