Suryansh Tiwari Profile picture
Mar 30 12 tweets 3 min read Read on X
Stop telling ChatGPT "Help me with my resume"
Stop telling ChatGPT "Improve my CV"
Stop telling ChatGPT "Make it better"

Bad prompt = generic resume.
Specific prompt = interview callbacks.

Use these 10 power prompts instead:
1. ATS Resume Rewrite (Copy-Paste)

Act as a senior recruiter + ATS screening system.

Your task: Rewrite my resume to maximize interview callbacks for this role.

Target Role: [Job Title]
Company Type: [Startup / FAANG / SaaS / Agency / etc.]
Industry: [Industry]
Experience Level: [Junior / Mid / Senior]

Requirements:
- Optimize for ATS keyword matching
- Naturally include keywords from job description
- Quantify achievements with numbers
- Replace responsibilities with impact
- Use strong action verbs
- Remove fluff and generic language
- Keep it concise and recruiter-friendly

Job Description:
[Paste Job Description]

My Current Resume:
[Paste Resume]
2. Bullet Point Transformer (XYZ Formula)

Rewrite my resume bullet points using the XYZ formula:

Accomplished X, as measured by Y, by doing Z

Requirements:
- Add metrics where possible
- Start with strong action verbs
- Make them results-driven
- Keep each under 2 lines
- Remove weak words (helped, worked on, responsible for)

Target Role: [Job Title]

My Bullet Points:
[Paste bullets]
3. Skills Gap Analyzer (Advanced Version)

Compare my resume with this job description.

Create 4 sections:
1. Strong skill matches
2. Partial matches
3. Missing skills
4. How to reframe my experience to cover gaps (without lying)

Then:
- Suggest resume improvements
- Suggest new bullet points
- Suggest skills to add
- Suggest summary rewrite

Job Description:
[Paste JD]

My Resume:
[Paste resume]
4. Resume Summary Generator (High Quality)

Write 4 professional summaries for my resume:

1. Results-focused
2. Leadership-focused
3. Technical-focused
4. Story-based

Requirements:
- 3–4 lines max
- Include measurable achievements
- Include target role keywords
- Make it recruiter-friendly

Target Role: [Role]
Years of Experience: [X]
Industry: [Industry]
Top Achievements:
- [Achievement 1]
- [Achievement 2]
- [Achievement 3]
5. Experience Section Rewriter

Rewrite my experience section to emphasize:

- Impact over responsibilities
- Quantified achievements
- Leadership and ownership
- Business outcomes
- ATS-friendly keywords

Use this format:
• Strong action verb
• What I did
• How I did it
• Measurable result

Target Role: [Role]

Experience:
[Paste experience]
6. Resume Keyword Optimizer

Extract the most important keywords from the job description.

Then:
- Insert them naturally into my resume
- Improve ATS compatibility
- Avoid keyword stuffing
- Keep it human sounding

Also highlight:
- Keywords added
- Keywords missing
- Suggested improvements

Job Description:
[Paste JD]

Resume:
[Paste Resume]
7. Career Switch Resume Prompt

Rewrite my resume to transition from:

Current Role: [Role]
Target Role: [Role]

Focus on:
- Transferable skills
- Relevant achievements
- Reframing experience
- Removing irrelevant info
- Adding role-specific keywords

My Resume:
[Paste resume]

Target Job Description:
[Paste JD]
8. Recruiter Review Prompt

Act as a hiring manager reviewing this resume.

Tell me:
- What stands out
- What is weak
- What is vague
- What lacks metrics
- What would cause rejection

Then rewrite:
- Summary
- Top 5 bullet points
- Skills section

Resume:
[Paste]
9. Interview Callback Optimizer

Rewrite my resume to maximize interview callbacks.

Prioritize:
- Achievements
- Metrics
- Impact
- Clarity
- Brevity

Remove:
- Generic phrases
- Responsibilities
- Fluff
- Weak verbs

Target Role: [Role]

Resume:
[Paste]
10. LinkedIn + Resume Alignment Prompt

Rewrite my resume and LinkedIn profile to align for:

Target Role: [Role]
Industry: [Industry]

Optimize:
- Headline
- Summary
- Experience
- Skills
- Keywords

Make them consistent and recruiter-friendly.

Resume:
[Paste]

