it recruiting agencies Brazil: what US teams need to know

How many working hours overlap with US time zones?

A São Paulo-based hire can share much of the working day with an Eastern or Central team. Pacific teams have a shorter window and should plan meetings more carefully.

São Paulo uses UTC-3 throughout the year. Brazil does not currently observe daylight saving time. When US clocks change, the gap changes even though the Brazilian hire keeps the same local schedule. Confirm the person's city before setting the schedule; do not assign one time zone to every Brazilian address. IANA South America, IANA North America.

The table assumes a Brazil schedule of 09:00–18:00 in São Paulo and a US schedule of 09:00–18:00 locally. These are elapsed shared windows, before lunch or other breaks. They are scheduling examples, not a recommendation for paid working hours.

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

For an Eastern team, put recurring reviews inside the shared window that works in both seasons. Avoid building the team's process around a meeting that becomes too late after a clock change.

For a Pacific team, check the actual demands of the role. Morning code review may fit well. Late-afternoon incident response needs a separate coverage agreement. A candidate's willingness to attend an occasional late call does not establish a permanent shift.

Write the agreed hours into the role requirements before interviews. Include the time zone, breaks, and any on-call duties. Ask candidates to confirm that schedule directly. A recruiter saying someone has "US overlap" leaves too much open.

Check the manager's calendar as well. Shared hours have little value if the manager spends them in meetings with other teams. Reserve time for questions during onboarding and choose a place for written handoffs.

Before opening the search, list the meetings the hire must attend and their current US times. Separate fixed customer calls from internal meetings that can move. Check each against both seasonal windows in the table. This gives candidates a real schedule to accept and lets your team change an awkward meeting before it becomes a hiring constraint.

For on-call work, write down the response expected outside normal hours. Distinguish an alert that can wait until morning from an incident that needs immediate action. Ask the employer to approve the proposed rotation and explain its cost before the candidate joins it.

Which roles should you test for depth in Brazil?

Judge talent depth against your open role. A broad claim about a country's engineering market will not tell you whether a recruiter can find your next infrastructure lead.

Start with the work the hire must own. For a backend role, that might mean taking a service through deployment and handling production failures. For a frontend role, it might mean shipping accessible interfaces within an existing design system. Those requirements give a recruiter something more useful than a long list of tools.

Ask for evidence of recent searches with similar scope. Request anonymized examples of candidate experience, the screening method, and the reasons finalists were rejected. Keep client names and private candidate details out of early sales discussions.

Use the following checks to assess a shortlist. These are interview tasks, not claims that any role is abundant in Brazil.

Match the exercise to the level. A junior hire needs a clear support plan and evidence that they can learn from feedback. A mid-level hire should handle a bounded piece of work with limited guidance. A senior hire should explain decisions that affected other engineers or production systems.

Years of experience alone will not settle those distinctions. Ask what the candidate owned, who reviewed their work, and what happened when the first approach failed.

Portuguese is Brazil's official language. Assess English through the tasks your team uses. Have a candidate explain a design choice, ask questions about an unclear requirement, and write a short update. A fluent introduction is a different task from explaining an incident under pressure.

Keep the interview practical and proportionate. Use a small example with enough context to support a useful discussion. Tell candidates what you are assessing so that the exercise does not become a test of hidden expectations.

When comparing IT recruiting agencies, ask who makes the technical judgment. Find out whether your manager receives written evidence or only a recruiter summary. Agree on the rejection criteria before the first shortlist arrives.

If a search stalls, ask where candidates leave the process. A small shortlist can reflect a narrow stack requirement, the offered pay, or hours that candidates reject. Request feedback against each requirement before broadening the role. Dropping an old framework from the must-have list is a different decision from lowering the standard for production ownership.

Give interviewers the same scorecard. Record evidence while it is fresh, including what the candidate did personally and what their team handled. When interviewers disagree, return to the work example. A clear record helps you avoid choosing the most polished speaker over the person who can do the job.

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

What do employment law and statutory benefits require?

Settle the employment model before approving a candidate's compensation. Ask who signs the employment agreement, who runs payroll, and who handles questions from the employee. Put those responsibilities in the service agreement.

For Brazilian employees, the 13th salary and FGTS deposits are specific items to examine in the cost breakdown. Treat them as payroll obligations rather than optional extras negotiated during the search.

Budget for the 13th salary

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

