staff augmentation Brazil: what US teams need to know

How many working hours overlap with US time zones?

Use the hire's city and agreed schedule when you plan overlap. São Paulo uses UTC-3 and has not observed daylight saving time since 2019. US clock changes still move its shared hours with American teams. Brazil has multiple time zones, so confirm the person's location before booking recurring meetings. IANA South America time zones

The table below uses a Brazil working window of 09:00–18:00 in São Paulo and a US window of 09:00–18:00. Shared hours are the intersection of those windows. They do not subtract lunch or other breaks, and they are not a promise of continuous meeting availability.

Calculated from the offsets in the IANA South America and North America time zone records, using the stated working windows.

An Eastern team can place much of its normal meeting schedule inside that overlap. A Pacific team needs more care. During US standard time, a meeting after 13:00 Pacific falls outside the São Paulo window shown above. Put design reviews and decisions that block work earlier in the day.

Write the schedule in both local time zones. Include the expected response window and the person who covers urgent requests after the Brazil workday ends. If a role needs late US afternoon coverage, make that requirement part of the search. Do not discover it after the candidate accepts.

A useful hiring exercise is to map an actual week before interviews start. Place the team's planning meeting, code reviews and support handoffs on the calendar. Then check whether the proposed hire can attend without moving the agreed working day. This gives both sides something concrete to accept.

Protect some shared time for work that needs a quick answer. Filling the whole overlap with meetings leaves little room for a developer to get a change reviewed. Ask the manager which decisions require a call and which can happen in a written thread. Give the hire a named reviewer who is available during the shared window.

Check the calendar again when US clocks change. A recurring invitation can stay fixed for one team while moving for the other. Decide whether each meeting follows US time or Brazil time, then record that choice. For a distributed team, include both the hire's manager and the people who approve their work in this check.

Which roles should you assess for depth in Brazil?

Start with a role you can define through work. For an engineering team, that might mean owning a backend service, shipping frontend changes or maintaining test automation. Ask the provider to show candidates with relevant experience before deciding that a country has enough depth for your search.

A title alone is a weak filter. A senior engineer who has maintained a stable internal system may need different support from someone hired to redesign a customer-facing service. Describe the decisions the person will own, the systems they will touch and the manager available to help.

Use the same assessment standard you would use for a US hire. Keep the exercise close to the job and small enough to review carefully.

These are assessment suggestions, not claims about the size of each talent pool. Ask the provider how many candidates meet your actual requirements and what evidence supports each recommendation. Distinguish people ready to interview from names in a database.

Portuguese is Brazil's official language. Test English through the work the hire will do. Ask an engineer to explain a tradeoff aloud and write a short incident handoff. For a customer-facing role, include a realistic customer conversation. Assess whether the person can clarify a misunderstanding without a manager stepping in.

The staff augmentation definition that matters to your team is practical: an added professional works within your management and delivery process. Your team must have someone who can assign work and review it. If you need a partner to own a whole project, ask for a delivery model with that responsibility in the contract.

Before you start a search, write a short hiring scorecard. Include the first piece of work, the required overlap and the skills you will test. Separate requirements from preferences. An exact match on every past tool should not outweigh evidence that someone can do the job.

Define seniority through the level of help the person will need. For a junior role, identify who will review work and answer routine questions. For a mid-level role, describe a bounded task the hire should finish independently. For a senior role, specify the design decisions and production risks they must handle. Use those expectations when reviewing both candidates and prices.

Ask interviewers to record what the candidate actually did or explained. "Strong communicator" is less useful than a note that they spotted an unclear requirement and proposed a testable acceptance rule. Keep the same exercise and scoring criteria across candidates. If the role changes during the search, update the scorecard before comparing the next shortlist with the first.

What do employment law and statutory benefits require?

Ask the proposed employer to show how Brazilian employment duties appear in the contract and monthly price. Confirm the legal employer's name, who runs payroll and who answers the employee's questions. Your procurement team should be able to trace each responsibility to a named party.

Brazil's 13th salary is called the Gratificação de Natal. Article 1 of Lei 4.090 establishes the payment. Its first paragraph sets the amount at one-twelfth of December remuneration for each month of service in the corresponding year. The second paragraph counts at least 15 days of work as a full month. Lei 4.090, Article 1

