Job description template

Operations Coordinator

We’re hiring a Mid-level Operations Coordinator to help keep our day-to-day operations reliable and scalable across teams. You’ll own key workflows, coordinate cross-functional requests, and improve operational visibility so work moves smoothly and issues get resolved quickly.

Responsibilities

Coordinate and execute recurring operational workflows (intake, tracking, follow-ups, and closure) across multiple teams
Maintain accurate operational documentation and process runbooks, ensuring information stays current and discoverable
Monitor work pipelines and service requests, proactively identifying blockers, escalations, and ownership gaps
Partner with stakeholders to gather requirements for operational improvements and translate them into clear, trackable actions
Track operational metrics and produce concise summaries for stakeholders when trends or risks emerge
Manage access/permissions and operational tooling hygiene (e.g., ensuring correct configurations and timely updates)
Support incident/issue coordination by collecting status updates, documenting timelines, and helping drive resolution to completion

Must-have qualifications

Hands-on experience coordinating operational workflows end-to-end (intake, tracking, follow-up, closure)
Proficiency in using spreadsheets and business tools to track work, statuses, and metrics reliably
Strong documentation skills with the ability to write and maintain clear runbooks and process notes
Experience coordinating across multiple stakeholders to resolve blockers and drive outcomes
Ability to manage competing priorities with consistent attention to detail in a fast-moving environment
Customer- and problem-focused approach to operational issues, including escalation when needed

Nice to have

Experience with ticketing/work management systems and operational dashboards (e.g., Jira, ServiceNow, or similar)
Basic knowledge of automation (e.g., Zapier/Make or lightweight scripting) to improve operational efficiency
Experience supporting onboarding or access workflows for distributed teams

What success looks like in 12 months

Operational workflow reliability
Process documentation that stays current
Actionable operational visibility
Faster issue resolution through coordination

Logistics

Full-time (40 hours a week), remote from Latin America.
Working hours overlap with US business hours.

About the company

[About your company: what you build, your stage and team size]

Want it tailored to your stack, seniority and time zone?

Customize with the free generator →

Interview scorecard

Score every candidate against the same bar

Ensure operational workflows run reliably by coordinating end-to-end processes, maintaining accurate visibility, and driving timely resolution of issues.

Outcomes to measure

What this hire should deliver in the first year. Replace [N] with your own targets.

Operational workflow reliability. Measure: close [X]% of tracked operational requests within the defined SLA/target timeframe
Process documentation that stays current. Measure: publish or update [N] runbooks/process documents and achieve [X]% completeness/accuracy as validated by stakeholder review
Actionable operational visibility. Measure: deliver [N] recurring operational status/metrics updates with [X]% on-time delivery
Faster issue resolution through coordination. Measure: reduce time-to-resolution for operational issues by [X]%

Competencies and weights

What to evaluate, how much it counts and what a strong answer looks like.

Workflow orchestration · 22%
This role depends on end-to-end coordination (intake to closure) and keeping work moving predictably. Evaluated in Round 1.

Weak: Tracks requests without a clear intake-to-closure trail or misses follow-ups.
Meets the bar: Maintains an end-to-end workflow with consistent tracking, follow-ups, and closure steps.
Strong: Designs and sustains an efficient workflow that prevents drop-offs and improves SLA adherence through proactive ownership.

Cross-functional coordination · 18%
The coordinator must align stakeholders, secure inputs, and drive resolution through clear ownership. Evaluated in Round 2.

Weak: Relies on ad-hoc outreach and struggles to get stakeholders to commit to next steps.
Meets the bar: Clarifies owners, deadlines, and next actions with stakeholders to resolve blockers.
Strong: Leads coordination through ambiguity, unblocks decisions early, and prevents repeated coordination overhead.

Operational metrics tracking · 16%
Accurate tracking and metrics are required to identify risks early and communicate status clearly. Evaluated in Round 2.

Weak: Uses spreadsheets/tools inconsistently, resulting in unreliable statuses or incomplete reporting.
Meets the bar: Builds and maintains reliable trackers and reports that stakeholders can trust.
Strong: Creates metric views that explain trends, highlight bottlenecks, and directly drive operational decisions.

Documentation and runbooks · 14%
Good documentation ensures continuity across teams and reduces repeated questions during incidents or busy cycles. Evaluated in Round 1.

Weak: Writes notes that are vague or hard to follow; runbooks don’t reflect current reality.
Meets the bar: Writes clear, step-by-step runbooks and keeps them updated as processes change.
Strong: Produces documentation that enables other teams to execute independently and reduces recurring operational escalations.

