Simulate how a recruiter will read my resume in 30 seconds

I'll paste my resume. Simulate a recruiter scanning it for 30 seconds and
tell me what they would walk away thinking.

Answer these specific questions:
1. In one sentence, what does this person do?
2. What role are they targeting? (Is it clear from the resume or do I have
   to guess?)
3. What are their 3 strongest signals?
4. What are their 3 weakest spots?
5. On a scale of 1-10, how likely is this resume to get a callback for a
   fresher tech role at a mid-tier Indian product company? Explain the score.
6. One sentence: what's the first thing I should change to move the score up?

Be honest. Don't soften the answer.

Here is my resume:
[PASTE RESUME HERE]

Who this is for

This prompt is for freshers who want to understand what impression their resume creates in the first 30 seconds. Recruiters at Indian tech companies — from mid-tier product companies like Zoho, Freshworks, and Razorpay to larger firms like Infosys and Wipro — spend an average of 15 to 30 seconds on a first scan. In that time, they form an impression that determines whether they read further or move on.

Most students have no idea what that impression is. They know what their resume says, but they do not know what it communicates. A resume full of projects and skills can still communicate "I do not know what I want" if it lacks a clear target role. A clean resume can communicate "I have nothing to show" if the projects are too generic.

This prompt gives you the recruiter's perspective. It tells you what a 30-second scan reveals: the role impression, the strongest signals, the weakest spots, and a realistic callback score. That feedback is worth more than hours of self-review because it catches gaps in communication that you cannot see from the inside.

It is useful at any stage, but especially right before you start applying. Run it once, fix the biggest issue, and run it again to see if the impression improves.

How to use it

Step 1: Paste your resume as plain text. Copy everything and paste it as-is. Do not add any context or explanation. The recruiter does not get context — they just get the resume.

Step 2: Copy the prompt and paste it into ChatGPT, Claude, or Gemini. Paste your resume in the placeholder. The AI will simulate a 30-second scan and answer six specific questions about the impression it creates.

Step 3: Focus on the gap between intent and impression. If you are targeting a frontend developer role but the AI says "this person seems to be a generalist with no clear focus," that is the gap to fix. The score and the one-line improvement suggestion give you a clear next step.

Example before and after

Before (the recruiter simulation):

1. What does this person do? "A B.Tech student who has done a few projects but it is not clear what kind of role they want."

2. Target role? "I have to guess. The summary says 'seeking opportunities in software development' which could mean anything."

3. Strongest signals: Python skills mentioned in 3 projects. One project has a live deployment link. Education from a recognized university.

4. Weakest spots: No clear target role. Summary is generic. Skills section lists 15 technologies with no prioritization.

5. Callback score: 4/10. "The resume has potential but does not make a case for any specific role. A recruiter scanning this would not know which team to route it to."

6. First fix: "Replace the generic summary with a role-specific one that names the target position and one standout project."

After fixing: The student writes a focused summary targeting "Backend Developer" and trims their skills list to the 8 most relevant technologies. The callback score on a re-run moves to 7/10.

Common mistakes to avoid

Treating the score as absolute. The 1-10 score is a rough estimate based on the AI's reading. It is useful for tracking improvement between iterations, but it is not a guarantee. A score of 7 does not mean you will get 7 out of 10 callbacks.

Focusing on the weakest spots and ignoring the strongest signals. The strongest signals tell you what is working. Double down on those. If your projects are your strength, make them more prominent. If your skills section is well-organized, keep it that way.

Running this prompt only once. The real value comes from running it, making one fix, and running it again. Each iteration should improve the impression. Two or three rounds are usually enough to land on a clear, focused resume.

Adding context that is not on the resume. Do not tell the AI "I am targeting frontend roles" in your input. If the target role is not clear from the resume itself, that is the problem to fix. The recruiter will not have context either.

When not to use this prompt

Skip this if you have not finished writing your resume. The simulation works best on a complete resume. Running it on a half-written draft will just tell you that the resume is incomplete, which you already know.

Also skip this if you are looking for detailed content feedback. This prompt focuses on impression and signal, not on line-by-line critique. For detailed content review, use the harsh critique prompt instead. The two prompts complement each other: one tells you what impression you create, the other tells you what is wrong with the details.