How to Prepare for an Interview in One Week

If you need to prepare for an interview in one week, the instinct is to reread notes and watch tutorials for hours. Learning research says that is one of the least effective ways to use limited time. A week is enough to improve noticeably if you study the right way: by testing yourself, spacing practice across days, and rehearsing under interview-like conditions.

What the research says about studying fast

A major review of ten common learning techniques rated two as having high utility: practice testing and distributed practice, meaning spreading practice across sessions instead of cramming. They worked for learners of different ages and abilities across many kinds of tasks. Self-explanation, explaining to yourself why something is true, was rated moderate (Dunlosky et al., 2013).

A classic experiment shows why testing beats rereading. Students who took recall tests on a passage remembered substantially more two days and one week later than students who reread it the same number of times. Rereading did help on a test five minutes later, and it made students feel more confident, which is exactly why it is so tempting (Roediger and Karpicke, 2006).

For interview preparation, that translates into three rules:

1. Answer questions, do not reread answers. Solve the SQL problem, then check.
2. Spread each topic across several days, a little each day, rather than one long block.
3. Explain your reasoning out loud, which combines practice testing with self-explanation and matches what interviews ask of you.

Day 0: plan the week (one hour)

Read the job description and list the three or four skills it emphasises. Find out the interview format if you can: a SQL test, a take-home, a case study, a coding round, a behavioural round. Ask the recruiter; they usually tell you. Then write a short list of topics in priority order. For most data roles it looks like: SQL, the main tool or language, statistics or data modelling depending on the role, your projects, and behavioural questions.

The seven days

Day 1: diagnose. Do a timed set of practice questions across your topics, without notes. Mark what you got wrong or could not explain. This is your study list; do not spend time on what you already know.

Day 2: core technical skill, round one. For data roles, usually SQL: joins, aggregation, window functions and edge cases such as nulls and duplicates. Solve problems; check answers only after trying.

Day 3: second skill, plus a SQL recap. Python, statistics, data modelling or system design, depending on the role. Start the session with fifteen minutes of yesterday's SQL from memory. That spacing is where the retention comes from.

Day 4: projects and stories. Prepare a two-minute walkthrough of your best two projects: problem, data, approach, result, what you would change. Write five behavioural stories in the STAR structure, covering conflict, failure, influence, a tight deadline and learning something fast. Say them out loud.

Day 5: mock interview. Do a full practice interview with a friend, mentor or a practice platform, under time limits, speaking throughout. Practising out loud the right way shows how to make it useful. Note the questions that stalled you.

Day 6: close the gaps. Rework the weak spots from day 5 and re-test yourself on day 1's mistakes. Research the company: its product, how it might use data, recent news, and the team. Prepare three thoughtful questions for your interviewers.

Day 7: light review and rest. Quick self-tests only, no new topics. Prepare your setup, documents and travel. Sleep normally.

What to skip when time is short

• Brand-new topics that are not central to the job. One week is for strengthening what the role needs, not for learning a new field.
• Long video courses. Watching feels productive but is closer to rereading than to testing.
• Memorising answers word for word. Interviewers change the question slightly; understanding transfers, scripts do not.
• Late-night cramming before the interview. The evidence for spacing applies; so does common sense about sleep.

Role-specific question banks

For practice questions, use the set closest to your role: data analyst interview questions, data engineering interview questions or SQL interview questions. Treat each as a test, not as reading.

If the interview is in two or three days

Compress the plan: one diagnostic session, one session on the weakest core skill, one on projects and stories, and one short mock interview. Testing yourself remains the priority; rereading remains the thing to cut.

Structured SQL and analytics practice for interviews is part of the Data Analytics course.

Sources

• Improving Students' Learning With Effective Learning Techniques (Dunlosky, Rawson, Marsh, Nathan and Willingham, Psychological Science in the Public Interest, 2013) — PubMed (US National Library of Medicine)
• Test-enhanced learning: taking memory tests improves long-term retention (Roediger and Karpicke, Psychological Science, 2006) — PubMed (US National Library of Medicine)