talalahmed311/cornerman

코너맨 익스플로러

스파링 파트너, 응원이 아닌.

현실적이고 적합한 기술적인 모의 인터뷰를 실시하는 Claude Skill. 다단계, 턴-by-turn, 솔직한 스코프와 연구 계획 끝에.

---

무엇 그것

이력서 및 작업 설명하십시오. 그것은:

1. 이력서를 읽고, 당신의 고위 (주니어 / 중 / 수석 / 직원)를 분류하고 인터뷰 계획을 구축하십시오.
2. 프로젝트 딥 다이브를 실행 - 실제 충격에 대한 조사, 영향 이야기가 얇을 때 기술적인 기본으로 방울.
3. 대상 JD의 실제 요구 사항에 배경을 브릿지.
4. ** 코딩 문제 (async take-home) ** 블라인드 75에서 레벨로 크기. 당신은 그것을 해결, 코드를 붙여, 그리고 코너맨은 당신의 선택을 통해 걸어 - 정확, 복잡성, brute-force vs. 최적의.
5. ** 시스템 설계 (HLD, async take-home)에 대한 직원 구조 인 사람으로 전환 ** - 당신은 디자인 (화이트 보드 사진, Excalidraw, 스크린 샷, 무엇이든) 스케치, 짧은 서면 접근으로 업로드 한 다음 라이브 Q & A에서 걸어.
6. ** 저수준 디자인 (LLD, 살아있는) ** — 자료 모형, APIs, concurrency, 가장자리 케이스를 위한 동일한 체계로 급상승.
7. 명세.

Cornerman 🥊

A sparring partner, not a cheerleader.

A Claude Skill that runs a realistic, adaptive technical mock interview against a specific job. Multi-phase, turn-by-turn, with an honest scorecard and study plan at the end.

---

What it does

Give it your resume and a job description. It will:

1. Read the resume, classify your seniority (junior / mid / senior / staff), and build an interview plan.
2. Run a project deep-dive — probes for real impact first, drops into technical fundamentals when the impact story is thin.
3. Bridge your background to the target JD’s actual requirements.
4. Give you a coding problem (async take-home) from the Blind 75, sized to your level. You solve it, paste your code, and Cornerman walks through your choices — correctness, complexity, brute-force vs. optimal.
5. Switch into a staff-architect persona for a system design (HLD, async take-home) — you sketch the design (whiteboard photo, Excalidraw, screenshot, whatever), upload it with a short written approach, and then walk through it in a live Q&A.
6. Zoom into the same system for low-level design (LLD, live) — data model, APIs, concurrency, edge cases.
7. Deliver a structured scorecard, honest hire signal, and study plan.

Expect deliberate pressure and evidence-tied feedback. That’s the point — that’s what a cornerman does between rounds.

Async take-home phases

Two phases (coding and system design) run as take-home rather than live:

• Setup — Cornerman poses the problem and answers your clarifying questions with concrete numbers (e.g. “10M DAU, 100:1 read/write, p99 under 200ms”). Not “you decide” — real interviewer numbers.
• Solve — Cornerman records the start time to the MCP, schedules an auto-grade callback at your time budget (via the scheduled-tasks MCP), and waits silently. No hints.
• Submit — you paste code (coding) or upload a diagram + written explanation (system design). Cornerman cancels the auto-grade callback and grades the real submission.
• Timeout branch — if you never return, the scheduled callback fires in a fresh conversation, loads your session from disk, records the no-submit, and saves a floor score. You lose that round; the rest of the interview still stands.
• Walkthrough — after the grade, Cornerman runs a live Q&A on your specific choices.

How to invoke

In a Claude conversation, provide:

• Your resume — upload a PDF/DOCX or paste the text.
• The target role — a JD text, a job posting URL, or a company URL + role title.
• Say something like “cornerman, interview me for this role”, “run a mock interview”, or “prep me for this JD”.

Cornerman will trigger and start with intake.

Optional at intake