How to Write a US-Style Resume: Guide for Indian Professionals

The single biggest mistake Indian professionals make when applying for jobs in the United States has nothing to do with their skills, their experience, or their education. It's simpler than that and somehow more painful: they send a biodata.

I know. You're thinking, "But that's what we call a resume in India." And yes, technically, the word "biodata" and "resume" and "CV" get used interchangeably back home. But the document itself — the format, the content, the entire philosophy behind it — is so wildly different from what American hiring managers expect that your application gets discarded in about six seconds. That's not an exaggeration. Recruiters at US tech companies spend an average of 6-7 seconds on an initial resume scan. If yours opens with "Name: Rajesh Kumar, Date of Birth: 15th March 1991, Father's Name: Suresh Kumar, Marital Status: Single" — those six seconds are already wasted on information that's not just irrelevant but actually illegal for American employers to consider.

Let me be very direct about this. American companies can't legally factor in your age, marital status, gender, religion, or family details when making hiring decisions. When you put that information on your resume, you're not being thorough. You're making the recruiter uncomfortable. They're now looking at information they're trained to ignore, and your resume is associated with a compliance headache before they've even read about your Python skills.

The Photo Problem

Remove your photo. Full stop. I don't care how professional the headshot is. I don't care that your cousin who works at Infosys told you to include one. In the US job market, a photo on a resume is — I'm pretty sure — a red flag. It signals that you don't understand American hiring norms, and in some cases, it can actually cause your resume to be auto-rejected by applicant tracking systems because the image file messes with the parsing software.

The only exception I can think of is if you're applying for an acting or modeling role. You're probably not. Take the photo off.

What a US Resume Actually Looks Like

A US-style resume is a sales document. That's the mental shift you need to make. Back in India, we tend to treat the resume as a complete record of everything we've done — every certification, every project in college, that two-week internship at your uncle's friend's software shop in 2014. American resumes are curated. They're edited. They only include what's relevant to the specific job you're applying for.

Here's the basic structure, and then I'll walk through each section with real examples:

Your name goes at the top. Big. Bold. Below it: email, phone number, LinkedIn URL, and optionally your city and state (not your full address — nobody mails resumes anymore, and including your street address is a security risk). That's it for personal information. No date of birth, no passport number, no visa status in the header.

A quick note on the visa thing. I know it feels dishonest to not mention your H1B status or your need for sponsorship upfront. But here's the reality: if the job posting says "must be authorized to work in the US" or "no sponsorship available," don't apply. If it doesn't say that, your visa status belongs in the conversation stage, not the resume stage. Some people disagree with me on this, and honestly, there's no perfect answer. But I've seen too many qualified engineers get filtered out by ATS systems that screen for visa-related keywords. Get the interview first, then have the conversation.

The Professional Summary vs. the Career Objective

Indian resumes almost always start with a "Career Objective" that reads something like: "To obtain a challenging position in a reputed organization where I can use my skills and contribute to the growth of the company." I want to be kind about this, but I also need to be honest — this sentence tells the recruiter absolutely nothing. Every candidate wants a challenging position. Every candidate wants to contribute. It's filler, and American recruiters know it.

Instead, you want a Professional Summary. Two to three sentences. Specific. Numbers if possible. Here's a before and after:

Before (Indian style): "Seeking a challenging position as a Software Engineer where I can use my technical skills and work experience to contribute to the success of a dynamic organization."

After (US style): "Backend engineer with 6 years of experience building distributed systems in Java and Go. Led the migration of a monolithic payment processing service to microservices at Flipkart, reducing latency by 40% and handling 50K+ transactions per minute. Looking to bring that scaling expertise to a growth-stage fintech company."

See the difference? The second one is specific. It has numbers. It names technologies. It tells a story in three sentences. The recruiter now knows exactly what you do, how well you do it, and what you're looking for. That's a professional summary.

Work Experience: The STAR Method Is Your Friend

This is where most Indian resumes fall apart, and it's not because the experience is lacking. It's because — I think — the experience is described wrong.

Indian professionals tend to list responsibilities. "Responsible for developing and maintaining web applications." "Worked on database optimization." "Handled client communication." These are job descriptions, not achievements. The recruiter already knows what a software engineer does. What they want to know is what YOU especially accomplished.

The STAR format — Situation, Task, Action, Result — is the standard framework, but honestly, for resume bullets, I think about it more simply: start every bullet point with a strong action verb, include what you did, and end with a measurable result.

Before: "Responsible for developing REST APIs for the e-commerce platform."

