Video summary
Gold Medalist & Chancellor Medalist's Journey | How She Became AKTU Rank 1 | Anshika Rana Podcast
Main summary
Key takeaways
Main ideas / lessons conveyed
-
Consistency over time
- Her “Day 1 vs today” difference was confidence gained through consistent effort, leading to high CGPA (e.g., ~9.4) and top rankings.
-
Build a strong academic base early (1st–2nd year)
- Use classroom learning + structured notes in year 1–2 so exams require less last-minute effort later.
-
Shift focus to skills and placement readiness later (3rd–4th year)
- In 3rd–4th year, she reduced visits to college and shifted more time to coding/DSA/projects/placement preparation, leveraging the strong foundation built earlier.
-
Use multiple learning resources strategically
- Rewatch complex topics multiple times (sometimes 3–5+ videos) until concepts become clear.
- She used:
- YouTube channels (notably Multi Atom; also others mentioned)
- ChatGPT for simpler explanations and concept clarity
- Gateway classes
- PYQs (previous year questions) heavily
-
AI and video learning as “explain until it clicks”
- If a concept is unclear, she asked ChatGPT to explain in easy language and cross-checked with videos.
-
Notes designed for exam-writing
- Notes were structured according to marks (especially ~7-mark answers):
- Use diagrams + bullet-point hierarchy
- Keep answers point-to-point, visually clear for evaluators
- Notes were structured according to marks (especially ~7-mark answers):
-
Concept-first approach for difficult subjects
- For tough subjects (e.g., COA, other numerical/concept-heavy courses), her strategy was:
- Go line-by-line with the syllabus
- Watch multiple explanations if needed
- Don’t move on until the concept is understood well enough to feel confident solving/revising
- For tough subjects (e.g., COA, other numerical/concept-heavy courses), her strategy was:
-
Domain selection and coding journey
- She emphasized selecting a domain early (not delaying too much), finalizing language by year 1–2, and then building:
- Front-end → back-end → full projects → DSA progression
- She emphasized selecting a domain early (not delaying too much), finalizing language by year 1–2, and then building:
-
Time management + routine
- Core mechanism: a timetable, plus avoiding wasting weekends.
- Academics: studied mostly closer to exams but smartly using PYQs.
- Skills: dedicated hours after college (e.g., ~4 hours) and daily coding practice.
-
Campus placement mindset
- She experienced setbacks (not clearing early rounds; demotivation due to competition and perceived cheating by others).
- Recovery approach:
- Keep applying widely (10–15 companies)
- Use each interview opportunity as learning
- Prepare consistently and adapt based on feedback/experience
Methodology / instructions (detailed bullet points)
1) Ideal Year-1 roadmap (as she recommends)
-
Maintain/boost CGPA early
- Focus on CGPA in year 1 so later CGPA issues don’t become hard to fix.
- Don’t rely on “studying only near exams”—build steadiness from the start.
-
Explore domains before locking in
- Spend year 1 exploring multiple fields and what you enjoy.
- Finalize your domain and language preference early enough so you don’t get stuck later.
-
Lock basics of your chosen language in year 1
- Examples she mentions: C++, Java, Python.
- Ensure you have a clear foundation so you can start DSA from year 2.
-
Plan for projects to start from year 2
- Once domain + language fundamentals are clear, begin project work from year 2.
-
Avoid wrong guidance
- Don’t follow seniors who push “study late; you’ll pass easily.”
- Correct decisions are harder to reverse in year 3–4.
2) Overall preparation strategy (academics + skills across years)
-
Year 1–2: classroom learning + exam-prep base
- Follow teachers closely.
- Create and refine notes while learning.
- Use classroom learning to reduce last-minute time waste.
-
Year 3–4: skills + placements
- Reduce non-essential activities (she reduced college visits).
- Focus on:
- coding
- DSA consistency
- projects
- placement preparation
-
Use AI + videos to remove confusion
- If concept is unclear:
- Ask ChatGPT to explain in easy language
- Watch YouTube lectures multiple times
- Continue until the concept becomes meaningful (then revision becomes easier)
- If concept is unclear:
3) Notes & exam-writing system (AKTU/ATU-style writing advice)
-
Write point-to-point
- Avoid long paragraphs.
-
Match answer structure to marks
- She designed notes based on ~7-mark question format so she could handle topic variations.
-
Use diagrams whenever possible
- “Diagrams are a must”
- Include hierarchy flow charts/visual structure.
-
Aim for evaluator-friendly presentation
- Teachers may not read every word; they respond to clear visuals.
4) How she tackled difficult subjects (concept-heavy/numerical)
-
Syllabus-driven study
- Sit with the syllabus and go topic-by-topic line by line.
-
Watch multiple explanations
- For difficult topics, watch several videos/channels (repeated viewing allowed).
-
Use ChatGPT for simpler breakdown
- Ask for easy explanations until you understand enough to proceed.
-
Revise until confidence is stable
- Once understood, repeated revision prevents confusion later.
-
If still stuck, seek help
- Use teachers/class faculty when YouTube/AI doesn’t solve it.
-
PYQs as the final accuracy tool
- Solve PYQs from the last 5–6 years and analyze patterns.
- She found that many questions repeat from PYQs.
5) Coding & DSA / domain-building progression (as described)
-
Start with language basics in year 1
- She began with C programming via a first-year course (TPS).
- Do basic exercises and conceptual questions.
-
Select Java as her domain language in year 2
- She used videos (including a referenced “Shraddha Ma’am” video) and senior recommendations.
-
Front-end focus in year 2
- Build simple projects and games:
- tic tac toe
- currency converter
- snake game
- Continue foundational coding questions and basic DSA.
- Build simple projects and games:
-
DSA consistency in year 3
- Follow DSA roadmap resources/sheets (she referenced Striver’s sheet, LeetCode practice plans).
-
Move from front-end to full-stack projects
- Add back-end after realizing front-end alone is insufficient.
- Build full-fledged projects (she indicated 2 key projects plus advanced concepts).
-
Advance topics near placement
- Use late year-3/early year-4 time to level up DSA and projects.
- Revise OOPs/CS fundamentals during short preparation windows (she suggested ~10–15 days for aptitude review).
6) Aptitude + placement preparation workflow
-
Time management for parallel tracks
- Create a timetable and follow it consistently.
- Skills: dedicated hours daily after college.
- Academics: smart revision closer to exams, heavily PYQ-based.
-
Daily coding practice
- She emphasized giving 7–8 hours daily to coding (especially during competitive period/after third year).
- Do large volumes of problem-solving and practice consistently.
-
Aptitude practice
- Prepare aptitude formulas and mock aptitude tests.
- She recommended using resources like:
- IndiaBIX
- campus mock aptitude channel (name not fully clarified)
-
Company interview prep structure
- For each company:
- Read job description and align preparation to the role
- Prepare likely questions from projects
- Revisit OOPs + DSA basics before interviews
- Use AI (ChatGPT) to brainstorm possible interview questions from your project
- Check role expectations (front-end/back-end/data analyst etc.)
- For each company:
-
Expected common rounds (typical sequence)
- CGPA/criteria and resume screening (eligibility gate)
- Round 1: Aptitude (often elimination)
- Round 2: sometimes coding or English/verbal communication (she described an English-reading/writing style round)
- Round 3: Technical interview (projects + DSA + OOPs/CS fundamentals)
- Round 4: HR round
7) If placement rounds fail: comeback mindset
-
Don’t become negative
- Maintain hope and keep applying to many companies.
-
Apply broadly
- She applied to 10–15 companies.
-
Use every interview as learning
- Even failing teaches patterns, confidence, and what to adjust next.
-
Keep preparing using experience
- Build from what you learn in earlier attempts.
Speakers / sources featured (as stated or implied)
Speaker(s)
- Anshika Rana (guest; gold medalist, Chancellor medalist; described as a software engineer at “SL Tech” / “SCL Tech”)
Hosts / podcast participants (implied)
- Podcast host(s) / Interviewers (un-named; multiple people speaking but no distinct names provided)
Mentioned external sources/resources
- ChatGPT (explanations and interview-question brainstorming)
- YouTube (general lecture learning; specific channel references included)
- Multi Atom (learning/notes preference)
- Gateway classes
- Striver’s sheet
- LeetCode
- IndiaBIX
- Edgbet (mentioned as another learning/search source; exact platform unclear)
- “Jenny’s lectures” / Jenny’s lecture (helpful for tough topic like Red-Black Tree)
- Lead Code / Coding Curry (platform/resource names mentioned; exact relationship unclear in subtitles)
- LinkedIn (used for job/role information during company preparation)
- AKTU / ATU (university context for exams and placement/copy checking)