← Back to Blog
September 8, 2026 · 4 min read

How to Write a Resume (Currículo) for the Brazilian Job Market in 2026

Brazil's job market has a genuinely distinct structure worth understanding before you write your currículo: the CLT vs. PJ employment distinction shapes how experience is often described, and Brazil's fast-growing remote tech sector has its own, more internationally-aligned expectations layered on top of local convention.

Understand CLT vs. PJ in how you describe past roles

CLT (formal, employee-status contracts) and PJ (contractor/freelance-style arrangements, common in tech) are both legitimate and common, but worth being precise about when describing past positions — some employers specifically screen for candidates comfortable with one arrangement or the other.

Local roles vs. international/remote roles need different documents

A currículo for a local Brazilian company follows regional convention; a resume aimed at a US or global remote employer should follow the international, photo-free, ATS-optimized format instead — including one-page length and quantified, keyword-matched bullets.

Brazil's tech and remote-work sector is genuinely internationally minded

If you're targeting Brazil's growing remote/global tech scene specifically, English fluency and remote-collaboration experience are worth foregrounding clearly — these roles are frequently screened by international hiring managers who expect US-style resume conventions, not local ones.

Frequently asked questions

What's the difference between CLT and PJ in a Brazilian resume?

CLT refers to formal employee-status work contracts; PJ refers to contractor/freelance-style arrangements, common especially in tech. Being clear about which applied to each past role helps recruiters understand your work history accurately.

Should I write my currículo in Portuguese or English?

For local Brazilian companies, Portuguese is standard. For international or remote roles with global employers, an English resume following US-style ATS conventions is usually expected instead.