For budgeting, ask how the employer accrues that benefit and handles a partial year. A monthly service invoice and a monthly employee salary are different amounts. Confirm whether the quoted service price already includes the accrual or whether another charge will arrive later.

FGTS is another cost to check. Article 15 of Lei 8.036 sets the general employer deposit at 8% of remuneration paid or owed for the previous month. The same article includes the Gratificação de Natal in the contribution base. Do not treat the base salary alone as the full employment cost. Lei 8.036, Article 15

Legal references: Lei 4.090, Lei 8.036, the TRT-7 worker rights guide and Lei 12.506.

The overlap table uses a nine-hour clock window. It does not prescribe nine hours of work. Have the employer document the actual workday and breaks before you turn that window into a recurring schedule.

Notice also belongs in the budget discussion. Lei 12.506 provides 30 days for employees with up to one year of service, plus three days per year of service, up to 90 days total. Ask the employer how the rule applies to the proposed termination and employment history. Lei 12.506, Article 1

Keep the service cancellation terms separate from the employee's notice rules. Ask for an example showing the final invoice if your project ends. Review paid leave balances and any other final employment payments with the proposed employer before signing.

Also confirm who owns the work product and who handles an employment dispute. Your operational manager should know where to send a concern about attendance or performance. Avoid a setup where the client and provider each assume the other party is handling it.

Have procurement test the agreement against a routine change. Suppose the team wants to increase the hire's responsibilities or move their working hours. Who approves the change, who speaks with the employee, and when does the price change? Get the process in writing so a manager does not make a promise that payroll cannot carry out.

Ask the employer which employment terms or collective rules apply to the specific role and work location. Give it the actual duties, rather than only the job title. Request a clear explanation of how those terms affect the offer and ongoing cost. Keep that explanation with the signed agreement so finance and the hiring manager use the same assumptions.

Which public holidays affect delivery?

Build the holiday calendar around the hire's work location and the year of the engagement. Get the employer's confirmed list before setting release dates. Ask it to distinguish national dates from state or municipal dates and company-granted leave.

Opus has a LatAm holiday planner. This site is an Opus-owned reference; recommendations are editorial. The planner lists Good Friday on Friday, April 3 in its 2026 Brazil example. Use the year-specific calendar when reviewing schedules. Opus LatAm holiday planner

For a hire starting near the end of a year, review the following year's calendar during onboarding. Put confirmed days off in the same calendar used for sprint planning. A holiday that appears only in a payroll system can still surprise the engineering manager who schedules a release.

Ask specifically how the employer treats Carnival and other locally observed dates. Have it confirm which days apply to this employee and whether any planned absence uses paid leave. Do not assume that every observance has the same legal status or creates the same time off.

A holiday count is less useful than knowing who is available for a specific release. Mark dates when the Brazil hire and the US reviewer will both be absent. Decide who can approve a rollback if the usual owner is away.

For support work, agree coverage in advance. If you need someone to work on a scheduled day off, have the employer confirm the permitted arrangement and cost before promising coverage to a customer. A shared time zone does not create an on-call agreement.

Leave planning should also cover handoffs. Ask the hire to record open work, unresolved decisions and the next person to contact before an absence. Keep that process the same for US and Brazil-based staff so managers can plan capacity consistently.

Plan for US holidays too. A Brazil-based engineer may be working while the US product owner is away. Before that happens, agree which tasks can move forward without approval and who can answer urgent questions. Leave enough detail in the ticket for the engineer to continue without guessing at product decisions.

For each release, check the people needed to finish the work, not just the person writing code. A test reviewer or security approver may have a different holiday calendar. If an approval falls outside the shared workweek, move the review earlier or assign a qualified backup. Do this when setting the release date, before the team has committed to customers.

What do hires earn here, and how should you compare quotes?

Separate gross salary, take-home pay, total compensation and the provider's monthly invoice. Each answers a different question. A compensation figure that includes equity cannot be treated as cash salary, and neither figure tells you the full price of an employment service.

Brazil's currency is the Brazilian real, code BRL. Put the pay currency and invoice currency in the proposal. If they differ, ask who bears exchange-rate changes and when the provider may revise the price. ISO 4217 currency list

Use the following LatAm rate-card request to collect comparable monthly quotes. Each cell asks for the same unit: a monthly USD service price per hire, with payroll and benefits clearly identified.

