rlhf services Brazil: what US hiring 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 is UTC−3 and does not observe daylight saving time. Brazil ended DST in 2019. US clock changes still move the shared window. IANA time-zone data for South America records the Brazilian rules.

The table below assumes a Brazil-based hire works 09:00–18:00 in São Paulo and the US team works 09:00–17:00 locally. These are calendar windows before lunch or other breaks. They are not a promise of continuous paid work.

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

For an Eastern team, this can support a broad window for live review. A Pacific team should reserve its morning for questions that need both sides present. Under the standard-time example, a Pacific meeting after 13:00 falls outside the Brazilian hire's stated day.

Put recurring review sessions inside that shared window. Use them to discuss disputed rankings, revise instructions, and check whether reviewers interpret a rule the same way. Leave independent scoring and written handoffs for the remaining hours.

Ask candidates to confirm their actual location and availability. Do not apply the São Paulo schedule to every person in Brazil. Put both local schedules in the offer, including breaks and any agreed shifts.

For RLHF work, specify what needs a same-day answer. A reviewer should know whether to pause an unclear task or flag it and continue. Name the person who resolves the question. Shared hours help only when someone can make the decision.

Recheck recurring meetings when US clocks change. Keep a written handoff for unresolved items so the next person can resume work without reconstructing a chat thread.

Before approving the schedule, walk through a normal workday with the hiring manager. Identify when new tasks arrive and when the team needs finished ratings. If a batch arrives after the reviewer finishes, set the next working day's deadline explicitly. Do not leave the hire to infer an evening shift from a late message.

Choose a backup contact for questions that block work. Give that person access to the rubric and authority to resolve routine cases. A shared calendar cannot replace a manager who is available during the agreed window.

Which roles should you test for depth in Brazil?

Start with the work the person must judge. A candidate who can rank general prose may need a different test from someone reviewing code or mathematical reasoning. Define the output before choosing a job title.

Treat talent depth as something to test through the search. Ask for candidates who meet the actual task requirements, then compare their work against the same rubric. A broad claim about a country's technical workforce does not tell you who can review your model.

Use this role map to build interviews and paid samples. It is a hiring checklist, not a claim about the number of available specialists.

For a coding role, include a plausible answer with a subtle error. Ask the candidate to explain the problem and propose a test. Judge the reasoning as well as the final verdict.

For language work, separate Portuguese fluency from English communication. Test Portuguese on the material the person will review. Test English on a written explanation your US manager can use. Neither test needs to become a general language exam.

For subject experts, ask about the boundary of their knowledge. Give them a task that should be escalated. A useful reviewer must know when a confident answer exceeds the evidence.

Define seniority by ownership. A junior reviewer might follow settled instructions under close review. A mid-level hire might handle common disputes and suggest examples. A senior hire might own the rubric, train reviewers, and decide when a task needs expert review. Put those expectations in the role description.

Ask the candidate to revise an answer after feedback. That exercise shows how they interpret a changed rule and explain their new decision. Keep the task bounded, pay for it, and avoid using confidential production data.

Make the sample match the hiring decision

Write the scoring guide before candidates begin. State which errors would rule someone out and which skills you can teach after hiring. For a code reviewer, missing a security flaw may matter more than a slow written response. For an editor, changing the answer's meaning may matter more than a minor grammar error.

Have your own lead complete the exercise first. If the lead cannot explain the expected answer, revise the task before using it to reject candidates. Include room for a defensible alternative when the rubric permits one.

Keep each candidate's explanation alongside the score. During the final interview, return to a disputed item and ask what would change their decision. This gives your manager a concrete basis for choosing between candidates with similar resumes.

Opus is one option to discuss for the hire. This site is an Opus-owned reference; recommendations are editorial. Opus reports that every candidate passes an 8-layer vetting process. It also reports that every Opus placement completes a 6-module internal AI certification before day one. Opus's hiring process describes those steps.

Ask how the assessment applies to your specific task. Keep your own sample and acceptance rules in the selection process.

Talk to Opus about a role.

What do employment law and statutory benefits require?

Before accepting a quote, identify the legal employer and the proposed working arrangement. Ask who signs the employment documents, runs payroll, and handles benefits. Your daily manager should also know whom to contact when hours or duties change.

For the cost review, separate salary from employer obligations. The Brazilian 13th salary and FGTS deposits deserve explicit line items. Ask whether the quoted monthly charge includes their accrual and payment.

Budget for the 13th salary

