Frequently asked questions

$3,500 per month for a mid-level engineer, $4,900 for a senior and $6,400 for a tech lead — full time, dedicated, billed monthly. No recruiting fee and no annual minimum.

No. Nothing to search, nothing to introduce, nothing on top of the monthly rate.

There is none. Thirty days notice in either direction, from the first month.

No. A Go engineer and a PHP engineer cost the same, which means the saving is much larger on skills that are scarce in the U.S.

The engineer full time, their hardware, their software licenses, their Brazilian taxes and contributions, and the replacement guarantee.

One monthly invoice in U.S. dollars, issued in advance for the coming month and due on the 5th, paid by bank transfer — wire or ACH. We do not take cards today; if your finance team needs one, say so in the first email rather than after signature. No payroll, no benefits administration.

No. A half-time engineer on a product team gets less than half the context. If your need is small, a fixed-scope project fits better and we will say so.

Brazil is UTC−3 with no daylight saving. São Paulo is one hour ahead of New York in U.S. summer and two hours ahead in U.S. winter; four to five hours ahead of Los Angeles.

On ordinary Brazilian hours (9 AM to 6 PM): seven to eight with U.S. Eastern, six to seven with Central, five to six with Mountain, four to five with Pacific. If the engineer shifts their day to end at 8 PM their time, Mountain rises to seven or eight and Pacific to six or seven — something we agree explicitly with them rather than assume.

No. Engineers shift their day within normal working hours in Brazil. If your requirements need someone awake at 2 AM their time, we will tell you this is the wrong model rather than agree and lose them in six months.

They differ from U.S. ones — Carnival is the one that surprises people. We send the calendar during onboarding so it lands in your sprint planning, not in your sprint.

No. Engineers are contracted by HireBrazilDevs and you receive a single invoice for services, like any other vendor.

You do. The agreement hereby assigns all intellectual property created under it, effective on creation and surviving termination, and it commits us to hold the matching assignment from your engineer — the chain has to run engineer to studio to you, and we warrant that link in writing. Ask any vendor to show you both links; a supplier who can only show the second one is selling you a gap.

Yes, yours or ours. Also MSAs, DPAs and security questionnaires.

The employment relationship sits between the engineer and the studio, not between the engineer and you. That is one of the main reasons companies use this structure rather than contracting individuals directly. Ask your own counsel — we are not lawyers.

Tell us which regime and what your auditor requires, in the first email. We will sign the paperwork it calls for — a BAA, a DPA, your security addendum — or say in writing which clause we cannot meet, before you commit to anything. We do not keep a pre-signed pack on the shelf and we would rather tell you that than discover the gap at signature. Work carrying U.S. citizenship or clearance requirements we cannot staff at all, and we say so upfront.

No. The brief, the scope, the candidate summaries, interview scheduling, contracts and invoices all happen in writing, in the client portal and by email, with a reply within one business day in U.S. hours. The only calls in the process are your own interviews with the engineers. Written-first is deliberate: it leaves a record, respects your calendar, and is how distributed teams already work.

Five business days for common stacks. Ten to fifteen for scarcer ones such as Go, Elixir or specialized machine learning. We tell you which category your role is in with our first written reply, within one business day.

In three steps. A free 40-minute online assessment filters first: twelve practical questions on their stack and a written code review in English, read and approved by a person. Those who pass do a 60-minute pairing session on real code and an unscripted technical conversation in English, plus a production-experience check. We do not use multi-hour take-home projects — they filter out senior engineers who already have jobs.

Written English is close to universal at senior level; spoken fluency varies and is what we screen for. Every engineer we place holds a technical conversation in English, including disagreeing with you.

Tell us in the first 30 days and we replace them, with no billing for the overlap.

As many as you want, in as many rounds as you want, at no cost.

No. Full time, one client. That is a contractual term, not a preference.

You do. This is staff augmentation — they join your standup, your board and your code review. If you have nobody available to direct them, we will tell you the model is a poor fit.

No. You talk to the engineer directly. We check in monthly to catch problems that people are too polite to raise.

Yes, arranged at cost. Budget time for a U.S. visitor visa if the engineer does not already hold one.

Yours. They work in your repository, your CI, your ticket tracker and your chat, on their own machine.

Four to six weeks for a senior engineer on a normally documented codebase — about the same as a local hire. If it takes twelve, the problem is onboarding.