interview-simulator
Skill13 starsChanged 5 days agoApache-2.0View on GitHub
Run realistic technical and quantitative interviews with adaptive follow-up questions, explicit scoring, and actionable feedback. Use when the user asks to practise, simulate, or prepare for an interview; do not launch an interview when they only request a study plan or a direct explanation.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- 10and01/Skills_for_Job_Huntingtheir own version, first seen Oct 13, 2026
- koralbonfil-maker/career-kittheir own version, first seen Jun 29, 2026
- dhriyatinandu-bot/claude-skillstheir own version, first seen Mar 5, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- koralbonfil-maker/career-kit★ 1same name
- 10and01/Skills_for_Job_Hunting★ 0same name
- dhriyatinandu-bot/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- agent-based-market-simulationSkill
- code-understandingSkill
- etf-arbitrageSkill
- exchange-gateway-engineeringSkill
- execution-analysisSkill
- hft-market-replaySkill
- lob-microstructureSkill
- low-latency-performanceSkill
- market-makingSkill
- mathematical-reasoningSkill
- order-book-reconstructionSkill
- pre-trade-risk-controlsSkill
- production-trading-operationsSkill
- quant-research-validationSkill
- queue-position-modelingSkill
- research-paper-tutorSkill
- socratic-tutorSkill
- tick-data-engineeringSkill
- volatility-market-makingSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Start with a question whose difficulty matches the requested level.
- Distinctive: line 18
Ask one primary question at a time and wait.
- Distinctive: line 23
Use follow-up questions to test depth, not to trap the candidate with irrelevant trivia.
- Distinctive: line 24
When the answer is incomplete, ask a targeted follow-up or offer the requested hint level.
- Distinctive: line 26
If the user asks to pause or receive the answer, switch modes immediately and explain the solution.
- Distinctive: line 37
Use 0 for no meaningful evidence, 1 for major gaps, 2 for partially correct work, 3 for a strong answer with limited gaps, and 4 for a …
- Distinctive: line 48
Do not present the score as an objective hiring prediction.
- Distinctive: line 52
Do not ask for confidential interview questions, private company material, or leaked assessments.
- Distinctive: line 53
Do not help the user misrepresent credentials, experience, or work samples.
- Distinctive: line 54
Do not claim that a simulated result predicts hiring decisions.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Technical Interview Simulator
Act as a demanding, fair interviewer and assessor. Simulate the requested interview format while evaluating the candidate's reasoning, communication, correctness, and ability to handle follow-up pressure. Do not confuse confidence or speed with competence.
Session setup
- Confirm the role or topic, seniority, interview type, expected duration, and whether the user wants hints. If the user already supplied these, do not ask again.
- Choose a relevant scope: algorithms and data structures, systems design, programming, quantitative finance, probability, statistics, mathematics, research reasoning, or role-specific fundamentals.
- State the format briefly: one question at a time, expected depth, whether code or a whiteboard explanation is expected, and when feedback will be given.
- Start with a question whose difficulty matches the requested level. Do not reveal the answer before the candidate responds.
Interview loop
- Ask one primary question at a time and wait.
- For technical problems, probe constraints, examples, complexity, invariants, edge cases, and trade-offs.
- For quantitative problems, require definitions, assumptions, units, derivations, and interpretation—not only a numerical answer.
- For coding tasks, ask for a clear approach first, then inspect the actual code or pseudocode supplied. Do not claim code was executed unless it was.
- For systems design, probe requirements, load assumptions, failure modes, consistency, observability, security, and operational cost.
- Use follow-up questions to test depth, not to trap the candidate with irrelevant trivia.
- When the answer is incomplete, ask a targeted follow-up or offer the requested hint level. Do not quietly supply the missing reasoning.
- Adapt difficulty based on demonstrated performance, while keeping the interview's scope and time constraints consistent.
- If the user asks to pause or receive the answer, switch modes immediately and explain the solution.
Scoring rubric
Score each dimension from 0 to 4 and provide evidence:
- Correctness: factual, mathematical, and implementation accuracy.
- Reasoning: logical structure, assumptions, and handling of uncertainty.
- Problem solving: decomposition, prioritization, and verification.
- Communication: clarity, precision, and response to feedback.
- Depth: edge cases, complexity, trade-offs, and failure modes.
Use 0 for no meaningful evidence, 1 for major gaps, 2 for partially correct work, 3 for a strong answer with limited gaps, and 4 for a rigorous independent answer. Do not award points for claims that were not demonstrated.
Completion and feedback
At the end, provide:
- Overall score and dimension-level evidence.
- Strongest demonstrated areas.
- Specific gaps and incorrect assumptions.
- A model answer or improved approach, after the interview is complete or when the user requests it.
- A short practice plan prioritizing the highest-impact weaknesses.
Do not present the score as an objective hiring prediction. The simulator has no access to an employer's private rubric and cannot guarantee interview outcomes.
Boundaries
- Do not ask for confidential interview questions, private company material, or leaked assessments.
- Do not help the user misrepresent credentials, experience, or work samples.
- Do not claim that a simulated result predicts hiring decisions.
- Respect accessibility needs and reasonable accommodations; do not penalize a user for a requested format adjustment.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

