24 ChatGPT prompts for recent grads in India to tailor resumes for remote US roles

If you are a 2024, 2025, or 2026 grad from an Indian college and you want a remote US job in 2026, this is the playbook. I am going to give you 24 ChatGPT prompts for India grad US remote resume tailoring, plus the exact framework, the 2026 numbers you need to know, and a 30-day sprint. No fluff. Just what works.

Here is the honest truth. Most Indian resumes I review for US remote roles die inside the applicant tracking system (ATS) before a human ever sees them. Recruiters in the US use tools like Lever, Greenhouse, and Gem to filter. Those tools look for US-style language, US dollar numbers, and US-style impact. When they don’t find it, you are out. That is why I built this prompt pack. It rewrites the Indian resume dialect into the US dialect the ATS actually wants.

Pull quote: In 2026, the US H-1B cap now uses a wage-weighted lottery (4x for Level IV, 1x for Level I) - which means the easiest path to a US paycheck is no longer a visa. It is a remote contract paid in USD through a platform like Deel, Oyster, Remote.com, or Turing. (Federal Register, Dec 29 2025)

By the end of this article you will have a US-ready resume, a matching LinkedIn headline, a cover letter, and a 30-day plan to land your first 3 US screening calls. Let’s go.

Quick answer / TL;DR

The fastest way to land a US remote job from India in 2026 is:

1. Use Turing, Toptal, Wellfound, or Arc.dev to apply to remote-first US startups. The talent pool is global. Visa is not part of the conversation.
2. Rewrite your resume into US “X-Y-Z by doing Z” bullet points, with USD-relevant numbers and US job titles.
3. Use ChatGPT (or Claude) with the 24 prompts below to do the rewriting in 30 minutes, not 30 hours.
4. Build a one-page portfolio on GitHub or a free Carrd site, and link it everywhere.
5. Cross-border employer pays you through Deel, Remote.com, or Oyster HR as an EOR (Employer of Record) or a contractor. You stay in India. They pay in USD. They handle US tax.

That is the whole game. The rest of this article is the how.

Why most Indian resumes die in the US ATS (with 2026 numbers)

An applicant tracking system (ATS) is software that scans a resume, extracts keywords, and scores it against the job description before a recruiter ever opens it. If your resume lacks the right nouns, verbs, and metrics, the ATS drops you. The harsh reality in 2026:

• The US H-1B cap hit a record number of registrations in FY25. The DHS final rule of December 29, 2025 moved to a wage-weighted selection that gives Level IV (67th percentile wage) 4 entries in the lottery and Level I (17th percentile) 1 entry. India grads on entry-level offers lose this lottery by design.
• The USCIS end-of-year review (Dec 22, 2025) shows the agency issued 196,600 Notices to Appear, cut EAD validity from 5 years to 18 months, and referred 14,400 cases to ICE. The signal is clear: physical US immigration is harder than ever.
• Meanwhile, Turing’s homepage now shows 4M+ vetted talent profiles, 100+ countries, 97% engagement success rate, and an average time from scope to first day of about 4 days.
• Wellfound lists 150K+ tech jobs and 8M+ matches made. Many of those jobs are remote-first.
• Remote.com reports an average onboarding time of 2.3 days vs the industry standard of 30 days. They have 4,000+ G2 reviews.
• Oyster HR charges $699/employee/month as an EOR and onboards compliantly in 180+ countries in as fast as 48 hours. G2 named them a Summer 2026 Leader.

The math is simple. Skip the H-1B queue. Go remote. The companies above are built to pay you in USD while you sit in Bengaluru, Hyderabad, Pune, or anywhere with good wifi.

But the gatekeeper is your resume. Indian resumes have three classic problems that US ATS systems penalize:

1. Photo, date of birth, father’s name, and marital status. US recruiters throw these out, and the ATS often chokes on the extra fields.
2. “Responsibilities” instead of outcomes. “Responsible for backend development” gets parsed as a task list. “Cut API latency from 1,200ms to 180ms for 50K MAU” gets parsed as impact.
3. No US dollar numbers, no US job titles, and Indian college names the ATS can’t parse. If your school is not in the LinkedIn Top Colleges list, the ATS may flag it as unverified education.

The 24 prompts below fix all three.

The 4-stage India-to-US resume framework

The “XYZ” resume formula means every bullet follows the pattern: “Accomplished X, as measured by Y, by doing Z.” It was popularized by Laszlo Bock, Google’s former SVP of People Operations, in his book Work Rules!. I adapted it for fresh grads.

Stage 1 is Format & Translation. US resumes are 1 page, plain text, no photo, no age, no father. Use ChatGPT to translate your Indian CV into the US layout.

Stage 2 is Bullet & Impact. Every bullet becomes a “did X, measured by Y, by doing Z” line. Numbers are mandatory. If you don’t have the exact number, give a range or a lower bound (e.g. “served 2,000+ students”).

Stage 3 is Projects & Open Source. Fresh grads with no US work experience need proof they can build. GitHub repos, Kaggle notebooks, hackathon wins, and shipped side projects all count. ChatGPT helps you describe each one in 2 punchy lines.

Stage 4 is Skills, Cover Letter, and Cross-Border Logistics. This is where you add US-friendly tool names (HubSpot, Mixpanel, AWS, Stripe), write a cover letter that doesn’t sound desperate, and put the right country, timezone, and visa-status lines at the top so recruiters don’t waste time.

Now let’s get to the prompts.

---

SECTION 1: Format & translation prompts (prompts 1–4)

Why this section matters first: The ATS is dumb. It reads the first 200 characters of your resume. If those characters are “Name, Father’s Name, DOB, Photo” you fail the parse step. If they are “Priya Sharma - Backend Engineer - Open to US remote roles - IST (UTC+5:30)” you win.

Prompt 1 - Translate an Indian CV into a US 1-page resume

Purpose: Take the messy Indian-style CV (with photo, personal details, “Objectives” section) and produce a clean US-style 1-pager that any ATS will parse cleanly.

You are a US career coach who has rewritten 500+ Indian resumes for US tech roles.

