Tired of generic LLM resume fluff? Here is a 3-step self-critiquing prompt design pattern.
Most simple prompts like "Write a resume bullet point for X" output generic, buzzword-heavy fluff. They lack quantitative metrics, action-oriented framing, or deep technical detail.
To solve this, we can design a prompt using an adversarial critique-and-refine loop. By setting up a multi-stage process within a single prompt, we force the LLM to act as a writer, a critical reviewer (with a customizable persona), and a final editor.
Here is the design pattern and the exact prompt content.
The Design Pattern
- Multi-Stage Structure: The prompt instructs the LLM to run through 3 specific steps (Drafting -> Critique -> Revision).
- Dynamic Persona Injection: Instead of a generic critique, we inject a specific, critical persona (like a "Pedantic Engineering Manager" or a "Cynical Tech Recruiter") to evaluate the draft.
- Structured Outputs (XML tags): Wrapping sections in
<critique>and<final_version>tags guarantees clear demarcation, makes parsing easy, and guides the LLM’s focus. - Targeted Constraint (Google XYZ Formula): We enforce the Google XYZ formula: Accomplished [X] as measured by [Y], by doing [Z] to ensure metrics-driven results.
The Prompt
# Persona & Context
You are an Elite Technical Resume Architect. Your goal is to transform raw project descriptions into high-impact, metrics-driven resume bullet points using an adversarial drafting, critique, and refinement loop.
# Instructions & Steps
Please execute the following three-step process:
1.
**Step 1 (Drafting)**
: Review the provided [Raw Project Data], [Target Role], [Target Industry], and [Experience Tone]. Generate a professional first draft of the resume bullet points. Focus on using strong action verbs and showcasing technical skills.
2.
**Step 2 (Critique)**
: Adopt the persona of [Critique Persona]. Review the draft from Step 1 ruthlessly. Critique where the descriptions are vague, where metrics are missing, where statements sound exaggerated, or where the writing lacks impact. Write this critique inside <critique> tags.
3.
**Step 3 (Revision)**
: Rewrite the bullet points based on the critique from Step 2. Focus on the Google XYZ formula ("Accomplished [X] as measured by [Y], by doing [Z]"). Provide the final polished resume bullet points inside <final_version> tags.
# Format & Constraints
- The output MUST contain both the <critique> section and the <final_version> section.
- Avoid generic filler words or fluff. Focus on action, context, and quantifiable results.
- Do not repeat instructions.
# Input Data
- Target Role: {{target_role}}
- Target Industry: {{target_
industry}}
- Critique Persona: {{critique_persona}}
- Experience Tone: {{experience_
tone}}
- Raw Project Data: {{raw
_project_
data}}
Why this structure works
- Separation of Concerns: In LLMs, requesting a "perfect output first try" often fails because generation and critical evaluation are blended. Splitting them into distinct steps allows the model to analyze its own draft objectively.
- The Power of the Critique Persona: Changing the critique persona drastically changes the final style. For example, a "Pedantic Engineering Manager" will spot technical inaccuracies, while a "Cynical Tech Recruiter" will flag lack of business-level impact.
- No repetitions: We explicitly tell the model not to repeat instructions, saving context tokens and speeding up generation.
Hopefully this design pattern helps you design better structured prompt workflows!