staff augmentation services Brazil: what US teams need to know

How many working hours overlap with US time zones?

A hire working São Paulo hours can join much of an Eastern team's day. A Pacific team needs to plan more carefully around its afternoon.

São Paulo uses UTC−3 year-round. Brazil ended daylight saving time in 2019, so the gap changes when US clocks change. Confirm the candidate's city before setting recurring meetings. Brazil has multiple time zones; São Paulo hours are a planning example, not a nationwide schedule. IANA South America time-zone data.

The table assumes the hire works 09:00–18:00 in São Paulo and US colleagues work 09:00–18:00 locally. Shared hours are elapsed clock hours before meal breaks or other time away. This is a scheduling comparison, not a statement of paid hours.

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

For an Eastern engineering team, put code reviews and planning inside the shared window. Leave work that needs fewer replies for the edges of the day. Avoid making the hire wait for a decision that routinely arrives after their workday ends.

For a Pacific team, look at the actual meeting calendar before opening the search. An afternoon design review may fall outside the proposed Brazilian schedule. Move the meeting or agree on a different work schedule before the candidate accepts.

Write required hours in named time zones. "US hours" leaves too much room for disagreement. Include how the schedule changes when US daylight saving time begins and ends.

Also separate daily overlap from on-call coverage. Joining stand-up does not establish an agreement to respond overnight. Ask who covers incidents outside the person's hours and how that duty is approved and paid.

A useful interview check is simple: show the candidate a normal week of meetings. Ask them to confirm the schedule they can sustain.

Then check the people the hire depends on. An engineer may overlap with their manager but miss the product owner who approves work. Put the necessary decision-makers into the same calendar view. Move a recurring review if it leaves the hire blocked until the following day.

Keep a written handoff for work that crosses the end of the shared window. It should say what changed, what needs a decision and who owns the next step. Agree on when replies are expected. A message sent after local working hours should not quietly become an extra shift.

Which roles should you test for depth in Brazil?

Test talent depth through a shortlist for your actual role. A provider's ability to find a general software developer says little about its ability to find your next database specialist.

Start with the work that is delayed. If your senior engineers spend their week fixing release scripts, describe that work in the search. If the backlog is mostly customer-facing product changes, ask for evidence of shipping and maintaining similar features.

Use the same evidence standard for every candidate.

These are hiring checks, not rankings of Brazil's talent supply. Ask how many candidates meet your required stack, work schedule and compensation plan before treating a search as ready.

Separate seniority from years worked. A senior hire may need to make design decisions, review other people's work and explain tradeoffs to product leaders. A mid-level hire may own a defined feature with support. A junior hire needs a named person with time to review their work.

That distinction changes the search. If nobody on your team can coach the person, a lower-priced junior shortlist may create more work for your existing engineers.

Portuguese is Brazil's official language. For a role inside a US team, assess English through the work itself. Ask the candidate to explain a technical decision, clarify an unclear request and write a short handoff. Do not confuse an accent with an inability to do the job.

An IT staff augmentation service should also understand your access needs. Tell the provider whether the role touches customer data or production systems. Decide which checks and approvals must happen before access is granted.

Give interviewers a shared scorecard. Record evidence for each requirement rather than a broad impression of whether someone "seems senior." This makes it easier to choose between candidates with different job titles and career paths.

Separate required experience from skills someone can learn

Keep the must-have list tied to work due soon after the hire starts. If a task requires deep knowledge of a particular database, explain why. If the team can teach an internal tool, avoid using that tool as an automatic rejection rule.

Ask candidates what they personally owned in a past project. Follow up on the decisions they made and what happened after release. A team achievement can be useful evidence, but it should not hide the person's actual contribution.

Use a bounded exercise based on the role. Remove customer data and avoid asking for unpaid production work. Tell the candidate what you will assess before they begin. A short review of a flawed design may reveal more about judgment than a long task with unclear scoring.

If the shortlist repeatedly misses the same requirement, review the search with the provider. Decide whether the issue is the role description, compensation or screening. Keep the requirement if the work demands it; change it only when your team can explain the tradeoff.

What do employment law and statutory benefits require?

Start by identifying the legal employer and the proposed employment arrangement. Ask who signs the local contract, runs payroll and handles employee questions.

For an employment arrangement, review the applicable terms against Brazil's Consolidação das Leis do Trabalho and the relevant benefit laws. Have the provider explain how those duties appear in the quote and contract.

Account for the 13th salary

