LavaStaff Nearshore Guide: How to Write a Job Description for a Latin America Hire

A good job description does more work than most teams give it credit for. It is the first filter, the first pitch, and the first impression a candidate forms of how you operate. When you are hiring locally, a vague posting still tends to work because the labor pool already understands your market, your pay norms, and your hours. When you hire offshore staff from Latin America, none of that shared context is automatic. A loose description that would pass at home will pull in the wrong applicants, set the wrong expectations, and cost you weeks of wasted screening.

This guide walks through how to write a job description for a Latin America hire that attracts the right nearshore talent and screens out the rest before a single interview. It covers what to include, how to set the time zone and English bar honestly, where to put a real salary range, the mistakes that quietly kill a good posting, and a reusable template you can copy and adapt to any role.

Why a nearshore job description is different

The instinct is to take your existing US job description, paste it into a new posting, and hope it travels. It rarely does. A nearshore hire reads your description with different questions in mind, and the strongest candidates are the ones asking those questions most carefully.

A skilled developer or assistant in Mexico, Colombia, or Argentina is usually weighing several offers at once. They want to know three things your domestic posting probably never spells out: which hours they are expected to be online, how you intend to engage and pay them, and whether the pay is competitive for their country and seniority. If your description is silent on those points, the best people assume the worst and apply elsewhere, while the people who do apply are the ones with no better options. A clear posting inverts that. It signals that you have hired across borders before, that you respect the candidate's time, and that the role is real and funded.

There is also a practical filtering benefit. Every specific detail you add is a self-selection gate. State the working hours and people on the wrong schedule opt out. Name the English bar and people below it opt out. Post a salary range and people outside your budget opt out. You spend your screening time on the short list that is actually a fit instead of reading through a hundred mismatched resumes.

Start with the outcome, not the task list

Most job descriptions open with a list of responsibilities. That tells a candidate what they will do on a Tuesday but not why the role exists or what success looks like. Strong applicants want the second thing. Open instead with the outcome you are hiring for, in one or two plain sentences.

Compare these two openings for the same role. The weak version says: "We are looking for a customer support representative to answer tickets, manage our inbox, and help customers." The strong version says: "We are hiring a customer support representative to own our first-response queue during US business hours, keep our resolution time under four hours, and turn frustrated customers into renewals." The second version gives a candidate something to aim at, a way to picture the job, and a reason to believe the role is owned rather than just staffed.

When you lead with the outcome, the responsibilities that follow read as the means to that end rather than a random pile of tasks. It also forces you to be honest with yourself about what you actually need, which is the part of hiring that the description quietly tests first.

The anatomy of a strong nearshore job description

A complete nearshore posting has a predictable shape. You do not need every section for every role, but the strongest descriptions tend to include all of these, roughly in this order.

• Role summary and outcome: Two or three sentences on what the role owns and what success looks like in the first six months.
• About the company: A short, honest paragraph on what you do and why the work matters. Skip the buzzwords; nearshore candidates have read enough of them.
• Responsibilities: Five to eight bullets of the actual work, written as verbs, not vague areas.
• Requirements: The genuine must-haves, separated from the nice-to-haves so you do not scare off a strong candidate who is missing one optional skill.
• Time zone and working hours: The exact overlap you expect, stated in a way both sides can read without confusion.
• English and communication bar: The level of spoken and written English the role truly needs, not a reflexive "fluent" for every job.
• Engagement model and what you provide: Whether the person is a contractor or an employee of record hire, and what they get for it.
• Compensation: A real range, in a currency the candidate understands.
• How to apply: A simple, respectful process with a clear next step.

The middle sections, time zone, English, engagement, and pay, are the ones domestic postings tend to skip and nearshore postings cannot afford to. The rest of this guide goes deep on those, because they are where most descriptions either earn trust or lose it.

Write the working hours section honestly

Time zone is the single most important practical detail in a nearshore posting, and it is the one teams are vaguest about. "Some overlap with US hours" means nothing. It could be two hours or eight, and the candidate has no way to plan their life around it. Be precise.

The good news is that Latin America makes this easy to state cleanly, because the region sits close to US time zones. Mexico and much of Central America align with US Central time. Colombia and Peru run on US Eastern time with no daylight saving, so they sit at the same hour as New York in winter and one hour off in summer. Brazil, Argentina, and Chile are one to two hours ahead of US Eastern. For most of the region, a US team and a nearshore hire share most of a normal workday without anyone working strange hours.

Say exactly what you want. A clean version reads: "This role works 9am to 5pm US Eastern time. Most of our team is on the East Coast, and we expect you to be online and reachable during those hours." If you only need partial overlap, say that too: "We need at least four hours of daily overlap with US Pacific time, roughly 9am to 1pm Pacific. The rest of your day is yours to schedule." Either way, the candidate knows whether the role fits their life before they apply.

