Why the difference is not a fixed number
Brazil abolished daylight saving time in 2019. The United States did not. So the gap between the two countries changes twice a year — in March and November — and any source that gives you a single fixed number is wrong for part of the year.
From November to March, São Paulo is two hours ahead of New York. From March to November, it is one hour ahead. Neither is a big enough gap to require anyone to change their life.
What overlap looks like in practice
An engineer working 9 AM to 6 PM in São Paulo is online from 7 AM to 4 PM Eastern in winter, and 8 AM to 5 PM Eastern in summer. Against a 9-to-5 Eastern team, that is seven to eight hours of shared time — effectively the entire workday.
Against Central time, the same schedule yields six to seven hours. Against Mountain, five to six. Against Pacific, four to five — and this is where it becomes a real design decision rather than a footnote.
For Pacific-time teams the workable pattern is a shifted Brazilian day — starting at 11 AM São Paulo, finishing at 8 PM — which buys six to seven hours with a 9-to-5 Pacific team. It works, and it costs the engineer their evening, so it should be agreed openly and compensated in flexibility elsewhere. Ask for it if you need it; do not assume it is included.
How this compares with the alternatives
India is nine and a half to ten hours ahead of New York. An Indian engineer on a normal 9-to-6 local schedule shares zero hours with a 9-to-5 Eastern team. Every hour of overlap comes out of somebody’s evening or night.
Poland is five to six hours ahead of New York; the Polish workday ends around 11 AM Eastern. Two to three hours, at the tired end of their day.
The Philippines and Vietnam are eleven to thirteen hours off. The entire outsourcing model there is built on night shifts, openly and by design.
This is the whole nearshore argument, and it is arithmetic rather than marketing. It does not make Brazil better at software — it makes the coordination cheaper.
Scheduling rules that hold up
Put the standup at the start of the U.S. day, not the start of the Brazilian one. The engineer is already three hours into their work by then and can report real progress.
Keep the last two hours of the Brazilian afternoon meeting-free. That is when a U.S. Eastern team is fully awake and unblocking happens fastest — do not spend it in a status call.
Brazilian public holidays do not match U.S. ones. Carnival and the June holidays surprise people every year. Ask for the calendar in month one and put it in your sprint planning.
Key takeaways
- Brazil is UTC−3 year round; the U.S. is what moves.
- São Paulo is one hour ahead of New York in summer, two in winter.
- Eastern and Central teams get six to eight hours of overlap with no schedule changes.
- Pacific teams get four to five on ordinary hours, or six to seven if the engineer shifts their day to end at 8 PM — which is a thing to agree explicitly, not to assume.
- Brazilian holidays differ from U.S. ones — get the calendar early.