portfolio

Use when someone needs a structured interview preparation plan before their interview process begins — a study schedule, gap analysis by topic area, and STAR story bank. This is planning, not practice. Triggers on: "interview prep plan", "how to prepare for FAANG", "coding test study plan", "면접 준비 계획", "코딩테스트 어떻게 준비해", "기술 면접 공부법", "FAANG 준비". Best for: engineers 2-12 weeks out from interviews who need a structured plan; gap analysis by coding/system design/behavioral topics; calibrating study to a specific company type. Not for: live interview practice (use portfolio-interview), portfolio review (use portfolio-feedback), or resume tailoring (use resume-tailorer).

Use when preparing for a job application or career transition end-to-end — from analyzing a JD through to interview preparation. Triggers on: "job application workflow", "이직 준비 전체", "취업 프로세스 시작", "career transition", "job search process", "이직 프로세스 처음부터". Best for: active job searches, targeting a specific role, or preparing for a company. Not for: general career advice, salary negotiation only, or passive networking.

Use when someone wants to know which companies or company types their portfolio would appeal to — without a specific JD in hand. Triggers on: "which companies fit my portfolio", "where should I apply", "어느 회사에 잘 맞아?", "네이버 지원하려는데 어때?", "어디 써볼 만해?", "어떤 회사 유형이 맞아?". Best for: candidates without a target company yet; fit scores across company types (large platform, startup, fintech, global tech); portfolio positioning advice. Not for: JD-specific matching (use portfolio-jd), resume tailoring (use resume-tailorer), or live interview practice.

Use when someone shares a portfolio and wants an overall assessment from an interviewer's perspective — overall impression, scoring across dimensions, and prioritized improvement areas. Triggers on: "포트폴리오 피드백 해줘", "내 포트폴리오 어때?", "portfolio review", "how does my portfolio look", "review my portfolio", or when a portfolio is shared without a more specific request. Best for: 5+ year backend engineers wanting an honest overall read; identifying which dimensions (technical depth, ownership, impact narrative) are strongest/weakest. Not for: rewriting specific sections (use portfolio-rewrite), JD matching (use portfolio-jd), live interview practice (use portfolio-interview).

Use when someone wants to practice defending their work in a realistic mock interview — the interviewer asks questions grounded in the actual portfolio, evaluates answers, and gives coaching feedback. Triggers on: "모의 면접 해줘", "인터뷰 연습", "면접 준비 같이 해줘", "질문 던져줘", "포트폴리오 기반으로 면접 봐줘", "mock interview", "interview simulation", "practice interview". Best for: 5+ year backend engineers preparing to defend their portfolio work; practicing technical depth probes, gap questions, and failure/recovery scenarios. Not for: study planning (use interview-prep), portfolio review (use portfolio-feedback), JD gap analysis (use portfolio-jd).