The 2026 hiring market looks at "the ability to actually perform in the field, not the credentials listed on a resume." Notion + GitHub + Behance and other searchable portfolioIf you accumulate these, a structure is formed in which offers come in from headhunters, Wanted, and Remember even if you do not apply yourself.
Supported Areas
| Area | Description |
|---|---|
| Field-specific Guide | Portfolio strategies tailored to developers, designers, marketers, and planners |
| Project Description | STAR-based project explanation, quantification of contributions |
| Platform Optimization | GitHub, Behance, Notion, personal blog portfolio |
| Portfolio Review | Analysis and feedback on improvements to existing portfolios |
Reference Guide: references/portfolio-by-field.md
Practical Portfolio Patterns (Korean Hiring Market)
1. "The Notepad Strategy That Passed Even Without Looking Pretty" (PMPO Passed)
It is not design but structure and quantificationthat make a pass.
[1] 한 줄 요약 (USP)
[2] 프로젝트 5개 (각 1페이지)
[3] 각 프로젝트:
- 배경 (1줄)
- 본인 역할 (1줄)
- 한 일 3~5 bullet
- 정량 결과 (숫자·배수·증감)
[4] 전체 6~10페이지 압축
It is possible to pass with only text at the level of a notepad (.txt).
2. 1-Hour Notion Portfolio (Verified by 20,000 Views)
6-section structure for making it quickly:
[1] 한 줄 자기소개 + 사진
[2] About — 경력 한 단락
[3] Skills — 기술·도구 5~7개
[4] Projects — 3~5 카드 (썸네일 + 한 줄 + 링크)
[5] Experience — 회사·기간·역할
[6] Contact — 이메일·LinkedIn·GitHub
Notion template + custom domain (oopy.io, super.so) — completed in 1 hour.
3. Job Posting-Tailored Portfolio (The Key That Sets You Apart)
- JD keyword frequency analysis → Select 3-5 matching projects from your own
- Company tone/style analysis → Adjust your portfolio design
- Reflect the company's recent issues → Emphasize cases connected to your experience
- Things not in the JD but helpful Add 1-2 (differentiation)
4. What Makes a PM Portfolio Different
For PMs, outputs are abstract — methods for making them concrete:
| PM Deliverable | Portfolio Expression |
|---|---|
| Decision-making | Before/After chart + decision tree |
| Collaboration | Stakeholder diagram + meeting minutes excerpts |
| Product changes | Pre- and post-launch screenshots + UX flow |
| Impact | Quantify revenue, retention, CSAT |
| Learning | Quote from retrospective (1-2 paragraphs) |
5. Searchable Notion Portfolio (Offers Even Without Applying)
- SEO optimization — title, description, URL slug
- Public settings + allow search engine indexing
- LinkedIn profile integration — portfolio URL in the headline
- GitHub Profile README — specify portfolio link
- 1-2 blog posts — project retrospectives and insights
6. Know-how from 877 shared resumes and career descriptions
- Most recent experience = detailed (40% weight)
- Mid-level experience = quantitative results only (30%)
- Early career = one-line summary (10%)
- Other (awards, qualifications, languages) = condensed (20%)
On the last page, one paragraph on "the kind of person I want to work with" — appeal to character.
7. One-page project overview (leading to results)
Each project is 1 page (A4).
project:
title: "○○ 프로젝트"
period: "2024.03 ~ 2024.08 (6개월)"
role: "PM (5명 팀)"
background:
problem: "..."
company_context: "..."
approach:
- "..."
outcome:
- metric: "월 매출 30% 증가"
- metric: "리텐션 15% 개선"
learning: "..."
Portfolio strategy by field
Developer
In the 2026 job market, the spread of Vibe Coding has raised the technical depth companies demand even further. The key is to demonstrate the ability to solve problems in collaboration with AI.
| Component | Requirement level | Description |
|---|---|---|
| GitHub profile | Required | Commit history, contribution graph, 3-5 pinned projects |
| Technical blog | Strongly recommended | Problem-solving process, reasons for technology choices, learning records |
| Project README | Required | Architecture diagram, tech stack, how to run |
| Live demo | Recommended | Vercel/Netlify deployment link, demo video |
| Open source contributions | Differentiator | PRs, issue resolutions, library contribution records |
Required items for a project README:
## 프로젝트명
한 줄 설명
### 기술 스택
[프레임워크] [DB] [인프라] [CI/CD]
### 핵심 기능
- 기능 1: 설명 (본인 기여 부분 명시)
- 기능 2: 설명
### 아키텍처
[다이어그램 또는 설명]
### 성과/배운 점
- 응답 시간 40% 개선 (Redis 캐시 적용)
- 동시 접속 1,000명 처리 (부하 테스트 결과)
Designer
In the AX (AI Transformation) era, a designer must go beyond making screens pretty and create business impact.
| Component | Requirement level | Description |
|---|---|---|
| Behance/Dribbble | Required | 5-8 highly polished projects |
| Figma file | Strongly recommended | Component system, prototype, design tokens |
| Process document | Required | Full process from problem definition → hypothesis → experiment → validation |
| AI use cases | Recommended | Process of using tools such as Midjourney and Figma AI |
| Collaboration records | Differentiator | Jira/Confluence collaboration, records of communication with developers |
Case study structure:
1. 문제 정의: 어떤 사용자 문제를 해결했는가
2. 리서치: 사용자 인터뷰, 데이터 분석 결과
3. 가설 설정: 어떤 가설을 세웠는가
4. 디자인 과정: 와이어프레임 → 프로토타입 → 최종 디자인
5. 실험/검증: A/B 테스트, 사용성 테스트 결과
6. 비즈니스 임팩트: 전환율 변화, 이탈률 감소 등 수치
Marketer
Proving results with numbers is the core of a marketing portfolio.
| Component | Requirement level | Description |
|---|---|---|
| Campaign case | Required | Structure: goal → strategy → execution → results (numbers) |
| Data analysis | Strongly recommended | GA4, SQL, Excel utilization analysis cases |
| Content portfolio | Recommended | SNS posts, blog, newsletter samples |
| Performance dashboard | Differentiation | KPIs organized with Notion/Looker Studio |
Planner (PM/PO)
The key is to show the thought process from problem discovery to resolution.
| Components | Necessity | Description |
|---|---|---|
| Proposal samples | Required | PRD, functional specification, wireframe |
| UX research | Strongly recommended | User interviews, survey analysis, personas |
| Data-driven decision-making | Recommended | A/B test results, metric analysis cases |
| Sprint operation | Differentiation | Agile process experience, retrospective records |
Project description writing framework
■ 프로젝트명
한 줄 요약
■ 기간/인원/역할
YYYY.MM - YYYY.MM | N명 | 담당 역할
■ 배경 및 문제
왜 이 프로젝트를 시작했는가
■ 나의 기여 (STAR 기반)
S: 프로젝트 시작 당시 상황
T: 내가 맡은 구체적 과제
A: 실행한 행동과 의사결정
R: 정량적 성과 또는 정성적 배움
■ 기술 스택 / 도구
사용한 기술, 프레임워크, 도구 목록
■ 링크
GitHub / 배포 URL / 발표 자료
Platform-specific optimization tips
| Platform | Optimization points | 2026 weights (as perceived in the Korean job market) |
|---|---|---|
| GitHub | Profile README, pinned projects, commit frequency, issue/PR activity, open source contributions | Required for developer roles — Wanted·Jobplanet IT weight is the highest |
| Behance/Dribbble | Cover image quality, tag optimization, project descriptions in both English and Korean | Required for design roles |
| Figma | Component system, prototype, design tokens, handoff guide | Design roles — proof of collaboration skills |
| Notion | Table of contents structure, use of toggles, embeds (Figma/YouTube), sharing settings, Allow search engine indexing | All roles — custom domain with oopy.io·super.so |
| Personal tech blog | SEO optimization, series composition, RSS feed, comment interaction, focused on the "problem-solving process" | Development·Planning — key differentiation for new hires |
| Headline + Featured section (pinned portfolio URL) + recommendations | Cumulative for employed professionals — triggers headhunter offers | |
| GitHub Pages·Vercel | Own domain + live demo + analytics tools (GA) | Developer differentiation — proof of collaboration·operations skills |
2026 field-specific portfolio differentiation points
According to IT role hiring trends on Wanted·Jobplanet, the number of roles where GitHub·Notion portfolios carry more weight than academic background has increased. This skill automatically recommends the following differentiation factors by field.
| Field | 2026 differentiation factors |
|---|---|
| Development | Problem-solving process working with AI tools (LLM pair programming retrospective), actual traffic operations experience |
| Design | Design system cases in the AX (AI Transformation) era, business impact (conversion rate·churn rate) |
| Marketing | GA4·SQL-based data analysis, A/B test results, performance dashboard (Looker Studio·Notion) |
| Planning/PM | A/B testing + user interviews + decision tree, "Why that decision" Why-First thought process |
Trigger keywords
Portfolio, project, GitHub, Behance, Figma, Notion, Notion portfolio, technical document, work collection, 1-page selling, searchable portfolio, headhunter exposure
Usage examples
- "Frontend developer portfolio structure guide — for a 5th-year job change"
- "Organize this project into a technical document. [Project description] (STAR + quantitative)"
- "Write a GitHub profile README. Emphasize backend + AI tool collaboration experience"
- "Designer Behance portfolio review — check whether business impact is lacking"
- "Notion portfolio 6 sections — marketing role, make it searchable"
- "1-page PDF exposed on Wanted + GitHub pinned project guide"
- "PM portfolio — turn abstract results into a decision tree + Before/After"
Standalone workflow
Reference guide (references/) cannot be used, proceed to the next step.
Step 1: Identify field/purpose
- Job field: development/design/marketing/planning
- Purpose: new build / improvement of existing / organizing a specific project
- Target platform: GitHub/Behance/Notion/blog/other
Step 2: Project inventory
- List owned projects
- Organize each project's contribution, tech stack, and results
- Select 3-5 projects to include in the portfolio (quality over quantity)
Step 3: Structure design
- Check required components by field
- Project placement order (put the strongest project first)
- Overall flow: self-introduction → key projects → tech stack → contact
Step 4: Content writing
- Write project technical document (STAR framework)
- Apply platform-specific optimization
- Place visual elements (screenshots, diagrams, videos)
Execution rules
- Receive user request → identify field and purpose
references/{id}.mdLoad if present → execute according to the guide--deepthinkor complex multi-field portfolio → if sequential-thinking MCP is installed,mcp__sequential-thinking__sequentialthinkinguse it; if not,ultrathinkreplace with keyword-based deep reasoning or general step-by-step reasoning- After generating structure and draft, request user review
Troubleshooting
- Lack of project experience: Personal projects, hackathons, open source contributions, and side projects are also excellent portfolio material. Even a solo project is fine if it shows the problem-solving process.
- Difficulty quantifying results: Even without direct sales results, you can quantify it with activity metrics such as "acquired N users," "N code reviews," and "N documents written."
- Lack of design skills (developer): Notion, a GitHub README, or a simple wireframe is enough. Content quality takes priority over visuals.
- Experience in multiple fields: Place the projects most relevant to the position you are applying for first, and separate supplementary skills into a separate section.
Related skills / post-processing chain
Descriptive text in the portfolio, such as project descriptions, About paragraphs, case studies, and README body text, are all deliverables meant to be read by people. After completing the draft, go through the following chain to remove AI patterns and polish it into natural Korean.
moai-career:portfolio-guide → moai-core:ai-slop-reviewer → moai-content:humanize-korean
moai-core:ai-slop-reviewer— First review and correction of AI-generated patterns (generic expressions, clichés, overuse of adjectives)moai-content:humanize-korean— Second humanization with sentence rhythm and colloquial expressions
For application documents, use moai-career:resume-builder, for JD analysis, use moai-career:job-analyzer, and for interview preparation, use moai-career:interview-coach.
Non-descriptive deliverables such as tables, screenshots, diagrams, and quantitative dashboards are not subject to this chain. Apply it only to the descriptive text portions.
Shared agents
Agents from other plugins available in this plugin:
| Agent | Affiliation | Purpose |
|---|---|---|
| quality-evaluator | moai-core | PASS/FAIL judgment of deliverable quality |
| korean-tone-reviewer | moai-hr | Review of honorific usage by job level and appropriateness of business tone |
When not to use this skill
- Writing cover letters/resumes: For writing application documents, use the
moai-career:resume-builderskill. - Interview preparation: For general interviews rather than portfolio presentation interviews, the
moai-career:interview-coachskill is suitable. - Job posting analysis: For JD analysis and competency matching, use the
moai-career:job-analyzerskill. - Actually building a website: To code a portfolio site yourself, use development tools.