Brazil's 13th salary is also called the Gratificação de Natal. Lei 4.090, article 1, establishes the annual salary bonus. Section 1 sets the calculation at one-twelfth of December remuneration for each month of service in that year. Section 2 counts a work period of at least 15 days as a full month. Lei 4.090, article 1.

Ask the employer how this calculation appears in the quote and payroll schedule. Confirm how the employer handles a midyear start and a later salary change. Finance should know whether the monthly invoice spreads the cost across the year or whether another payment is due.

Do not treat this bonus as a discretionary reward for performance. Keep any separate incentive plan distinct in the offer and cost sheet.

Include FGTS in the employer cost review

Lei 8.036, article 15, generally requires employers to deposit 8% of the prior month's paid or owed remuneration into the worker's linked FGTS account. The same article includes the Gratificação de Natal in the calculation base. Lei 8.036, article 15.

Ask the employer to confirm the applicable calculation for the proposed hire. Require a clear explanation of how deposits are funded and tracked. An invoice labeled "benefits included" should still give you enough detail to understand the cost.

These items do not make a complete employment budget. Ask for the applicable leave rules, working-hour limits, and termination costs. Have the employer identify any collective agreement that affects the role. Get those answers before approving a start date.

Put responsibility into the agreement

Use the contract review to answer practical questions:

• Who approves leave and records changes to the schedule?
• Who reviews requests for work beyond the agreed hours?
• Who handles payroll errors and employee questions?
• Who calculates costs when employment ends?
• Who owns equipment, accounts, and work product?

If you already have a candidate, an employer of record service may be a model to evaluate. If you need candidates as well, make the search responsibility explicit. Do not assume every employment service includes recruiting.

Ask the proposed employer to explain why the engagement structure fits the actual work. Describe how closely your manager will direct the person and whether you expect fixed hours. Give the employer the real operating plan before it prepares the agreement.

Plan for changes after the start date, too. A promotion, new shift, or extended absence should have a named contact and an approval process. Ask how each change affects payroll and the invoice. Keep written approvals with the employment records so finance and the daily manager work from the same terms.

Opus states: "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.

Ask for the proposed arrangement in writing. Your approval should cover the role, included costs, and responsibilities on both sides.

Which public holidays affect delivery?

Plan from the calendar for the hire's work location and the year of service. Ask the employer to confirm which dates apply to that person. Add approved leave and your US team's closures to the same schedule.

The LatAm holiday planner includes Brazil and lists Good Friday among its calendar entries. Use the calendar to begin the coverage discussion, then confirm the applicable dates with the employer.

A holiday count alone is a poor delivery plan. Look at what is due on each affected date. An independent review task may move earlier. A release decision may need someone else with access and authority to make the call.

For an RLHF team, review the work around each planned closure:

Keep the calendar visible to the people assigning tasks. A holiday should not first appear as a missed deadline in a status meeting.

Build a handoff that includes the current rubric, open questions, and any paused work. The backup reviewer should be able to see why an item was stopped. Avoid passing a queue of unexplained flags to someone who was not part of the original discussion.

Agree on how holiday coverage affects the bill. Ask whether the service pauses, another person covers the queue, or a separately approved arrangement applies. Keep those terms beside the delivery schedule.

Check the backup person's task knowledge before assigning coverage. Someone who can monitor a queue may still need help judging specialist answers. Give the backup a clear boundary: which items they can accept and which must wait for the regular reviewer.

When the team returns, review held items before adding a fresh batch. Record any decisions made during the closure and share them with the returning hire. Otherwise, the team may continue using different interpretations of the same rule.

What do hires earn here?

Published Brazil-specific RLHF monthly salary ranges by seniority: Not published. Request a quote for the actual role, required expertise, and working schedule.

Use the LatAm rate-card table below to structure that request. Ask each provider to use the same seniority definitions and price basis. Every monthly quote should state its currency and whether it means gross salary or the full service cost.

Compensation context: Levels.fyi Brazil, Levels.fyi Mexico, and the Stack Overflow Developer Survey 2025. The table requests role-specific quotes; it does not convert software-engineering survey results into RLHF rates.

Keep salary and service price separate

Levels.fyi describes total compensation as base salary plus the annual value of stock grants and bonuses. That measure differs from take-home pay and from a provider's invoice. Levels.fyi Brazil.

A useful quote states what the number buys. Ask whether it covers a dedicated person, a defined number of hours, or an accepted batch of work. For output-based pricing, define an accepted item and who pays for rework.

Brazil's currency is the Brazilian real, coded BRL. ISO 4217 currency list. If the invoice is in US dollars, ask who carries exchange-rate changes and when the price can change.