Brazil's 13th salary is also called Gratificação de Natal. Article 1 of Lei 4.090 establishes the annual payment. Paragraph 1 sets the accrual at one-twelfth of December remuneration for each month of service. Paragraph 2 counts at least 15 days of work as a full month. Lei 4.090, Article 1.

Ask whether the monthly service price includes this obligation. Finance should know whether the provider spreads the cost across invoices or bills it separately. Confirm what happens when someone joins or leaves partway through the year.

Check the FGTS calculation

Article 15 of Lei 8.036 requires an employer deposit of 8% of the worker's applicable remuneration into an FGTS account. The article includes the Gratificação de Natal in the calculation base. Lei 8.036, Article 15.

Do not treat that percentage as the whole employer cost. Ask for the complete employment-cost calculation and the records used to confirm deposits.

Notice also needs a place in the budget. Lei 12.506 provides 30 days for employees with up to one year of service. It adds three days per year of service, up to a total of 90 days. Ask how the rule applies to the proposed hire and termination scenario. Lei 12.506, Article 1.

Get written answers on paid leave, applicable agreements and final payments. A monthly service cancellation clause should explain how it interacts with the person's employment.

Keep a responsibility list alongside the contract. Your manager should know where to send a leave request or payroll concern without interpreting legal terms during a busy week.

Resolve employment questions before the offer

Ask the provider to explain the proposed arrangement using the actual role and schedule. A contract label alone should not settle whether the arrangement suits the work. Have qualified Brazilian counsel review any classification questions before the person starts.

Check what happens if a manager asks for extra hours. Name the person who approves the request and how the employer records it. The hire should not have to choose between following the manager's instructions and following the agreed work schedule.

For work product, have counsel check the path of ownership from the individual through any contracting entity to your company. Confirm confidentiality terms and which systems the person may use. Keep the access approval process separate from the hiring decision so a signed offer does not grant automatic production access.

Before signing, request an exit walkthrough. Ask who gives notice, calculates final payments and retrieves equipment. Assign access removal to a specific internal owner. These steps should be clear while the relationship is working well.

Talk to Opus about a role. This site is an Opus-owned reference; recommendations are editorial.

Which public holidays affect delivery?

Use a Brazilian work calendar alongside your US calendar. Confirm the dates that apply to the hire's location and employment terms before committing to a release.

The LatAm holiday planner includes Brazil alongside US federal holidays. Its 2026 calendar includes Good Friday on April 3. Use the calendar for the year you are scheduling; do not carry movable dates into the following year.

Ask the employer to confirm national, state and municipal holidays. Ask separately how Carnival and optional closures are handled. A date appearing on a general calendar does not, by itself, settle the person's work obligations.

For each confirmed day off, decide whether work can pause or needs a backup owner. A product engineer's absence may be easy to plan around. A person who handles urgent customer issues may need a documented handoff.

Put holidays into the team's shared calendar when the hire starts. Include the person's planned leave through your usual approval process. Keep private reasons for leave out of calendars that the whole company can see.

Release planning should account for who can fix a problem after launch. Before a holiday, check that someone available has the access and context to roll back a change. Avoid making the absent hire the only person who knows the recovery steps.

Cross-border holidays can also affect decisions. If the Brazilian hire is working while the US product owner is away, leave clear acceptance criteria. Agree on which decisions can proceed and which should wait.

Confirm how holidays affect invoices. Ask whether the monthly price stays fixed, what happens if holiday work is required and who approves any extra cost. Put the answer in the commercial terms.

Review the next year's calendar before setting annual delivery targets. This is especially useful when several team members work in different countries. Count available people against the work planned for each week instead of assuming every location follows the US calendar.

For example, suppose a Brazilian engineer owns a release scheduled just before a confirmed local holiday. The release owner should decide whether to move the date or assign another engineer to support it. That backup needs the deployment notes and permission to make changes. A name on a rota is not enough.

Ask the hire to review the calendar with their manager during onboarding. Keep a clear route for corrections if their location or employment terms change. Recheck coverage when someone changes teams, since the new team may have different release days and support duties.

What do hires earn, and how should you compare LatAm rates?

Keep employee pay, total compensation and the monthly service invoice separate.

Brazil's currency is the Brazilian real, with the code BRL. Ask whether a quote is denominated in BRL or US dollars and who bears exchange-rate changes. ISO 4217 currency list.

A salary benchmark can help frame questions, but it does not establish the price of a placement. Levels.fyi reports total compensation, including base pay, stock and bonuses. Use its Brazil compensation page with that definition in mind.

Request a country-by-country rate card

