Twenty guides. One shelf.

"Q. Why is String immutable in Java? A. Security, caching (String pool), thread-safety, hash consistency. Deliver it in that order — interviewers tick each box."

Tap to flip back ←

"Rank employees by salary within each department — a canonical window-function question. If ROW_NUMBER, RANK, and DENSE_RANK don't feel distinct, start here."

Tap to flip back ←

"3NF in one line: every non-key attribute depends on the key, the whole key, and nothing but the key. Say that cleanly and you're ahead of most freshers."

Tap to flip back ←

"useEffect isn't 'onMount'. It's 'sync my component with an external system.' Every time you reach for it, name what you're syncing with."

Tap to flip back ←

"401 vs 403: 401 is 'I don't know who you are'; 403 is 'I know who you are, and you can't.' Getting this wrong in a design round is a small tell that adds up."

Tap to flip back ←

"Bias vs variance in one sentence: bias is being wrong on average, variance is being unstable across samples. Every model choice is a trade between these two."

Tap to flip back ←

"Present → Past → Future. 90 seconds. No adjectives about yourself — let the facts do the work. Interviewers remember specifics, not enthusiasm."

Tap to flip back ←

"Structure every project answer as: Problem → Your role → Stack choices (with a trade-off) → Outcome. Skip the 'we did agile' filler — interviewers switch off."

Tap to flip back ←

"Every bullet: verb + what you did + measurable outcome. If a line can't answer 'so what?', it doesn't earn its space on the page."

Tap to flip back ←

"Your headline isn't your job title — it's the search string a recruiter would type to find you. 'Frontend developer · React, TypeScript · Open to internships' beats 'Passionate learner.'"

Tap to flip back ←

"Line 1: how you found them. Line 2: why you're relevant. Line 3: the ask, small and specific. No 'hope this finds you well.' No resume as the first message."

Tap to flip back ←

"Monday: apply to 10. Wednesday: follow up on last week's 10. Friday: audit — which channels replied, which didn't. Repeat. Volume without a review loop is just noise."

Tap to flip back ←

"Record yourself answering three prompts. Play it back once at 1× and once at 1.5×. What sounds okay at 1× is often waffle at 1.5×. Cut those lines."

Tap to flip back ←

"Columns: Company, Role, Applied On, Referral?, Round, Next Action, Deadline. If 'Next Action' is empty, that row is dead. Fill it or delete it."

Tap to flip back ←

"Start with the bullet, not the layout. Fill the bullet bank first, choose the template second. Most freshers do the opposite and end up with a pretty empty page."

Tap to flip back ←

"Open with a fact, not a feeling. 'Final-year CSE student building a full-stack booking app in React and Java' outperforms 'Passionate about tech and always eager to learn.'"

Tap to flip back ←

"The 'no reply after interview' follow-up: one line acknowledging their time, one line reiterating fit, one line naming a date you'll follow up again. Then actually do it."

Tap to flip back ←

"Three questions after each round: Where did I stall? What did I over-explain? What would I cut in half next time? Written, not remembered — memory lies."

Tap to flip back ←

"Fill four boxes per project: the one-line pitch, the trade-off you owned, the metric you moved, the thing you'd redo. That's the entire script — everything else is improv."

Tap to flip back ←