Post by Kriti Jaiswal

If I had to restart my DSA prep today, here’s how I’d approach it: → Pick one language and stick to it I chose C++ because it’s efficient and widely used. Java or Python works fine too, but don’t waste time switching. → Start simple Begin with arrays, strings, and math-based problems. The goal is to understand problem statements first, not chase “hard” tags on Day 1. → Follow a clear roadmap Arrays → Strings → Recursion → Linked List → Stack & Queue → Trees → Graphs → DP. Jumping around only breaks consistency. → Use Striver’s DSA Sheet Once basics are in place, Striver’s Sheet gives a structured set of easy-to-hard problems aligned with placements. If stuck, check editorials — but understand before coding. → Consistency is everything 1 hour every day > 5 hours once a week. Small steps, daily progress. But remember: solving problems alone won’t land the job. Your resume matters just as much. Here’s a quick checklist I’d follow for resumes: → Tailor for every role Pick the job description and align your resume with its keywords. → Cut the fluff, add impact ❌ “Team player and hardworking.” ✅ “Built a monitoring dashboard that reduced manual checks by 40%.” ✅ “Improved database queries to cut report generation time from 5 mins to 1 min.” → Keep it ATS-friendly Simple fonts, no tables or graphics. Save as PDF/Word for safe parsing. → Show your work Add GitHub, LinkedIn, or portfolio links so recruiters can see your projects directly. DSA gives you the skills. A strong resume gets you in the door. Both together make the difference. #DSA #CodingInterview #ResumeTips #PlacementPreparation #SoftwareEngineering #InterviewPreparation #LeetCode #StriversSheet #JobSearch