After: "Designed and implemented 15+ REST APIs for product catalog and order management, reducing page load times by 30% and supporting a 3x increase in daily active users during Diwali sale events."

Before: "Worked on improving the CI/CD pipeline."

After: "Rebuilt the CI/CD pipeline using Jenkins and Docker, cutting deployment time from 45 minutes to 8 minutes and eliminating 90% of deployment-related outages in Q3 2023."

Notice how the "after" versions are longer? That's fine. American resumes aren't about being brief for brevity's sake. They're about being specific. A two-page resume is completely acceptable if you have more than 3-4 years of experience. For senior engineers, even three pages can work, though most people should aim for two.

Translating Indian Company Names

This one's subtle but important. If you worked at TCS, Infosys, or Wipro, American recruiters generally know those names. But if you worked at, say, Zoho or Razorpay or a mid-size company that's well-known in India but not in the US, you need to provide context.

Don't just write "Software Engineer, Razorpay." Write "Software Engineer, Razorpay (India's largest payment gateway processing $80B+ annually, comparable to Stripe)." That parenthetical comparison does enormous work. Suddenly the recruiter understands the scale and prestige of where you worked.

For smaller companies, a brief description is even more critical. "Full Stack Developer, QuickHeal Technologies (cybersecurity company with 30M+ users across Asia)" gives the recruiter the context they need to value your experience appropriately.

Education: Less Than You Think

Indian resumes love to detail education. Your 10th standard marks. Your 12th standard board. Your CGPA. Your college's NAAC rating. The American recruiter doesn't know what any of this means, and frankly, they don't care.

For education on a US resume, here's what to include: degree name, university name, graduation year. That's it. If you went to an IIT or a well-known institution, you might add a brief note — "Indian Institute of Technology Bombay (acceptance rate: 2%, ranked #1 engineering university in India)" — but even that's optional if you have solid work experience.

Don't include your percentage or CGPA unless it's mainly asked for in the job application. American GPAs are on a 4.0 scale, and trying to convert your 8.2 CGPA into a GPA equivalent is messy and often inaccurate. If pressed, you can say something like "8.2/10, top 5% of class" which gives relative context.

Your 10th and 12th standard results should never, ever appear on a resume for a US job. I don't care if you scored 98% in your boards. By the time you have a college degree and work experience, high school results are irrelevant everywhere, but especially in the US.

The Skills Section: Be Strategic, Not Exhaustive

I've seen Indian resumes with skills sections that run 15-20 lines. Every programming language you've ever touched, every framework you used once in a college project, every tool you've seen demonstrated in a YouTube tutorial. This hurts you more than it helps you.

Here's why: if you list "Machine Learning" as a skill and the interviewer asks you about gradient descent and you fumble, you've just torpedoed your credibility. Only list skills you can confidently discuss in an interview. Better to have a focused list of 8-12 strong skills than a sprawling list of 30 that includes things you barely remember.

Organize your skills by category. Something like:

Languages: Java, Python, Go, SQL
Frameworks: Spring Boot, Django, React
Cloud & DevOps: AWS (EC2, S3, Lambda), Docker, Kubernetes, Terraform
Databases: PostgreSQL, MongoDB, Redis

Notice I specified which AWS services I know, not just "AWS." This is important because "AWS" is so broad it's almost meaningless. Saying "AWS (EC2, S3, Lambda, RDS, CloudFormation)" tells the recruiter exactly what you've worked with.

Formatting Details That Matter More Than You'd Think

Use a clean, single-column format. No tables, no columns, no graphics, no colored headers. I know it looks boring. I know you found a cool two-column template on Canva. Don't use it. Most large US companies use Applicant Tracking Systems that parse your resume into a database, and fancy formatting breaks the parser. Your beautiful two-column resume turns into jumbled nonsense in the ATS, and a recruiter who can't read your resume isn't going to fix it — they'll just move on.

Font: stick with Arial, Calibri, or Garamond. Size 10-11 for body text, 12-14 for your name. Margins of 0.5 to 1 inch on all sides. Save as PDF unless exactly asked for a Word document. PDFs preserve your formatting across devices; Word documents can look different on every computer.

File name matters. "Resume.pdf" is bad. "Rajesh_Kumar_Resume.pdf" is fine. "Rajesh_Kumar_Backend_Engineer.pdf" is better. The recruiter downloads dozens of resumes — make yours identifiable.

The "Declaration" Has Got to Go