Rewrite the resume below into a US-standard 1-page resume.

Rules:
- Output must be plain text (no tables, no columns, no images).
- Start with this 3-line header:

  Full Name | US-style Job Title (pick from job description) | Email | Phone (with +91) | LinkedIn URL | GitHub URL | Portfolio URL | Open to US remote roles (IST, UTC+5:30)

- Remove: photo, date of birth, father's name, marital status, gender, religion, caste, languages known, passport number.
- Add a 3-line "Summary" tailored to the job description pasted after the resume.
- Use 4–6 bullet points per role. Every bullet follows: "Did X, as measured by Y, by doing Z." Put numbers in USD or count form, never "good", "many", "various".
- Education: list school, degree, year, GPA only if 7.5+/10 or 3.0+/4.0.
- Skills: comma-separated single list, no tables, no logos.
- No "References available on request."
- If a bullet is missing a number, replace the number with [CONFIRM: user count / revenue / latency] so I can fill it in.

My Indian CV:
[PASTE CV HERE]

Target job description (paste full JD):
[PASTE JD HERE]

Example output (truncated):

Priya Sharma | Backend Engineer (Python, FastAPI) | [email protected] |
+91 98XXX XXXXX | linkedin.com/in/priyasharma | github.com/priyasharma |
priyasharma.dev | Open to US remote roles (IST, UTC+5:30)

Summary
Backend engineer with 2 internships building payment APIs in Python and
FastAPI. Cut p99 latency 87% for a 12K-user fintech app. Strong in SQL,
PostgreSQL, Redis, AWS (EC2, S3, Lambda). IIT Hyderabad, B.Tech CS, 2025.

Experience
Backend Engineering Intern - FinNova (Bengaluru, Remote)        Jun 2024 – Aug 2024
- Cut p99 API latency from 1,200ms to 180ms by rewriting the payment
  endpoint in async FastAPI and adding Redis caching for 12,000 MAU.
- Reduced monthly AWS bill by $1,800 by moving 14 cron jobs from EC2 to
  Lambda and right-sizing RDS instances.
- Wrote 42 unit tests covering 91% of the new payment module.

Education
Indian Institute of Technology Hyderabad - B.Tech, Computer Science  2021 – 2025
GPA: 8.4/10. Coursework: Distributed Systems, DBMS, Computer Networks.

Skills
Python, FastAPI, Django, PostgreSQL, Redis, AWS (EC2, S3, Lambda, RDS),
Docker, Git, Stripe API, pytest, Linux, REST, GraphQL.

Pro tips:

• Paste the full JD. If you only paste the title, ChatGPT will guess and you will get generic bullets.
• Always skim the output. ChatGPT invents numbers if you let it. Replace any number you can’t prove with the [CONFIRM: …] marker.
• Run the same resume through Teal (free) to see a match score against the JD before you apply.

Prompt 2 - Translate an Indian objective/summary into a US summary

Purpose: Indian resumes often open with “Objective: To secure a challenging role in a reputed organization.” US recruiters stop reading right there. This prompt rewrites that line into a 3-line value statement.

Rewrite the following Indian resume opening into a 3-line US-style professional
summary for a [JOB TITLE] role at a US remote company.

Rules:
- First line: who you are in one sentence (role + years of experience or
  internship count + stack).
- Second line: 1–2 measurable wins in numbers (users, dollars, latency, GPA).
- Third line: 1 sentence on what you want and the timezone you work in.
- No "I am passionate about…", no "I am a hardworking team player",
  no buzzwords. Sound like a person, not a LinkedIn influencer.
- Keep total length to 50–70 words.

Input:
[PASTE EXISTING SUMMARY / OBJECTIVE]
Target role: [JOB TITLE]

Pro tips:

• If you don’t have numbers yet, run Prompt 9 first (the impact-extractor), then come back.
• Mirror 2–3 exact phrases from the JD. The ATS rewards keyword overlap.

Prompt 3 - Fix the header (name, contact, links, US signals)

Purpose: Most Indian resumes bury the contact info or leave out a GitHub link. The US header has to be scannable in 5 seconds.

Rewrite my resume header below into a US-style header for a [JOB TITLE]
application at a US remote company. Output exactly 3 lines.

Line 1: Full Name | US-style Job Title
Line 2: Email | Phone (with +91 and country code) | LinkedIn URL | GitHub URL | Portfolio URL
Line 3: One short US-signal phrase - pick one from the list below, or write your own.

US-signal phrases (pick the best match):
- "Open to US remote roles (IST, UTC+5:30, overlap 6pm–11pm ET)"
- "US remote-ready. India-based. B1/B2 visa valid through 2028."
- "US remote engineer. India-based. Available for US-friendly payroll via Deel/Remote.com/Oyster."
- "Green Card holder, India-born, US remote roles only."
- "Indian dev, US-friendly contract. Will invoice in USD."

My current header:
[PASTE CURRENT HEADER LINES]

Target job description:
[PASTE JD]

Pro tips:

• Use the timezone line. It pre-answers the recruiter’s first worry.
• If you are on F-1 OPT, write “OPT eligible, US remote contract only.” Recruiters in the US know what that means.

Prompt 4 - Convert Indian college and company names to US-readable forms

Purpose: US ATS systems often fail to parse “Indian Institute of Technology Hyderabad” or “Tata Consultancy Services” because the token “of” and the long string break them.

Convert the following Indian education and work entries into US-friendly
one-line formats that an ATS will parse correctly.

Rules:
- Keep the full official school name first, then add a short alias in
  parentheses on the same line.
- For companies: use the legal name first, then the common English name
  in parentheses if different.
