When a staff augmentation project has sold a developer: who manages delivery?

What should a project manager own on your US team?

Give the project manager ownership of the delivery plan and the work needed to keep it current. That includes tracking dependencies, getting answers from decision-makers and showing how a change affects a promised date.

Keep approval rights explicit. Your product owner sets priorities. Your technical lead owns engineering decisions. A named client leader approves changes to budget or release scope. The project manager brings those people a clear decision when the plan needs to change.

When you hire dedicated developers, define who will turn business requests into work the team can start. If that responsibility already sits with a product manager and engineering lead, you may need less project management capacity. Adding another person to collect status can create another handoff.

Write a short role charter before requesting candidates. Describe the release the person will support, who they report to and which decisions they can make without approval. Include the problems you expect them to solve.

Use the charter in interviews. Ask candidates how they would handle a sponsor who adds work without moving the date. A useful answer identifies the decision required, the person who can make it and what happens while the team waits.

Decide whether the problem needs a full-time hire

Look at a recent missed milestone. Was work blocked by another team? Did a decision sit unanswered? Did someone change scope after engineers had committed to a date?

Those are useful cases for a project manager interview. If the problem was a technical estimate, ask how the manager would involve engineering. Do not make the new hire personally responsible for estimates they cannot assess.

Before the person starts, give them access to the backlog and the people whose decisions affect it. Agree on a reporting format that shows changed dates, blocked work and requests for approval. Avoid asking for a separate presentation when the same information already lives in your tools.

For example, suppose a customer launch depends on an API that another team has not scheduled. The project manager should get an owner and a proposed date for that dependency. Your engineering lead assesses the technical options. Your product owner decides whether a smaller release still meets the customer need.

Write the resulting decision into the plan, including who accepted the tradeoff. This gives the new hire a concrete job beyond reminding people to update tickets. It also gives you something to assess: did the manager get a decision early enough for the team to act?

How should you compare US pay with LatAm project manager costs?

Start with the duties, then choose the pay benchmark. A project coordinator, a software delivery manager and a program manager may carry different workloads. A title alone will not make their prices comparable.

For a US baseline, use the matching occupation in BLS Occupational Employment and Wage Statistics. Check the survey period and geography before putting a figure into the budget. Compare a national figure with a national figure, or explain why a local market matters.

BLS reports a median annual wage of $135,980 for software developers in May 2025. That figure describes developers and should not set your project manager budget. It can inform a separate engineering headcount discussion. BLS software developer pay

Request a role-specific monthly rate card

Use the table below to request quotes for a Latin American project manager. Ask each provider to price the same duties and shared working hours. All requested ranges are monthly and in USD.

Published project manager ranges for these entries: Not published. Ask for a written quote rather than treating software engineer compensation as a project manager rate.

Compensation context: Levels.fyi Brazil, Levels.fyi Mexico and Stack Overflow Developer Survey. These engineering compensation pages should not be used as project manager service quotes.

Define seniority through the work you expect. A junior hire might maintain a plan under an experienced manager. A mid-level hire might run delivery for a defined team. For a senior hire, test judgment when dependencies cross departments and stakeholders disagree. Treat these as your hiring criteria, then ask candidates for evidence.

Keep these price categories separate:

• Employee base pay is the person's salary.
• Total compensation may include bonuses or equity.
• Employment cost includes the obligations attached to the employment arrangement.
• A service invoice includes whatever the provider agrees to cover.

The Opus salary guide cautions against treating a local salary band as an all-in service price.

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. Published dollar rates: Not published. Opus pricing

Ask how the quote handles currency changes and any work outside the agreed schedule. Confirm the billing start date. Keep the cost of your own management time in the budget, since your team still makes operating decisions.

Compare the same job across quotes

Send each provider the same role charter. Include the number of teams involved, the reporting line and whether the manager will speak directly with customers. State whether the work covers one release or a continuing roadmap. These details let you question a price difference without assuming the cheaper quote covers the same job.

Ask for exclusions beside the monthly total. Confirm how leave coverage, equipment and a change in responsibilities would affect the agreement. If a quote assumes a narrower role, revise the scope before comparing it with another proposal.

Do not turn the difference between a US salary and a service invoice into a savings claim. First account for what each figure includes.

Which project management skills should you test, and how?

Use a work sample based on the delivery problems the hire will face. Keep it fictional so the interview does not become unpaid work on a live project.

Give the candidate a release goal, a small backlog and a dependency on another team. Add a stakeholder who wants more scope without changing the deadline. Ask the candidate to prepare a plan and explain what needs approval.

The exercise should reveal how the person thinks when the available information is incomplete. A candidate who asks about acceptance criteria may be more useful than one who immediately produces a detailed schedule.

Test the work your developers will actually do

If you plan to hire dedicated React developers, include a frontend change that depends on an API. Ask how the manager would expose that dependency before the team commits to a release date.

If you plan to hire dedicated mobile developers, include device testing and app review in the scenario. Ask what the manager would communicate when a release depends on a step outside the team's direct control.

For a .NET team, use a service change that affects another application. The project manager should know when to ask about compatibility and test coverage. Let the technical lead judge the engineering answer.

Do not require coding simply because the role sits beside developers. Require enough understanding to follow the work and ask precise questions. If the job also includes technical leadership, name that duty and assess it separately.

Score evidence before discussing impressions

Write the scoring criteria before interviews start. Give candidates the same core scenario so the hiring team can compare their responses.

After the exercise, ask about a real project that went off plan. Request the candidate's own actions and the decisions they needed from others. Ask what they changed after the problem appeared. A polished account without clear ownership deserves follow-up.