If you are unsure how the hours line up for a given country, the time zone overlap calculator shows the shared working window between your city and each Latin American country, so you can write the hours section from real numbers instead of a guess.

Set the English and communication bar precisely

Defaulting every role to "fluent English required" is lazy and it costs you. English ability varies across the region and across individuals, and the level a role genuinely needs varies just as much. A senior developer who pairs with your team all day and a back-office data entry assistant do not need the same English, and pretending they do either narrows your pool needlessly or sets a bar the work does not require.

Describe the communication the job actually involves, then state the matching level. For a customer-facing or client-facing role, you might write: "You will talk to US customers by phone and video every day, so you need clear, confident spoken English." For a heads-down engineering role, you might write: "Most of our communication is written, in Slack and pull requests, so strong written English matters more than a perfect accent." For an internal support role with light interaction, "comfortable written English and conversational spoken English" is honest and opens your pool.

Latin America has a wide range of English proficiency, and several countries punch well above the regional average for professional, business-level communication. If you want to ground the bar in real data rather than assumption, the English proficiency comparison tool ranks the major nearshore countries so you can set expectations that match where you plan to hire.

Be specific about seniority and scope

"Developer" is not a seniority. Neither is "assistant." A junior and a senior version of the same title do different work, command different pay, and need different descriptions. Vague seniority is one of the most common reasons a nearshore posting attracts a flood of mismatched applicants, because everyone from a bootcamp graduate to a ten-year veteran reads themselves into the gap.

Name the level and back it with scope. Instead of "React developer," write "mid-level React developer, three to five years of experience, comfortable owning features end to end but not expected to architect the whole front end." Instead of "executive assistant," write "senior executive assistant who can manage a founder's calendar and inbox with minimal oversight and make judgment calls without checking in on every detail." The scope language does the real work, because experience-year ranges alone are easy to inflate.

Tying seniority to pay also keeps your description internally consistent. A senior role with a junior salary range reads as either a mistake or a bad-faith offer, and strong candidates treat both the same way. If you want benchmark pay by seniority for a specific role, the salary benchmarks by role pages break down junior, mid, and senior bands across Latin American countries, which makes it straightforward to match the level you describe to a range that will actually attract it.

Name the engagement model and what you provide

Domestic candidates assume they are being hired as employees with the usual protections. Nearshore candidates assume nothing, because the engagement model genuinely varies. The two common paths are an independent contractor agreement, where the person invoices you and handles their own taxes and benefits, and an employer of record arrangement, where a third party legally employs them in their country and provides local benefits while you direct the work.

State which one this is, and say what comes with it. A contractor posting might read: "This is a full-time contractor role. You will invoice us monthly and are responsible for your own local taxes. We provide a hardware stipend and twenty days of paid time off." An employer of record posting might read: "You will be employed through our local partner in your country, with full statutory benefits, paid local holidays, and a thirteenth-month bonus where the law requires it." Either is fine; what is not fine is leaving the candidate to guess, because the guess shapes whether they trust the offer.

The choice between models affects cost, risk, and retention, and it is worth getting right before you write the posting rather than after. If you are still deciding, our guide on EOR vs contractor in Latin America walks through how each model works, where the legal and tax risk sits, and how the answer shifts by country.

Compensation: post a real range

The fastest way to improve a nearshore job description is to put a real salary range in it. Many teams resist, out of habit or a worry about anchoring, and it backfires every time. A posting with no pay range gets applications from people at every salary expectation, and you spend the screening call discovering you are tens of thousands of dollars apart. A posting with a range filters that out before anyone wastes their time.

Post the range in a currency the candidate reads easily. Most nearshore professionals quote and compare in US dollars, so an annual or monthly USD figure usually communicates most clearly. Make the range honest and reasonably tight; a band so wide it covers junior to senior tells the candidate nothing and reads as a dodge. And make sure the number is competitive for the country and seniority, because a strong candidate knows their market value and a lowball range marks you as a buyer to avoid.

To set a range you can defend, start from regional benchmark data rather than your domestic salary minus a discount. The Latin America salary guide gives market pay by role and country, and the hiring cost calculator shows the fully loaded cost of a seat once benefits and overhead are included, so the range you post lines up with what the hire will actually cost you.

A reusable nearshore job description template

Here is a skeleton you can copy and fill in for almost any role. Keep it tight; a description that runs past a page or so tends to lose the people you most want.