- Add the city and country. Add the year range.
- Never use Indian government degree codes (like "B.Tech (CSE)") without
  also writing the English form ("Bachelor of Technology in Computer
  Science") in parentheses.

Input:
[PASTE EDUCATION AND WORK HISTORY LINES]

Example output:

- Indian Institute of Technology, Hyderabad (IIT Hyderabad) - Bachelor of
  Technology in Computer Science (B.Tech CS) - Hyderabad, India - 2021–2025
- Tata Consultancy Services (TCS) - Software Engineer Intern - Mumbai, India
  - May 2023 – Jul 2023

Pro tips:

• Add the school rank if it’s in the top 20 in India (e.g. “IIT Hyderabad, ranked 8th by NIRF 2024”). US recruiters like to see a benchmark.
• If your school is not well-known, add one line of context: “Equivalent to top 100 US universities per QS Asia rankings 2025.”

---

SECTION 2: Bullet & impact prompts (prompts 5–10)

Why bullets matter most: US recruiters spend 6 seconds on a resume, and the bullets are the only thing they read. If your bullets are not in the “X by doing Z” format, the recruiter (and the ATS) skip you.

Prompt 5 - Rewrite a responsibility as an XYZ impact bullet

Purpose: Convert a one-line task into a metric-backed achievement. This is the single highest-leverage prompt in the pack.

Rewrite the following Indian resume bullet into a US-style impact bullet.

Rules:
- Use the formula: "Did X, as measured by Y, by doing Z."
- Include a number (users, requests, dollars, percent, time saved). If I
  did not give a number, mark it [CONFIRM: X metric].
- Start with a strong past-tense verb (Built, Cut, Shipped, Reduced,
  Increased, Automated, Migrated, Replaced, Owned).
- One bullet = one outcome. If I gave you three things, split them into
  three bullets.
- Max 22 words. Aim for 18.
- No "Responsible for…", no "Worked on…", no "Helped with…".

Input bullet:
[PASTE BULLET]

Example output:

• Before: “Responsible for backend development of the company’s customer dashboard.”
• After: “Built a customer dashboard backend in FastAPI serving 8,500 daily active users, cutting average page load from 4.1s to 0.9s.”

Pro tips:

• If you can’t remember the number, estimate with a range and add a confidence tag: “served ~2,000 students (best estimate)”. US recruiters respect honesty.
• Use $1,000+ thresholds. Recruiters think in USD. “Saved ₹5,00,000” gets parsed as a small number. “Saved $6,000 in cloud spend” lands harder.

Prompt 6 - Rewrite 10 bullets at once for one role

Purpose: Batch-mode for one internship. Faster than running Prompt 5 ten times.

I will paste 10 bullet points from a single internship at [COMPANY NAME],
[JOB TITLE], [DATES].

For each bullet:
1. Rewrite using the XYZ formula (Did X, as measured by Y, by doing Z).
2. If a bullet is too vague, write a [NEED MORE INFO] note asking for one
   number, and then write 2 alternative versions with placeholder numbers.
3. Sort the rewritten bullets by impact (largest number first).
4. Cap each bullet at 22 words.

Output format:

Original 1: …
Rewritten 1: …
Original 2: …
Rewritten 2: …
…

Bullets:
[PASTE 10 BULLETS]

Pro tips:

• The 2-alternatives trick is gold. ChatGPT will show you 2 ways to write the same win with different framings (e.g. “saved time” vs “saved money”). Pick the one that matches the JD.
• The “sort by impact” instruction forces the highest-number bullet to the top. US recruiters read the first 3 bullets only.

Prompt 7 - Extract impact from a vague role description

Purpose: You did the work, but you wrote “worked on various features” and now you need real metrics. This prompt reverse-engineers metrics from a vague role.

I did this work: [DESCRIBE THE WORK, 2–3 SENTENCES, EVEN IF VAGUE].

Generate a list of 10 plausible US-style resume bullets covering what I
probably did. For each, put a placeholder number in square brackets
(e.g. [CONFIRM: MAU count]) so I can replace it with my real number.

Rules:
- Cover: scale (users/requests), speed (latency/throughput), cost (USD
  saved or earned), quality (bugs, errors, uptime), and team (engineers
  led, juniors mentored).
- Use US tech terms (p99, MTTR, SLA, throughput, MRR, ARR, churn).
- Max 22 words per bullet.

Role context:
- Title: [JOB TITLE]
- Company type: [B2B SaaS / D2C e-commerce / Fintech / etc.]
- Stack: [Python/FastAPI, AWS, PostgreSQL, etc.]

Pro tips:

• Do not paste the generated bullets into your resume as-is. The numbers are placeholders. Replace each one with your real number, even if it is “5” or “10”. A real small number beats a fake big number every time.
• Use this prompt to remind yourself of wins you forgot. Then go back to Prompt 6 with the real bullets.

Prompt 8 - Quantify soft skills (leadership, communication, mentorship)

Purpose: Indian resumes often hide leadership behind words like “team lead” or “coordinator.” US resumes want outcomes: “mentored 4 juniors, 3 of whom got promoted.”

I held one of these roles: [team lead / class rep / club president /
event coordinator / TA / mentor].

Rewrite the role as 4 US-style impact bullets.

Rules:
- One bullet on number of people you led or mentored.
- One bullet on a measurable result (events run, students taught, hours
  saved, dollars raised).
- One bullet on a process you created or improved (onboarding doc, weekly
  standup, syllabus).
- One bullet on a stakeholder outcome (NPS, retention, satisfaction).
- All bullets in the XYZ format, max 22 words each.

Context:
- Role: [PASTE ROLE]
- Team size: [N or unknown]
- Outcome: [PASTE WHAT HAPPENED]

Pro tips:

• For “NIRF ranking” or “GPA in top 10% of class” - that is a metric. Use it.
• “Organized 3 hackathons with 200+ participants” beats “Organized hackathons.”

Prompt 9 - Convert marks/percentile/CGPA into US-friendly signals

Purpose: Indian marks use CGPA, percentage, and percentile. US recruiters don’t know the scale. Convert it.

Convert the following Indian academic and test scores into US-friendly
resume lines.

Input:
- B.Tech CGPA: 8.4/10
- Class 12 percentage: 92%
- JEE Main percentile: 99.2
- GRE: 320 (170Q, 150V)
- TOEFL: 110/120

Output rules:
- For each, write 1 line that a US recruiter understands.
- If the score is in the top 10% of test-takers, say so.
- For university GPA, convert to US 4.0 scale in parentheses.
- For GRE/TOEFL, add a short context line ("top decile" or "above 90th
  percentile") so a recruiter knows it's strong.

Also tell me the US 4.0 conversion for an Indian 8.4/10 CGPA. (Standard
WES conversion: divide by 10, then multiply by 4. So 8.4/10 ≈ 3.36/4.0.)

Example output:

• “Graduated with a CGPA of 8.4/10 (≈ 3.4/4.0 US scale), placing in the top 8% of the B.Tech CS class of 480 students.”
• “GRE 320 (170 Quant, 150 Verbal), 90th percentile Quant, 60th percentile Verbal.”

Pro tips:

• If you are below 7.5/10 or 3.0/4.0, drop the GPA entirely. US recruiters only use it as a positive filter.
• “Top 8% of class” is a stronger line than “CGPA 8.4/10” because the comparator is included.

Prompt 10 - Add a “Selected Results” or “Highlights” strip

Purpose: US resumes often open with a 4-tile highlights strip right under the summary. It works well for fresh grads with no US work experience.

I am a [JOB TITLE] targeting [TARGET JD] at a US remote company. Below
are 6 of my strongest wins. Rewrite them as a one-line "Highlights"
strip, 4 tiles max, each ≤ 12 words, each starting with a verb.

Wins:
1. [WIN 1]
2. [WIN 2]
3. [WIN 3]
4. [WIN 4]
5. [WIN 5]
6. [WIN 6]

Output as 4 tiles. Pick the 4 that match the JD most.

Example output:

Highlights
- 50K-user SaaS app | 87% latency cut | $24K cloud savings
- 4 hackathon wins | 1 open-source library (1.2K GitHub stars)
- Mentor of 6 juniors | 3 promoted to SDE-1 in 2024
- Built payment pipeline handling 2,000 tx/day on AWS Lambda

Pro tips:

• This is the only place where a horizontal “tile” format is OK. ATS systems still parse it as 4 separate lines.
• Keep each tile to 4–6 words separated by pipes. The visual scannability helps the human reader.

---

SECTION 3: Projects & open-source prompts (prompts 11–14)

Why projects matter for fresh grads: US recruiters hiring a 22-year-old from India know you have no US work experience. What they want is proof you can ship. GitHub repos, Kaggle notebooks, hackathon wins, deployed side projects, and one well-written case study beat any internship.

Prompt 11 - Describe a GitHub project for a resume

Purpose: GitHub READMEs are written for developers, not recruiters. This prompt gives you a 2-line recruiter-friendly version.

Rewrite the following GitHub project description for my US-style resume.

Rules:
- Line 1: What the project does, who it serves, in plain English (no jargon).
- Line 2: Tech stack, scale, and one measurable outcome (stars, users, latency).
- Total max 22 words.
- Skip setup steps, skip installation, skip "Features" lists.
- If there are GitHub stars or downloads, include them ("1,200+ stars").

Project name: [NAME]
Repo URL: [URL]
What it does: [1 SENTENCE]
Stack: [LIST]
Stars / users / scale: [N]

Example output:

• Before: “A full-stack e-commerce platform built with Next.js, Prisma, and Stripe. Features include auth, cart, checkout, and an admin panel.”
• After: “Open-source e-commerce template with Stripe checkout, used by 1,200+ GitHub stars. Built in Next.js, Prisma, Postgres.”

Pro tips:

• If your repo has 0 stars, do not include the line. Write the line as: “Side project; 200+ users in personal network.”
• Always link the GitHub URL in the resume. Recruiters check.

Prompt 12 - Turn a hackathon win into a resume line

Purpose: Indian hackathons produce 30-second pitches. US resume lines need a one-line outcome.

I won [HACKATHON NAME] ([SCALE: college / national / international]) in
[DATE] out of [N TEAMS].

My project: [1 SENTENCE]

Tech: [LIST]

Rewrite this as 2 US-style resume bullets.

Rules:
- Bullet 1: What the project did, who it served, what the measurable win
  was (judges' score, prize, ranking, or users post-hack).
- Bullet 2: Tech stack and any post-hack life (open-sourced, acquired, used
  by a real org).
- Max 22 words each.
- If the hack had 500+ teams, add the scale so the US reader knows.

Pro tips:

• “Won Smart India Hackathon 2024 (out of 10,000+ teams, ₹1,00,000 prize)” lands harder than “Won a hackathon.”
• If your hack project was open-sourced and got 100+ stars, that line beats the win itself.

Prompt 13 - Build a one-page project case study

Purpose: US startup recruiters love a 1-page PDF case study. It’s the closest thing to “work samples” for a fresh grad.

I will paste a project description below. Build a one-page case study I
can host at [URL].

Structure:
1. Title + 1-sentence tagline.
2. The problem (2 sentences, written for a US business reader).
3. The solution (3 bullets, each ≤ 15 words).
4. Outcome (2 bullets with numbers, even if small).
5. Tech stack as a single line.
6. 1-line "what I learned" honest reflection.

Output in Markdown. Max 350 words total.

Project:
[PASTE DESCRIPTION]

Pro tips:

• Host the case study on a free Carrd site or a case-study.md in your GitHub repo.
• Link the case study from your resume AND your LinkedIn. This is the highest-leverage thing a fresh grad can do.

Prompt 14 - Build a “Projects” section ordering

Purpose: You have 6 projects. Which 3 go on the 1-page resume and in what order?

I have 6 projects. Target JD is [PASTE JD]. I can put 3 on my 1-page
resume.

For each project below:
- Name, 1-line description, stack, scale (stars/users/hack wins).
- Score it 1–10 on (a) JD keyword match, (b) scale/impact, (c) recency.
- Recommend: KEEP on resume, MOVE to portfolio only, or CUT entirely.
- Suggest the order of the kept projects (best first).

Projects:
1. [NAME] - [DESC] - [STACK] - [SCALE]
2. …
3. …
4. …
5. …
6. …

Pro tips:

• The 3 projects on the resume should be the 3 with the highest JD-keyword match, not the 3 you’re proudest of. Pride is for the portfolio site. The resume is a sales sheet.
• Drop school projects older than 24 months. US recruiters want recent shipped work.

---

SECTION 4: Skills & US-market prompts (prompts 15–18)

Why this section: US job descriptions have tool names you may not know. “HubSpot” beats “CRM.” “Mixpanel” beats “analytics.” “Stripe” beats “payments.” The right tool name in your Skills line is a 1-line ATS win.

Prompt 15 - Map Indian-stack skills to US-stack equivalents

Purpose: Your Indian tool stack may use open-source tools that US startups haven’t heard of. This prompt aligns your skills to the JD’s tool names.

Below is my current Skills section. Below that is the JD. Rewrite my
skills section so the words line up with the JD as much as possible.

Rules:
- Keep the same skills, but rename them to the US market term if one
  exists. Example: Razorpay → Stripe, Freshdesk → Zendesk, Google
  Analytics → Mixpanel or Amplitude, AWS Mumbai → AWS (ap-south-1),
  Razorpay → Stripe, Node.js → Node.js (Express/Fastify).
- Group into 4 buckets: Languages, Frameworks, Cloud/Data, Tools.
- One line per bucket, comma-separated.
- No logos, no tables.
- Add the US dollar context in parentheses for cost-related tools
  (e.g. "AWS (~$1,200/mo bill, 14 services)").

My skills:
[PASTE]

JD:
[PASTE]

Pro tips:

• Run the JD through Simplify or Teal to extract the keyword list first, then map your skills against it.
• Do not invent tools you have not used. The interviewer will ask.

Prompt 16 - Build a US-market skills proficiency grid

Purpose: US resumes sometimes add a “Proficiency” hint. “Python (5 years)” beats “Python.” This prompt helps you write that without overclaiming.

For each skill below, write a one-line proficiency tag in the format
"Skill (N years, last used YYYY, used in production at scale of M)".

Scale guide for "at scale of M":
- Personal projects: M = "side project"
- Class projects: M = "class project"
- Internship / production: M = "[N] MAU" or "[N] requests/day" or "[N] TB"

Rules:
- Never round up. If you used Python for 1.5 years, say 1.5.
- If you used it only in class, say "class project".
- If a skill is from a tutorial, list it under "Familiar" instead.

Skills:
[PASTE LIST]

Example output:

• “Python (4 years, last used 2026, 12,000 MAU production)”
• “React (3 years, last used 2026, 4 production apps)”
• “Rust (6 months, last used 2025, side project only) - Familiar”

Pro tips:

• Recruiters in 2026 have started asking ChatGPT-style “tell me about a time you used X at scale.” This grid makes it easier for you to answer.

Prompt 17 - Add a “Tools I Have Shipped” line under Skills

Purpose: Fresh grads often have a 20-line skills block. US recruiters want 6–8 lines. The trick is to be specific.

Pick the 8 most JD-relevant skills from my list below. For each, write
a 1-clause parenthetical that shows I have used it in production, not
just in a tutorial.

Format: "Skill (used in production for [USE CASE])"

My list:
[PASTE FULL SKILLS LIST]

JD:
[PASTE]

Example output:

• “FastAPI (payment API serving 12,000 MAU)”
• “PostgreSQL (8M-row analytics tables with sub-200ms p99 reads)”
• “Stripe (recurring billing for 2,000 paying customers)”

Pro tips:

• If you only used a tool in a tutorial, replace the parenthetical with “tutorial” or remove the line. Honesty wins.

Prompt 18 - Write a “Why US remote” 2-sentence blurb for the resume footer

Purpose: Some US recruiters are skeptical of India-based candidates because of timezone. A 2-sentence blurb in the resume footer pre-empts the worry.

Write a 2-sentence "Why US remote" blurb for the footer of my resume.

Sentence 1: I am in IST (UTC+5:30) and I work [N] hours of overlap with
US Eastern / Pacific time. (Pick the overlap that matches the JD's
listed timezone.)

Sentence 2: I invoice in USD through [Deel / Remote.com / Oyster / my own
LLC] and handle my own Indian taxes, so there is no US entity or
sponsorship needed.

Rules:
- Max 30 words total.
- No "I am a hardworking team player" or "I am passionate about…"
- No mention of H-1B or visa status unless I tell you my status.

My status: [e.g. "Indian citizen, no US visa, will work as contractor"]

Footer draft:
[PASTE EXISTING OR "WRITE FROM SCRATCH"]

Pro tips:

• The “no US entity needed” line is a 2026 magic phrase. US hiring managers love it.
• If you already have an LLC or GST-registered business, mention it. It signals seriousness.

---

SECTION 5: Cover letter & LinkedIn prompts (prompts 19–22)

Why this section: Most fresh-grad applications get rejected because the cover letter is generic and the LinkedIn is empty. The fix takes 20 minutes with the right prompts.

Prompt 19 - Write a 200-word US-style cover letter

Purpose: US cover letters for fresh grads are 150–250 words, 3 short paragraphs, no flattery. The first line names the role and where you saw it.

Write a US-style cover letter for a [JOB TITLE] role at [COMPANY NAME].

Rules:
- Paragraph 1 (2–3 sentences): Name the role, where I saw it, and the
  one thing about the company that genuinely excites me (not a generic
  line about "your innovative culture").
- Paragraph 2 (3–4 sentences): 2 measurable wins from my resume, written
  in XYZ format. Tie each win to a specific need in the JD.
- Paragraph 3 (2 sentences): My availability, timezone, payment
  arrangement, and one line inviting the recruiter to a 20-min intro call.
- Total: 180–220 words. No "I am writing to express my interest." No
  "I am a perfect fit." No flattery about how great the company is.
- Sign off: "Best," or "Thanks," - not "Sincerely."
- Subject line of the email: [Role] - [My name] - [1-line proof]

My resume highlights:
[PASTE 4 BULLETS]

JD:
[PASTE]

Pro tips:

• The subject line is the most-skipped part. It decides whether the email is opened.
• Send the cover letter as plain text in the email body. Do not attach a PDF. Recruiters open text faster.

Prompt 20 - Write a 5-sentence LinkedIn “About” section

Purpose: A blank or generic LinkedIn “About” is the #1 reason recruiters skip your profile after they see your resume. This prompt writes a 5-sentence version that ranks in search.

Write a 5-sentence LinkedIn "About" section for a [JOB TITLE] open to
US remote roles.

Sentence 1: Who I am (role, B.Tech from [SCHOOL], 2 internships).
Sentence 2: My strongest measurable win (number + outcome).
Sentence 3: My tech stack (5–8 tools, comma-separated).
Sentence 4: My work setup (IST, overlap with US time, payment via
Deel/Remote.com).
Sentence 5: What I'm looking for right now (1 line, specific).

Rules:
- First-person voice.
- No "passionate", no "rockstar", no "ninja", no "guru".
- Drop a 5–8 keyword list at the end as hashtags (only if the platform
  shows them, e.g. #OpenToWork #USRemote).
- Total ≤ 80 words for the prose, then a separate keyword list.

Input:
[PASTE 4 BULLETS + JD]

Pro tips:

• Turn on LinkedIn “Open to Work” only for recruiters, not public. The public green banner hurts callbacks in some studies.
• Re-write the “About” every quarter. LinkedIn ranks active profiles higher.

Prompt 21 - Rewrite the LinkedIn headline for ATS and recruiter search

Purpose: Your LinkedIn headline shows up in Google, in recruiter search, and in every comment you leave. Treat it like a one-line job ad for you.

Rewrite my LinkedIn headline for a [JOB TITLE] targeting US remote roles.

Rules:
- Format: "[Job Title] | [1 measurable proof] | [Stack] | [US signal]"
- Max 220 characters.
- Include 1 number or dollar amount.
- Include the country and timezone if they help (IST, UTC+5:30).
- Do not include "Open to work" - that goes in the "About" or the
  private setting.

My current headline:
[PASTE]

Target JD:
[PASTE]

Example output:

• Before: “Student at IIT Hyderabad | Aspiring SDE”
• After: “Backend Engineer (Python, FastAPI) | 50K-user app, 87% latency cut | Open to US remote (IST, UTC+5:30)”

Pro tips:

• The headline is the single most-edited line on LinkedIn. Tweak it for each application cycle.
• Do not put emojis. They break some recruiter search queries.

Prompt 22 - Write 3 LinkedIn connection request notes for US recruiters

Purpose: Cold-connection works on LinkedIn only if the note is short and specific. This prompt gives you 3 versions.

Write 3 LinkedIn connection request notes (under 300 characters each)
for the following US recruiters / hiring managers.

Rules:
- Note 1: Pure value - share a relevant article, no ask.
- Note 2: Specific role - mention 1 job posting and 1 reason I am a fit.
- Note 3: Alumni / common-interest - leverage a shared school, city, or
  community.
- No "I admire your work." No "I would love to pick your brain." No
  flattery.
- End with a soft ask: "happy to share my resume" or "would love a 15-min
  intro."

Recruiter name and role: [NAME], [TITLE] at [COMPANY]
My role target: [JOB TITLE]
My 1 strongest proof: [BULLET]

Pro tips:

• Send at most 20 connection requests per day. LinkedIn throttles you.
• Wait 24 hours after they accept, then send a longer message. Do not pitch in the request.

---

SECTION 6: Cross-border logistics prompts (prompts 23–24)

Why this section matters: Getting paid across borders is the operational problem that kills more India-to-US remote placements than visa issues. The 2026 stack is Deel, Remote.com, Oyster HR, plus a US-friendly bank account like Wise or Mercury. These prompts help you decide and prepare.

Prompt 23 - Compare Deel vs. Remote.com vs. Oyster HR vs. Wise for a US client

Purpose: You are about to get your first US contract. You need to pick the right payment platform. Each has different fees, currency, and tax treatment. This prompt lays them out for your specific situation.

I am an Indian freelancer / contractor about to be paid by a US company
for a [JOB TITLE] role at $[ANNUAL SALARY] USD/year, paid monthly in
USD.

Compare the 4 main options a US startup will offer me, in the order a
US recruiter is most likely to suggest them. Use verified 2026 data only.

Cover for each option:
- Official pricing (EOR per-employee-per-month, contractor per-month, or
  % fee).
- Country coverage (does it legally employ in India as a contractor?).
- Payment currency and method (USD wire, ACH, PayPal, etc.).
- Tax treatment in India (will I get a Form 16, will I owe GST, will
  there be TDS?).
- Onboarding time from contract signature to first paycheck.
- Hidden fees (FX margin, withdrawal fee, contract amendment fee).
- One specific use case where this option wins over the others.

Constraints:
- I will work as a contractor (not an FTE) for the first 12 months.
- I will invoice monthly in USD.
- I want the lowest total cost of receiving money, including FX.
- I do not have an LLC yet but can register one in India (LLP / Pvt Ltd
  / OPC) within 2–4 weeks.
- All data points must be sourced to 2026 official pages (link them).

Pro tips from the data I verified in 2026:

• Oyster HR is priced at $699/employee/month for EOR and $29/contractor/month for global contractors, in 180+ countries, with 48-hour onboarding in many cases.
• Remote.com advertises an average onboarding of 2.3 days vs the 30-day industry standard, SOC 2 Type 2 and ISO 27001 certified.
• Turing for full-time US remote engineering roles, with 4M+ profiles and 97% engagement success rate. Average scope-to-start is 4 days.
• Deel is the largest EOR by volume. Pricing is quote-based; expect a contractor-only plan around $49/month per contractor.

In plain terms:

• If you are doing a short (under 6 month) US contract, take the client’s default. It’s usually Deel or Remote.com. Don’t argue about platform choice.
• If you are doing a 12+ month engagement with the same US company, push for Oyster HR EOR. You get benefits and they handle Indian tax withholding. It saves you 10+ hours a month of compliance work.
• Always open a Wise multi-currency account in parallel. It gives you a USD receiving account for free, and FX is mid-market + 0.5%.

Prompt 24 - Write the “country, timezone, and payment” line for the top of your resume

Purpose: Recruiters in the US need to know 4 things in the first 3 lines: who you are, where you are, what time you work, and who pays you. This prompt writes that one line.

Write the exact "country, timezone, and payment" line for the top of my
resume. Output exactly 1 line, max 200 characters.

Variables to use (replace placeholders):
- Country / city: [CITY, INDIA]
- Timezone: [IST, UTC+5:30, X hours overlap with US ET/PT]
- Payment: [contractor via Deel / EOR via Oyster / FTE via Remote.com / my own LLC]
- US visa status: [none / F-1 OPT / B1/B2 / Green Card]
- Work authorization for US: [contractor only / needs sponsorship / no sponsorship needed]

Rules:
- 1 line.
- Use pipe " | " to separate fields.
- Put the most important field first for the recruiter (country +
  timezone + payment).
- No buzzwords. No emojis. No "Open to work."
- US recruiters scan this in 2 seconds. Make it answer 4 questions in
  1 line.

Example output (no US visa, contractor):

Bengaluru, India | IST (UTC+5:30), 6pm–11pm ET overlap | Contractor via Deel or Oyster | No US sponsorship needed

Example output (F-1 OPT, US-based):

Austin, TX (US) | CST (UTC−6) | F-1 OPT, valid through Aug 2027 | EOR via Remote.com

Pro tips:

• If you have an LLC registered in India, write “Bengaluru, India | IST, UTC+5:30 | Invoicing via [LLC NAME], GSTIN [NUMBER]”. It signals professionalism and saves the recruiter 2 back-and-forth emails.
• If you are on F-1 OPT in the US, this line is your lifeline. US recruiters will skip you without it.

---

Comparison table: prompt categories vs. resume section vs. output

This table is the at-a-glance map of the full prompt pack. Use it to jump to the right prompt when you are short on time.

#	Category	Prompt purpose	Resume section it touches	Output type	Time to run
1	Format	Translate Indian CV → US 1-pager	Whole resume	Plain text	5 min
2	Format	Rewrite Indian objective → US summary	Summary	50–70 words	2 min
3	Format	Fix the header (name, contact, US signals)	Header	3 lines	1 min
4	Format	Convert Indian school/company names	Education + Experience	One-liners	3 min
5	Bullets	Responsibility → XYZ impact bullet	Experience	1 bullet	1 min
6	Bullets	Batch-rewrite 10 bullets for one role	Experience	10 bullets	5 min
7	Bullets	Extract metrics from a vague role	Experience	10 drafts	4 min
8	Bullets	Quantify soft skills (leadership, mentorship)	Experience	4 bullets	3 min
9	Bullets	Convert CGPA / GRE / TOEFL → US signals	Education	1–4 lines	2 min
10	Bullets	Build a “Highlights” strip	Summary area	4 tiles	2 min
11	Projects	Describe a GitHub repo for a recruiter	Projects	2 lines	2 min
12	Projects	Turn a hackathon win into a resume line	Projects	2 bullets	2 min
13	Projects	Build a 1-page project case study	Portfolio	Markdown, 350 words	8 min
14	Projects	Order 6 projects for the resume	Projects	Ranked list	2 min
15	Skills	Map Indian stack → US stack	Skills	4 lines	3 min
16	Skills	Add proficiency tags (years, scale)	Skills	1 line per skill	3 min
17	Skills	Add “used in production” hints	Skills	8 tiles	3 min
18	Skills	Write a “Why US remote” footer blurb	Footer	2 sentences	1 min
19	Cover letter	200-word US-style cover letter	Cover letter	180–220 words	5 min
20	LinkedIn	5-sentence LinkedIn “About”	LinkedIn About	80 words	3 min
21	LinkedIn	Rewrite the LinkedIn headline	LinkedIn headline	1 line, 220 char	2 min
22	LinkedIn	3 connection request notes	LinkedIn DMs	3 short notes	4 min
23	Cross-border	Compare Deel vs. Remote.com vs. Oyster vs. Wise	Decision	Comparison table	6 min
24	Cross-border	Write the “country, timezone, payment” line	Header	1 line	1 min

Total time to use the full pack: roughly 70 minutes. That is the entire investment to get a US-ready resume, cover letter, LinkedIn, and payment plan.

---

People Also Ask: 8 questions Indian grads ask about US remote jobs in 2026

Q1. Can I really get a US remote job from India in 2026? Yes. Remote-first US companies like Turing, Toptal, Wellfound, and Arc.dev hire globally. Turing reports 4M+ profiles and 100+ countries. Wellfound shows 150K+ tech jobs. The jobs are real, the pay is in USD, and the work is done in your timezone with US overlap.

Q2. Do I need an H-1B for a remote US job? No. H-1B is for US-based employment by a US entity. Remote contractor roles paid through an EOR like Deel, Remote.com, or Oyster HR do not need H-1B. You stay in India, you invoice in USD, you pay Indian income tax. The client has zero US immigration paperwork.

Q3. What is the new H-1B wage-weighted lottery and how does it affect fresh grads? The DHS final rule of December 29, 2025 changed H-1B selection from a pure random lottery to a wage-weighted one. Level IV (67th percentile wage) gets 4 entries, Level III gets 3, Level II gets 2, Level I gets 1. Fresh-grad offers typically fall in Level I, so they get 1 entry. Older experienced candidates get more entries. Net effect: fresh grads lose the H-1B lottery more often than before. Skip it. Go remote. (Federal Register)

Q4. What is the easiest way to get paid in USD from a US client? Open a Wise multi-currency account. You get a USD receiving account (free) and an INR payout. FX is mid-market + 0.5%. The US client sends USD to your Wise USD account. Wise converts to INR and deposits in your Indian bank. Total cost: 0.5–1% of the invoice. For larger engagements, push the US client to use Deel or Oyster HR EOR. The fee is in the $29–$699/month range but they handle tax, contracts, and benefits.

Q5. Do I need a US LLC or a US bank account? No. Most India-based contractors invoice from an Indian LLP, Pvt Ltd, or OPC. The US client pays your Indian bank (or your Wise USD account). You do not need a US LLC. A US LLC only becomes useful if you want a US business address, a US bank account, or US tax-resident status - none of which a remote contractor needs.

Q6. What ATS systems do US startups use in 2026? The big three are Greenhouse, Lever, and Ashby. For higher volume, Gem, Workable, and iCIMS are common. All of them parse plain-text resumes. All of them fail on tables, columns, and images. That is why Prompt 1 forces plain text output.

Q7. What is the typical salary for an India grad in a US remote role in 2026? For a backend / full-stack / data engineer with 0–2 years of experience: $30,000 – $80,000 USD per year is the realistic 2026 range for a contractor. The top of that range is at companies like Toptal (top 3% network) and Turing (top 1% of developers). For a full-time FTE role paid by an EOR: $50,000 – $120,000 USD is common. The number depends on stack, English fluency, and US-overlap hours.

Q8. What about GST in India? Do I need to register? If you invoice under ₹20 lakh per year (₹10 lakh in special category states), you generally do not need GST registration, but the US client may still ask for a GSTIN. Register for GST voluntarily if you are going over those thresholds. Most platforms (Deel, Remote.com, Oyster) will withhold a small US-side “platform fee” but they do not pay Indian GST for you. You file it yourself quarterly.

---

A 30-day “first 3 US calls” sprint

Use this 30-day plan if you have no US calls yet. It assumes 2 hours per day, 5 days a week, for 4 weeks.

Week 1 - Resume + portfolio

• Day 1: Run Prompt 1 to produce the US 1-page resume. Manually fix every placeholder number.
• Day 2: Run Prompts 5, 6, 7, 8 to rewrite all bullets. Run Prompt 10 to add the Highlights strip.
• Day 3: Run Prompts 11, 12, 14 to finalize the Projects section. Build the case study with Prompt 13, host on Carrd or GitHub.
• Day 4: Run Prompts 15, 16, 17 for the Skills section. Run Prompt 9 for CGPA conversion.
• Day 5: Run Prompts 3, 18, 24 for header, footer, and country/timezone line. Export the resume as both PDF and plain .txt.

Week 2 - LinkedIn + cover letter

• Day 6: Run Prompts 20 and 21 for LinkedIn About and Headline.
• Day 7: Connect with 20 Indian alumni who now work at US remote companies. Use Prompt 22 templates.
• Day 8: Run Prompt 19 for 3 cover letters, one per target role.
• Day 9: Post 1 LinkedIn long-form post about a project. Use Prompt 13’s case study as the body.
• Day 10: Apply to 5 jobs on Turing, 5 on Wellfound, 5 on Toptal, 5 on Arc.dev.

Week 3 - Apply + outreach

• Day 11–15: 10 applications per day, using the rewritten resume and the right cover letter. Track every application in a Notion or Google Sheet.
• Day 12: DM 10 recruiters of US startups you applied to, using Prompt 22.
• Day 14: Apply to 5 cold-outreach roles on AngelList (now Wellfound) for seed-stage startups.
• Day 15: Apply to 3 contracting platforms: Toptal (top 3% screening), Turing (1% vetting), Arc.dev (15% cut).

Week 4 - Conversion + follow-up

• Day 16–20: Follow up on every Week 2 and 3 application with a 1-line “any update?” message.
• Day 18: Open a Wise account. Get the USD receiving details ready.
• Day 19: Run Prompt 23 to pick your payment platform (Deel, Remote.com, Oyster, or Wise).
• Day 20: Book 3 mock US-style interviews with Indian seniors on Pramp or InterviewBit.
• Day 21: At the end of 30 days, you should have 3–5 first-round US calls booked. If not, the bottleneck is applications, not the resume. Triple the application count in month 2.

The math: 30 days × 10 applications per day = 300 applications. At a 1–2% callback rate, you get 3–6 first-round calls. That is the realistic baseline. It is not glamorous. It is just what works.

---

Common mistakes to avoid

1. Sending the same resume to every US job. US ATS penalizes generic bullets. Use Prompt 1 for every single role. The 5 minutes it takes is the difference between a callback and a ghost.

2. Listing “References available on request.” It says nothing. US recruiters know you have references. Remove it.

3. Putting a photo, age, gender, or father’s name. The US recruiter doesn’t want it, and the ATS may fail to parse the file. Use Prompt 3 to remove these fields.

4. Using “Responsible for…” or “Worked on…” as bullet starters. Both signal low ownership. Use Prompt 5 to convert every bullet to XYZ format.

5. Hiding numbers behind “various” or “many”. “Various users” gets parsed as 0 users. Use real numbers, even if they are small. A real 50 users beats a fake 50,000.

6. Mentioning H-1B or visa status on the resume unless asked. For remote roles, the visa question is irrelevant. The payment line from Prompt 24 is enough.

7. Applying to roles that don’t match your stack. Indian grads often apply to “any tech role.” US recruiters filter by stack keyword match. Run Prompt 14 to align your projects to the JD.

8. Skipping the LinkedIn rewrite. US recruiters will check your LinkedIn after they read your resume. An empty or generic profile gets you deprioritized. Run Prompts 20 and 21.

9. Negotiating on platform choice when the US client offers Deel or Remote.com. It feels expensive. It is the cheapest way to get compliant USD pay. Don’t argue. Sign.

10. Quoting salary in INR. Always quote in USD when talking to US clients. The 2026 mid-rate is roughly 1 USD = 83 INR (RBI reference). Use USD. It signals you’re already thinking like a US contractor.

---

Final word

The 24 ChatGPT prompts for India grad US remote resume tailoring above are not a magic wand. They are a translator. You do the thinking. ChatGPT does the language conversion. The combination is what gets you from a 1% callback rate to a 3% callback rate. Over 300 applications, that is the difference between 3 calls and 9 calls. It is the difference between “still looking” and “first offer.”

Start with Prompt 1. Finish with Prompt 24. Send the resume to 10 US remote roles tonight. Apply to Turing and Wellfound before you do anything else. The 2026 remote US market for Indian grads is the most open it has ever been. The visa math is against you. The remote math is for you.

Now go ship the resume.

---