Skip to the notes
JSGroundwork
JSGroundwork handwritten · web dev
✎Playground→⌘Problems↻Review🔥Progress

Chapters

20 chapters
⌕
Beginner15›
00Scouting reportR1Screening callR2Machine codingR3JavaScript & TSR3·TSTypeScriptR4React & Next.jsR5Node & NestJSR6Databases & RedisR7DSA roundR8System designR9AWS, Docker, CI/CDR10Resume grillingR11BehaviouralR12HR & the number✓The week before
Advanced5›
50LWhat changes at ₹50L50LHard DSA50LDistributed systems50LRuntime internals50LStaff behavioural
/ search[ ] chaptert top

Ready to read

JSJavaScript⑂Git◎Interview prepΣDSA in JSSDSystem Design
More topics15›
</>HTML{ }CSS⚛ReactNNext.jsNeNest.jsTSTypeScriptNoNode.js🐳DockerDBSQL & Databases✓Testing🔒Web Security☁Cloud & DevOps◈GraphQL◆Redis☸Kubernetes
100%
✓

The week before, and the day itself

UseSeven days out
If you have one nightDo day 1 and go
serviceproductsaasagency

If you have a week before the interviews you actually care about, spend it like this. If you are walking in tomorrow, do day one tonight and go — your own story is worth more than any amount of revision.

PLAN.1
The seven-day plan
What they are really testingSequence. Most people revise what they already know and skip what they will be asked.
DayFocusThe actual work
1Your own storyWrite real answers to all ten metric questions in R10. Practise the two-minute GetDandy walkthrough out loud five times. Draw its architecture on paper three times from memory. Fix the two resume lines in the scouting report.
2JavaScript & TypeScriptR3 and R3·TS end to end, out loud. Write debounce, throttle, Promise.all and the promise pool from scratch without looking. Make the event-loop ordering automatic.
3React & Next.jsR4. Prepare the Redux→Zustand defence properly — it is the most likely deep question in your loop. Re-read the Next 15/16 caching change until you can explain why the default flipped.
4Backend & dataR5 and R6. Rehearse the no-message-broker answer until it sounds like judgement rather than apology. Write the five SQL queries by hand.
5Machine codingBuild the task board and the data table under a real 90-minute timer, twice. The highest-return day on this list.
6System designDesign the booking marketplace and the real-time dashboard out loud with a timer, using the seven-step frame. Record yourself once and listen back — it is unpleasant and it works.
7DSA & behaviouralEight problems each from hash map, two pointers and sliding window. Then write the six stories in R11 as bullet points, not scripts.
PLAN.2
Walk-in day
What they are really testingLogistics decide more outcomes than people admit.

Sequence the campaign

Interview at the companies you want least in the first two days. You will be sharper by day four, and you want your best performance where it pays most. Compress everything into one week so offers overlap.

Carry paper

Six printed resumes, a pen, a small notebook. Write down the interviewer's name and one thing they said in each round — it makes your follow-up email specific instead of generic.

Arrive early, and eat

Walk-ins run long and unpredictably. A four-hour queue on an empty stomach is how good candidates fail the last round. Water and something to eat.

Ten minutes of homework per company

In the queue, look up what they build and who their customers are. It costs nothing and turns "why do you want to work here" from a stumble into a strength.

Send the note the same evening

Short email to the recruiter: thanks, one specific thing from the conversation, one line restating availability. Very few candidates do this and it keeps you visible while they sort fifty resumes.

Debrief every loop

Write down every question you were asked and every one you fumbled, the same day. By interview four you will have a personalised version of this page that is better than this one.

←previousStaff behavioural↑ Cover