Step by step
- 1
Build a US-format resume first
One page, no photo, no date of birth, no marital status. Use a US phone format and Month-Year dates. Standard headings (Experience, Projects, Education, Skills) and a single column so the ATS parses cleanly.
- 2
Decide how to signal work authorization
Many employers ask 'will you require sponsorship?' early. Some students add a short, factual line — for example, 'Work authorization: F-1 OPT (STEM extension eligible)' — near the contact info or in a footer. This is optional; the goal is to reduce uncertainty, not to overshare.
- 3
Treat CPT internships as real experience
CPT work is professional experience — list it under Experience with company, title, dates, and quantified bullets, exactly like any job. Don't bury it under 'Academic' just because it was CPT.
- 4
Lead with projects if experience is thin
Course projects, research, hackathons, and open-source work count. Give your strongest project real bullets with outcomes and a link. A project with real users and a measurable result competes with an internship.
- 5
Quantify academic and project work
Numbers translate across borders: users served, accuracy improved, time saved, dataset size, team size. 'Built a class-scheduling app used by 800+ students' is far stronger than 'developed a web app.'
- 6
Target employers who hire international talent
Prioritize companies with a track record of hiring OPT/STEM-OPT candidates. Tailoring each resume to the posting's stack raises your callback rate and is worth the 10–15 minutes.
- 7
Keep it honest and be ready to explain
Whatever you put about authorization must be accurate. Have a clear, calm one-line explanation of your status and timeline ready for phone screens.
Checklist
- One page, US format — no photo, DOB, or marital status
- US phone format and Month-Year dates
- Optional, factual work-authorization line if you choose to include one
- CPT internships listed as real Experience with quantified bullets
- Strongest projects given real bullets and links
- GPA on a 4.0 scale (include if 3.3+)
- Stack tailored to each target job description
- Standard headings, single column, ATS-safe
- Authorization details verified with your DSO
Optional authorization line
Priya Nair · Boston, MA · (617) 555-0142 · priya.nair@email.com · github.com/priyanair Work authorization: F-1 OPT (STEM extension eligible) — no current sponsorship required Software Engineer Intern (CPT), Brightwave Systems — Jun 2024 – Dec 2024 • Built REST APIs in Python used by 3 internal teams, cutting report time 40%.
Tips
- Don't hide CPT experience under 'academic' — it's professional experience.
- Keep any authorization note short and factual; never guess at legal specifics.
- Lead with projects and internships, not a generic objective statement.
- Match the posting's keywords — tailoring matters even more when you need a callback.
- Verify your status and timeline with your school's DSO before writing authorization lines.