Prioritization under pressure · 10%
Operational work often has competing demands; consistency and attention to detail matter. Evaluated in Round 3.

Weak: Lets urgent work displace important work and misses details that cause downstream rework.
Meets the bar: Balances competing requests using clear prioritization and reliable follow-through.
Strong: Anticipates priority shifts and adjusts plans proactively while keeping quality high.

Issue escalation mindset · 10%
Operational incidents and blockers require timely escalation and structured resolution support. Evaluated in Round 3.

Weak: Waits too long to escalate or communicates only after delays become visible.
Meets the bar: Escalates when thresholds are hit and coordinates resolution with clear updates.
Strong: Defines escalation criteria and improves resolution outcomes by driving structured incident coordination.

Customer-focused problem solving · 10%
The role impacts internal stakeholders; the candidate must remain solution-oriented and responsive. Evaluated in Round 2.

Weak: Communications are reactive or blame-oriented during operational problems.
Meets the bar: Responds with empathy, clarifies needs, and drives toward practical resolution.
Strong: Turns recurring stakeholder pain into durable process improvements that reduce future friction.

Interview questions

Questions for every interview round

Each round has an owner, a time box and questions that test the competencies above.

Round 1: Operations Workflow & Documentation Interview
Operations Lead · 45 min

Describe an end-to-end operational workflow you coordinated (intake to closure). What tools did you use, how did you track ownership, and how did you ensure nothing fell through?
Walk me through a time you updated documentation or created a runbook to address a recurring operational problem. How did you confirm it stayed accurate after changes?
Give an example where you had incomplete or conflicting information. How did you make progress while keeping the process trustworthy?

Round 2: Metrics, Coordination & Stakeholder Impact Interview
Program Manager · 55 min

Tell us about a time you built or improved a tracker/report in spreadsheets or business tools. What metrics did you include, and how did those metrics change decisions?
Describe a cross-functional situation where multiple stakeholders had different priorities. How did you align owners and drive the work to completion?
Share an example of customer- or stakeholder-focused problem solving in an operations context. What was the outcome and what did you do differently afterward?

Round 3: Prioritization & Escalation Interview
Head of Operations · 50 min

Tell me about a time you had competing priorities and tight deadlines. How did you decide what to do first, and how did you prevent quality issues?
Describe an operational issue you helped coordinate through to resolution. What signals told you it needed escalation, who did you involve, and how did you keep stakeholders informed?
If two critical issues arrived at the same time and you only had partial information, what steps would you take in the first [30] minutes to stabilize the situation?

Red flags to watch for

Cannot explain a complete intake-to-closure workflow; relies on memory instead of reliable tracking
Documentation is inconsistent, out of date, or lacks actionable steps someone else could follow
Avoids escalation or communicates without clear next actions and ownership
Inconsistent use of tools/metrics leading to unclear status or frequent rework

How much does it cost to hire an Operations Coordinator in Latin America?

In 2026, a senior Operations Coordinator in Latin America costs $3,000 to $3,500 a month all-in, versus $7,500 in the US: up to 60% less. Mid-level starts at $2,000.

Country

Mid-level

Senior

Argentina

$2,000

$3,000

Brazil

$2,250

$3,375

Colombia

$2,000

$3,000

Mexico

$2,375

$3,500

United States

$5,000

$7,500

Monthly cost in USD, all-in: the talent's salary plus Teilur's flat 20% fee, from our 2026 rates. The United States row shows what the same role typically costs there.

Compare costs in the calculator →

Frequently asked questions

What does an Operations Coordinator do?

Typical responsibilities include: coordinate and execute recurring operational workflows (intake, tracking, follow-ups, and closure) across multiple teams; maintain accurate operational documentation and process runbooks, ensuring information stays current and discoverable; monitor work pipelines and service requests, proactively identifying blockers, escalations, and ownership gaps. The full list is in the template above.

How much does it cost to hire an Operations Coordinator in Latin America?

In 2026, a senior Operations Coordinator in Latin America costs $3,000 to $3,500 a month all-in, versus $7,500 in the US: up to 60% less. Mid-level starts at $2,000.

Can I customize this Operations Coordinator job description?

Yes. Teilur's free Job Description & Scorecard Generator rewrites it for your stack, seniority, time zone and hiring urgency in about 15 seconds. No sign-up needed.

Book a Free Consultation

Operations Coordinator Job Description Template