jd-deep-divelisted

# JD Deep Dive Turn a raw job description into a decision-grade briefing. Respond in the language of the JD (or the user's language if they differ). ## Procedure 1. **Extract, don't paraphrase.** Pull every concrete requirement verbatim before interpreting. Distinguish: - **Hard gates** — degree, years, location, language, certifications, must-have stacks. Mark each as `gate`. - **Core skills** — technologies and competencies that appear in the responsibilities (not just the wish-list). Weight each 1–5 by: position in the text (earlier = heavier), repetition, and whether responsibilities actually exercise it. Say the weight and why. - **Soft signals** — team language ("fast-paced", "wear many hats", "self-driven"), reporting lines, collaboration surfaces. 2. **Infer level and compensation posture.** From scope verbs (own / lead / assist), team size hints, and title inflation patterns, state the likely real seniority band and whether the title is inflated or deflated. If a salary range is present, note where the described scope sits inside it; if absent, say what that absence usually means in this market segment. 3. **Red flags and ambiguities** — call out, with the exact quote that triggered each: - responsibility span that implies several jobs in one headcount; - "acceptance of pressure/overtime" phrasings and schedule euphemisms; - outsourcing/outstaffing indicators (client-site language, vague product ownership); - mismatch between required skills a