LinkedIn Profile:
[Paste]
These prompts work because they:

assign a role

give context

define output

specify constraints

request structure

That's what turns AI into resume co-pilot instead of text generator.

Save this.
Use before every job application.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Suryansh Tiwari

Suryansh Tiwari Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @Suryanshti777

Apr 29
Claude Opus 4.7 isn’t a coding tool.
It’s a thinking partner most people are using completely wrong.

And that mistake is costing them hours every day.

Even Andrej Karpathy thinks differently about this.

Here’s how to actually use it (9 tweets): Image
Image
Most people still treat Claude Opus 4.7 like this:

“write this function”
“fix this bug”
“explain this code”

That’s not leverage.
That’s just faster Googling.

The real shift?

👉 You don’t use AI.
👉 You direct intelligence.
Stop asking for outputs.
Start giving ownership + context.

Bad prompt:
“Build a login system”

Better:
“You are a senior backend engineer. Design a scalable auth system for a SaaS with 10k users/day. Prioritize security + simplicity.”

Now it thinks, not just responds.
Read 9 tweets
Apr 27
Claude Opus 4.7 didn’t just improve coding.

It quietly killed the way most developers think about coding.

But almost no one is using it the way Andrej Karpathy describes.

People are still stuck in:

“write this function”
“fix this bug”
“explain this code”

That’s not wrong.

It’s just… low-leverage thinking.

Karpathy’s real idea?

👉 You don’t write code anymore.
👉 You design systems.
👉 You steer intelligence.

And once you see it…

you can’t go back.

Here are 10 advanced prompts to use Claude Opus 4.7 like an actual engineering partner (not a tool):Image
Image
Prompt 1 — Think Before You Code (Architect Mode)

Act as a staff-level software architect and my Claude Opus 4.7 coding partner.

We are building: [project]

Before writing any code:

First, clarify: Ask focused questions about requirements, users, scale, constraints, and edge cases. Challenge anything vague or assumed.

Then, design: Propose 2–3 possible architectures. Compare them on simplicity, scalability, cost, and speed of execution. Recommend one with clear reasoning.

Then, plan: Break the system into components. Define responsibilities, data flow, and key interfaces.

Only after alignment, proceed to implementation.

Goal: Prioritize thinking and system design over rushing into code.
Prompt 2 — Context-Driven Engineering (No Generic Output)

You are working as my dedicated AI engineer.

Project context:

Goal: [goal]

Users: [target users]

Stack: [tech stack]

Constraints: [time, cost, scale]

Your job: Analyze this deeply. Identify hidden risks, bottlenecks, and incorrect assumptions.

Then: Suggest the most appropriate approach for THIS context (not generic best practices).

Finally: Write clean, production-leaning code and briefly explain key decisions.

Rule: Every output must be tailored. No generic patterns.
Read 12 tweets
Apr 24
🚨 Claude Opus 4.7 just changed how coding works.

But almost no one is using it the way Andrej Karpathy thinks about it.

People are still stuck in:

“write this function”
“fix this bug”
“explain this code”

That’s outdated.

Karpathy’s idea?

You don’t code everything anymore.
You steer intelligence.

Here are 9 high-leverage, value-packed prompts inspired by his “vibe coding” mindset:Image
Image
1. Think Like a Senior Engineer Before Writing Code

Act as a senior software architect and AI coding partner.

We are building: [project]

Before writing ANY code:

Step 1: Clarify
- Ask me detailed questions about requirements, constraints, scale, and edge cases
- Challenge vague or weak assumptions

Step 2: Design
- Propose 2–3 possible architectures
- Compare them based on scalability, complexity, and speed of execution
- Recommend the best approach with reasoning

Step 3: Plan
- Break the system into components/modules
- Define responsibilities and data flow

Only after alignment, proceed to implementation.

Goal: Think first, code later.
2. Build With Full Context (No Generic Output)

You are working as my dedicated AI engineer.

Project context:
- Goal: [goal]
- Users: [target users]
- Tech stack: [stack]
- Constraints: [time, cost, scale]

Your job:
- Analyze this context deeply
- Identify hidden constraints or risks
- Suggest the most appropriate approach (not the most popular one)

Then:
- Generate code that strictly aligns with this context
- Explain key decisions briefly

