Find red flags in my resume before recruiters do

Act as a skeptical recruiter reviewing my resume. Your job is to find red
flags — the things that would make you pause or reject the resume.

Look for:
1. Gaps in dates that aren't explained.
2. Vague claims like "improved performance" without numbers.
3. Skills listed but never demonstrated in projects.
4. Projects that sound too similar to tutorial walkthroughs.
5. Inconsistent formatting or tense shifts.
6. Buzzwords that signal padding.
7. Contact info issues (unprofessional email, missing LinkedIn).
8. Anything that sounds inflated or invented.

Output:
RED FLAGS FOUND: [numbered list, each with the exact line from my resume
and why it's a red flag]
NONE FOUND: [list of sections that passed inspection]
FIX PRIORITY: [top 3 to address first]

Here is my resume:
[PASTE RESUME HERE]

Who this is for

This prompt is for freshers who are applying to competitive tech roles — product companies, well-funded startups, or any position where the rejection rate is high — and want to make sure their resume does not contain anything that would make a recruiter pause.

Red flags are not the same as weak content. A weak bullet might get overlooked. A red flag actively hurts you. A recruiter who sees a vague metric like "improved performance by 200%" from a fresher with no internship will immediately doubt the entire resume. Skills listed in the skills section but never demonstrated in any project suggest padding. Projects that read like standard tutorial outputs suggest a lack of genuine experience.

This prompt is particularly useful for Indian freshers applying off-campus to companies like Google, Microsoft, Amazon, Atlassian, or Razorpay, where recruiters are experienced and can spot inflated resumes quickly. At these companies, one red flag can mean instant rejection, even if the rest of the resume is strong.

Think of this prompt as a pre-flight check. You have built your resume, you have tailored it, and now you want to make sure there is nothing in it that will work against you.

How to use it

Step 1: Paste your resume as plain text. Copy everything from your resume and paste it as-is. Do not clean it up first. The point is to see what a recruiter would see, including any inconsistencies in formatting or tone.

Step 2: Copy the prompt and paste it into ChatGPT, Claude, or Gemini. Paste your resume in the placeholder. The AI will scan it like a skeptical recruiter and report back with specific lines and explanations.

Step 3: Address the red flags before the weak content. The output separates red flags from clean sections and gives you a fix priority list. A red flag is worse than a mediocre bullet. Fix the flags first, then use other prompts to improve the overall quality.

Example before and after

Before (the red flag report):

RED FLAGS FOUND:

1. "Improved application performance by 300%" — No context, no methodology, no baseline. A recruiter will assume this number is invented. Red flag: unverifiable metric.
2. Skills section lists "Docker, Kubernetes, AWS" but none of these appear in any project description. Red flag: skills not demonstrated.
3. Project "E-Commerce Website" has identical description to a popular YouTube tutorial project. Red flag: tutorial walkthrough, not original work.
4. Email address is "[email protected]." Red flag: unprofessional contact info.

NONE FOUND: Education section, date formatting, professional summary.

FIX PRIORITY: 1. Change email to a professional format ([email protected]). 2. Remove or add context to the 300% metric. 3. Either modify the e-commerce project to show original work or replace it with a different project.

After fixing: The student creates a professional email, replaces the inflated metric with a realistic one, and adds custom features to their e-commerce project that differentiate it from the tutorial version.

Common mistakes to avoid

Ignoring the "tutorial walkthrough" flag. Many Indian freshers build projects by following YouTube tutorials step by step. There is nothing wrong with learning that way, but putting the exact tutorial project on your resume is a red flag. Add at least two or three custom features that the tutorial did not cover.

Arguing with the AI about metrics. If the AI flags a metric as unverifiable, it is probably right. Instead of defending the number, either add the methodology (how you measured it) or replace it with a number you can actually explain in an interview.

Listing skills you cannot discuss. If you list Kubernetes on your resume but have only watched a few videos about it, remove it. A red flag finder will catch this, but more importantly, an interviewer will catch it too.

Assuming zero red flags means a perfect resume. A clean red flag report means your resume is not actively hurting you. It does not mean the content is strong. Use the harsh critique prompt to assess quality separately.

When not to use this prompt

Skip this if your resume is still in draft form. Red flag detection works best on a resume you consider finished. If you are still adding sections or rewriting bullets, finish the resume first and then run this check.

Also skip this if you are applying to entry-level roles at service companies where screening is less rigorous. The red flag finder is calibrated for competitive roles where scrutiny is high. For bulk hiring at large service companies, content quality matters more than red flag detection.