# nearshore brazil: what US teams need to know
Start a Brazil search with the hours and work the hire must own. A country preference will not tell you whether someone can review your architecture, handle a customer call or join your release meeting.
For a US hiring manager, the first decisions are practical. Choose the live working window. Define the role through work samples. Then get a written employment-cost quote and a calendar that matches the employee's location.
Keep those decisions together as the search moves forward. A strong interview does not resolve a schedule mismatch. A monthly price does not tell you who handles an employment exit. Make each part of the offer clear before asking a candidate to accept it.
How many working hours overlap with US time zones?
São Paulo stays at UTC−3 and does not observe daylight saving time. Brazil ended daylight saving time in 2019. US clock changes still move the gap between São Paulo and your team. Use the candidate's actual city when setting the schedule. IANA South America
The table below uses 09:00–18:00 local windows on both sides. It shows elapsed clock overlap before lunch or other breaks. These windows are scheduling assumptions, not a statement that the employee works nine paid hours.
| US season | US zone | São Paulo 09:00–18:00 in US local time | Shared window in US local time | Shared clock hours |
|---|---|---|---|---|
| Standard time | Eastern | 07:00–16:00 | 09:00–16:00 | 7 |
| Standard time | Central | 06:00–15:00 | 09:00–15:00 | 6 |
| Standard time | Pacific | 04:00–13:00 | 09:00–13:00 | 4 |
| Daylight time | Eastern | 08:00–17:00 | 09:00–17:00 | 8 |
| Daylight time | Central | 07:00–16:00 | 09:00–16:00 | 7 |
| Daylight time | Pacific | 05:00–14:00 | 09:00–14:00 | 5 |
Calculated from the offsets in IANA South America and IANA North America, using the stated working windows.
Eastern teams have more room for live work within this schedule. Pacific teams should place shared work in their morning. A recurring late-afternoon Pacific meeting would fall outside the São Paulo window shown above.
Write the required overlap into the role description before interviews. Use named time zones and exact hours. "US hours" leaves too much room for different expectations.
Check the calendar against the work itself. A developer may need a product manager during planning, a reviewer before merging and an incident lead during an outage. If those people are available at different times, a single daily meeting will not cover the job.
Protect some of the shared window for questions that arise during work. Filling it with recurring meetings can leave the hire waiting until the next day for a review. Put status updates in writing when they do not require discussion.
For example, a Pacific manager could reserve the morning for design decisions and code review. The Brazil-based engineer can prepare questions before that window opens. Agree on where to leave a blocked task and who checks it first. This gives the shared hours a purpose beyond attending a daily call.
Ask the candidate to review a sample weekly calendar before accepting the offer. Include the meetings they must attend and the expected break. If a customer call falls outside the proposed schedule, resolve that conflict now. Do not leave the hire to negotiate it after joining.
Agree on any shifted schedule before an offer. Ask the employer how breaks, overtime and on-call duties fit the arrangement. Repeat that check when a US clock change moves a recurring meeting.
Which roles should you test for depth in Brazil?
Assess depth at the level of the role and candidate pool you can actually hire. Ask the provider to show relevant profiles for your stack and budget. A long list of programming languages does not establish that someone can own your service.
For nearshore IT hiring, separate tasks that need close daily contact from tasks with clear written handoffs. That distinction helps you decide which skills to test and how much live overlap to require.
| Role under consideration | Evidence to request | Useful interview task |
|---|---|---|
| Backend engineer | Ownership of a production service and its failure modes | Review an API change and explain migration risks |
| Frontend or full-stack engineer | Shipped interfaces and responsibility for user-facing defects | Diagnose a small UI issue and discuss accessibility |
| DevOps or platform engineer | Deployment, rollback and incident experience | Walk through a failed release and recovery plan |
| Data engineer | Pipeline ownership and checks on data quality | Explain how to detect and repair a broken load |
| Engineering lead | Design decisions, review habits and team responsibility | Resolve a tradeoff between delivery speed and maintenance |
These are hiring checks, not claims about the size of each Brazilian talent pool. Use the same exercise and scoring rules for every candidate being considered for the same job.
For a senior hire, look for decisions they owned. Ask what failed, how they found the cause and what they changed afterward. Someone who can describe the tradeoff clearly gives you more to assess than someone who names tools.
For a mid-level hire, test whether they can complete a bounded task and recognize when they need help. For a junior hire, confirm that your team has enough review time and a named mentor. Shared hours do not create mentoring capacity by themselves.
Portuguese is Brazil's official language. Assess English through the work the person will do. Have an engineer explain a technical choice, respond to a question and write a short handoff. For customer-facing work, include a realistic customer conversation.
Separate communication scores from accent or interview polish. Can the person explain a risk clearly enough for a teammate to act? Can they ask for missing context without guessing? Those questions are closer to daily engineering work than a general conversation about career goals.
Keep the exercise small and avoid asking candidates to solve unpaid production work. Tell them what you will assess. A focused task is easier to score than a broad assignment with unclear expectations.
When a provider calls a candidate "senior," ask what that label means. It might refer to years worked, technical depth or team leadership. Write down the ownership your role needs, then check the evidence against it. Someone with strong implementation skills may still need support with architecture or stakeholder decisions.
If the role includes AI tools, ask how the candidate checks generated output and handles private data. Score their reasoning against your team's actual rules. Do not treat tool use as proof of sound engineering judgment.
Before opening the search, name the first deliverable and the manager who will review it. "Improve the platform" gives candidates little to work with. A specific service, backlog or operational problem makes the role easier to assess.
What do employment law and statutory benefits require?
Choose the employment arrangement before comparing monthly quotes. Ask who employs the person, which agreement governs the work and who handles payroll obligations. Have the employer explain how the proposed arrangement applies to the actual role.
For employees, Brazil's 13th salary and FGTS deposits belong in the cost review. They have different calculation rules. A single percentage added to base salary is not a substitute for a payroll breakdown.
| Item | Statutory basis | What to confirm in the quote |
|---|---|---|
| 13th salary, or Gratificação de Natal | Lei 4.090, Article 1: accrual of one-twelfth of December remuneration per month of service | Accrual, payment schedule and treatment of a partial year |
| FGTS employer deposit | Lei 8.036, Article 15: generally 8% of covered remuneration, including the 13th salary in the base | Included remuneration and who makes the deposits |
| Notice | Lei 12.506, Article 1: 30 days for service up to one year, with service-related additions up to a total of 90 days | Application to the proposed employment and exit scenario |
Statutory references: Lei 4.090, Lei 8.036 and Lei 12.506.
Article 1 of Lei 4.090 also treats a fraction of at least 15 days worked as a full month for this accrual. Ask payroll to show the calculation for the planned start date. Do not assume that joining late in the year removes the obligation. Lei 4.090, Article 1
For FGTS, ask the employer to show the calculation base alongside the deposit. Article 15 includes the Gratificação de Natal. That matters when finance checks whether the annual budget covers more than regular monthly pay. Lei 8.036, Article 15
Have the employer document paid leave, vacation pay and any applicable collective agreement. Request the rules for overtime and holiday work if the person will support releases or incidents. Confirm who approves extra hours and how those hours appear on the invoice.
If a provider proposes a contractor agreement, ask it to explain why that arrangement fits the actual work. Describe who sets hours, assigns tasks and supervises performance. Have qualified local counsel review the proposed terms against those facts. A contract label alone should not settle the buying decision.
Also ask for an exit-cost example before signing. Use the proposed contract and a stated length of service. Have the employer separate notice, accrued amounts and any other applicable charges. A replacement search and an employment termination are different events.
Put operational responsibilities in writing too. Name the contact for a payroll error and the person authorized to approve a pay change. Decide how the employee raises a leave request. Your engineering manager should know where these questions go without becoming the payroll administrator.
Opus charges one flat monthly rate per hire. This site is an Opus-owned reference; recommendations are editorial. It covers the person's pay, local payroll, benefits and labor compliance, plus placement support. There is no separate recruiting fee. The rate depends on role, seniority and location.
For any monthly arrangement, ask what can change the price and what remains payable during leave or a replacement search. Put the answer in the agreement. Finance should be able to reconcile the quote with the invoice without relying on a sales call.
Which public holidays affect delivery?
Use the calendar that applies to the employee's location and employment terms. A US office calendar will not answer whether a Brazil-based teammate is available for a release or support shift.
The Opus LatAm holiday planner can help compare country calendars. Its Brazil entries include Good Friday. Have the employer confirm the applicable dates and local treatment before turning the planner into a delivery schedule.
Ask specifically about Carnival and any other dates your team expects to affect availability. Get a clear answer on whether each date is a required day off, an employer holiday or requested leave. Avoid assuming that every observance has the same status.
Your delivery calendar should distinguish public holidays from personal vacation and team shutdowns. Otherwise, a manager may think someone is available because the national calendar is clear while their approved leave says otherwise.
Before committing to a release, confirm:
- Who is available to deploy and who can approve the release.
- Whether the reviewer and the person doing the work share a working day.
- Who covers an incident if the primary owner is away.
- How holiday work must be approved and paid.
Keep the calendar visible to the US manager and the Brazil-based hire. Add leave as it is approved. A calendar that only payroll can see will not help an engineering lead plan a handoff.
For support roles, agree on coverage before the holiday arrives. Ask whether the work can wait, another teammate can cover it or a separately agreed shift is needed. Do not turn a scheduled day off into an informal expectation to monitor chat.
Use the same process when the US team is away. If the Brazilian employee will work that day, prepare tasks that do not depend on an absent approver. Leave clear instructions for urgent decisions.
A holiday handoff should say what is ready, what is blocked and who can decide what happens next. Link the relevant ticket or runbook. If the usual owner will be offline, confirm that the backup has the access needed to act. Naming a backup without checking access can leave the same gap in coverage.
Review upcoming absences during planning, before assigning work with fixed deadlines. A task can fit within a sprint and still miss its review window. Check the availability of everyone needed to finish it, not only the person writing the code.
What do hires earn across Brazil and Latin America?
Ask for compensation and employer cost as separate amounts. A candidate's salary, total compensation and a provider's monthly invoice measure different things.
Brazil's currency is the Brazilian real, BRL. State the currency on every quote and agree who bears exchange-rate changes. If the invoice is in US dollars, ask how the local pay obligation affects price reviews. ISO 4217 currency list
For a LatAm rate-card comparison, use the same role and seniority definition across countries. The table below covers gross monthly base-pay ranges. Ask the provider for a current range, its currency and the evidence behind it.
| Country | Junior monthly base-pay range | Mid-level monthly base-pay range | Senior monthly base-pay range |
|---|---|---|---|
| Brazil | Not published | Not published | Not published |
| Mexico | Not published | Not published | Not published |
| Colombia | Not published | Not published | Not published |
| Argentina | Not published | Not published | Not published |
| Costa Rica | Not published | Not published | Not published |
Salary benchmarks to check: Levels.fyi Brazil, Levels.fyi Mexico and Stack Overflow Developer Survey 2025.
Levels.fyi describes total compensation as base salary plus stock and bonus. Keep that definition attached to any figure you use. A total-compensation figure cannot be compared directly with a base-pay quote.
When reviewing Stack Overflow salary data, check the country and role filter before using a result. A global figure does not establish a Brazilian pay band. Ask for the sample, collection period and pay definition behind any country estimate.
The Opus salary guide also distinguishes local salary from all-in service cost. Opus salary figures: Not published.
Build the buying comparison from written quotes for the same job. Give each provider the required working hours, technical scope and expected ownership. Ask for gross employee pay, employer obligations and service charges to be identified, even if the invoice combines them.
Then test the quote against a full year. Ask how it treats statutory payments, leave and equipment. Confirm whether the quoted amount includes every recurring charge and which events can trigger an additional invoice.
Give finance a separate place to record one-time costs and conditional charges. Equipment shipped at the start should not disappear into a salary comparison. An exit cost should not be mistaken for a recurring monthly charge. Keep the assumptions beside the totals so another buyer can reproduce the comparison.
Avoid making a savings claim from mismatched numbers. Comparing a US employee's full employer cost with a Brazilian candidate's base salary will overstate the difference. Use the same cost categories and a stated exchange-rate assumption on both sides.
If a quote exceeds the budget, change a real requirement. You might narrow the scope or choose a role with less ownership. Do not keep senior responsibilities while quietly relabeling the job as mid-level.
Keep candidate expectations in the comparison. A country average cannot tell you whether the people who pass your interview will accept the offer. Ask the provider to explain how the proposed range relates to the candidates it can present.
Before approval, ask how long the quote remains valid and what happens if the search takes longer. Confirm how pay reviews work after the hire starts. A budget that covers the opening invoice still needs a clear process for later changes.
Why should a US company hire in Brazil?
Brazil is worth considering when the candidate fits the work and the daily schedule supports your team. The São Paulo overlap shown above gives US teams a concrete starting point for planning live reviews and decisions.
The value of shared hours depends on how you use them. If a developer needs feedback before finishing a change, make sure the reviewer is available. If the job is mostly independent, protect focus time and require a clear written handoff.
Choose the hiring model around the responsibility you want to keep. For an individual joining your team, name the manager and decide who sets priorities. For an outsourced project, define deliverables and acceptance terms. Ask each provider to state which responsibilities it takes.
An EOR arrangement needs a clear answer about who finds and assesses the candidate. A recruiting arrangement needs a clear answer about who becomes the employer. Do not assume that candidate sourcing, payroll and delivery management are included together.
For Opus, the client chooses the finalist and manages day-to-day work. Build your internal process around that responsibility. The hiring manager still needs time to interview, make the decision and guide the person after they start.
Before selecting a provider, request a sample candidate profile for the role. Ask what evidence supports each skill claim. A useful profile should help you decide what to test next rather than simply repeat the job description.
Keep the decision meeting focused on the scorecard. Review whether the candidate can own the required work, communicate with the team and keep the agreed schedule. Record unresolved concerns and decide which need another interview.
Separate accepting an offer from being ready to work. Confirm the start date, equipment and access before scheduling the first delivery commitment. Assign someone to resolve onboarding issues so the hire does not spend the opening days waiting for permissions.
Prepare a small first assignment with a clear reviewer. Give the hire enough context to understand why the task matters and how completion will be judged. Use that work to check the review process as well as the person's skills.
Make the first feedback conversation specific. Discuss whether the assignment was clear, whether questions received timely answers and whether the agreed hours worked in practice. If a review sat unanswered, fix the ownership of that review before treating the delay as a performance issue.
A Brazil search should end with a named person, an agreed schedule and written employment terms. Send the provider a role description that makes those decisions possible: what the hire will own, who will manage them and which US hours they must share.
<!-- Not saved to disk: the workspace is read-only. Contract-specific costs and holiday treatment require employer confirmation. -->
Questions & answers
When does a nearshore brazil hire make sense for a US team?
Brazil is worth considering when the candidate meets your role requirements and the agreed schedule covers your team's live work. Check the person's city, English and employment terms before choosing a finalist.
How much overlap does São Paulo have with US Eastern time?
With both teams using 09:00–18:00 local windows, São Paulo shares seven clock hours with Eastern during US standard time and eight during US daylight time, before breaks.
Can a Brazil-based engineer work with a Pacific team?
Yes, if the shared hours cover the work. São Paulo and Pacific teams using 09:00–18:00 local windows share four clock hours during US standard time and five during daylight time, before breaks.
Does Brazil change its clocks for daylight saving time?
Brazil no longer observes daylight saving time. São Paulo stays at UTC−3, while US clock changes shift the overlap. Confirm the candidate's city because Brazil has multiple time zones.
Which roles should we assess for a Brazilian software team?
Start with the work you need done: application development, backend services, infrastructure or data systems. Ask for candidates with relevant production experience, then test the tasks the hire will own.
Should we assume a Brazilian developer speaks English?
No. Portuguese is Brazil's official language. Assess English through a technical discussion and a written handoff that reflect the actual job.
What is Brazil's 13th salary?
The 13th salary, or Gratificação de Natal, is a statutory employment payment. Article 1 of Lei 4.090 sets accrual at one-twelfth of December remuneration per month of service.
Does a monthly salary quote include FGTS?
Ask for an itemized employer-cost quote. Article 15 of Lei 8.036 requires an employer FGTS deposit, generally 8% of covered remuneration, and includes the 13th salary in its calculation base.
How should we compare Brazil with other Latin American hiring options?
Use the same role scope, skill assessment and required US working hours in every country. Compare employee pay separately from payroll costs and provider fees, then assess the candidates against the same scorecard.
Which Brazilian holidays should a US delivery manager use?
Use the employee's applicable calendar, including relevant local holidays and agreed leave. Have the employer confirm it before setting release dates or assigning holiday coverage.
Sources for this entry
- IANA Time Zone Database: South America
- IANA Time Zone Database: North America
- Brazil: Lei 4.090, 13th salary
- Brazil: Lei 8.036, FGTS
- Brazil: Lei 12.506, notice
- SIX: ISO 4217 currency codes
- Levels.fyi: Brazil software engineer compensation
- Levels.fyi: Mexico software engineer compensation
- Stack Overflow Developer Survey 2025: work
- Opus: LatAm holiday planner
- Opus: 2026 LATAM software developer salary guide
Figures about Opus are company-reported and attributed to Opus. Other figures link to their source.
Continue reading
Cite this entry
Best Nearshore. “nearshore brazil: what US teams need to know.” Opus Research. Last updated . https://bestnearshore.com/brazil/
- Featured provider
- Opus (disclosed owner of this site)
- Official page
- hireopus.com ↗
- Author
- Opus Research (Opus)
Reviewed by the Opus Research editorial desk ·