The night before a Swiggy interview, most candidates are grinding LeetCode at midnight. By 10 AM the next day, they're blanking on problems they've solved twenty times. The preparation wasn't the problem. The timing was.
This before technical interview checklist isn't about what to study. It's about what to do with the 24 hours you have left, hour by hour, so your brain is actually working when it matters. The research on cognitive performance is consistent enough that you don't need a citation: sleep-deprived people make worse decisions, recall less, and communicate poorly. You already know this. The problem is that anxiety overrides what you know.
Here's how to override the anxiety instead.
T-24 Hours: Stop Adding New Information
At exactly 24 hours out, close the new-material tab. Done. No new LeetCode problems. No new system design videos. No "let me just quickly review consistent hashing one more time."
Your brain consolidates memory during sleep. Anything you learn in the last 24 hours has almost no chance of being solidly retrievable under interview pressure. What you're actually doing when you cram the night before is making yourself anxious, not smarter. You're surfacing everything you don't know right before a test where confidence matters as much as knowledge.
The candidates who show up sharp to a Razorpay or CRED interview are almost always the ones who stopped adding new material a day early. They look calm because they are calm. They're calm because they stopped feeding the anxiety spiral.
T-22 Hours: Do One Light Review Pass, Then Close the Laptop
One pass. Not five. Pick the three or four topics most likely to come up based on the job description and your past rounds. Spend 30 minutes reading through your own notes, not new content. If you've done mock interviews on PrepFinity, skim your feedback summaries from the last week. Look for patterns, not gaps.
The goal here is activation, not acquisition. You want those concepts sitting near the top of your mental stack, easy to reach. You are not trying to fill new gaps at this stage. If you find a gap right now, write it down, accept that it exists, and move on. You cannot fix it tonight.
Close the laptop after 30 minutes. Physically close it.
T-20 Hours: Eat a Real Meal and Go Outside
This sounds obvious. It isn't, because almost no one does it.
Eat something substantial. Not Maggi. Not chips. A real meal with protein and carbohydrates. Your brain runs on glucose and your stress hormones are already elevated. Skipping meals or eating junk the night before compounds the cognitive load you're already carrying.
Then go outside for 20-30 minutes. Walk. Don't listen to a podcast about interview prep. Just walk. Physical movement before sleep improves sleep quality and reduces cortisol. This is not optional self-care advice. It is performance optimization.
T-18 Hours: Do Your Mental Rehearsal
Mental rehearsal is the one preparation activity that's worth doing in the final 24 hours, because it doesn't require learning anything new. It uses what you already know.
Sit somewhere quiet. Close your eyes. Walk through the interview in your head from the moment you join the call. You greet the interviewer. They ask you to introduce yourself. You give your two-minute pitch. They ask the first technical question. You take 30 seconds to think, you talk through your approach before you code.
Run through the version where everything goes slightly wrong too. You blank on a question. You take a breath. You say "let me think through this out loud." You recover. Rehearse the recovery, not just the ideal run.
Candidates who do this arrive feeling like they've already been in the room once. That familiarity reduces the spike of first-question panic that derails otherwise prepared people.
T-16 Hours: Sort Your Logistics, Then Protect Your Sleep
Logistics anxiety is underrated as a performance killer. If you're doing an onsite at a Google or Microsoft campus in Bengaluru or Hyderabad, check travel time right now. Add 40 minutes of buffer. Know where you're going, know how you're getting there, know where to park or which gate to enter.
If it's a video call, test your setup tonight. Check your internet. Check your camera and microphone. Have a backup hotspot ready. Know what IDE or coding environment they use. Some companies want you in CoderPad, others want a shared Google Doc, others have their own platform. Find out now, not at 9:58 AM.
Once logistics are sorted, protect your sleep window. Aim for seven to eight hours. Set one alarm, not six. Tell whoever you live with that you need quiet. This is the single highest-leverage thing you can do in the last 24 hours, and it's the thing most candidates sacrifice.
The Morning Of: Eat Before You Think
Wake up with enough time to eat before your brain needs to perform. Sixty to ninety minutes before the interview start time is the minimum. Eat something you've eaten before. Interview morning is not the time to try the new protein smoothie your roommate recommended.
Avoid excess caffeine if you're not a regular coffee drinker. One cup if you drink it daily. Caffeine amplifies anxiety in people who aren't habituated to it, and interview nerves are already running high. The goal is alert and steady, not jittery.
T-1 Hour: The Before Technical Interview Checklist Runs Here
This is where your final before technical interview checklist items actually execute. Work through these in order:
Environment check. Laptop charged. Charger plugged in anyway. Water on the desk. Phone on silent and face-down or in another room. Notifications off on your laptop.
Mental state check. Take five slow breaths. Not as a ritual, as a physiological intervention. Slow exhales activate the parasympathetic nervous system and lower your resting heart rate. It takes about 90 seconds to work.
One warm-up problem. Not a hard one. A problem you've solved before, something easy, just to get your brain into "coding mode." Five minutes maximum. This is the equivalent of a warm-up set before lifting. You're not trying to get stronger; you're priming the movement pattern.
Review your own resume for 10 minutes. Not someone else's notes. Your resume. Know every project on it well enough to field a follow-up question. The most common early-round failure we see at PrepFinity is candidates who can't speak confidently about their own work because they haven't thought about it recently.
When You're Live: The First 60 Seconds Are Not Wasted Time
The interviewer asking "tell me about yourself" is not a throwaway question. It is your chance to set the frame for everything that follows. Give a structured, practiced 90-second answer. Practice it the night before as part of your mental rehearsal. Know how it ends so you can transition cleanly into the technical portion.
Candidates who fumble the intro spend the first real question still mentally recovering. Candidates who nail it carry that momentum into harder problems. The intro is not small talk. Treat it like the first technical question.
What You're Actually Optimizing For
Most interview prep advice optimizes for knowledge. This checklist optimizes for performance under pressure, which is a different thing. You can know the answer to a question and still fail to retrieve it in a high-stakes moment if your sleep is bad, your cortisol is elevated, and your working memory is overloaded with last-minute cramming.
The candidates who consistently perform well in interviews at Flipkart, PhonePe, and similar companies aren't the ones who studied the most the night before. They're the ones who showed up with a clear head, a rested body, and a plan for the first five minutes. Everything else follows from that.
Check the PrepFinity blog for a related read on the mistakes candidates make during mock interview sessions themselves. Fixing those before you get to interview day makes this checklist even more effective.
Want to run a full mock interview before your real one tomorrow? Start with 3 free interviews on PrepFinity — no credit card needed.