How to write jiko-PR: turn a strength list into evidence and a usable example

A self-introduction gives the listener basic career context. A strength is a characteristic or capability. Jiko-PR makes a work-related claim, proves it with an episode, and connects it to the target role. "I am responsible" is a label; "I surface delivery risks early and close the follow-up work" is a claim that an example can support.

The Ministry of Health, Labour and Welfare My Job Card guidance recommends connecting career strengths with the employer's needs, and organizing what you have done, what you can do, and what you want to do. That is a useful check on any structure: the paragraph must be about both your evidence and the job.

Underline repeated capabilities in the job description. Separately list episodes where your decision or behavior changed an outcome. Choose the overlap. If the role needs cross-team delivery and your best evidence is a migration where you clarified ownership across three teams, that is stronger than choosing "leadership" because it sounds senior.

Do not change your identity for every application. Keep a small evidence-backed set of strengths and choose the one most relevant to the role. If two strengths rely on the same episode, one clear claim is usually easier to remember and defend.

Lists are prompts, not finished copy. Ask, "What do I repeatedly do that earns this label?" Then use a verb and a work situation. Keep only wording that a former colleague could confirm with an example.

Open with one sentence that names the behavior. Use most of the space for one episode: context, problem, your action, and result. Close with the part of the target role where the same behavior is useful. A number helps when it is accurate and meaningful; a specific changed state is enough when no honest number exists.

Copyable frame: "My strength is [repeatable behavior]. In [situation], [problem] was happening. I [your decisions and actions], which led to [result or changed state]. In this role, I would use the same strength when [specific work]." Replace every bracket with a fact you can explain in a follow-up.

Before: "My strength is communication. I worked with many stakeholders on a migration and completed it successfully. I will use this skill at your company." The reader cannot see what the candidate did, what was difficult, or whether the claim is relevant.

After: "My strength is turning ownership gaps into explicit decisions. During a billing migration involving product, support, and two engineering teams, release criteria had no single owner. I wrote a decision log, assigned each open item to an owner, and ran a 15-minute risk review twice a week. The team released without unresolved ownership questions. I would use the same approach when this role coordinates platform changes across product teams." Keep the example only if those facts are true for you.

In a work history, the paragraph must be scannable and fit the surrounding page. Use the claim, one compact episode, and relevance. In an interview, start with the claim and result, then pause for follow-up or tell a roughly one-minute version. Keep deeper context and a second example ready.

Do not submit one strength and perform a different identity in the interview. The wording can change, but the action pattern and evidence should match. Be ready for "When did this strength fail?" with a real limit and the adjustment you now use.

Do not compare yourself with the best person you know in each category. Look for work colleagues repeatedly bring to you, problems that become calmer when you enter, and a before-and-after change you helped create. Performance reviews, thank-you messages, incident notes, and project retrospectives can recover evidence that memory misses.

Ask two former colleagues, "What kind of problem did you rely on me to handle?" Their answer is not automatically your jiko-PR, but it often points to a behavior worth investigating. Verify it against a specific episode before using it.

Check that the claim appears once, your own action is distinguishable from the team result, technical language is understandable to the intended reader, and the final sentence names real work in the target role. Remove unsupported superlatives and invented precision. If the example is confidential, anonymize the customer and omit protected details.

InterviewTrail AI can keep the project and work story behind each claim, then help draft a role-specific version. Treat the draft as editing material: compare it with the real episode, correct ownership and numbers, and keep the final submitted version with the application.