How to Prepare for a Job Interview: Research, Practice, and Follow-Up

An interview invitation means your application has done its first job. The next step is to show how you would do the work—and decide whether you want to do it there. Reading the company’s homepage won’t be enough, but memorizing answers to dozens of questions isn’t the answer either.

A useful preparation workflow has four parts: learn what the role needs, choose evidence from your experience, practice saying it clearly, and prepare questions that help you judge the opportunity. Then, after the conversation, follow up while the details are fresh.

Start with the job description, not a list of interview questions

Read the posting again, even if you studied it before applying. Highlight the responsibilities that seem central to the job. Separate requirements you can demonstrate from those you’ll need to learn. Then look at your résumé and ask: “If someone challenged me to prove I can do each of these things, what would I tell them?”

Make a short working sheet with three columns: what the employer needs, your best example, and the question you still have. For a project coordinator role, it might look like this:

This sheet does two jobs. It keeps your answers tied to the role, and it stops you from asking questions whose answers are already in the posting.

Research the employer until you can explain your interest

Start with the company’s own material: its products or services, customers, recent announcements, and the team or department you’d join. Check the job posting for clues about a new project, expansion, or problem the hire is meant to address. If the organization publishes an annual report or substantial updates, look for priorities that connect directly to your role.

Then widen the view. CareerOneStop’s guide to researching employers points job seekers to company sites, business coverage, industry publications, annual reports, and employee reviews. Each serves a different purpose. A company site tells you how the employer describes itself; outside coverage may give you context; reviews can suggest questions worth asking. Don’t treat one anonymous review as a settled account of the workplace.

Aim to leave your research with three usable notes, not a file of copied facts:

• What the organization does: Explain it in plain language, including whom it serves.
• Why this role matters: Identify one or two needs you could help meet.
• What you want to learn: Turn an uncertainty into a question for the interviewer.

That gives you a specific answer to “Why do you want to work here?” You don’t need to praise the company’s mission if that isn’t what draws you. “Your team is bringing customer support in-house, and I’ve helped build training materials for a growing support team” is stronger than “I’m passionate about your brand.” Research is useful when it changes what you say.

If you know who will interview you, check their role so you can speak at the right level. A recruiter may be best placed to explain the hiring process; a hiring manager can usually tell you more about priorities and performance; a potential teammate may offer the clearest picture of day-to-day work. Don’t pretend to know a person because you read their profile.

Build a small set of stories you can reuse

Interviewers may phrase questions differently, but many are looking for evidence of the same abilities: judgment, collaboration, initiative, learning, and results. Prepare four or five true stories that cover your strongest matches to the posting. Include a challenge or mistake, not just wins. A credible account of what you changed after something went wrong often says more than another polished success story.

For behavioral questions—“Tell me about a time when…”—the STAR technique organizes an answer around the situation, task, action, and result. Give enough context to make the problem clear, then spend most of your time on what you did. Finish with the outcome or what you learned. If it was a team effort, give the team credit while making your own contribution clear.

Suppose you’re asked about handling competing deadlines. A concise answer could sound like this:

“In my last role, two client reports were due the same Friday, and a teammate became unavailable. I needed to keep both commitments without sending work we hadn’t checked. I reviewed what was left, asked each client which sections they needed first, and arranged a second review with a colleague. Both clients received their priority sections on time, and we agreed on delivery times for the rest. Afterward, I added an earlier capacity check to our weekly planning.”

That example works because the listener can follow the decision, not just hear that the candidate is “good under pressure.” Use numbers when you know them and they add meaning. Don’t invent a percentage because you think every story needs one.

Your examples can come from paid work, school, volunteering, caregiving, or personal projects when those experiences show the skill in question. If you’re changing fields, explain the connection rather than expecting the interviewer to make it.

Practice answers out loud, but don’t memorize a script

Draft notes in bullets, then answer aloud without reading full sentences. Written answers often sound clear until you try to say them. Speaking reveals where you spend too long setting up a story, skip your own contribution, or trail off without a result.

Practice these prompts first:

