How do I explain a career gap in an interview without it sinking me?
14-month gap for family health reasons, now getting interviews again but freezing whenever the gap comes up. How do I handle it?
5 members · 20 questions
Mock rounds, DSA, system design and behavioural prep — together.
14-month gap for family health reasons, now getting interviews again but freezing whenever the gap comes up. How do I handle it?
Application forms and HR calls keep demanding a number. As a fresher I have zero leverage and zero idea what's normal. What do I say?
'Tell me about yourself' opens every interview and I ramble every time — half my college syllabus, my hobbies, everything. What's the structure that works?
It's the first question in every interview and I always ramble through my whole life story. What is the interviewer actually looking for?
I have an interview loop coming up at a large company and don't know what to expect across the rounds.
I have a coding interview in a month. What should I actually spend that month on to maximise my chances?
This is apparently the classic interview question and I realize my answer is embarrassingly vague. Can someone give the answer that would actually satisfy an interviewer?
Self-taught developer here building working apps without ever formally studying DSA. Is it a real gap or just interview theatre?
I can follow tutorials fine, but the moment I face a blank editor and a real problem, I freeze — no idea how to break it down. How do I build actual problem-solving…
Interview advice always mentions STAR. What does each part actually need to contain and how long should an answer be?
I'm fine with technical rounds but freeze on 'tell me about a time when...'. How do I prepare without sounding scripted?
People online report anywhere from 100 to 1500 problems solved. There has to be a smarter target than 'more'. What actually matters?
Froze completely last week when asked about something I'd never used. Sat there in silence, interview never recovered. What's the right move in that moment?
'Do you have any questions for us?' — I always say something generic about culture and instantly regret it. What do strong candidates ask?
I usually want the job because I need a job. How do I answer this without lying or sounding sycophantic?
I have a fourteen-month gap and I dread the question. What's the best way to handle it?
Every senior role wants system design but all the resources assume years of experience. Where does someone with zero production experience actually start?
Every answer feels either fake or self-sabotaging. What are they actually testing and what's a good response?
Cleared the technical rounds, HR round next week. People say 'it's just a formality' but I've also heard of rejections there. What's actually being evaluated?
It's been a week with no response. When and how should I follow up, and what should it say?