Use the same role description and seniority expectations across countries. Ask providers to fill the monthly ranges below in one stated currency. Require them to label each range as employee pay or the full service price.

Benchmark context: Levels.fyi Brazil, Levels.fyi Mexico and Stack Overflow Developer Survey 2025. This table requests quotes; it does not present measured salary bands.

Opus salary figures: Not published. Opus dollar rates: Not published. Request a written quote for the role and location. The salary guide distinguishes salary benchmarks from all-in service prices.

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

For any provider, request the quote's effective date and validity period. Ask which events can change the invoice, including a salary review or a change in employment costs. Confirm whether equipment and extra-hours work are included.

Compare the same scope

A recruiting fee and an ongoing employment invoice buy different work. Before comparing totals, list who handles hiring and who handles employment after the candidate starts.

Then compare the proposed people. A senior engineer who can own the service may fit a different need from someone who requires daily design support. Price each against the work your team expects them to complete.

Do not convert a monthly quote into an hourly rate without defining the divisor. Holidays, paid leave and work schedules affect the result. Ask the provider for its billing basis if procurement requires an hourly comparison.

For budget approval, model the expected length of the engagement and the contract's exit terms. Include costs your company will still carry, such as equipment or manager time. Keep those assumptions visible so finance can change them without rebuilding the comparison.

Separate recurring charges from costs triggered by an event. A starting invoice, a normal working month and an exit invoice may need different budget lines. Ask the provider to show how each would be calculated under the proposed contract. Do not assume that a flat monthly price answers every question about an early departure.

Check payment terms as well as the headline rate. Record the invoice currency, due date and any deposit. If a quote permits exchange-rate changes, ask which rate is used and when it resets. Finance should be able to reproduce the calculation without relying on a verbal explanation.

Finally, ask what happens when the role changes. If a developer takes on team leadership, confirm whether that triggers a new search, a pay review or a revised service rate.

Why should US companies consider Brazil for nearshore hiring?

Brazil is worth evaluating when your team needs daily contact with someone who will work inside its existing processes. The schedule can support live reviews and quick decisions, provided those activities fit the agreed hours.

Start with a specific staffing problem. Perhaps a back-end service has a clear owner but too much maintenance work. An added engineer could take a defined part of the backlog while your manager keeps responsibility for priorities and quality.

That is a practical staff augmentation example. The person joins your workflow, uses your review process and has a manager who can answer questions. Before hiring, make sure that manager has enough time to onboard them.

The managed service vs staff augmentation decision comes earlier than the country decision. If you want a provider to own a defined service, specify its output and service standards. If you want another person on your team, specify the role and who will direct the work.

Staff augmentation services also need a clear boundary around hiring support. A provider can help find a candidate, but your interview team still needs to decide whether that person can do your work. Keep the final assessment tied to the role's demands.

For a Brazil search, prepare a short hiring document that includes:

• The work the person will own and the manager they will report to.
• Required working hours in named time zones.
• Evidence you expect from interviews and work samples.
• The access and equipment needed before the first day.
• The budget basis and planned length of the engagement.

Share the same document with everyone involved in approval. A search can stall when engineering expects a senior owner while finance has approved a support role.

Plan onboarding before selecting the finalist. Name a person who will answer questions, prepare access requests and choose an initial task with a clear completion test. Give the hire enough context to understand why the task matters to customers.

Check progress through work you can inspect. Review the first handoff, code change or completed operational task. Address unclear expectations while the work is still small.

Make the first assignment ready before the hire starts

Choose work that lets the person learn your system without becoming its sole owner immediately. For an engineer, that could be a bounded bug fix with a documented review process. Make sure someone is available to explain the test setup and approve the change.

Give the hire a map of who makes decisions. Include the manager, the person who reviews work and the contact for employment questions. Tell them where to raise a blocker and when to escalate it. Avoid leaving those rules buried across old chat threads.

Agree on what successful progress looks like for the role. Use completed work and the quality of decisions, rather than online status alone. If progress stalls, check access, task clarity and review delays before assuming the hire lacks skill.

Keep the hiring decision separate from a broad claim about a country. A Brazilian candidate still needs to meet your role requirements, and your team still needs to support the work. Request the actual schedule and employment terms alongside the candidate assessment.

Before approving the offer, have the manager and finance owner review the same written proposal. Resolve any disagreement about scope or cost while the candidate can still receive a clear offer.

Talk to Opus about a role.

<!-- File not saved because the workspace is read-only. Live legal updates and individual provider quotes were not checked. -->