# Turn a Job Description Into an Interview Preparation Plan

To prepare for an interview, turn each important duty in the actual job description into one possible question. Then connect that question to a true example from your own work. Record what the example proves, what it does not prove, and what you need to ask the employer. Use one saved full description throughout. The description guides your preparation. It cannot tell you the actual interview questions.

Start with the description you already have from the employer or your application. Read it yourself. You do not need a data collection tool to prepare for one interview when you have the full text.

Your result will be a set of interview evidence cards. Each card is a short worksheet that connects a source duty to an honest answer. Evidence means a specific task, action, or result you can explain truthfully.

A public post about self-taught development asks what a person needs to know to get a first job. That broad concern supports a useful preparation rule: explain work you have actually done. The post does not establish how often applicants ask this exact question or what employers will ask. [Public first-job context — published 3 June 2022, retrieved 16 August 2026; one public post, not a demand measure](https://www.reddit.com/r/learnprogramming/comments/v47qfk/i_selftaught_had_my_firstever_interview_for_a_web/).

## 1. Save one full description

Freeze the description before you write answers. Here, freeze means save a copy that stays unchanged during this preparation session.

1. Save the full description for the job you will discuss.
2. Save the role title and employer name when available.
3. Save the source URL, which is the page address.
4. Record when you read or saved it.
5. Keep the saved text beside your preparation cards.

Use the full description, not only the job title or a short search extract. A short extract can omit a duty or its limits. For example, it can leave out words that show whether you will own a task or help someone else do it.

Do not combine duties from several jobs into one interview plan. You are preparing for a specific role. If two copies of its description differ, name the copy you use and keep the difference as a question. Do not silently merge them.

If the full text is unavailable, record that gap. Missing text does not mean the role has no duties. Obtain the full description before you treat the duty list as complete. You can still prepare general personal examples, but their connection to this role remains uncertain.

## 2. Collect public text only if you need it

If you need to collect the public description, the [LinkedIn Jobs Actor](https://apify.com/chronometrica/linkedin-jobs-scraper) is a documented collection option. An Actor is a hosted program that collects data. A Task is a saved set of inputs for an Actor.

The public [Extract LinkedIn Job Descriptions from URLs Task — checked 25 October 2026; page presence confirmed, saved settings and runtime unverified](https://apify.com/chronometrica/linkedin-jobs-scraper/examples/extract-linkedin-job-descriptions-from-urls) is a starting point. Its title does not prove what its current saved settings contain. Check those settings before use.

The following input is a proposed small search. It is not a copied Task setting, and it was not run for this guide.

```json
{"fetchJobDetails":true,"location":"United States","maxItems":3,"maxPagesPerSearch":1,"saveOnlyUniqueItems":true,"searchTerm":"data analyst"}
```

2. Collect public text only if you need it

Replace `data analyst` with your role and `United States` with your location. Keep one role and one location. The purpose is to obtain text you can inspect, then select the one description for your interview.

The input asks for job details through `fetchJobDetails`. It sets `maxItems` to 3 and `maxPagesPerSearch` to 1. These are limits of three records and one page per search. They do not promise three results, complete descriptions, or collection of your target job. `saveOnlyUniqueItems` requests unique items. Still check that the selected record belongs to the correct job.

The public default build, version 0.2.26, declares these input fields. A static schema check passed. A schema defines allowed field names and value types. A static check examines the input without running the Actor. It does not prove live collection, complete coverage, or successful output. [Public default build — checked 25 October 2026; declared fields and static validation only, no live run](https://api.apify.com/v2/acts/kkH2KvT3IfbFf6A6P/builds/default).

A field is one named value. A record is one collected job entry. Keep these declared output fields when available:

| Field | What to retain or check |
| --- | --- |
| `jobId` | The LinkedIn job identifier. Keep it as text. |
| `jobUrl` | The source address for the selected job. |
| `title` | The title as collected. |
| `companyName` | The employer name as collected. |
| `locationRaw` | The source location wording. |
| `descriptionText` | The description you will read and save. |
| `descriptionStatus` | The returned description status. Check it with the text. |
| `scrapedAt` | The recorded collection time. |

Some values can be missing. A missing employer name means unknown, not an unnamed employer you may invent. Missing description text means unavailable evidence, not zero duties. The collection time does not establish when the employer last changed the description.

Check identity and text before you prepare cards. If you cannot connect the record to your interview role, leave that connection unresolved. If collection fails or returns no records, return to the employer page or your saved application copy. An empty result does not prove that the job does not exist.

Use public job text for collection. Keep your own interview notes, application records, and private project files separate. The declared fields support collecting description evidence. They do not establish that the Actor writes or verifies your interview answers.

## 3. Separate duties from other wording

Read the saved description once for meaning. Read it again to mark three groups:

- Central duties: work the person will perform.
- Required conditions: qualifications or conditions the description treats as necessary.
- Preferred extras: things the employer wants but does not state as necessary.

Keep each exact source passage beside your label. A company paragraph that names a tool does not automatically make that tool a required applicant skill.

Choose duties because they describe important work in this description. Use stated responsibility, recurring outputs, and explicit emphasis as guides. If the description gives no order of importance, do not invent one.

This guide starts after you have chosen the role for interview preparation. If you still need to compare roles against your experience, use the separate [job fit guide](/en/articles/jobs-fit-shortlist/). Keep job ranking out of these cards.

For each selected duty, write one plausible scenario question. A scenario is a possible work situation. The question is a preparation aid, not a forecast of the interview script.

## 4. Build one evidence card per duty

Use the same fields on every card. This makes gaps easy to see and keeps source wording separate from your interpretation.

| Card field | What to write |
| --- | --- |
| Card name | A short name for the duty. |
| Source reference | The job reference, source URL, and saved observation time. |
| Exact duty | The unchanged source passage. |
| Possible question | One plausible question about doing that work. |
| Example type | Paid work, class project, volunteer work, other personal work, or hypothetical response. |
| Situation | The real task and its setting. |
| Your action | What you personally did. |
| Result | What happened and what you can support. |
| Evidence limit | What the example does not demonstrate. |
| Employer question | A question about an unclear duty, review process, or measure of success. |
| Open gap | Missing experience or information. |

Situation, action, and result form a simple answer structure. The situation explains the task. The action explains your contribution. The result explains what followed.

Keep team work and personal work distinct. You can describe a team result, but say which actions were yours. Do not change “helped check” into “owned the process.”

Use a number only when you know its basis and unit. A count of files is not a count of people. A count of checked rows does not show money saved. If you do not know the result, write that it is unknown. Do not replace an unknown result with zero or an estimate presented as fact.

## 5. Work through one fictional example

This complete example is original fiction. It is not an Actor run, a customer result, or an observed employer finding. All duties, applicant actions, and outcomes below are invented for teaching.

The fictional full description contains three duties:

1. “Reconcile source files.”
2. “Explain a report.”
3. “Handle a failed refresh.”

Reconcile means compare records or totals and explain differences. A refresh is an update that brings new data into a report or system.

The fictional applicant has a class project for reconciliation and a volunteer report example. The applicant has no example of handling a failure in a live work system.

### Card 1: Reconcile source files

Exact fictional duty: “Reconcile source files.”

Possible question: “Tell me about a time you found and explained a difference between source files.”

Example type: Class project.

Situation: The applicant compared two files supplied for a class assignment. The files described related records, but some totals differed.

Your action: The applicant checked the record keys, which are values used to identify records. The applicant compared totals and recorded the differences. The applicant kept the original files unchanged.

Result: The class submission explained the differences found in those supplied files. This is a fictional result, not a measured product outcome.

Evidence limit: The example supports a discussion of checking and explaining differences. It does not establish responsibility for a live employer reporting process.

Employer question: Use question Q1 below to clarify who reviews changes that follow these checks.

A concise fictional answer could be: “In a class project, I compared two source files. I checked their record keys and totals, then documented the differences. My submission explained those differences. This was class work, so I have not shown ownership of a live reporting process.”

### Card 2: Explain a report

Exact fictional duty: “Explain a report.”

Possible question: “Tell me about a report you explained to someone who did not prepare it.”

Example type: Volunteer work.

Situation: The applicant prepared an explanation of a volunteer report.

Your action: The applicant described what the report covered, explained its main figures, and stated a known limit. The applicant separated the report findings from suggestions about what to do next.

Result: The applicant delivered the explanation. The example does not include evidence that it changed a decision or improved an outcome.

Evidence limit: Giving an explanation does not prove that every reader understood it. It also does not establish a financial benefit.

Employer question: Use Q1 to clarify who reviews report changes.

A concise fictional answer could be: “For a volunteer report, I explained its scope, main figures, and one limit. I separated the findings from my suggestions. I can describe what I presented, but I have no evidence that it changed a decision.”

### Card 3: Handle a failed refresh

Exact fictional duty: “Handle a failed refresh.”

Possible question: “What would you do if a report refresh failed?”

Example type: Hypothetical response. Hypothetical means proposed, rather than something that happened.

Situation: No past incident is claimed.

Proposed action: The applicant would first check what failed and whether the displayed data remained current. The applicant would follow the employer's procedure, record the problem, and contact the responsible support person. Any repair would depend on the applicant's authority and the available instructions.

Result: No actual result exists for this proposed response. Record “not applicable to a past event,” not “zero failures.”

Evidence limit: The answer shows a proposed approach. It does not prove experience with live incident handling or a successful repair.

Employer question: Use Q2 to ask what support is available.

A clear fictional answer could be: “I have not handled a failed refresh in a live work system. I would check the failure and the data status, then follow the team procedure and contact the responsible support person. I would need to learn your process and my authority before taking repair action.”

### Keep the counts separate

The fictional worksheet contains two distinct employer questions:

- Q1: “Who reviews report changes?”
- Q2: “What support is available when a refresh fails?”

Q1 supports two cards. Repeating its reference does not create another distinct question.

The arithmetic is:

- 3 source duties × 1 card per duty = 3 preparation cards.
- 2 cards with past examples + 1 card with a stated gap = 3 cards.
- 2 distinct employer questions = 2 questions, separate from the card count.

There are two past examples in this fiction. There are not three proven work experiences. The hypothetical response adds preparation, not experience.

## 6. Keep gaps and private evidence clear

A gap belongs on the card. It does not need an invented story.

If you have related experience, explain the connection and its limit. A class reconciliation task can help you explain your checking method. It does not become paid production experience because the duty sounds similar.

If you have no relevant past example, state that fact and prepare a clearly labelled hypothetical response. Ask what the employer expects you to own and what support exists.

Do not turn each gap into a course list during interview preparation. If you later decide to study the missing work, use the separate [skills learning plan guide](/en/articles/jobs-skills-curriculum/). The current task is to prepare an honest answer and a useful question.

Keep confidential files private. Describe your work without sharing private customer records, internal reports, or restricted project files. If you cannot show an item, state that limit. Do not imply that the interviewer has inspected evidence you have only described.

## 7. Rehearse and check the complete worksheet

Read each possible question aloud. Answer from the card in short sentences. Keep the duty, your action, the result, and the limit easy to identify.

Check every card against the saved description:

1. Confirm that the quoted duty exists in that description.
2. Confirm that the possible question concerns that duty.
3. Name the example type before describing it.
4. Separate your action from the team's action.
5. Check each result against what you actually know.
6. Keep unknown values unknown.
7. State the evidence limit.
8. Keep proposed actions separate from past actions.
9. Connect an unclear point to an employer question.

Stop and correct a card if its source text is missing, its job identity is unresolved, or its answer claims work you did not do. If you remember the task but cannot support a number, remove the number and explain the result you can support.

Keep your source copy unchanged. If new source facts arrive, save them with their date and revise the affected cards. If you correct a mistake in your own account, correct the card at once. Keep new employer facts separate from your earlier assumptions.

## Use the cards to decide what to say and ask

Start with one important duty from your saved description. Complete one card and rehearse it. Then prepare the remaining central duties. Bring the employer questions that resolve the most important unknowns about responsibility, review, and success.

Use your own copy of the description when it is complete. If you need public job text, start with the [LinkedIn Jobs Actor](https://apify.com/chronometrica/linkedin-jobs-scraper), inspect the input, and verify the selected description before using it. The finished result is a truthful preparation worksheet. It is not a predicted interview script or a score for your chance of being hired.

## Sources

- [LinkedIn Jobs Actor public default build 0.2.26 — checked 25 October 2026; declared input and output fields, static validation only, no live collection or coverage claim](https://api.apify.com/v2/acts/kkH2KvT3IfbFf6A6P/builds/default)
- [Extract LinkedIn Job Descriptions from URLs Task — checked 25 October 2026; exact Task ID and page presence confirmed, saved settings and runtime unverified](https://apify.com/chronometrica/linkedin-jobs-scraper/examples/extract-linkedin-job-descriptions-from-urls)
- [Public first-job preparation context — published 3 June 2022, retrieved 16 August 2026; one public post, not representative demand or employer evidence](https://www.reddit.com/r/learnprogramming/comments/v47qfk/i_selftaught_had_my_firstever_interview_for_a_web/)