Guide · 5 min read
After the application: how to prepare for a first interview
How to prepare for a first interview after you apply: reread what you sent, choose your stories, research the role, and plan the questions worth asking.
Published
A first interview usually arrives after you have forgotten the application. You applied three weeks ago, alongside dozens of others, and now a recruiter wants thirty minutes on Thursday. The preparation that matters most is not memorising answers. It is knowing exactly what you told this company, having three or four true stories ready, and understanding what the role needs.
This guide walks through that preparation in order: what to reread, what to research, which stories to prepare, how to answer well, and what to ask. We build Aplies, which applies to jobs for you, and the last section covers how its record of every application helps here. Everything else holds however you applied.
What should you do as soon as an interview is booked?
Start with the application itself. Find the posting, the CV you sent and every answer you gave on the form. The interviewer may have all three in front of them, and the first questions often come straight from them: your notice period, your salary expectation, your years with a tool, why you want to work there.
If the posting has been taken down, the company's careers page sometimes still lists the role. From now on, save a copy of every posting you apply to; postings disappear without warning.
Then confirm the practical details: who you are meeting, their role, the format, how long it lasts, and whether you need to prepare anything.
Why reread the answers you sent?
Because a contradiction between your application and your interview is one of the few mistakes a strong candidate cannot talk their way out of. If the form says four years with SQL and you say six in the interview, the interviewer now has a question about you that has nothing to do with SQL.
Read each answer the way the interviewer will. Is the salary figure one you still stand behind? Is the notice period right? Does the written answer to "Why us?" sound like you? If something is wrong, raise it early and plainly: "I put four years on the form; counting my contract work it is closer to five, and here is what that covered." A correction you offer reads as honesty; one they discover reads as the opposite.
The interviewer has your application in front of them. Make sure you do too.
How do you research the company and the role?
Twenty focused minutes beat two scattered hours:
- 01The posting, line by line. Mark the three things it asks for most, and find one piece of your experience for each.
- 02The product or service. Use it if you can, and read how the company describes what it does.
- 03Recent news. A launch, an expansion, a new market: one specific thing you can mention naturally.
- 04The people. Look up your interviewers on LinkedIn: their role, how long they have been there, what their team does.
The point is not to recite facts back. It is to understand the problem the hire is meant to solve, so your answers can be about that problem.
Which stories should you prepare?
Most first-interview questions ask for evidence: a time you solved a hard problem, handled a disagreement, missed a deadline, changed someone's mind, or delivered something you are proud of. Prepare three or four true stories from your CV that between them cover most of these, and practise telling each in about two minutes:
- 01The situation, in one or two sentences.
- 02What you personally did, which should be most of the story.
- 03The result, with a number if you honestly have one, and what you learned.
Choose stories that match the three things you marked in the posting. If your CV says "grew engagement by 40% in six months", the interview is where you explain how. Our screening questions guide has the written version of the same structure, and the ATS-friendly CV guide covers putting numbers on your CV in the first place.
What are interviewers actually listening for?
Less polish than you think, and more thinking. A first interview usually checks a few things: whether you can explain clearly what you did, whether your experience fits the role's main needs, how you approach a problem you have not seen before, and whether you are genuinely interested.
- 01Explain how you think, not only what you concluded. Given a hypothetical, talk through your reasoning; a sound approach often counts for more than a perfect answer.
- 02Be specific. "We improved the process" is weaker than "I rebuilt the intake form and cut the backlog from three weeks to four days."
- 03Be honest about gaps. "I haven't used that tool, but I have used a similar one for two years" is a strong answer.
- 04Sound like yourself. Prepared stories should feel told, not recited.
Which questions should you ask?
Prepare three or four, and ask the two that fit by the end:
- 01What would success look like in this role after six months?
- 02What is the biggest challenge the team is facing right now?
- 03How is the team organised, and who would I work with most?
- 04What are the next steps, and when should I expect to hear back?
The last one matters most: it gives you a date to follow up against.
What should you do after the interview?
Send a short thank-you within a day, mentioning one specific thing from the conversation. Note the date they gave for next steps, and follow up once if it passes; our guide on how to follow up after applying has short templates. Then write down what you were asked and which answers felt weak, while you still remember.
If several first interviews in a row go no further, look at your preparation before you send more applications. How many jobs to apply to a week explains how to read that signal.
How does Aplies help you prepare?
If Aplies applied for you, you do not have to remember what it said. Its Application Report keeps every application: the job, the company, the link, every question on the form and the answer given, including the answers you typed when it asked you. Your dashboard on aplies.com lists every submitted application with its questions and answers.
So when an interview is booked, open the report, find the application and reread it before anything else. If an answer is wrong, correct it there: the corrected version is what the Agent uses the next time a form asks the same question, so one interview improves every application after it. You can also export the record as a CSV, one row per question, to keep alongside your interview notes.
How it works shows the full flow, and the pricing page has the credit costs. The interview itself is yours. The aim of everything above is that you walk in knowing exactly what you said, with true stories ready to back it up.
Related guides
Guide ·
Your LinkedIn profile before you apply: what recruiters see
What recruiters see when you apply on LinkedIn, the profile fixes that matter before you send applications, and how to keep your profile and CV telling one story.
Guide ·
ATS-friendly CV (resume): how to write one software can read
What an applicant tracking system does with your CV or resume, the formatting that breaks parsing, the myths to ignore, and how to use keywords honestly.
Guide ·
How many jobs to apply to a week, and a routine that works
How many jobs to apply to each week, worked out from your own numbers, and a daily and weekly routine for applying to more jobs without lowering the quality.