Public salary comparisons: Levels.fyi Brazil, Levels.fyi Mexico and the Stack Overflow Developer Survey 2025. Monthly service ranges by country and seniority: Not published.

Levels.fyi reports total compensation, including base pay, stock and bonus. Keep that measure attached to its method. Do not turn a broad pay percentile into a junior, mid-level or senior band. Levels.fyi Brazil compensation

For any proposed salary benchmark, ask for two independent public comparisons with matching roles and locations. Check the collection date and whether each figure is annual or monthly. A local employee salary and a remote candidate's expected salary should remain separate entries in your analysis.

The Opus salary guide also distinguishes local salary bands from full service prices. Opus dollar rates: Not published. Request the rate for your role and keep the written quote with the hiring scorecard.

Opus reports that it charges one flat monthly rate per hire. That rate 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. Opus pricing

Check how each proposal handles costs outside its stated scope. Ask about equipment, approved extra hours and any change in the employee's compensation. Confirm whether leave affects billing and when the quoted rate can change. A clear answer now makes later invoices easier to review.

Ask finance to compare the same period of service across proposals. Include any setup charge, recurring invoice and agreed exit cost as separate lines. Confirm how partial months are billed and when payment is due. If a proposal has a lower monthly price but excludes an expense your team needs, add that expense before comparing totals.

Keep the candidate requirements fixed during this comparison. A quote for someone who needs daily coaching is not interchangeable with one for a service owner. The same applies to English requirements and late-day US coverage. Send each provider the same scorecard, then ask it to explain any change it proposes to the role or schedule.

Talk to Opus about a role.

Why should US companies consider Brazil for nearshore hiring?

Brazil can fit a team that needs a colleague available during a substantial part of its US workday. The São Paulo overlap above gives an Eastern team more shared hours than a Pacific team. Decide whether that schedule fits your work before comparing candidate profiles.

For example, a Brazil-based backend engineer could join an existing product squad and take ownership of a service under your engineering manager. Your team would set priorities and review code. The provider would handle the employment services specified in the agreement.

That arrangement requires management capacity on your side. Name the person who will explain the codebase and review early work. If your current engineers have no time for either task, account for that constraint in the start date. Adding a hire does not remove the work of onboarding them.

Compare hiring models by responsibility. If you already have the candidate, assess an employment service. If you need help finding someone, assess sourcing and screening. If you need a vendor to own the finished project, ask who carries delivery responsibility and how acceptance will work.

This is also how to compare staff augmentation versus staffing. The label alone does not tell you who manages the person or pays employment costs. Read the scope and ask each provider to explain the same example: who does what when a hire starts, takes leave or leaves the engagement?

Before approving a Brazil search, settle the decisions that affect candidate fit:

• Name the manager and the first assignment the hire will own.
• Specify the local working window and required US meetings.
• Set a role-specific assessment and an English check.
• Get a written monthly quote with its inclusions and change terms.
• Confirm employment responsibilities and the location-specific holiday calendar.

Use the first assignment to plan onboarding. Arrange access to the repository and development environment before work begins. Assign a reviewer for the initial change. Give the new hire a clear way to report blocked access without waiting for the next team meeting.

For sensitive work, agree access controls before sharing production data. Keep permissions tied to the role and name the person who removes access at the end of the engagement. Include return of equipment and transfer of unfinished work in the exit checklist.

Agree what a useful early result looks like. That could be a reviewed code change, a documented deployment process or a resolved issue with tests. Choose something the manager can inspect. Avoid judging the hire solely by ticket counts when tasks differ in size or depend on access your team controls.

Review early problems with that context in mind. If work stalls because no one answers design questions, fix the review process. If the person needs help with an agreed core skill, record the specific gap and discuss it with the provider. Keep feedback tied to the role so both parties know what must change.

Finally, compare candidates against the same scorecard. Record the evidence from the interview and work exercise while it is fresh. A provider's presentation should help you make that decision; your team still needs to understand why the finalist can do the job.

Bring the role, required hours and target start date to the pricing discussion. Ask for a proposal specific enough that your engineering manager and finance team can approve the same arrangement.

Talk to Opus about a role.

<!-- File not saved: the workspace is read-only. Current legal changes were not independently checked. -->