Indian resumes often end with: "I hereby declare that all the information provided above is true to the best of my knowledge." Sometimes it even includes a place and date, like a sworn affidavit. Don't include this on a US resume. American recruiters find it strange at best and amusing at worst. It's understood that you're being truthful on your resume — you don't need to declare it. And if you're not being truthful, a declaration at the bottom certainly isn't going to help.

Similarly, skip "References available upon request." This was standard practice in the 1990s. It's now considered filler. If the company wants references, they'll ask for them during the process.

Tailoring for Each Application

This is the part nobody wants to hear. You shouldn't be sending the same resume to every job. I know it's tedious. I know you're applying to 50-100 positions and customizing each one feels impossible. But at minimum, you need to do two things for each application:

First, read the job description and identify the key technologies and requirements. If the job mentions "experience with Kubernetes," make sure that word appears on your resume — in your skills section and ideally in a work experience bullet point. ATS systems often screen for specific keywords, and if yours doesn't match, a human may never see it.

Second, reorder your bullet points so the most relevant experience comes first. If you're applying for a data engineering role and your current job involves both data engineering and frontend work, lead with the data engineering bullets. It sounds obvious, but I've reviewed hundreds of resumes where the most relevant experience is buried in the third bullet point under their second job.

Things That Are Normal in India but Weird in the US

Putting your gender on a resume. Weird in the US. Mentioning your languages spoken (unless the job requires multilingual ability). Mostly unnecessary. Listing "hobbies and interests" like "reading books, playing cricket, listening to music." Please don't. Including your passport number. Absolutely not. Putting "Mr." or "Mrs." before your name. Skip it.

On the flip side, things that are normal in the US but might feel weird: using first names in your resume header (not "Mr. Rajesh Kumar" but just "Rajesh Kumar"), writing in a somewhat conversational tone in your summary, and being openly proud of your achievements. Indian culture often teaches humility, and that's a wonderful value, but your resume isn't the place for it. If you increased revenue by 25%, say so. If you led a team of 12 engineers, say so. This isn't bragging — it's providing the information the recruiter needs to evaluate you fairly.

ATS Optimization: the Boring Part That Gets You Interviews

Applicant Tracking Systems are the gatekeepers at most US companies. Before a human reads your resume, software reads it first. Here's what you need to know:

Use standard section headings. "Work Experience" not "Professional Journey." "Education" not "Academic Credentials." "Skills" not "Technical Arsenal." The ATS is looking for standard headings to categorize your information. Get creative with your bullet points, not your headers.

Don't put critical information in headers or footers. Some ATS systems can't read them. Your contact info should be in the body of the document.

Spell out acronyms at least once. Write "Amazon Web Services (AWS)" the first time, then use "AWS" afterward. This way the ATS catches both the full name and the abbreviation.

Avoid special characters where possible. Bullets are fine (use standard round bullets), but fancy symbols, icons, or emojis can confuse parsers.

A Real-World Example

Let me walk through a quick transformation. Say you're a senior backend developer at Infosys with 7 years of experience, applying for a Staff Engineer role at a Series C startup in San Francisco.

Your Indian-style resume might open with a career objective, list Infosys without context, describe your work as "handled development of microservices for banking client," include your 10th and 12th marks, list 25 skills including some you used once five years ago, and end with a declaration.

Your US-style resume would open with: "Staff-level backend engineer with 7 years of experience at Infosys (India's second-largest IT services company, 300K+ employees). Specialized in building high-throughput financial systems processing $2B+ in daily transactions. Core expertise in Java, Spring Boot, Kafka, and AWS." Then your work experience would tell a story with numbers: "Architected an event-driven microservices platform using Kafka and Spring Boot that replaced a legacy batch processing system, reducing settlement time from T+1 to near-real-time for 15M+ daily transactions." Your skills section would be tight — maybe 12-15 technologies you're genuinely strong in. Your education would be one or two lines. No declaration. No photo. No personal details beyond contact info.

That's the transformation. It's not about lying or inflating your experience. It's about presenting the same experience in a format that American recruiters are trained to read and evaluate.

One Last Formatting Detail

Use consistent date formats throughout your resume. American convention is "Month Year" — so "January 2020 - Present" or "Jan 2020 - Present." Don't use "01/2020" because Americans write dates as MM/DD/YYYY and the ambiguity of whether "01/03" means January 3rd or March 1st creates unnecessary confusion. And definitely don't use the DD/MM/YYYY format common in India. Stick with written-out months and you'll avoid the issue entirely. Also, use an en dash (--) between dates, not a hyphen, if your word processor supports it. It's a tiny detail. But tiny details are what separate a resume that looks polished from one that looks almost right.