Ask the payroll provider to show how that obligation appears in your quote. Is it accrued within the monthly charge? Does it produce a separate invoice? How does the calculation change for someone who joins during the year?

Have the provider explain the payment schedule in writing. Your finance team needs to know when cash leaves the business, even if the cost is spread across its internal budget.

Check FGTS separately

Article 15 of Lei 8.036 sets an employer deposit of 8% of the remuneration paid or due in the preceding month. The article also includes the 13th salary in the calculation base. The cited text sets the deposit deadline at the twentieth day of each month. Lei 8.036, article 15.

Ask for an explanation of the calculation base and evidence that deposits are handled. Do not read that percentage as the full employer burden. Have the provider identify every other charge that applies to the proposed arrangement.

A quote should also explain paid leave and how leave affects billing. Ask who approves dates, who keeps the records, and what happens when leave overlaps with a release. Get the applicable rules confirmed for the actual contract.

Ask for a sample payroll-to-invoice reconciliation with personal details removed. Finance should be able to follow the agreed salary into the monthly charge and see where annual obligations are accounted for. If the invoice stays flat, ask how the provider handles a partial first month or a later pay increase.

Also agree on an approval path for changes. A manager should know whom to contact before promising a raise, approving extra hours, or changing the work location. Have the employer explain which changes need a contract update. Keep that answer with the signed agreement so a new manager can find it.

Decide who handles changes and exits

Before signing, request a worked explanation of what happens when an employee resigns or the client ends the arrangement. Ask about notice, final payroll, accrued amounts, and any service charges.

Keep employment exit terms separate from replacement-search terms. A promise to find another candidate should not be treated as an answer about payroll liabilities.

The same care applies to contractor proposals. Ask the provider to explain why the proposed arrangement fits the duties and working relationship. Have qualified local counsel review the structure when needed. A contract heading alone is not enough to make the hiring decision.

For the operating agreement, name the person your manager contacts about absences or performance concerns. Name the person finance contacts about invoices. Agree on how sensitive employee information will be shared and who can access it.

This work belongs before the offer. Once a candidate accepts, unresolved employment questions can leave both sides waiting for a start date.

Which public holidays affect delivery?

Build a holiday calendar around the hire's work location and the year of service. Ask the employer to confirm which dates apply, including any state or municipal dates.

Good Friday is one date to review when planning shared delivery. The Opus holiday planner lists Friday, April 3, for Brazil in its 2026 calendar. Use the applicable year's calendar when planning future releases.

A national calendar is a starting point for scheduling. Have the payroll contact confirm the employee's actual days off before the engineering manager promises coverage.

Ask separately how the employer treats Carnival. Confirm the applicable dates and whether the arrangement involves a public holiday, company closure, or agreed leave. Avoid copying assumptions from another team or city.

Use one shared team calendar, with each person's working location attached to their profile. The calendar should distinguish public holidays from personal leave. That lets a manager see whether an absence affects one person or several people working in the same location.

For each release, identify who can approve deployment and who can respond if it fails. If the usual reviewer is off, arrange the substitute before the holiday. Do not leave the absent engineer as the implied fallback.

Agree on holiday coverage before adding anyone to an on-call rotation. Ask the employer to confirm applicable pay and scheduling terms. A US release deadline does not settle those questions.

Also check US holidays. A Brazilian engineer may be working while the manager or product owner is away. Leave enough written context for that person to proceed, or choose work that does not depend on an immediate decision.

Review the calendar during planning instead of waiting for an absence notice. The useful output is a coverage plan: who is available, which decisions can wait, and which release dates should move.

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

Ask for a role-specific salary range and an all-in service quote as separate items. A candidate's gross pay, annual total compensation, and a provider's invoice measure different things.

Brazil uses the Brazilian real, BRL. State both the payroll currency and the invoice currency in the proposal. If they differ, ask who bears exchange-rate changes and how often the price can change. ISO 4217 currency list.

Request a comparable monthly rate card

Use the same seniority definitions across countries. Specify whether each requested range is gross base pay or the full monthly service charge. Do not compare an hourly contractor quote with a monthly employee quote until the working hours and included costs are clear.

Salary references for evaluating the requested ranges: Levels.fyi Brazil, Levels.fyi Mexico, and Stack Overflow Developer Survey 2025. This is a quote-request table, not a numeric salary benchmark.