Test spoken and written English through the work. Have the candidate explain a schedule risk, then write the message they would send to a US stakeholder. Judge whether the reader can act on it.

During the discussion, change one assumption. Tell the candidate that the dependency owner cannot meet the agreed date. Watch whether they update the plan, ask about alternatives and identify which commitment now needs review. Keeping the original date without explaining how it remains possible should prompt a follow-up question.

Ask interviewers to record what the candidate actually said before sharing a recommendation. Separate a weak answer from a difference in preferred tools. Someone who uses a different ticketing system may still reason clearly about dependencies.

For references, ask the candidate's former manager how they handled unwelcome news. Request an example of a risk they raised and what happened next. Keep the questions tied to the duties in your role charter.

Read the Opus guide to hiring a nearshore development team.

Which Latin American countries fit your team's working hours?

Choose the working schedule before choosing the country. A project manager needs access to the people who can resolve blockers. Start with the hours when your product owner and technical lead are available.

Use the candidate's city when checking overlap. Mexico City and Tijuana follow different time rules. Brazil also spans multiple time zones, so a São Paulo schedule should not stand in for every Brazilian candidate. IANA North America, IANA South America

The table assumes both people work from 9 a.m. to 5 p.m. locally. It shows shared working hours, not a promise of candidate availability. Standard-time examples use January 15, 2027; daylight-time examples use July 15, 2026.

Time-zone rules: IANA North America and IANA South America. Shared hours follow from the stated local schedules.

Use location to narrow the schedule, then assess the person

Mexico City stays at UTC-6 without seasonal clock changes. Tijuana follows US daylight saving dates. If your team works Pacific hours, compare those cities separately. IANA North America

Bogotá stays at UTC-5. It shares a full local workday with Eastern time during US standard time under the table's assumptions. Check the meeting schedule again for US daylight time. IANA South America

Buenos Aires and São Paulo stay at UTC-3. For a Pacific team, place shared meetings earlier in the US workday or agree on a different local schedule. Ask the candidate directly before treating later hours as part of the role. IANA South America

San José stays at UTC-6. Its overlap in this table matches Mexico City. Compare candidates on delivery experience and communication once the required schedule fits. IANA North America

Ask for candidate availability in each market before committing the search to one country. A country choice should not replace a role-specific shortlist. Keep the same work sample and acceptance criteria across locations.

Write down release-day coverage separately from normal hours. Agree on who handles urgent questions when the project manager is offline. Put local holidays and planned leave into the delivery calendar before setting milestones.

Also check the schedule of the people outside engineering. A manager may overlap with developers but miss the finance lead who approves spending. Ask candidates to review a sample week of recurring meetings. Resolve conflicts before an offer, including whether a meeting follows US time when clocks change.

Avoid using nationality as a shortcut for English ability or delivery experience. Assess the person through the same stakeholder exercise, regardless of location. Ask about projects with a similar approval process and level of customer contact.

Which hiring route fits: recruiter, EOR, augmentation or managed team?

Choose the route based on the work you need help with and the authority you want to retain. Ask each provider to explain its responsibilities in the contract.

A recruiting engagement can focus on finding the person. An EOR arrangement can address employment for someone you have chosen. Team augmentation can add people who work inside your operating process. For a managed delivery engagement, inspect the promised outputs and acceptance terms.

These are buying distinctions to confirm, since the service label alone does not define the contract.

Opus finds, vets and installs the whole team. The client chooses the finalist and manages day-to-day work. Structure the engagement as a dedicated development team inside your process, with your team retaining operational control.

A project manager in that team can maintain the schedule and coordinate delivery. Give the person the same clear authority you would give an internal hire. Keep approval of product scope, budget and releases assigned to your leaders.

Separate hiring dates from working dates

Ask for distinct dates for candidate review, offer acceptance and the first working day. Plan onboarding around the final date.

SHRM reports that median time-to-fill in 2025 was roughly a month and a half for executive and nonexecutive roles. Its measure runs from job requisition to offer acceptance. Use that as general recruiting context, rather than a deadline for this specific search. SHRM State of Recruiting 2025

Keep interview feedback moving by naming the final decision-maker before the search begins. Reserve time for the work sample and decide who will evaluate it. Ask the provider about notice periods and start-date dependencies before making a release plan around the hire.

Put the operating agreement beside the hiring agreement

Before signing, confirm who supplies equipment and grants access. Identify the person who approves time off and handles performance concerns. Ask how a replacement would affect an active release and who maintains the handover documents.

For onboarding, give the project manager a real delivery problem with a named sponsor. Ask them to map dependencies and identify decisions that are already overdue. Review whether their updates help people act.

If they need permission to move a date or escalate a blocked decision, say so. If they can make that call within agreed limits, write those limits down. The hire should enter a team where authority is clear enough to use.

Keep the initial review tied to work you can inspect. Open the delivery plan together and ask which assumptions have changed. Check whether blocked tasks have owners and whether pending decisions have reached the right person. Ask engineers whether they can see what must happen before their work can ship.

If the manager is still chasing the same unanswered request, inspect the escalation route before adding more reporting. Your sponsor may need to make a decision or grant authority. Record that change in the role charter so the next release uses the revised process.

Before requesting candidates, have the role charter, shared-hours requirement and interview exercise ready. Send them together so the search starts with the job you expect the person to do.

Read the Opus guide to hiring a nearshore development team.

<!-- File not saved: the workspace is read-only. Live pages were not checked; confirm quoted pricing and contract terms before hiring. -->