Hiring latin american engineers Brazil: what US teams need

How many working hours overlap with US time zones?

Use the engineer's city and your team's actual calendar to assess overlap. A country name alone does not settle meeting times.

São Paulo stays at UTC-3. Brazil ended daylight saving time in 2019. US Eastern, Central and Pacific change their offsets during daylight time, so shared hours change during the year. See the IANA South America rules and North America rules.

The table assumes a São Paulo schedule of 9:00–18:00 and a US schedule of 9:00–18:00 in each listed zone. Shared hours are clock windows before breaks. They are not a promise of continuous meeting availability or a statement of paid working time.

Calculated from the offsets in the IANA South America and North America time-zone records, using the schedules stated above.

For an Eastern team, this leaves room for morning planning and afternoon reviews. A Pacific team should put shared work earlier in its day. A late Pacific meeting can fall outside the engineer's agreed hours.

Before interviewing, list the meetings the person must attend. Include the weekly product review and any incident handoff. Check each meeting against both US seasons. A schedule that works when US clocks are forward may fail after they move back.

Also separate routine collaboration from support coverage. Being available for a stand-up does not mean someone has agreed to evening on-call work. Put support hours, escalation duties and backup coverage in writing.

Ask candidates whether the proposed schedule works for them over the long term. If a later local start is needed, discuss it before the offer. Have the employer confirm the permitted arrangement, including breaks and any overtime treatment.

Test the schedule against a real task before you approve it. For example, imagine a pull request needs a product decision before the engineer can finish. Identify who can answer during the shared window. If that person is usually in meetings, the nominal overlap will not solve the delay. Give the engineer another contact or move the decision earlier.

Use calendar invitations with named time zones, and review recurring meetings when US clocks change. Keep a short written handoff for work that crosses the end of someone's day. It should identify the blocker, the decision needed and the next person responsible. This gives the team a way to keep work moving without expecting replies after agreed hours.

Which roles should you test for depth in Brazil?

Treat talent depth as a question about your role. Ask the provider to demonstrate a pool of candidates who meet the same requirements. A broad claim about Brazilian engineering talent will not tell you whether a candidate can own your billing service.

For a full-stack hire, define the balance between interface work and backend ownership. A person who builds screens from clear designs faces a different job from someone who must also change data models. Describe which decisions the engineer will make without waiting for a lead.

For backend roles, ask about production systems with similar demands to yours. Have the candidate explain a failure, the evidence they used and the repair they shipped. A useful follow-up is what they changed to prevent the same failure.

For infrastructure work, name the expected responsibility. Maintaining deployment scripts differs from owning incident response. Ask who approves production changes and whether the hire will carry a pager.

Use the same job-relevant assessment across candidates:

Ask the provider which requirements narrow the pool and which are preferences. Keep the requirements tied to work the person will actually do. If your team can teach a framework, decide whether experience with that framework belongs in the rejection criteria.

For a senior hire, test judgment as well as code. Present a small design problem from your own environment, with confidential details removed. Ask what the candidate would clarify before making a change. Listen for how they handle incomplete requirements and whether they can explain the cost of their preferred approach. Avoid treating agreement with your current design as the correct answer.

Portuguese is Brazil's official language. Test the English needed for the job through normal engineering tasks. Ask candidates to explain a pull request or write a short incident update. A customer-facing engineer may need a different level of spoken fluency from an engineer working mostly through code reviews.

Searches for the best Latin American universities can help you explore education backgrounds. For a hiring decision, give more weight to demonstrated work. Do not reject a capable candidate because their school is unfamiliar to your interview panel.

Before sourcing starts, settle who will interview and who can approve an offer. Give reviewers the same scorecard. Otherwise, one interviewer may test coding speed while another expects system ownership, leaving the candidate to guess which job is open.

Ask reviewers to record evidence before discussing a candidate together. "Explained how to reverse a failed migration" is more useful than "seemed senior." Where reviewers disagree, identify the untested requirement and ask a focused follow-up. Repeating a broad interview adds time without necessarily resolving the question.

What do employment law and statutory benefits require?

Budget for the employment arrangement before comparing candidates. Ask who will employ the worker, which agreement applies and who handles payroll. Have the responsible employer explain how the proposed schedule and benefits fit the role.

Brazil's employment framework includes the Consolidação das Leis do Trabalho, or CLT. Some obligations discussed below sit in separate laws. Ask for the legal basis beside each line in the employer's cost breakdown.

