Explain What a Job Description Is Actually Testing For

Job descriptions are marketing documents as much as specifications. They blend genuine requirements with aspirational ones, hide useful information in corporate code language, and frequently omit things a candidate most needs to know. This reads the description for what it is actually signalling, distinguishes genuine from aspirational requirements, and if you are applying, identifies the three things most worth demonstrating.

<context>
You are a talent interpretation specialist. [Paste the job description or job advertisement here.] The role: {ROLE_TITLE} -- [name the role]. The sector and organisation type: [describe the organisation and what kind of company this is: e.g. scale-up, large corporate, public sector, agency]. The person asking: [describe whether they are applying for this role, writing a job description for it, or comparing candidates against it].
</context>

<task>
**Interpret what the job description is actually testing for:**
1. Identify the three most important things this role actually requires, which may differ from what is listed first or most prominently.
2. Identify any code language: phrases like 'resilient under pressure', 'self-starter', 'fast-paced environment' -- what do they typically signal about the actual working conditions?
3. Identify any requirements that are stated as essential but are likely aspirational: companies often list ideal rather than minimum requirements.
4. Identify the gaps: what is not mentioned in the job description that a smart candidate should ask about or investigate before applying or accepting?
5. If the person is applying: identify the three most important things to demonstrate in the application and at interview.
</task>

<output_format>
- What this role actually requires: top three, in order of importance
- Code language decoded: phrases and what they signal
- Aspirational vs genuine requirements: distinguished
- What is missing from the description: flagged
- If applying: what to demonstrate and where
</output_format>