# Single Listing Deep-Dive

When the user picks one specific job listing and says "I want to work there" — extract ALL contact info, application method, and provide a tech stack comparison.

## Workflow

### 1. Extract Full Listing Details

Navigate to the job detail page and capture:

- **Company name** and description
- **Role title** and experience level
- **Full description** (not just summary)
- **Required skills** (exact list)
- **Tech stack** (exact list from "our offer" / "what we use")
- **Location** and remote/hybrid policy
- **Posted date** (check freshness)
- **Contact info**: phone number, email address, website URL
- **Application method**: is there a "Solliciteer nu" / "Apply now" button? Does it link to a form, a mailto, LinkedIn, or an external ATS?

### 2. Find the Company's Own Website

- The job listing page may have a company website link — extract it
- If not, search: `"<company name>" <city> <country>`
- Navigate to the company site to understand what they actually do
- Check for a `/careers` or `/jobs` page on their own site (may have more detail)

### 3. Identify the Application Path

Determine exactly how to apply:

| Signal | Action |
|--------|--------|
| `mailto:...` link | User emails directly — offer to draft an email |
| External form link | Navigate to it, check what fields are needed |
| LinkedIn "Easy Apply" | Open the LinkedIn listing |
| "Solliciteer nu" button | Click it to see where it goes (form, mailto, redirect) |
| No button, just contact info | Email the listed contact address |

### 4. Tech Stack Comparison

For each technology in the job's stack that the user doesn't know:

1. **Name what it is** (runtime? framework? database? tool?)
2. **Give a parallel** the user already knows (e.g. "Bun is like Node.js but faster")
3. **Show syntax** — a minimal code example the user can recognize
4. **Rate difficulty** (Low / Medium / High) and estimated ramp-up time
5. **Explain why the company chose it** (startup speed, ecosystem, etc.)

Format as a table or structured list — not a wall of text. Use code blocks for syntax.

### 5. Present Actionable Summary

End with a clear summary:

```
═══════════════════════════════════════════
 RECOMMAND — JUNIOR SOFTWARE ENGINEER
═══════════════════════════════════════════

WEBSITE:    https://recommand.eu/
EMAIL:      info@recommand.eu
PHONE:      +32 474 68 68 87
LOCATION:   Corda Gebouw Corda 6 - HAL A, Hasselt
APPLY:      Email info@recommand.eu (no form)

STACK:      Bun · Hono · TypeScript · React 19 · PostgreSQL · Docker

YOUR FIT:   TypeScript ✓  Docker ✓  Full-stack ✓  AI-native ✓
            (React 19 and Bun/Hono are new — 1-2 week ramp-up)

═══════════════════════════════════════════
```

## Pitfalls

1. **"Solliciteer nu" may be a mailto link in disguise** — click it and check the browser URL / console to see if it's `mailto:...` or an external URL.
2. **Company website may auto-redirect** (e.g. `recommand.eu` → `recommand.eu/en`). Navigate to the root and let it redirect, then snapshot.
3. **Job may be listed on multiple platforms** (Corda Campus + LinkedIn + company site). Check if the application method differs per platform.
4. **Don't assume a form exists** — many early-stage startups just want an email. Check before telling the user to fill out a form.
5. **Phone numbers on job pages are often the company's general line** — not a recruiter's direct line. Flag this to the user.