US recruiters often decide in under a minute whether your resume goes forward. In IT hiring, the format matters almost as much as the content, because the resume is read by software first and by a person second. Here is a clear format that works for most IT roles in the US.
The basics
- Length: two pages is normal for 5 or more years of experience. One page is fine for freshers.
- File type: Word (.docx) or a text-based PDF. Avoid scanned images and fancy templates with columns and icons, which many systems read badly.
- Font: a clean, standard font such as Calibri or Arial, 10 to 11 pt.
- File name: FirstName_LastName_Role.docx.
What to leave out
US resumes do not usually include a photo, date of birth, marital status, religion, father’s name or a full home address. A city and state, a phone number, an email and a LinkedIn link are enough. Leaving these out is the standard practice, and it keeps the focus on skills.
Section order
- Header: name, city and state, phone, email, LinkedIn.
- Professional summary: three to five lines. Years of experience, main stack, domains and the type of role you want.
- Technical skills: grouped lines, for example Languages, Frameworks, Cloud, Databases, Tools.
- Experience: most recent first.
- Education and certifications.
How to write each job
For each employer, list the company, your title, the location and the dates by month and year. Then add short bullet points that show what you built and what changed because of it.
- Start each bullet with a verb: built, migrated, reduced, automated, designed.
- Add a number where you honestly can: response time, number of users, release frequency.
- Keep each bullet to one or two lines.
- End each role with an “Environment” line listing the tools used on that project.
Example: “Migrated a monolithic order service to Spring Boot microservices on AWS, cutting average API response time from 900 ms to 400 ms.”
Keywords and ATS
Applicant tracking systems match your resume against the job post. Read the post and use the same names for the same tools, as long as you really have used them. If the post says “Amazon Web Services (AWS)”, write it that way once. Do not paste a long list of tools you cannot discuss. Interviewers will ask about every item on your resume.
Common mistakes
- Writing duties (“responsible for”) instead of results.
- Gaps in dates with no explanation. A short line, such as “Career break for family reasons”, is better than a silent gap.
- Different job titles on the resume and on LinkedIn.
- Copying another person’s project descriptions. Recruiters and clients notice, and it can end the process.
- Listing a skill you have only read about.
A sample summary
“Java developer with 7 years of experience building REST APIs and microservices in banking and retail. Strong in Spring Boot, AWS and SQL. Experienced in agile teams, code reviews and production support. Looking for a contract or full-time backend role.”
Notice that it names the stack, the years, the domains and the target role, in four lines. Change it for every application so it matches the job post.
Fresher or career-change resumes
If you have little paid experience, put projects first. Give each project a name, the tools used, what it does and your part in it. Add internships, certifications and open-source work if you have them. Be exact about what you did yourself and what was a team effort, because interviewers will ask.
Work authorization line
Many US recruiters want to know your status quickly. Some candidates add a single line near the top, such as “Work authorization: OPT, valid through 2027”. If you are unsure how to phrase it, read our guide on how to answer the sponsorship question so that your resume and your call say the same thing.
A quick checklist
- Two pages or less, simple layout.
- Summary matches the role you are applying for.
- Skills are grouped and honest.
- Each job has results, not only duties.
- Spelling and tense are consistent. Past tense for old jobs, present tense for the current one.
- You can explain every line in an interview.
Next step
Once the resume is in shape, prepare for the call with our guide to explaining your project in an interview, see our training courses, or reach out to our candidate team.
