Turn a Job Description Into an Interview Prep Sheet

An interview prep sheet turns a job description from a page you read into a set of prompts you can practice. The goal is to connect the employer’s priorities to a small number of genuine examples from your experience, then prepare questions that help you understand the role.

This approach reflects how job-related interviews may be designed. The U.S. Office of Personnel Management explains that job analysis connects a role’s tasks with the competencies needed to perform them. Its guidance on structured interviews also distinguishes between behavioral questions about past experience and situational questions about what a candidate would do.

You can use the same logic from the candidate’s side: identify the work, name the skills behind it, and prepare evidence that shows what you have actually done.

Step 1: Mark the job description by priority

Save the exact job description you applied to. Postings can be edited or removed, and you want to prepare from the version connected to your application.

Read it once for context. On the second pass, mark:

• Recurring responsibilities
• Required technical knowledge
• Transferable skills, such as communication, prioritization, or collaboration
• Deliverables, such as reports, launches, analyses, or client presentations
• People the role works with
• Problems the person will be expected to handle

Pay particular attention to repeated verbs. Words such as analyze, coordinate, present, improve, advise, and lead point toward actions the employer may want to discuss. MIT recommends reviewing the job description for technical and transferable skills and noticing the action verbs used.

Next, combine related items into three to five priority themes. For example, a project manager posting might produce these themes:

• Planning work across multiple teams
• Managing deadlines and changing priorities
• Communicating with stakeholders
• Identifying and resolving delivery risks
• Improving processes

You don’t need a separate story for every sentence in the posting. A strong example may support several themes.

Step 2: Turn each priority into possible questions

For every theme, write one behavioral question and, when useful, one situational question.

Behavioral question pattern

Use prompts such as:

• Tell me about a time you had to coordinate work across several groups.
• Give me an example of a deadline that was at risk.
• Describe a time you explained a complex issue to a nontechnical audience.

Situational question pattern

Use prompts such as:

• What would you do if two stakeholders gave you conflicting priorities?
• How would you approach a project with an unclear scope?
• What would you do if an important deliverable was likely to be late?

This exercise doesn’t predict the exact questions you’ll receive. It gives you realistic practice prompts based on the work described. The University of Pennsylvania’s interview guidance recommends looking at situations in the job description and considering how an interviewer could ask about similar past experiences.

Step 3: Select three to five genuine examples

Choose a small set of stories you can adapt rather than trying to prepare a different answer for every possible question. MIT recommends preparing three to five stories as bulleted outlines.

Your examples can come from:

• Current or previous jobs
• Freelance or contract projects
• Internships
• Volunteer responsibilities
• Academic projects
• Student organizations
• Community activities

Relevance matters more than finding an example with an identical setting. A volunteer project may demonstrate planning, stakeholder communication, or conflict resolution just as clearly as a paid role.

Create a quick story inventory. For each possible example, write:

• The job requirement it supports
• The situation or problem
• Your specific responsibility
• The actions you personally took
• The result you can substantiate
• What you learned or would repeat

If an example doesn’t clearly show your contribution, replace it or narrow it until your role is understandable.

Step 4: Build an evidence card for each story

Use the STAR structure to organize your notes:

• Situation: What was happening, and why did it matter?
• Task: What were you responsible for?
• Action: What did you personally decide, create, change, or communicate?
• Result: What happened, and what evidence supports that outcome?

Both MIT and the University of Pennsylvania emphasize making your own actions clear. This is especially important when the work involved a team. Explain the team context, then shift to what you contributed.

Your result doesn’t always need to be a percentage or dollar figure. You might be able to substantiate that the team met a deadline, reduced an approval step, completed a migration, retained a client, received approval, or created a process that colleagues continued using. If you don’t have an exact number, don’t manufacture one. You can also review this guide to describing resume accomplishments without exact numbers.

Editorial example

Suppose the posting says: “Coordinate cross-functional projects and communicate progress to senior stakeholders.”

A prep-sheet entry might read:

• Requirement: Cross-functional coordination and stakeholder communication
• Likely question: Tell me about a project that required coordination across several teams.
• Situation: A product update depended on input from operations, support, and engineering.
• Task: I was responsible for maintaining the schedule and preparing weekly status updates.
• Action: I created a shared milestone tracker, confirmed owners for unresolved items, and separated decisions from general updates in the weekly summary.
• Result: The teams completed the required reviews before the planned release meeting.
• Possible follow-up: What did you do when an owner missed a deadline?

This is an illustration, not a script or a performance claim. Your version should use only details you can explain and support.

Step 5: Prepare honest bridges for gaps

You may find a requirement for which you don’t have a direct example. Don’t force an unrelated story or claim experience you don’t have.

Instead, prepare a bridge with three parts:

1. State the limit clearly.
2. Identify the closest relevant experience.
3. Explain how you would approach the new responsibility.

For example:

“I haven’t owned an enterprise software migration. I did coordinate a smaller system rollout for two departments, including requirements, testing, user communication, and issue tracking. I’d bring that process discipline while learning the organization’s migration standards and escalation paths.”

This keeps the answer grounded in real experience while showing how you think. The same principle applies when you tailor a resume without inventing experience.

Step 6: Add questions for the employer

Your prep sheet should also help you evaluate the opportunity. UC Berkeley advises candidates to research the role, prepare meaningful questions, and consider how well their experience matches the employer’s needs.

Build questions from areas where the job description is vague. Useful options include:

• Which responsibilities will need the most attention during the first few months?
• What would a strong first project look like?
• How are priorities set when several stakeholders need support?
• Which teams does this role work with most often?
• What problems prompted the organization to open this position?
• How will the manager evaluate progress in this role?

Avoid using interview time to ask questions that the posting or employer website answers clearly. Focus on priorities, working relationships, constraints, and expectations.

Step 7: Rehearse from notes, not a script

Practice each example aloud, but keep the written version short. MIT cautions that scripting or memorizing stories can make it harder to adapt them during an interview. The same story may need a different emphasis depending on whether the question concerns leadership, communication, planning, or problem-solving.

Ask a practice partner to listen for three things:

• Was my personal contribution clear?
• Did the example answer the question?
• Could you understand and remember the result?

The University of Pennsylvania also recommends practicing with someone who doesn’t already know the situation, since an interviewer will need enough context to follow your answer.

A one-page prep-sheet format

For each priority requirement, capture:

• Requirement or competency
• Words used in the job description
• Likely behavioral question
• Primary example
• Backup example
• My responsibility
• Two or three key actions
• Supportable result
• Likely follow-up question
• Question I want to ask the employer

Keep the sheet compact enough to review shortly before the conversation. If you need help checking whether your existing positioning matches the role, My Role Builder is a tool that shows how a profile reads for target roles.

Your finished prep sheet should give you three to five flexible stories, a clear view of the employer’s priorities, honest language for experience gaps, and several useful questions. That preparation gives you a practical structure while leaving room to listen and respond naturally.