• Title and level: "Mid-level [role], [3 to 5] years of experience."
• Outcome: "We are hiring a [role] to own [the outcome] and deliver [the measurable result] in your first six months."
• About us: One honest paragraph on what you do and why the work matters.
• What you will do: Five to eight verb-led bullets of the real work.
• What we are looking for: The genuine must-haves, with nice-to-haves listed separately.
• Hours: "This role works [exact hours] in [time zone]. We expect you online and reachable during that window."
• Communication: "[Spoken/written] English at [level], because [the actual communication the job involves]."
• Engagement: "[Contractor / employer of record] role, with [what you provide: PTO, stipend, benefits]."
• Pay: "[Currency and range], based on experience."
• How to apply: "[One clear step] and what happens next."

The template is deliberately plain. Its value is in forcing you to fill in the blanks the domestic version lets you skip, especially hours, communication, engagement, and pay. Once those four are specific, the rest of the posting almost writes itself.

A worked example: nearshore React developer

To make the template concrete, here is how it reads filled in for a real role. "We are hiring a mid-level React developer, three to five years of experience, to own our customer-facing dashboard and ship features end to end. You will work in a small product team, pair with our two US engineers daily, and take features from a Figma file to production. This role works 9am to 5pm US Eastern time, and we expect you online during those hours because we move fast and decisions happen in real time. Most of our communication is written, in Slack and pull requests, so strong written English matters more than a perfect accent. This is a full-time contractor role at 4,500 to 6,000 USD per month, with twenty days of paid time off and a hardware stipend. To apply, send us a short note and a link to something you have built, and we will reply within a week."

Notice what that posting does. It names the level and the scope, sets exact hours, calibrates the English to the actual work, states the engagement and pay plainly, and closes with a respectful, specific next step. A developer in Colombia or Mexico reading it knows in thirty seconds whether the role fits their hours, their English, and their pay expectations, which is exactly the filtering you want a description to do.

Common mistakes that sink a nearshore job description

A few patterns show up again and again in postings that underperform.

• Copying the US posting wholesale. It carries domestic assumptions about hours, pay, and employment that do not translate, and it reads as if you have never hired across borders.
• Hiding the salary. No range means you screen on pay during the call instead of before it, wasting everyone's time and signaling that the number might be bad.
• Defaulting to "fluent English" for every role. It narrows your pool for jobs that do not need it and tells a candidate you have not thought about the actual communication involved.
• Being vague about hours. "Some US overlap" is unanswerable. The best candidates need to plan their day, and silence reads as a red flag.
• Listing twenty requirements. A long must-have list scares off strong people who are missing one item. Separate the genuine requirements from the wish list.
• Skipping the engagement model. Leaving contractor versus employee ambiguous makes a careful candidate assume the riskier answer and pass.

Each of these has the same root cause: treating a nearshore posting as a domestic one with a different audience. The fix is to write for what the nearshore candidate actually needs to know before they will say yes.

Frequently asked questions

Should I include a salary range in a nearshore job description? Yes. A real range is the single biggest improvement you can make. It filters out mismatched applicants before the first call, signals that the role is funded and serious, and earns trust with strong candidates who already know their market value. Post the range in US dollars, since most nearshore professionals compare offers that way.

What English level should I ask for? Only as much as the work genuinely requires. A customer-facing or client-facing role needs clear, confident spoken English. A heads-down engineering role can prioritize strong written English over accent. Describe the actual communication the job involves and set the bar to match, rather than defaulting every posting to "fluent."

How do I write the working hours section? State the exact hours and time zone you expect, not a vague "some overlap." Latin America aligns closely with US time zones, so most roles can share a normal workday. If you are unsure how the hours line up for a given country, check the overlap before you write the section so the hours are accurate.

How long should a nearshore job description be? Roughly a page. Long enough to cover outcome, responsibilities, requirements, hours, English, engagement, and pay clearly, short enough that a busy candidate reads to the end. If it runs past a page, you are probably padding the requirements or the company section.

Should I list the role as a contractor or an employee? Decide before you post, because the model changes cost, risk, and retention, then state it plainly in the description. If you are unsure which fits, read through how contractor and employer of record arrangements differ by country and pick the one that matches the role and the relationship you want.

The bottom line

A job description for a Latin America hire is not a domestic posting with a wider mailing list. It is a different document, written for a candidate who needs to know your hours, your English bar, your engagement model, and your pay before they will take you seriously. Get those four specific and the posting starts working for you: the right people self-select in, the wrong people opt out, and you spend your screening time on a short list that actually fits.

If you would rather skip the posting entirely and have vetted candidates brought to you, that is what we do. Browse the roles we staff to see what a nearshore hire looks like for your function, or tell us about the role and we will bring you a shortlist of Latin American talent that already matches the hours, English, and seniority you need.