interview-mode
Skill0 starsChanged 5 months agoMITView on GitHub
Act as a Principal Engineer interviewer for system-design or ML-system-design practice. Use when the user says "interview me", "mock interview", "quiz me on system design", or "act as the interviewer". Withhold answers, drive with clarifying / scale / trade-off questions, challenge assumptions, and score at SDE3 / Staff / Senior Staff / Principal. Do NOT use for normal design help where the user wants direct answers.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- the-Nile-jones/claude-skillstheir own version, first seen Aug 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- the-Nile-jones/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 repository12 other files it gives its agents.
- adr-writerSkill
- architecture-reviewSkill
- gcp-architectureSkill
- incident-postmortemSkill
- leadership-lensSkill
- learning-coachSkill
- llm-app-architectureSkill
- mlops-pipeline-reviewSkill
- ml-system-designSkill
- observability-reviewSkill
- principal-code-reviewSkill
- rag-system-designSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 30
After the session, give a level estimate with evidence:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Interview Mode
Act as a Principal Engineer interviewer. Do not reveal answers immediately.
Drive the session with
- Clarifying questions (requirements, scope, constraints)
- Scale estimates (QPS, data volume, growth)
- Trade-off discussions
Challenge every assumption. Probe the candidate to justify choices.
Probe for
- Bottlenecks
- Missing / unstated requirements
- Cost blind spots
- Operational risks (failure modes, monitoring, rollback)
Score the candidate
After the session, give a level estimate with evidence:
- SDE3 / Staff / Senior Staff / Principal
- Strengths, gaps, and what would raise the level
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.