Pitfall quick-ref
Validity, submission format, screenshots, romanized names — points that can't be circled on one spot, gathered as a read-only reference.
- Certificate ≠ score report
- Easily confused: the certificate only proves the pass with no scores; the score report lists them. Read the posting for which one — the wrong one gets bounced.
- Validity / expired scores
- 「Validity」differs per credential (rough guide): TOEFL — ETS stops sending after ~2 years; TOEIC — no official score expiry, but paper certificate reissue is within ~2 years and employers often want the last ~2 years; IELTS — the TRF has no hard limit, but receiving bodies often ask for ~2 years [please verify]. Confirm whether an expired score is accepted, per each body's rules — don't hunt for the file in your account on the day.
- Screenshot ≠ formal proof
- Web / system screenshots aren't always accepted; save the full official PDF or apply per the body's rules — never pass off a self-made file as formal.
- Romanized name match
- The romanized name must match your passport, resume, and company systems; double-check after a passport change or with long vowels / macrons.
- Intl. students: don't write ID numbers
- Never write your residence-card number or passport number into the checklist / resume / uploaded proof; if you must indicate work eligibility, state the「在留資格」status name and your post-graduation plan in words, not the number. Use the official name + a consistent translation for home-country degrees / credentials.
- Submission & deadline
- Official score-send, PDF upload, or paper original? Get the format wrong and it never arrives. Back-count the deadline from issuing / delivery lead time.
- Credential ≠ whole story
- Credentials are supporting evidence: IT / SE roles also weigh projects, logic tests, coding; language roles weigh real communication. Don't make the credential your only pitch.