Hundreds of thousands of developers outside the United States apply to US tech companies every year. Most of them send a resume that was optimized for their local job market — and it doesn't travel well.
US tech recruiting has specific conventions: format, section order, phrase choices, and the handling of visa status. If your resume violates those conventions, it gets filtered before a human reads it. This guide is a practical walkthrough of exactly what to change.
The US Tech Resume Format Is Different From Most Countries
Before content, understand format expectations. US tech resumes differ from European, Asian, and Latin American conventions in several ways:
| Convention | US Tech Standard | Common International Variations |
|---|---|---|
| Length | 1 page (< 10 years), 2 max | 2–3 pages common in Europe, India |
| Photo | Never include | Required in many countries |
| Age/DOB | Never include | Common in Asia, Middle East |
| Marital status | Never include | Common in several regions |
| Objective statement | Usually omit | Common in many markets |
| References | Never list on resume | "References available upon request" is standard elsewhere |
Include a photo and ATS systems may flag it, or worse, human reviewers may unconsciously factor appearance into decisions — which is both illegal in US hiring and bad for you. US companies often actively exclude personal information to stay compliant.
Section 1: Handling Your Location and Visa Status
This is the question that causes the most anxiety, and there is no perfect answer. Here are the three scenarios:
Scenario A: You're Applying to Remote-Only Roles (No Sponsorship Needed)
# Yuki Tanaka
yuki@email.com | github.com/yukitanaka | linkedin.com/in/yukitanaka
Tokyo, Japan (UTC+9) | Authorized to work remotely worldwide
"Authorized to work remotely worldwide" signals that you're not asking for sponsorship — just that you're a remote worker based outside the US. Include your time zone so the company can assess overlap.
Scenario B: You're Applying to US-Based Roles and Need Sponsorship
# Yuki Tanaka
yuki@email.com | github.com/yukitanaka | linkedin.com/in/yukitanaka
Relocating to San Francisco, CA | H-1B sponsorship required
Be upfront. Companies that don't sponsor will filter you regardless — being clear saves everyone time. Companies that do sponsor will appreciate the directness. Hiding it and getting three interviews in only to have it come up in the offer stage wastes everyone's time.
Scenario C: You Already Have Work Authorization
# Yuki Tanaka
yuki@email.com | github.com/yukitanaka | linkedin.com/in/yukitanaka
San Francisco, CA | US work authorized (OPT/Green Card/Citizen — whichever applies)
If you have authorization, state it explicitly. "US work authorized" removes the ambiguity that causes many resumes to get passed over silently.
Section 2: The English Writing Test Is Happening On Your Resume
US tech companies, especially for engineering roles, conduct written communication in English every day: Slack messages, code review comments, design documents, Jira tickets. Your resume is your first English writing sample.
Common issues in international developer resumes:
Overly formal language:
Before:
- Contributed to the development and implementation of software solutions for enterprise clients
After:
- Built and maintained three enterprise client integrations in Python, handling 500k API calls/day
Inconsistent tense:
Use past tense for completed roles, present tense for your current role. Not mixed.
## Experience
**Senior Engineer** — Current Company
*Jan 2024 – Present*
- Build and maintain [present tense]
**Engineer** — Previous Company
*Jan 2022 – Dec 2023*
- Built and maintained [past tense]
Non-standard date formats:
# Wrong (European format):
15/03/2022 – 20/09/2023
# Correct (US standard for resumes):
Mar 2022 – Sep 2023
Section 3: Translating Non-US Company Names and Roles
A hiring manager at a US company may not know whether your previous employer is a local startup, a government agency, or a Fortune 500 equivalent. Give them context.
**Senior Software Engineer** — Kakao (South Korea's largest internet company, ~10k engineers)
*Jan 2021 – Dec 2023*
One parenthetical is enough. Don't oversell, but don't assume they'll Google it. If your company is globally recognized (Samsung, SAP, Tata Consultancy Services), no explanation needed.
Section 4: International Education and Degrees
US recruiters may not know the ranking of your university or the equivalence of your degree. A few practices help:
## Education
**B.S. Computer Science** — IIT Bombay (India Institute of Technology, ranked #1 in India)
*Graduated 2020*
**M.S. Artificial Intelligence** — TU Delft, Netherlands (Top 10 European technical university)
*Graduated 2022*
For non-English degree names, translate them and add the original in parentheses:
**Licenciatura en Ingeniería en Sistemas Computacionales (B.S. Computer Systems Engineering)**
UNAM, Mexico City, 2021
Section 5: The Skills Section — Use US Market Terminology
Technical terms are mostly universal, but some have regional variants. Use the US standard:
| Your region may say | US tech says |
|---|---|
| "agile methodology" | "Agile" or "Scrum" (just the noun) |
| "object-oriented programming" in bullets | It's assumed — skip unless required |
| "micro-services" | "microservices" (no hyphen) |
| "REST API's" | "REST APIs" (no apostrophe) |
These are small details, but they signal that you read US technical writing and communication.
Complete Example: International Developer Markdown Resume for US Roles
# Carlos Mendoza
carlos@email.com | github.com/carlosmendoza | linkedin.com/in/carlosmendoza
São Paulo, Brazil (UTC-3) | Available for US remote roles, open to relocation with sponsorship
## Skills
**Languages:** Python, TypeScript, Java
**Frameworks:** FastAPI, React, Spring Boot
**Cloud:** AWS (EC2, S3, RDS, Lambda), Google Cloud Platform
**Tools:** Docker, Kubernetes, Terraform, GitHub Actions, PostgreSQL
## Experience
**Senior Backend Engineer** — Nubank (Brazil's largest fintech, ~100M customers)
*Jun 2022 – Present*
- Designed and built a payment processing microservice in Python + FastAPI handling 2M transactions/day with 99.99% uptime SLA
- Led migration of monolith payment module to event-driven architecture using Kafka, reducing processing latency by 65%
- Mentored 3 junior engineers, established code review standards adopted by the 20-person backend team
**Software Engineer** — TOTVS (Brazilian enterprise software company, NYSE-listed)
*Mar 2020 – May 2022*
- Built RESTful APIs in Java + Spring Boot consumed by 500+ enterprise clients
- Reduced ERP report generation time by 70% through query optimization and caching layer
## Projects
**PayFlow OSS** — [github.com/carlosmendoza/payflow](https://github.com)
Open-source Python library for payment gateway integrations. 800+ GitHub stars, used in 30+ production systems.
## Education
**B.S. Computer Science** — Universidade de São Paulo (USP, ranked #1 in Latin America)
*Graduated 2020*
## Languages
Portuguese (native), English (professional), Spanish (conversational)
A clean Markdown format ensures this exports cleanly regardless of your region's typical resume conventions. Tools like markdownresume.app produce single-column PDFs optimized for US ATS systems.
Frequently Asked Questions
Q: Should I include a languages section if English is not my first language?
Yes, with your proficiency level. "English (professional)" or "English (fluent)" signals that you're comfortable with professional written and spoken communication. Don't overstate your level — interviews will reveal it anyway.
Q: Is it worth applying to US companies if I need H-1B sponsorship?
Large companies (FAANG, Stripe, Salesforce, etc.) sponsor regularly. Early-stage startups almost never do. Mid-stage startups vary. Research the company's sponsorship history on myvisajobs.com before applying.
Q: Should I convert my salary from my local currency when asked for expectations?
US tech companies typically have set salary bands. Research the role on Levels.fyi or Glassdoor to understand the range and give a number in USD.
Q: My resume is two pages because I have extensive experience. Will US companies reject it?
For senior engineers (7+ years), two pages is accepted. Prioritize cutting anything older than 8 years and any bullets that don't add new signals.
Q: Can I apply to US remote roles from a country with a large time zone difference?
Yes, if the company is async-first or accepts significant overlap challenges. Explicitly note your time zone and availability for US morning meetings if you're willing to do them.
US tech hiring is standardized in ways that most countries aren't — and that standardization works in your favor once you understand it. A well-formatted, clearly written Markdown resume that follows US conventions will be evaluated on its merits. The format stops being a barrier and the content does the work.