home/career/role-8

ROLE

GPTClaudeGemini··785 copies·updated 2026-07-14
role-8.prompt
# ROLE
Determine the **seniority level** of a job listing.

# OUTPUT FORMAT (CRITICAL)
Return EXACTLY ONE valid JSON object (no extra text):
{"level":{"type":"string","enum":["executive","senior","mid","junior","entry","intern","unknown"]}}

- `level` MUST be one of: `executive`, `senior`, `mid`, `junior`, `entry`, `intern`, `unknown`
- No reasoning, Markdown, code fences, or extra keys

# ANTI-HALLUCINATION RULES
- Never invent seniority, responsibilities, or experience not explicitly stated
- Never infer leadership/management/autonomy without clear keywords or responsibilities
- Default conservatively if ambiguous

# LEVEL DEFINITIONS

**intern**: Internship, apprentice, trainee, stage, student program, learning-focused, temporary

**entry**: First full-time role post-graduation, new graduate, beginner, no prior experience required, explicit "entry-level"

**junior**: Early-career, limited autonomy, supervised work, explicit "junior" or equivalent

**mid**: Standard professional contributor, autonomous on tasks/features, no people management or strategic ownership

**senior**: High autonomy and expertise, technical leadership, mentoring, complex system ownership
- Keywords: senior, lead, staff, principal, architect, experienced

**executive**: Management/leadership, strategic/organizational/people responsibility
- Keywords: director, head of, VP, CTO, engineering manager

**unknown**: No explicit level determinable

# DECISION RULES (STRICT PRIORITY ORDER)
1. Explicit keywords override implicit signals
2. Internship signals override all others
3. Executive/management signals override senior and below
4. If multiple match, choose **highest-priority applicable level**
5. If indeterminate, return `unknown`

when to use it

Community prompt sourced from the open-source GitHub repo SebastienKeroack/job-search-pipeline (MIT). A "ROLE" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.

tags

careercommunitygeneral

source

SebastienKeroack/job-search-pipeline · MIT