Interview Experience Compilation Skill

name: Interview Experience Compilation
description: Assist users in recording and reviewing interview experiences, outputting according to the interview template (Info + Detail + Analysis + Summary). Use when the user is organizing interview notes, conducting a post‑interview review, recording interview details, or providing interview dialogue/transcripts.

Interview Experience Compilation

Help users complete interview documentation and review, and create the corresponding file in Yuque.

1. Core Requirements

Content format: Use Markdown. List every question asked by the interviewer in the Detail section in chronological order. Casual or non‑technical chat (e.g., “Where are you now?”, “Did you graduate?”, “That’s about it, do you have any questions?”) can be omitted. Numbering for the candidate’s questions restarts: the interviewer’s questions are numbered consecutively (1, 2, 3 …), and when the “candidate questions” segment begins, the candidate’s questions start again from 1 (1, 2, 3 …), independent of the previous sequence.
Highlighting: Questions whose answer coverage is below 80 % must be bolded in the Detail section; “standard‑answer” (八股) questions are subject to stricter handling.
Separate answer block: Poorly answered questions are listed separately in the Brief Complete Answer Summary: problem analysis + reference standard answer, isolated from the main question list. One analysis per bolded question: each bolded question in Detail must have exactly one corresponding analysis in the Analysis section; do not merge multiple bolded items into a single analysis.
Chronological order: Sections and questions in Detail must follow the exact order of the interview.
User‑filled fields: Interview Result, Interview Recording, and Value are to be left for the user to fill; do not modify or overwrite them. When outputting, leave them empty or use the default placeholder (see below). Do not insert “(please fill in)”.
Document placement & table entry: New interview documents must be saved under the “Interview Experiences” node of the Record knowledge base, ordered most recent first (newest on top). At the same time, add a new row to the table inside the “Interview Experiences” document; columns that are uncertain can be left blank for the user to complete later.
Question wording – parentheses integration: If a question in Detail contains parenthetical additions (e.g., “Follow‑up: xxx”, “Interviewer example: xxx”), merge the parenthetical content into the main question, forming a single complete sentence, and do not keep the parentheses separately.
Example: “How is data consistency ensured between multi‑level caches? (Follow‑up: how to guarantee strong consistency for orders?)” → “How is data consistency ensured between multi‑level caches? How do you guarantee strong consistency for orders?” The corresponding title in Analysis must match the merged wording.
Question wording – single coherent item: When a question consists of multiple sub‑questions but should remain a single item (i.e., not split into separate questions), ensure the wording is self‑contained. Add any missing subjects (based on context, e.g., “ConcurrentHashMap”) and combine sub‑questions into one fluent sentence so that the question makes sense on its own and avoids ambiguous pronouns or disjointed fragments.

2. Yuque Interview Document Template

(Template content to be inserted here by the system when creating the document.)

3. Template Explanation & Prohibited Actions

Item	Explanation
Info – optional fill	Company full name, interview department, position, date, and duration. These can be completed via online search or from user input. If interview duration is unknown, use `min`.
Info – do not modify	Interview Result, Interview Recording, Value: keep empty or retain whatever the user has already entered; do not replace or generate content, and do not show “(please fill in)”.
Detail	Divide into sections according to interview flow (e.g., Self‑Introduction & Background → Project Deep‑Dive → Technical Challenges / Coding / Standard Questions → Candidate Questions). Interviewer‑asked questions are numbered consecutively; candidate‑asked questions restart numbering at 1. Bold any poorly answered questions. Parenthetical follow‑ups or examples must be merged into the main question. When multiple sub‑questions form a single item, add missing subjects and make the wording seamless.
Brief Complete Answer Summary	Only for the bolded questions in Detail. Provide one entry per bolded question: the question (in bold), analysis of the problem point, a reference standard answer, and an empty Analysis field for the user to fill later. Do not use headings for these entries (avoid `###`).
Summary	Leave Feeling and Shortage empty or write them based on the bolded questions. Shortage must point to specific knowledge or skill gaps, not vague statements.

4. Execution Steps

Parse input: Identify company/department, interviewer questions, candidate answers, and the order of interview stages from the user‑provided transcript.
Complete Info (fields only): Fill in company full name, department, position, date, and duration using web search or inference. Keep Interview Result, Interview Recording, and Value empty or as originally provided; never output “(please fill in)”.
Write Detail: Follow the chronological flow, list each question, bold those with < 80 % coverage, merge parenthetical notes, and ensure each combined question is self‑contained.
Create Brief Complete Answer Summary: For every bolded question, add a separate entry containing:
- Question (bold, using **Q序号：问题** placeholder)
- Problem‑point analysis
- Standard answer reference (concise, sourced from reliable material)
- Analysis field left blank for later personal notes.
Write Summary: Populate Feeling and Shortage (specific gaps) based on the bolded items; leave other fields empty if no information is available.

5. Important Notes

No fabrication: All questions and answers must come from the user’s transcript or reasonable web research. If something cannot be inferred, mark it as “(to be completed)”.
Stricter handling of standard questions: Any basic or “standard” question that is answered incompletely or incorrectly must be bolded and supplied with a reference answer.
Output format: The entire output must be a single Markdown document ready to be pasted into Yuque. If a new Yuque document is required, the title should be formatted as YYYY/MM/DD 公司/部门一面/二面/三面.
Prohibited output: Never include “(please fill in)” anywhere. Leave the user‑filled sections (Interview Result, Interview Recording, Value) blank.

Originally written by Li Wei (李唯_) and published in Chinese on 后端技术栈全书 (Full-Stack Backend Engineering). Translated and adapted for DriftSeas with permission.

Interview Experience Compilation Skill