Deep Job Description Analysis for Interview Preparation

Format

Markdown Parameterized

Inputs

job_description (text) · Required company_context (text) · Required

Outputs

job_description_analysis (text, markdown)

Replace the ${…} placeholders with your values before using this prompt. See parameters and defaults below.

Analyze the following job description (JD) in depth and with a practical, real-world focus. My goal is not only to understand the written requirements, but also to uncover the role’s function in actual business settings, its responsibilities, required capabilities and working methods, collaboration patterns, risks, and development paths. Use this analysis to guide targeted learning, skill development, and interview preparation.

Job description:
${job-description}

Company or business context, if available:
${company-context}

Analyze the role from the perspective of its actual work inside an organization, not just the language used in the job posting. When the JD is vague, abstract, or overstated, clearly distinguish among:
- **Explicitly stated:** directly supported by the JD or supplied context.
- **Inference:** a reasonable interpretation, not a confirmed fact.
- **Needs confirmation:** information that should be verified with the employer.

## 1. Core role profile and positioning
Summarize the role’s core mission in 3–5 sentences, explaining the fundamental problem the company is trying to solve by hiring for it. Then discuss:
1. The role’s typical position in the organization.
2. Its likely reporting line and most frequent cross-functional partners.
3. Its internal and external functions.
4. The typical pace, workload, response expectations, and prioritization demands.
5. Whether the role is primarily strategic, execution-focused, coordinating, delivery-oriented, supportive, or a combination.

Label conclusions that are inferences and identify what needs confirmation.

## 2. Essential knowledge areas
Organize the required knowledge by importance and level, and break it down into specific concepts, rules, methods, tools, processes, or industry standards. Explain:
1. What knowledge the role must have and the concrete subtopics within each area.
2. What is essential at entry level, what is an advanced requirement, and what is an added advantage at a higher level.
3. For specialist fields or regulated industries, the relevant rules, standards, methodologies, regulatory logic, and industry practices.
4. For cross-border, cross-region, or cross-business-line work, the differences in requirements across locations, situations, or business units.
5. If formal credentials are not emphasized, what business understanding, commercial judgment, or industry knowledge is actually needed.

Make the breakdown specific enough to support study and skills review; do not stop at broad topic labels.

## 3. Key documents, materials, and deliverables
List the types of documents, materials, templates, reports, proposals, records, forms, or system outputs this role is likely to handle. For a non-document-focused role, cover its equivalent core outputs, such as plans, requirements documents, process designs, dashboards, user feedback, project plans, retrospective reports, meeting notes, presentations, campaign strategies, pricing proposals, or experiment records.

For each type, explain:
1. Its purpose.
2. The business situations in which it is used.
3. What the role should focus on when reviewing, writing, revising, or using it.
4. Common risks, errors, and overlooked details.
5. What demonstrates professionalism, experience, and practical capability.

Mark uncertain items as inferences rather than established facts about this specific employer.

## 4. Practical skills and working methods
Go beyond the wording of the JD and describe how the work is likely to be done in practice. Cover:
1. The end-to-end workflow: receiving a request, identifying the problem, breaking down the work, planning, executing, tracking, validating, reviewing, and closing the loop.
2. The key actions at each stage.
3. The role’s most important judgment skills and common decision points.
4. How to collaborate with business teams, management, peers, upstream and downstream teams, external vendors, and partners.
5. Methods for managing external resources, suppliers, partners, customers, or third parties where relevant.
6. How hard skills are applied in real situations—for example, research, writing, data analysis, project coordination, tool use, reporting, solution design, presentations, risk identification, and retrospectives.
7. Whether the role most tests efficiency, accuracy, communication, judgment, influence, or resilience under pressure.

Describe concrete actions and methods, not just abstract qualities such as “strong communication skills.”

## 5. Role-specific strategies, judgment frameworks, and working models
Where relevant, identify the strategies, mental models, and decision frameworks commonly used to handle typical problems in this role. These may include:
- Prioritization and urgency assessment.
- Risk classification.
- Cost-benefit trade-offs.
- Resource allocation.
- Planning a path to execution.
- Decision trees for trade-offs.
- Escalation mechanisms.
- Boundaries of responsibility and collaboration.
- Goal decomposition.
- Standard response paths for recurring problems.

For each applicable model, explain why it suits the role, what problem it solves, and when it is most useful. Do not imply a framework is used by this employer unless the supplied information supports that conclusion.

## 6. Competency checklist: simulate a typical work scenario
Simulate a central business scenario for this role as a timeline, project progression, or representative “mission.” Show the full process, including:
1. How the request or issue arrives.
2. How urgency and importance are assessed.
3. How information is gathered and the problem diagnosed.
4. How relevant people are consulted and coordinated, and how work is moved forward.
5. How a solution is developed and the deliverable produced.
6. How unexpected issues, repeated revisions, or conflicts among stakeholders are handled.
7. How the work is closed out and reviewed.

Demonstrate the role’s analysis, decision-making, execution, and retrospective capabilities across the full workflow. Base the scenario on the JD and label any assumptions as inferences.

## 7. Learning plan and career development
For preferred qualifications, bonus skills, or advanced requirements that an applicant may not yet have, provide a specific and actionable plan. Address:
1. The most significant likely capability gaps implied by the JD.
2. Which areas to prioritize if my current foundation is incomplete.
3. How to build each capability, including learning topics, practice methods, concrete outputs, and practical experience.
4. Which skills can be improved in the short term and which require sustained development.
5. How to progress from being able to do the work, to doing it well, and then doing it reliably and deeply.

Recommend relevant industry reports, research sources, professional databases, specialist media, high-quality newsletters or columns, books, public materials from benchmark companies or teams, and useful case studies or public retrospectives. Keep recommendations relevant to the role and clearly identify suggestions that depend on assumptions about the industry or employer.

## 8. Output requirements
- Use a clear hierarchy and make the analysis easy to scan.
- Briefly define specialized terms at first use.
- Label inferences explicitly and never present them as confirmed facts.
- If the JD lacks information, provide the most rigorous analysis possible from what is available rather than resorting to generic filler.
- Make the result useful for interview preparation, targeted learning, role understanding, and realistic work simulations.
- Avoid empty adjectives; provide specific, actionable, and verifiable analysis.