Start Here
What this site is, who it is for, and the order to read it in.
This site is a 34-week preparation plan for backend SDE-1 roles in India, from October 2026 to June 2027. It combines interview practice, a focused project portfolio, and an adaptable job search.
Before you start, read the Do’s and don’ts for practical guidance on using the plan, preparing well, and avoiding common mistakes.
The short version
You will work on five tracks:
- Work through Striver's A2Z DSA sheet in C++ and track completed problems.
- Build a focused portfolio, starting with Ledgerline and one additional project.
- Drill CS fundamentals, low-level design and system design until you can answer out loud.
- Apply and ask for referrals every week from December onward.
- Read a few relevant engineering posts each week and connect them to your projects.
Use Bengaluru, Hyderabad, and remote roles as starting filters. Set a compensation goal that fits your needs, then assess each offer by fixed pay, variable pay, benefits, location, and role scope. The plan cannot promise an offer or a salary.
Read this page once, then start
Do not try to memorise the whole site. Read this page, then open Operating Rules and Week 1 of the plan. The rest is reference material you will open when the calendar reaches it.
Who this is for
This plan was written for one specific person:
- Final-year Computer Science student at Osmania University, graduating June 2027.
- Comfortable with Go, TypeScript and PostgreSQL, but no professional team experience.
- Studying from a tier-4 college with no useful campus placements.
- Able to commit 40 to 60 hours per week for 34 weeks.
If that sounds like you, follow the plan in order. If you only need one track, use the "choose your path" section below.
The plan at a glance
| Phase | Weeks | Main work |
|---|---|---|
| Start | Week 1 | Baseline test, contest, set up repo |
| Build 1 | Weeks 2 to 7 | Ledgerline: payments ledger in Go |
| Build 2 | Weeks 8 to 13 | Logsmith or one selected systems project |
| Build 3 | Weeks 14 to 19 | Deploy and operate a service with Shiplane |
| Operate | Weeks 20 to 25 | Observe a service, run failure drills, and document recovery |
| Interview | Weeks 26 to 34 | Mocks, revision, applications, offers |
Each phase has its own page in The 34-Week Plan. The detail is in the week tables.
Choose your path
I want the full plan
Start with the week template, then follow the calendar week by week.
I only need DSA
The complete A2Z schedule, revision system and mock ladder.
I only need projects
A focused portfolio guide, existing project specs, and detailed systems options.
I need a job now
The off-campus playbook and the referral engine.
I need interview prep
Practise clear stories about teamwork, feedback, conflict, and company values.
I want AI prep
Learn how language models work, how engineers use them, and how to build AI features safely.
What you need before week 1
Check these off before you start. None of them take more than an hour.
- A LeetCode account, registered for the Sunday contest.
- A takeuforward account, so the A2Z sheet tracks your progress.
- A public GitHub account and one repository for Ledgerline. Create later repositories when you choose their scope.
- A notes app for the revision deck and daily log (Obsidian, Notion, or a spreadsheet).
- One tracker for DSA, projects, mocks and referrals. Keep it in one file.
- Wait until the deployment phase to choose hosting. Check current prices and set a monthly limit first.
How to read a page here
Every page follows the same shape:
- The first paragraph says what the page is for.
- The next section tells you what to do, in order.
- Later sections explain why, or add depth. You can skip these on a busy day.
- Do and Don't sections collect the mistakes that cost people offers.
If you are ever unsure which page to open, follow the calendar in The 34-Week Plan. It points to the right page for every week.
What to do next
Read Operating Rules. It takes five minutes and applies to every other page.
Run the Week 1 baseline in DSA. Three timed problems. Log the result.
Open Week 1 to 13 and start the first row.