Final revision plan before placement season
40 min · Intermediate
Need help? Ask a tutor on WhatsApp (opens in a new tab)A few weeks before the drives most students panic and start new topics. This lesson turns the last four weeks into a fixed schedule, five one-page sheets, mock dates and a calm placement-day routine.
Last four weeks: a revision schedule by topic
A revision schedule gives each of the last four weeks one theme and each day fixed slots, so you never waste time deciding what to study and you add no new topics.
A common order is core Python and OOP first, then collections and DSA, then DBMS, OS and networks, and mocks, projects and HR in the last week.
Example 1 · A four-week plan, printed from data
themes = [ "Core Python and OOP", "Collections and DSA patterns", "DBMS and SQL, OS, networks", "Mocks, projects and HR",]morning = [ "Mutability, strings, exceptions, OOP questions", "Lists, two pointers, hashing, sorting", "Joins, normalisation, ACID, SQL queries", "Coding mock or core CS mock",]evening = [ "Output-prediction puzzles", "Trees, graphs, DP basics", "Processes, memory, TCP/IP, DNS", "Project pitch, HR answers, GD topics",]hours_per_day = 5study_days = 6 # one lighter day each week
for week, (theme, am, pm) in enumerate(zip(themes, morning, evening), start=1): print(f"Week {week}: {theme}") print(f" Morning (2.5 h): {am}") print(f" Evening (2.5 h): {pm}")print(f"Total: {hours_per_day * study_days * len(themes)} hours over 4 weeks")Week 1: Core Python and OOP Morning (2.5 h): Mutability, strings, exceptions, OOP questions Evening (2.5 h): Output-prediction puzzles Week 2: Collections and DSA patterns Morning (2.5 h): Lists, two pointers, hashing, sorting Evening (2.5 h): Trees, graphs, DP basics Week 3: DBMS and SQL, OS, networks Morning (2.5 h): Joins, normalisation, ACID, SQL queries Evening (2.5 h): Processes, memory, TCP/IP, DNS Week 4: Mocks, projects and HR Morning (2.5 h): Coding mock or core CS mock Evening (2.5 h): Project pitch, HR answers, GD topics Total: 120 hours over 4 weeks
What this code does
- Keeping the plan as data (three lists) makes it easy to change a week without touching the loop.
zipwalks the three lists together. - 120 focused hours is a realistic budget alongside college; adjust
hoursPerDayto your timetable. - Week 4 is mostly practice and speaking, because by then the gap is usually speed and calm, not knowledge.
Revise from your own notes and solved problems, not from new books or courses. A new topic in the last month usually adds stress and few marks. For coding, go back to the problems you solved in the Python DSA 150 sheet (open it at /learn/python/dsa-sheet) and the pattern practice must-do problems (opens in a new tab). Revise: Placement preparation timetable (opens in a new tab).
Formula and concept sheets to keep
A concept sheet is one page per subject with the facts you must recall instantly, such as time complexities, key definitions and the differences interviewers love.
Write it yourself; making the sheet is half the revision. Keep five sheets: Python and OOP, collections and complexity, DBMS and SQL, OS, and networks.
Example 2 · A one-page collections and complexity sheet
Operation Typical timeitems[i] / items[i] = x O(1)items.append(x) O(1) on average (occasional resize)items.insert(i, x) / items.pop(0) O(n)x in items O(n)deque.append / deque.popleft O(1)dict or set: get, add, in O(1) on averageheapq.heappush / heapq.heappop O(log n); heap[0] is O(1)bisect on a sorted list O(log n)sorted(items) / items.sort() O(n log n)Must-say differences== compares values; is compares identity (use is only for None)list, dict and set are mutable; str, tuple and frozenset are notdict keys must be hashable, so a list cannot be a keysorted(key=...) orders once; __lt__ gives a class its natural orderCover the right-hand column and say each answer aloud. Any line you hesitate on goes on tomorrow's revision list.
What this code does
- These are the complexities interviewers ask most; "on average" matters for dict, set and list append.
- The "must-say differences" are short enough to recall in a rapid-fire round.
- Make the other four sheets (Python and OOP, DBMS and SQL, OS, networks) in the same one-page style.
Read all five on the evening before every test or interview. Revise the facts themselves: Dictionaries and sets must-do problems (opens in a new tab) and Strings must-do problems (opens in a new tab).
Mock-test schedule and rest
A mock schedule fixes the dates of your practice tests in advance, about two a week in the last month, each followed by a review on the same day.
Alternate coding assessments with core CS and HR or GD mocks. The review matters more than the mock itself.
Example 3 · Mock dates for the last four weeks
from datetime import date, timedelta
def label(day): return f"{day} {day:%A}".upper() # e.g. 2026-06-03 WEDNESDAY
start = date(2026, 6, 1)placement_day = date(2026, 6, 29)rest_day = placement_day - timedelta(days=1)types = ["Coding mock", "Core CS + HR mock"]count = 0
for offset in range((rest_day - start).days): day = start + timedelta(days=offset) if day.weekday() in (2, 5): # Wednesday or Saturday print(f"{label(day)}: {types[count % 2]}, review the same evening") count += 1print(f"{label(rest_day)}: rest, read concept sheets, pack documents")print(f"{label(placement_day)}: placement day")print("Mocks planned:", count)2026-06-03 WEDNESDAY: Coding mock, review the same evening 2026-06-06 SATURDAY: Core CS + HR mock, review the same evening 2026-06-10 WEDNESDAY: Coding mock, review the same evening 2026-06-13 SATURDAY: Core CS + HR mock, review the same evening 2026-06-17 WEDNESDAY: Coding mock, review the same evening 2026-06-20 SATURDAY: Core CS + HR mock, review the same evening 2026-06-24 WEDNESDAY: Coding mock, review the same evening 2026-06-27 SATURDAY: Core CS + HR mock, review the same evening 2026-06-28 SUNDAY: rest, read concept sheets, pack documents 2026-06-29 MONDAY: placement day Mocks planned: 8
What this code does
- The loop stops before the day before placement day, so that day stays free for rest.
count % 2alternates the two mock types, so both kinds get four practice runs.dateandtimedeltahandle month lengths and weekdays for you; changestartandplacement_dayto your own dates.
Plan rest as seriously as work: 7 to 8 hours of sleep, one lighter day a week, no new topics and no all-nighter before a test. A tired brain makes silly mistakes in easy questions. Revise: Mock coding assessment (opens in a new tab) and Mock HR interview (opens in a new tab).
Document checklist: resume copies, ID, mark sheets
A document checklist is the list of papers and files you keep ready in one folder, on paper and on your phone, before the placement season starts.
Prepare it once, in the first week of the plan, and keep it packed. Companies differ, so always follow the drive notice.
Example 4 · The placement-day folder
Physical folder On your phone (offline copy)[ ] Resume, 4-5 copies, latest version [ ] Resume PDF (same version)[ ] Photo ID as per notice + college ID [ ] Scans of ID and mark sheets[ ] 10th and 12th/diploma mark sheets [ ] Admit card / registration email[ ] All semester mark sheets + copies [ ] TPO and recruiter phone numbers[ ] 2-4 passport-size photos [ ] Concept sheets (photos)[ ] Two pens, a small notebook [ ] Charged phone + power bankEverything ticked -> folder by the door, clothes ironed, alarm set
What this code does
- The phone copies save you if a paper is forgotten or a company asks for an email upload on the spot.
- Use the same resume version everywhere; interviewers sometimes compare the copy with your online application.
- The drive notice is the final authority: add anything it asks for that is not on this list.
Most drives ask for a similar set:
- Resume: 4 to 5 printed copies, plus the same version as a PDF.
- Photo ID (as the notice asks) and your college ID card.
- Mark sheets: 10th, 12th (or diploma) and all semesters, with photocopies.
- Passport-size photos, a pen, the admit card or registration email.
Mindset on placement day and handling rejection
A placement-day routine is a simple, fixed plan for the day itself: sleep well, eat breakfast, reach early, read your concept sheets once, and then stop studying.
Between rounds, rest and drink water instead of discussing every question with friends.
Example 5 · A reflection after a rejection
Drive: Company A, Python developer, 12 JuneReached: technical round 1 (cleared online test)Went well: online test both problems solved; calm in the interviewTo fix: could not explain how a dict handles collisions; project answer went on for 3 minutesAction: revise the collections sheet tonight; practise the 60-second project pitch 3 times tomorrowFeeling: disappointed, which is normal; next drive on 15 JuneTurns a "no" into two specific fixes and one dated next step, instead of a vague "I am not good enough".
What this code does
- Writing "went well" first is not just kindness: it shows what to keep doing.
- The fixes are small and specific, so they can be done before the next drive.
- Naming the feeling and the next date helps you let the result go and move on.
Rejection is normal in placements: most students hear several "no" results before a "yes", often for reasons outside their control, such as a fixed number of seats. After each one, write a short reflection: what went well, what to fix, and one dated action for the next drive. Then let it go.
Practise these answers aloud in the timed Mock Interview Mode (opens in a new tab).
What's next
You finished the preview of Mock Placement Rounds
Python Programming has 21 sections, 110 modules and 609 lessons. An account opens every lesson and saves your progress.
Next step
Check your understanding
12 quick questions