• “Tell me about yourself.” Give a brief account of your relevant background, what you’ve been doing recently, and why this role is a sensible next step. It isn’t a request for your whole life story.
• “Why this role and this organization?” Connect a real feature of the work to your experience or interests.
• “Tell me about a challenge, disagreement, or mistake.” Use a specific story and explain your response without blaming others.
• “What would you bring to this job?” Choose two or three strengths and back them with evidence.

A friend or mentor can ask follow-up questions; a recording can show you habits you don’t notice while speaking. Ask for pointed feedback: Was the answer easy to follow? Did I answer the question? Could you tell what I actually did? Then practice once more with the feedback in mind.

Treat a technical exercise, case interview, presentation, or portfolio review as a separate assignment. Ask the recruiter what format to expect, review the instructions, and practice the kind of work you’ll be asked to show. Generic interview stories won’t replace preparation for a job-specific assessment.

Bring questions that help you make a decision

An interview should leave you with a clearer picture of the job, not just a chance to appear interested. Prepare more questions than you expect to ask so you can choose the ones the conversation hasn’t answered, including CareerOneStop’s recommended questions about responsibilities, how performance is measured, development, and the challenges of the role.

Good questions are specific enough to prompt a useful answer:

• “What would you want the person in this role to accomplish in the first three months?”
• “What tends to slow this team down, and how would this role help?”
• “How do you decide which work takes priority when requests arrive at once?”
• “What does strong performance look like after the first year?”
• “How does the team give feedback and handle mistakes?”

Adapt the questions to the person you’re meeting. Ask a teammate how work gets handed off; ask the hiring manager what success looks like; ask the recruiter about the remaining steps and expected timeline. Pay attention to whether answers are concrete and consistent. If something important remains unclear—hours, location, travel, pay, or reporting lines—it’s reasonable to ask. You need enough information to decide if the role fits your life.

Remove avoidable problems the day before

Confirm the time, time zone, address or meeting link, interviewer names, and any materials you were asked to bring. Re-read your application so you can discuss what you actually submitted. Choose clothes that fit the setting and let you focus on the conversation. Pack or save your résumé, portfolio, work samples, and a few notes if they’ll help.

For an in-person meeting, check the route and allow for delays. For a video interview, test your camera, microphone, connection, lighting, and meeting setup. Close distracting tabs and notifications, and keep a phone number handy in case the connection fails. You can glance at a short list of examples or questions, but reading from a script usually makes it harder to listen.

During the interview, pause if you need to think. Ask for clarification when a question is vague, and answer the question you were asked before adding context. If you don’t know an answer, say how you would approach the problem instead of bluffing. Near the end, ask about next steps so you know when—and with whom—to follow up.

Send a specific thank-you, then respect the hiring timeline

As soon as the interview ends, jot down who you met, what each person emphasized, any concern you want to address, and the timeline they gave you. Those notes will make your follow-up useful rather than generic.

Send a short email, ideally within a day. Thank the interviewer, refer to something you discussed, and restate your interest if it’s genuine. Penn Career Services advises keeping the note brief and tailored. If several people interviewed you, send each a distinct note when you have their contact information; if you don’t, ask the recruiter whether they can pass along your thanks.

A note might read:

Subject: Thank you — Project Coordinator interview

Hi Maya,

Thank you for speaking with me about the Project Coordinator role. I appreciated hearing how the team is improving handoffs between sales and operations. The process work I described—especially setting clearer review points for client reports—seems closely related to that priority. I enjoyed our conversation and remain interested in the role.

Best,
Jordan

Don’t use the thank-you note to repeat your entire interview or claim a connection that wasn’t there. If you promised a work sample or other information, send it promptly and say what you’re attaching.

If the employer gave you a decision date, wait until it has passed before checking in. If no timeline was given, a polite message after about two weeks is reasonable: restate your interest, ask whether there’s an update, and leave it there. Keep pursuing other opportunities while you wait.

Preparation can’t guarantee an offer. It can give you something better than a rehearsed performance: clear evidence of what you can do, questions that reveal what the job is really like, and a professional way to close the conversation.