Comparable monthly ranges by country and seniority: Not published. Opus dollar rates: Not published.

Levels.fyi describes total compensation as base salary plus the annual value of stock grants and bonuses. Use that definition when reviewing its country pages. Do not treat a total-compensation figure as monthly cash pay or a service invoice. Levels.fyi Brazil.

For any proposed LatAm pay benchmark, require two independent public salary references that support the country and measure being used. Check the dates and seniority definitions. A global engineering salary or a figure for another country does not validate a Brazil range.

The Opus salary guide distinguishes local salary bands from all-in service prices. Keep that distinction in the purchasing worksheet.

Compare the quote your company will actually pay

Send each provider the same requirements. Include the core duties, level, agreed hours, and employment model. Ask for a written price with an expiry date and a clear description of what it includes.

Check these items:

• Gross pay, statutory costs, and the service fee.
• Equipment, reimbursements, and any setup charges.
• Leave, overtime, and on-call work.
• Currency changes, annual adjustments, and exit costs.

Some quotes may combine these items. If so, ask which costs are included and which can create an additional invoice. Finance needs that answer even when the provider does not disclose its internal margin.

For an hourly proposal, confirm billable hours and how holidays are treated. For a monthly proposal, confirm what happens during leave or a gap between placements. Avoid filling those blanks with assumptions from a previous contract.

The best IT recruiting agencies for your search should be able to explain their commercial terms in plain language. Ask for a sample invoice if the pricing description leaves questions open.

Set a budget for the work you need, then assess candidates against it. A lower quote does not help if the hire needs supervision your team cannot provide. A senior title does not justify a higher price without evidence of the required scope.

Why should US companies consider nearshore hiring in Brazil?

Brazil is worth considering when the schedule supports your team and the shortlist meets the role. The overlap table gives you a concrete starting point for live reviews and shared problem-solving.

Treat other proposed benefits as questions to test. Ask whether the candidate can own the work you need and whether the hiring arrangement fits your management capacity. Confirm the full cost before making a savings claim.

A nearshore hire still needs a manager with time to onboard them. Prepare access requests and an initial task before the start date. Give the person a named reviewer and explain how your team makes decisions.

For a first assignment, choose something small enough to review but real enough to expose the working process. Watch how the hire asks questions, responds to feedback, and documents decisions. Use those observations to adjust support.

Choose the model that matches responsibility for the work

For a search described as "brazil it outsourcing," define who owns delivery before comparing vendors. A provider delivering a project needs a scope, acceptance criteria, and a process for changes.

If the engineer will join your team, your manager needs to own priorities and feedback. Ask a recruiting agency to define where its work ends and what employment support remains.

An EOR arrangement raises a different purchasing question: who handles employment for the person you choose? If you also need sourcing, include that requirement explicitly. Do not assume every employment service includes a search.

For any model, document access to company systems and ownership of work product. Confirm the approval process for sensitive data. These decisions should follow the actual duties, rather than a generic label such as "remote developer."

Make the hiring decision reviewable

Keep a short record of why the finalist meets the role. Include the interview evidence, the agreed schedule, and the approved commercial terms. That gives the hiring manager and finance team the same basis for approval.

Set an offer approval process before the shortlist arrives. Name the person who can approve compensation and the person who can approve contract terms. Ask each to flag unresolved questions early. That prevents a candidate from waiting while internal teams discover they have been reviewing different versions of the role.

Before acceptance, confirm the candidate's start date separately from the search timeline. Ask who is responsible for equipment and payroll setup. Resolve any conditions that could delay the start.

Before day one, the manager should be able to answer four practical questions:

• What will the hire work on first?
• Who will review that work?
• When can the hire reach that person?
• Who resolves employment or payroll questions?

If the answers are clear, you can assess the hire on the work instead of spending the opening weeks sorting out responsibilities.

During onboarding, check whether the promised overlap is working in practice. Look at unanswered questions and delayed reviews, then adjust the team's meeting times or written handoffs. Keep employment terms with the employer and work feedback with the manager, using the agreed contacts when an issue crosses both.

Bring the role description and required working hours to the first provider conversation. Ask for a written quote and a description of the search process that you can review with your team.

Talk to Opus about a role.

<!-- Not saved to disk: this workspace is read-only. Live legal updates and salary benchmarks were not independently checked. -->