Budget for the 13th salary

The statutory 13th salary is also called Gratificação de Natal. Lei 4.090, Article 1, provides for the payment independently of regular remuneration.

Article 1, paragraph 1, sets the accrual at one-twelfth of December remuneration for each month of service. Paragraph 2 counts a period of at least 15 days as a full month. These rules come from Lei 4.090.

Ask how the employer accrues this cost and how it appears on your invoice. Confirm the treatment of a midyear hire or a change in pay. A quote should make clear whether the monthly charge already includes the relevant accrual.

Do not treat this payment as a discretionary performance bonus. If you also plan a separate incentive, ask payroll how it should be documented and treated.

Include FGTS in the cost review

Lei 8.036, Article 15, requires an employer deposit equal to 8% of remuneration paid or owed in the previous month. The article also includes the statutory Christmas bonus in the calculation base. See the FGTS law.

Ask the employer to show the base used for the calculation. Confirm which amounts are included in the monthly service charge and how changes are handled. Do not assume that multiplying base pay by this percentage gives the total employment burden.

Ask about leave and the end of employment

Request a written explanation of paid leave, vacation pay and the rules that apply when employment ends. Ask the employer to identify the relevant provisions and any applicable collective agreement.

Brazil's notice law specifies 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. Have the employer explain how Lei 12.506 applies to the proposed arrangement.

For planning, ask for a worked exit-cost example based on the intended role and pay. Keep the example separate from a service cancellation clause. Ending a commercial agreement and ending a worker's employment require their own review.

Ask who handles routine changes after the person starts. A manager may approve a pay increase, a new schedule or a move between teams. Name the person who must review each change before it takes effect. Keep payroll instructions out of informal chat threads, and require written confirmation that the employer has processed them.

Give finance and the hiring manager the same cost breakdown. Finance needs to know when charges can change. The manager needs to know which decisions require employer approval. Resolve any difference between the sales proposal and the employment paperwork before setting a firm start date.

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. See Opus pricing.

Use the written quote to check how those terms apply to your hire. Ask about any cost your finance team cannot place in the budget.

Talk to Opus about a Brazil engineering role.

Which public holidays affect delivery?

Build the calendar around the employee's location and the applicable employment terms. A US holiday calendar alone will not tell your team when a Brazil-based colleague is off.

Good Friday appears for Brazil in the Opus LatAm holiday planner. Use the planner to start the discussion, then have the employer confirm the calendar that applies to the worker.

Ask specifically how Carnival is treated for that location and arrangement. Do not assume every day associated with the event is a nationwide statutory day off. Confirm any planned leave and the team's coverage before placing a release in that week.

Keep public holidays separate from annual leave. A holiday calendar cannot show when someone plans to take a longer break. Ask about known absences during the offer process, then use the same leave-planning process you apply to the rest of the team.

For each release, name the person who can approve a rollback. Check that the backup has access and understands the change. If the only engineer who knows a service is away, move the release or prepare another owner.

A shared calendar should show:

• The holidays confirmed by the employer for the worker's location.
• Approved leave and the dates when the engineer will return.
• US team absences that affect code review or product approval.
• The person covering any support duty during those dates.

Review both sides of a handoff. A Brazil-based engineer may finish work while the US reviewer is away. Agree whether the work should wait, go to a backup reviewer or move to another release. Do not leave that choice to whoever happens to answer a message.

December hiring needs the same check. Confirm who can issue equipment, grant access and review the first pull request. Also ask payroll how the start date affects the statutory bonus calculation.

If your team has a release freeze, explain it before the hire starts. Give the new engineer work they can complete during the freeze, such as a local setup check or a small reviewed change. Avoid leaving them dependent on an absent manager.

For November or December starts, review the first working weeks with the candidate and their manager. A signed offer does not ensure that an approver will be available. Move access requests and introductory meetings ahead of known absences. If a start date falls into a quiet week, agree on useful work and a reachable contact.

Review the calendar when a worker moves to another city. Ask the employer whether any local holiday or employment detail changes. Keep the approved schedule with the role's other working agreements.

What do hires earn, and how should you compare rate cards?

A search for "software engineer salary Brazil" can lead to several different measures. Gross base salary, total compensation and a provider's invoice answer different budget questions.

Brazil's currency is the Brazilian real, BRL, as listed in the ISO 4217 currency list. State the currency beside every quote. If your budget is in US dollars, agree on the exchange-rate rule and who bears changes.