Keep the salary currency and invoice currency visible in the cost sheet. Do not compare one vendor's dollar invoice with another quote's local gross salary as though they cover the same costs.

The 2026 LATAM software developer salary guide makes the same distinction: "Do not treat a local salary band as an all-in service price."

Price the work you will actually manage

Ask for an itemized explanation of the full monthly charge. Include employment costs, equipment, and any platform license. Confirm whether a quality lead is included or must be hired separately.

For a specialist reviewer, define the subject depth before discussing price. For a coding evaluator, name the languages and the expected testing work. A broad "AI reviewer" label leaves too much room for different assumptions.

If a quote is based on hours, agree on how meetings and training count. If it is based on output, agree on how ambiguous tasks are handled. Reviewers should not have to guess whether escalating a problem will count against their accepted work.

Compare proposals using the same example workload. Send each provider the task description and an approved sample. Ask what work the quoted hire can complete independently and what your manager must review. Keep those answers beside the price.

Include your own review time in the buying decision. Ask the manager to estimate the attention each proposed arrangement needs, then revisit that estimate during onboarding. A quote that requires daily coaching should be evaluated against your team's available time.

Confirm when billing begins and what happens if access is delayed. Ask about invoice disputes, planned absences, and the notice required to change the engagement. Resolve these terms before treating the monthly number as an approved budget.

Opus dollar rates: Not published. Its pricing page states that the rate depends on role, seniority, and location. Request the rate for your role and compare it with quotes that cover the same responsibilities.

Why should US companies consider Brazil for a nearshore team?

Consider Brazil when the candidate's skills and agreed schedule fit the work. The São Paulo overlap table gives you a concrete starting point for live collaboration. A Portuguese evaluation task gives you a separate reason to assess local language judgment.

Make the decision at the role level. An Eastern-based quality lead may have a broad shared window with a São Paulo hire. A Pacific-based lead should plan around the shorter window. Both should test whether the candidate can explain disputed decisions clearly.

Choose who will own daily quality

When comparing RLHF companies, ask who writes the rubric and who accepts finished work. The service model should make those responsibilities clear.

With staff augmentation, plan for your team to direct the added workers. Name a manager who can answer questions and review results. If your own team cannot support that work, account for the missing management capacity before hiring.

For managed services, require a named delivery owner and written acceptance rules. Ask how the provider trains replacements, handles disputed results, and reports rework. A provider should be able to explain the path from an unclear task to an approved decision.

Apply the same questions when a proposal uses the label business process outsourcing services. Read the staffing and delivery terms. The category name does not tell you how much management your team must supply.

Opus states that the client chooses the finalist and manages day-to-day work. Opus's process should therefore be assessed alongside your own capacity to direct the hire.

Confirm the platform and data workflow

Ask whether the hire will use your RLHF platform or a provider's tool. Identify who pays for licenses and who owns the accounts. Confirm that your team can export completed work with its review history.

Before giving access, define the data the person may see and the tools they may use. Keep any restrictions on external AI tools explicit. Use an approved sample for hiring assessments.

Assign someone to remove access when a placement ends or changes. Include stored files and shared credentials in that process. Resolve these details before production work begins.

Test the handoff from completed review to your internal dataset. Check that ratings remain attached to the correct prompt, response, and rubric version. Ask the hire to explain an exported record so you can confirm that both sides understand the fields.

Decide how to correct a rating after it has been accepted. Preserve the reason for the change and identify who approves it. This gives your team a way to revisit earlier work without losing the original decision.

Approve a role with a workable start plan

Give the hiring partner a role description tied to real tasks. Include the sample exercise, shared hours, and the manager who will review work. State what the hire should be able to do independently.

Separate the hiring decision from the first working day. Confirm the start date with the selected candidate and the employer. Have access, instructions, and a first review session ready before then.

Start with a bounded batch and inspect the explanations behind the ratings. Record unclear cases and revise the instructions before increasing volume. Keep the review record so later hires can learn from the same decisions.

Set an early checkpoint with the hire and daily manager. Review where work stalled, which instructions caused disagreement, and whether the shared hours were sufficient. Change the workflow when the problem is an unclear rule. Give specific feedback when the problem is how the reviewer applied it.

Approve the hire when you have evidence of task fit, a usable schedule, and a written cost agreement.

Talk to Opus about a role.

<!-- File not saved because the workspace is read-only. Live legal updates were not checked; confirm applicable employment terms before hiring. -->