Skip to content
Skills Library
Personal productivity · Learning & explanation

interview-simulator

/interview-simulator

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.

Licence
Apache-2.0
Last repository change
11.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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.

Original author description

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.

How it works

  1. Session setup
  2. Interview loop
  3. Scoring rubric
  4. Completion and feedback
  5. Boundaries
Original SKILL.md headings · 52 lines, 517 words
SKILL.md preview
---
name: interview-simulator
description: 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.
---
# 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

1. 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.
2. Choose a relevant scope: algorithms and data structures, systems design, programming, quantitative finance, probability, statistics, mathematics, research reasoning, or role-specific fundamentals.
3. 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.
4. 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.

Versions

RepositoryScoreLicence
This page · voyager67/JaneStreet-Agentic-Skills100Apache-2.0
curiositech/windags-skills100Apache-2.0
curiositech/some_claude_skills100MIT
serejaris/kimi-skills100MIT

Database snapshot: 13.11.2026 · package version 7c13ba5ceccb (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100clarice
    Conducts realistic mock interviews with detailed feedback and scoring. Use for interview prep, behavioral questions, technical interviews, STAR practice, system design interviews, or interview coaching.
  • 90interview-prep
    Use when the user asks to prepare for an interview, run a mock interview, practice interview questions, or get ready for a graduate application interview. Generate question sets, simulate Q&A, and provide feedback around the target supervisor, program, and the user's own experience.
  • 100technical-interview-roadmap
    This skill should be used when the user wants a technical interview preparation roadmap, coding interview study plan, or DSA practice plan tailored to a specific company and role. Trigger phrases include "technical interview roadmap", "coding interview prep for", "DSA roadmap…
  • 96prepare-for-interview
    Prepare for a specific job interview with GetMattered and practice answers grounded in the user's experience. Use this skill whenever the user has an interview invite, wants questions for a role or company, or wants to rehearse an interview. Does not apply to a job.
  • 86interview-coach
    When user asks for interview prep, mock interview, practice questions, behavioral questions, technical interview, HR round, salary negotiation, STAR method, common interview questions, company research, interview tips, confidence building, answer feedback, body language tips,…
  • 100mock-interview-drill
    Conduct realistic mock interviews with follow-up question drills across Behavioral, Technical, and Case scenarios, providing structured STAR framework diagnostics and polished sample answers to improve performance. Triggers when users mention practicing for interviews, preparing…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.