Compare the same pay measure

Use this LatAm rate-card format when requesting quotes. Each cell refers to a gross monthly base-pay range for the stated level. Keep benefits and service charges outside these cells so the comparison stays consistent.

Pay-method references: Levels.fyi Brazil, Levels.fyi Mexico and Stack Overflow Developer Survey 2025.

Levels.fyi measures total compensation, including base salary, stock and bonus. That measure should not be entered as gross base pay. Likewise, a global survey result should not be labeled a Brazilian senior engineer rate.

The Opus salary guide distinguishes local salary from a fully loaded placement cost or hourly agency rate. Use that distinction when reviewing a proposal. Opus dollar rates: Not published.

Get a quote your finance team can use

Send each provider the same role scope. Include the expected level of ownership, agreed hours and any support duties. Ask for the quote date and how long the price remains valid.

Request separate figures for gross base pay and the full monthly invoice. Ask which benefits and employment costs are included. If a provider quotes only an all-in price, request a clear list of what it covers and what can change.

Define seniority through the work. A senior engineer expected to lead a migration has a different scope from someone implementing well-defined tickets. A cheaper quote can reflect a smaller role, so compare candidate expectations before comparing totals.

Review the annual budget as well as the first invoice. Ask how pay reviews, currency changes and statutory payments affect future charges. Confirm whether any equipment or exit costs sit outside the monthly rate.

You can use a simple internal comparison without inventing a market benchmark:

• Record the candidate's proposed gross pay and currency.
• Record the provider's full monthly price and exclusions.
• Add any separate costs confirmed in writing.
• Compare the resulting budget with the role's expected output.

Keep assumptions visible. If a cost depends on the start date or a contract term, have the responsible party calculate it. Do not turn an open question into a zero in the spreadsheet.

Ask for an example invoice for an ordinary month and an explanation of what could produce a different total. Check whether a pay increase changes only the salary component or other charges too. If the invoice currency differs from payroll currency, request the conversion date and rule. Your finance team should be able to reproduce the calculation without guessing.

Avoid comparing a candidate's take-home expectation with another candidate's gross salary. Ask the employer to put both proposals on the same basis. Keep the candidate's agreed pay separate from your internal budget ceiling so each approval refers to a clear amount.

Why should US companies consider nearshore hiring in Brazil?

Brazil is worth considering when the candidate and working schedule fit a specific team need. The São Paulo overlap windows above can support live code reviews, product discussions and incident handoffs during part of the US day.

That is useful when your team makes decisions through conversation. Put those decisions inside the shared window. Reserve the remaining hours for work the engineer can complete without waiting for someone in another time zone.

Start with the work that needs an owner. If a senior engineer is spending much of the week on routine implementation, define what a new hire could take over. If a service lacks clear ownership, decide the authority and support the incoming engineer will have.

Then compare hiring models. Ask a recruiting agency which search tasks it handles and who employs the successful candidate. For an EOR arrangement, confirm who supplies the candidate and who manages employment. Read those responsibilities in the contract.

With Opus, the client chooses the finalist and manages day-to-day work. Its stated monthly pricing scope includes pay, local payroll, benefits, labor compliance and placement support. Review the pricing terms against the work you expect each party to do.

Do not let the country decision replace an onboarding plan. Name a manager who can review early work. Prepare repository access and a development setup that someone has recently tested.

Give the engineer an initial task with a clear completion test. Explain who reviews it and where questions should go. The first task should reveal whether the person can work in your codebase without exposing production systems to unnecessary risk.

Agree on how you will judge progress after the person starts. Use work the engineer can control, such as completing a reviewed change or taking ownership of a documented service. Record dependencies on other teams so delayed access does not become a performance concern. Discuss problems with the engineer while the details are still clear.

If you want to hire Latin American talent across several countries, keep the scorecard consistent. Change the country-specific employment and calendar checks, then assess candidates against the same role outcomes.

Before approving the hire, confirm that the candidate can do the work, the schedule fits and the full cost is understood. Record the agreed start date separately from the offer date. Ask the employer to resolve any open payroll or contract questions before onboarding.

Bring the role scope, required overlap and budget currency to the first conversation.

Talk to Opus about a role.

<!-- Not saved to disk because this workspace is read-only. Live legal updates were not checked; confirm applicable terms with the employer before signing. -->