Pick an experience card, or paste research summaries, project notes, internship records, old ES text, or resume text. The tool separates facts, actions, results, and items to verify.
Using the target industry and role, it maps what you did to competencies companies actually evaluate: issue structuring, continuous improvement, client communication, data analysis, team progress, and more.
From the same material, it generates self-PR, a ~200-character ES version, a one-minute oral version, and a technical explanation, reweighted toward the target role.
It returns competency mapping, roles this can extend toward, gap hints, and facts to verify. It uses only your input and selected cards, and never invents numbers or outcomes.
For a job application, begin with an experience that best supports the role you want. Tailoring keeps the event and its evidence while changing how you present it, helping your application speak to the position and giving you a factual story to use in an interview.
No general cards yet → start with “Turn an experience into PR material”
The strengths to emphasize can change with the role, even when the experience stays the same. Think about the industry, position, or company you are applying to, then compare the posting with your experience. A clear context makes it easier to connect what you did with what the job calls for.
Look for actions and results in your experience that demonstrate the abilities the role values. Industry materials and job postings can suggest useful angles; you choose which facts belong in your application. When material is limited, use the employer's posting and your own experience as the guide.
Strength to show: careful analysis. Evidence: I found a boundary condition others missed in a math contest and won.
Strength to show: patient, precise problem isolation. Same evidence: finding a boundary condition → debugging and test-case design for an SE role. Add the factual scope of your pre-release self-testing if you have it.
Choose the output language before generating, and use a saved job profile to help fill in the application context if you have one. The tailored card is saved to your library while the general source card remains, so you can adapt the same experience for other roles.
Submission documents are written in Japanese or English only. Reading aids, notes, open items and revision suggestions still follow your interface language.
These three are where students who have been through this step keep getting caught. What changes is the wording, never the facts.
put method names and jargon later.
say what moved, from what, and how it was verified.
a lab-wide result is not your achievement.
pair it with a probe-ready example, not a label.
order it as result, method, outcome.
sales, planning, data, and research value different things.