# Role-to-evidence map

## Baseline and claim rules

Baseline: the two user-supplied PDFs in `/Users/pj/Downloads/Headhunter for Job/`, read on 23 October 2026. Exact paths, modification times, SHA-256 hashes and page counts are in `sources/cv_baseline.json`; extracted text is retained alongside it. File modification dates in Seoul time: Leadership 10 October 2026, 22:34; Senior Product 18 October 2026, 03:28. Modification time is file metadata, not a new approval date. They are the supplied application baseline, not independently audited business records. Draft answers below are proposed phrasing, not new approved facts.

The latest supplied versions are used rather than assuming an older registry is current. The Leadership CV separates KidsLoop Education Director (April–September 2019) and Senior PM (September 2019–August 2021). The Senior Product CV dates Senior PM from April 2019. Preserve both source documents; confirm chronology before reusing exact dates externally. No CV was edited.

| Role need | Strongest project / personal decision | Supported result | Source | Claim limit | Likely follow-up |
|---|---|---|---|---|---|
| Roadmap and requirements coordination | Rakuten: combined 20 interviews, account health and 30-day usage to prioritize reliability, sharing and access over expansion | Broader improvements associated with 40% growth in active business accounts during tenure | Both CVs, p1 Rakuten | Association; cannot attribute all growth to one prioritization decision | What did you defer? How was active business account defined? |
| Feature-to-launch decisions | Edugo: sole product leader, delivery with five engineers; prototyped workflow in Gumloop then partnered on LangChain deployment | Tested workflow logic moved into engineering delivery | Both CVs, p1 Edugo | Engineers were delivery partners, not established direct reports; no model-training claim | What was your artifact? What changed before production? |
| Metric-based improvement | KidsLoop: centralized automated learner reporting across five regions | 80% fewer staff hours per reporting cycle | Both CVs, p1 KidsLoop Senior PM | Operational hours, not learner achievement; exact baseline window absent from CV | How measured? What quality checks remained? |
| AI-agent prototype or automation | Edugo transcript-to-activity agents, prompt/input/output records and rapid workflow tests | Prototyping and engineering handoff supported by CV | Both CVs, p1 Edugo | Gumloop prototype is not personal implementation of all production code | Show input/output, failure path, handoff and your decision |
| Team workflow adoption | Fayston: ChatGPT/Codex training, reusable workflows/templates for ten teachers/leaders | Estimated 20% savings on supported tasks from feedback and observation | Both CVs, p1 Fayston | Estimate; no controlled trial, no whole-school savings claim | Which tasks? How did people verify outputs? |
| B2B pricing and plans | KidsLoop: worked with sales, finance and data to model learner acquisition and content costs in five regions | Informed pricing recommendations | Both CVs, p1 Head of Product | Not a pricing launch, payment integration or conversion uplift | What assumptions dominated? What would you test? |
| Global operations / English | Edugo distributed engineers in Dubai, Argentina and Germany; Rakuten global platform | Cross-region product delivery and executive reporting | Both CVs, p1 | Do not invent launch-by-country results | How did you resolve conflicting requirements asynchronously? |
| B2B customer needs | Rakuten interviews, usage reviews and core access/share workflows | Prioritization informed by customer evidence | Both CVs, p1 | Interview anecdotes are not prevalence estimates | How did you avoid the loudest customer's roadmap? |
| Generative AI product experience | Edugo quality criteria, Sentry tracing, teacher/client checks | Broader improvements: 30% content relevance increase, 25% fewer support tickets | Both CVs, p1 | Attribution across broader changes; metric method not in CV; not model training/RLHF | How was relevance labeled? Which trace led to which action? |
| Delivery reliability | Rakuten cycle-time analysis and repeatable Jenkins checks with engineering | Release cycle time reduced 30% | Both CVs, p1 | Shared implementation; exact distribution/window need original evidence | What bottleneck? What guarded escaped defects? |
| Leadership / coaching | KidsLoop: led ten PMs/designers, promoted three, managed $500K hiring/training budget | People and budget responsibilities | Both CVs, p1 | Distinguish this leadership scope from five-engineer Edugo delivery | How did you coach decision quality? |
| APIs / technical partnership | HYCON: coordinated mainnet, wallet, developer-tool/API releases | Twelve releases; APIs enabled 100+ hackathon participants | Both CVs, p1 | Delivery leadership, not blockchain protocol invention | How did you define developer readiness? |
| Adoption and enablement | Collaborative Classroom: coordinated curriculum, tools, documentation and training with distributed team | Tools served 2,000+ districts; launches contributed to 20% first-year revenue growth | Both CVs, p2 | Contribution, not sole cause; districts served not personal direct customers | What made adoption stick after launch? |
| Early commercial product building | Talklet co-founder product strategy, personalized lessons, feedback and subscriptions | Business secured first paying institutional client | Senior Product CV p2 | Team/company outcome; no verified client count beyond first or personal sales attribution | What was your contribution? What is still a prototype? |

## Three story cards to memorize

**Rakuten / prioritization:** “I use customer evidence to decide what deserves attention.” Problem: core reliability and access needs competed with expansion. My behavior: combined interviews with health/usage evidence and prioritized core workflows. Impact: broader work was associated with active business-account growth; this is not an isolated causal estimate. Stop after the impact.

**Edugo / AI delivery:** “I turn a promising AI workflow into testable product behavior.” Problem: generated activities needed level fit and trustworthy release. My behavior: prototype, specify, investigate with traces, partner with engineers and retain teacher/client checks. Impact: broader improvements reported better relevance and fewer tickets; detailed attribution remains a follow-up.

**KidsLoop / useful automation:** “I measure automation by completed work and remaining staff effort.” Problem: regional reporting relied on manual collection. My behavior: led centralized automation across five regions. Impact: staff hours per reporting cycle reduced 80%. Do not add unverified implementation mechanics or claim learning gains.

## Evidence retrieval before the interview

For each chosen story, find the original artifact if available: Rakuten prioritization/health definitions; Edugo prototype/PRD/evaluation record; KidsLoop reporting before/after method. The CV supports the statements above but does not supply exact metric formulas, baseline dates, cohort sizes, or a specific interpersonal-conflict anecdote. Say what you remember accurately; do not fill these gaps with this guide's synthetic SQL.

The senior technical CV is useful for H5P/xAPI, permission requirements and prototypes. The leadership CV foregrounds team/budget scope. Choose the evidence to answer the question; do not narrate both CVs.