interviewing

Overview

Manage the interview stage of an application. This skill owns tracker advancement to interviewing, interview logs, follow-up notes, and handoff to interview-coach for deep preparation.

Use interview-coach when the user only wants a prep brief. Use interviewing when there is process state to track.

Workflow

State layer: reads and updates applications.md, writes per-application interview notes, and may invoke interview-coach. See state-layer contract.

1. Identify the application

Run node "{job_hunt_skills_root}/scripts/scaffold-state.mjs" if state files are missing.

Gather:

• Company.
• Role.
• Application id if known.
• Interview stage: recruiter screen, hiring manager, technical, panel, presentation, final, or other.
• Date/time, format, interviewer names/functions, and recruiter notes if available.
• Job posting or application folder if available.

If no tracker row exists, offer to create one directly at status: interviewing. This is allowed by state-layer section 4. When inserting, populate comp_expected, source, and next_action_date (default: the next interview date if known, otherwise today + 7 days) from conversation. See state-layer §3 for the back-compat read/write rules.

If a row exists at saved or applied, ask whether to advance it to interviewing. Never regress a later status. When advancing, also update next_action_date to the next concrete commitment (interview date, take-home due date, or follow-up window).

2. Create or update the interview log

Write or append my-documents/applications/{id}/interview-log.md.

Suggested structure:

# Interview Log - {Company}, {Role}

## Current Status

- Stage:
- Next interview:
- Format:
- Contacts:
- Open questions:

## Timeline

### YYYY-MM-DD - {Stage}

**Before:** What is known going in.

**After:** Notes, signals, concerns, and follow-up actions.

**Follow-up:** Sent / not sent / not needed.