+# Interview Template — Backend Developer
+ 
+## Stage 1 — Screening (15–20 min)
+ 
+Conducted by Project Manager (Mikkel Nygaard) or hiring manager. Video call, no panel.
+ 
+**Goal.** Confirm interest in this role specifically, availability, work authorisation, salary expectation in our range, no honesty red flags.
+ 
+**Template.**
+ 
+1. *(2 min)* Welcome. Brief intro to Media Tech and SPYN. Frame: short, mutual screening.
+2. *(3 min)* Candidate's two-minute version of why this role specifically.
+3. *(5 min)* Two structured questions: see Screening questions below.
+4. *(3 min)* Practicalities: location, availability, salary, notice period.
+5. *(3 min)* Candidate's questions.
+6. *(close)* What happens next; expected timeline.
+ 
+**Screening questions for Backend Developer.**
+ 
+- The AI Diary generation queue is backing up at peak.
+- We're adding a new sub-processor for AI translation.
+ 
+**Scoring categories.** Communication clarity (key risk), motivation fit, basic role fit.
+ 
+## Stage 2 — Main interview (45–75 min)
+ 
+Conducted by hiring manager plus one team member from an adjacent role.
+ 
+**Template.**
+ 
+1. *(5 min)* Welcome. Set expectation: depth, not breadth.
+2. *(20–30 min)* Two scenario-based questions:
+   - **Scenario A.** The AI Diary generation queue is backing up at peak. p95 latency for the user-visible 'generate' call has gone from 4s to 14s. Walk us through your investigation, in order.
+   - **Scenario B.** We're adding a new sub-processor for AI translation. From a backend perspective, what changes — code, config, tests, deploy?
+3. *(10–15 min)* Past-work conversation. Candidate picks one project they're proud of; we ask: what was the goal, what trade-offs, what would you do differently, what did you learn, who else was involved.
+4. *(5–10 min)* Working-style: deadlines, feedback, disagreement.
+5. *(10 min)* Candidate's questions.
+ 
+**Scoring categories.** Role-specific technical depth (key risk), problem decomposition, working-style fit, communication of judgement, candidate's questions.
+ 
… 23 more lines

• Markdown lintpassed
• Spell-checkpassed
• Skill-references resolvepassed