Candidate Positioning

Purpose

A reader should be able to understand the candidate's target role and strongest evidence quickly and without decoding a long technology inventory.

Do not rely on a fixed "6-second" rule.

Positioning Process

1. Choose a Primary Role Family

Examples:

• Software / Backend / Full-stack
• Applied AI / ML
• Data / Analytics
• Cloud / DevOps
• ERP / Enterprise systems

2. Choose Supporting Evidence

Select:

• 1–2 strongest experiences;
• 2–3 relevant projects;
• core skills actually used;
• relevant credentials.

3. Remove Dilution

Reduce:

• unrelated framework lists;
• duplicate project/experience content;
• weak credentials;
• technologies that cannot be defended;
• projects unrelated to the target role.

4. Positioning Statement

Internally define: "Final-year IT student targeting [role family], with strongest evidence in [experience/project areas] using [core technologies]."

This sentence guides ordering; it does not need to appear as a summary section.

Output

• Primary role family
• Secondary role family, if useful
• Strongest proof points
• Content to emphasize
• Content to de-emphasize
• Project ordering
• Skills ordering
• Any identity conflicts in the current resume

Guardrails

• Role identity must come from evidence, not aspirational keywords.
• Certifications alone do not create a new role identity.
• One resume does not need to represent every skill the candidate has ever learned.