Sooner or later in a conversation about hiring in Brazil, someone says "he is PJ" and the American on the call nods without knowing what was just agreed. It is worth ten minutes, because the term carries a specific legal structure, a specific tax treatment, and one specific risk — and the risk is not where most buyers assume it is.
What PJ actually is
PJ is short for pessoa jurídica, which simply means legal entity, as opposed to pessoa física, a natural person. A Brazilian engineer working "as PJ" has registered a company — typically a single-member limited company, and often under a simplified tax regime called Simples Nacional — and provides services through it. Each month the company issues an invoice, called a nota fiscal, and is paid against it.
This is not a loophole and it is not unusual. It is the ordinary arrangement for senior technology work in Brazil, for the same reason U.S. consultants incorporate: the effective tax burden on service income through a small company is materially lower than personal income tax at the top of the CLT scale, and the engineer keeps control over how they work.
The other model, CLT, and why engineers avoid it
The alternative is CLT — the Consolidação das Leis do Trabalho, Brazil's employment statute. A CLT employee gets a signed work card, paid vacation with a one-third bonus, a thirteenth salary, FGTS deposits, notice protections and a long list of other entitlements. It is a strong employment regime, and it is expensive: employer cost typically runs well above the gross salary once the statutory items are added.
A senior engineer comparing a CLT offer with a PJ contract is usually comparing a lower net figure with a higher one, and most of them choose the higher one. That is why the senior end of the Brazilian market is predominantly PJ, and why a U.S. company insisting on a direct employment relationship will find the candidate pool smaller and more expensive than it expected.
Where the real risk is: pejotização
Here is the part worth knowing. Brazilian labour law looks at the substance of a relationship, not its label. If a person works exclusively for one client, on that client's fixed schedule, under its direct supervision, doing work indistinguishable from an employee's, a labour court can rule that an employment relationship existed regardless of the contract — and order payment of the entitlements that were never paid. The practice of disguising employment as a service contract has a name in Brazil: pejotização.
The four elements a court examines are roughly: personal service by a specific individual, habitual work, subordination to the client's orders, and payment for time rather than for a result. Subordination is the one that decides most cases.
For a U.S. buyer, the practical question is therefore not "is PJ legal" — it is who is exposed if a court takes that view. And that depends entirely on who signed what.
Three structures, three very different exposures
| Structure | Who holds the Brazilian relationship | Where the exposure sits |
|---|---|---|
| You contract the engineer's PJ directly | You | You. A Brazilian claim would name your company, and you would defend it in a Brazilian court. |
| You contract a Brazilian studio or vendor | The studio | The studio. You hold a B2B services contract with a company, not a relationship with an individual. |
| You use an employer of record | The EOR, as the legal employer | The EOR, at a monthly fee on top of salary. |
This is the substantive difference between "hiring a Brazilian contractor" and "buying engineering services from a Brazilian company", and it is invisible in the price comparison. When you work with a studio, the engineers are contractors of the studio, not of you: you need no Brazilian entity, you run no Brazilian payroll, and the employment question is not one you have to answer. The contractor-versus-EOR comparison sets out the trade-offs when you do want to hold the relationship yourself.
What PJ changes about your day-to-day — almost nothing
Buyers sometimes assume PJ means a looser commitment: part-time, multiple clients, unpredictable. In a properly structured full-time engagement it means none of those things. The engineer works your business hours, joins your standups, is on your Slack and owns their part of the roadmap. What differs from a U.S. employee is administrative, not behavioural: there is no W-2, no benefits enrolment, no U.S. payroll line, and one monthly invoice instead.
Two things do genuinely change, and both are worth agreeing explicitly up front:
- Intellectual property. Brazilian law does not assign work product to a client by default the way a U.S. employment relationship does. The assignment has to be written into the contract, and it has to name the deliverables. The IP and NDA guide covers the clauses that hold up.
- Time off. A PJ contractor has no statutory vacation, which means either the contract sets an allowance or nobody ever agrees one and it becomes an argument in month eight. Fifteen working days a year is a common and reasonable figure.
Questions worth asking any vendor
- Is the engineer contracted by you or by me? Ask for the answer in writing.
- If a Brazilian labour claim were filed, whose company would be named?
- Does the contract assign IP to me, and does it survive the engineer leaving?
- What happens to my code and my access on the day the engagement ends?
A vendor that answers those four clearly is a vendor whose paperwork exists. One that answers with reassurance rather than clauses is telling you something else. If you want the cost side of the same decision, pricing has the monthly figures and the rate index shows the methodology behind them.
None of this is legal advice, and a Brazilian labour lawyer will give you a sharper answer for your specific structure than any article will. But knowing that the word PJ describes a company, not a job title — and that the question to ask is who holds the contract — puts you ahead of most buyers in this market.