Avoid generic patterns. Everything must be context-aware.
Read 11 tweets
Apr 22
🚨 Stop using Claude Design like it’s Figma.

“make a UI”
“design a page”
“create a prototype”

That’s not just beginner mode.
That’s outdated thinking.

You’re sitting on a system that can replace entire design workflows.

Figma helps you place pixels.
Claude decides what should exist in the first place.

One follows instructions.
The other builds direction.

And most people still don’t get it.

Here are 7 battle-tested prompts
to turn Claude into your full design stack ↓Image
Image
01 — UX Research

User Persona + Pain Map Generator

Copy:

You are a senior UX researcher specializing in behavioral psychology and Jobs-To-Be-Done.

My product: [DESCRIBE YOUR PRODUCT]
Industry: [YOUR INDUSTRY]
Current users: [WHO IS USING IT NOW]

Generate 3 detailed user personas:

1. Demographics, motivations, goals

2. Top 5 pain points (ranked by severity)

3. Trigger moment (what makes them seek a solution)

4. Current workarounds (apps/tools they use)

5. Internal monologue during frustration

Then create a Pain Priority Matrix:

High pain + High frequency → Design first

Map each pain point to specific screens/flows.

Format: Persona cards → Pain map → Design priorities
02 — Information Architecture

Full IA + Navigation Architect

Copy:

You are an information architect designing products at scale.

My product: [NAME + DESCRIPTION]
Core features: [5–8 FEATURES]
User types: [SINGLE / MULTI-ROLE]

Design the complete Information Architecture:

1. Full sitemap (screens + sub-screens)

2. Navigation system (primary / secondary / tertiary)

3. User journeys per role

4. Friction points (where users get lost)

5. Progressive disclosure strategy

Also define:

Clear naming for navigation

Mobile vs desktop nav patterns

Search + filter structure

Format: Sitemap → Navigation → Journeys
Read 8 tweets
Apr 13
I've written 500 articles, 23 whitepapers, and 3 ebooks using Claude over 2 years.

These 10 prompts are the ONLY ones I actually use anymore because they handle 90% of professional writing better than any human editor I've worked with and cost me $0.02 per 1000 words: 👇 Image
1. The 5-Minute First Draft

Prompt:

"Turn these rough notes into an article:

[paste your brain dump]

Target length: [800/1500/3000] words
Audience: [describe reader]
Goal: [inform/persuade/teach]

Keep my ideas and examples. Fix structure and flow."
2. Headline Machine (Steal This)

Prompt:

"Topic: [your topic]

Write 20 headlines using these formulas:
- How to [benefit] without [pain point]
- [Number] ways [audience] can [outcome]
- The [adjective] guide to [topic]
- Why [common belief] is wrong about [topic]
- [Do something] like [authority figure]
- I [did thing] and here's what happened
- What [success case] knows about [topic] that you don't

Rank top 3 by click-through potential."
Read 11 tweets
Apr 4
During the Cold War, the CIA created a manual for interrogation, persuasion, and psychological leverage.

It wasn’t written for the public.
It was designed to control conversations.
Extract information.
Shift power without force.

Years later, parts of it leaked.

I turned those tactics into 10 AI negotiation prompts.

Describe any situation — salary, client, deal, conflict, interview — and it gives you the psychological edge.

Here are all 10:Image
Prompt 1:

You are a CIA negotiation strategist trained in psychological leverage and conversational control. I will describe a negotiation or difficult conversation. Analyze power dynamics, incentives, fears, leverage points, and hidden motivations for both sides. Identify who holds perceived vs real power and how to rebalance it. Recommend language that builds control without aggression, questions that reveal hidden information, and pacing that increases pressure subtly. Suggest what to say first, what to avoid, and how to guide the conversation toward my desired outcome while maintaining cooperation. My situation: [describe negotiation, person, stakes, constraints]. Provide a calm, psychologically aware strategy.
Prompt 2:

Act as a CIA behavioral analyst preparing me before a high-stakes negotiation. Based on my situation [describe], infer what the other party likely wants, fears, and is trying to protect. Explain how to create psychological comfort while slowly guiding them to reveal information. Recommend conversational framing, tone, and sequencing that increases openness. Suggest questions that sound neutral but uncover leverage. Provide a strategy that makes the other side feel in control while I guide the direction.
Read 11 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(