Head of Operations

Rwazi, Inc.

About The Position

Rwazi’s data engine operates across Retail Mapping (RM), Consumer Insights (CI) and Multimodal AI Datasets deployments spanning dozens of countries and millions of contributors. The Head/Director of Operations owns the global execution system that ensures data capture fulfills predictably, economically, and at decision-grade quality. This role is responsible not only for delivery, but for architecting the operational machine itself — activation logic, deployment economics, QA governance, contingency infrastructure, and cross-functional alignment. The Head of Operations defines how Rwazi executes at scale. This is a system-ownership role with direct impact on revenue reliability and client trust.

Requirements

8–12+ years operating complex, multi-region execution systems
Proven experience managing gig or distributed contributor networks
Strong quantitative reasoning (rates, throughput, forecasting, cost modeling)
Comfort operating in high-friction, rapidly changing environments
Builder mentality — able to create scalable systems from ambiguity
Experience leading cross-functional delivery organizations

Nice To Haves

Candidates may come from high-scale marketplaces, field operations platforms, logistics, gig networks, or complex B2B SaaS delivery environments.

Responsibilities

Ensuring every client log fulfills on time and at required quality thresholds
Designing scalable activation and contributor supply systems across regions
Governing QA standards to protect client-grade data integrity
Controlling cost structures and payout economics
Building multi-path contingency frameworks to eliminate delivery risk
Scaling a high-performance global operations team
Own end-to-end execution across RM and CI deployments
Maintain operational predictability across geographies, time zones, and product types
Establish clear escalation pathways and risk thresholds
Design global contributor acquisition and reactivation systems
Optimize throughput per city and per log
Align incentives with delivery velocity and QA quality
Lead the QA function as a control system, not just a review layer
Define pass-rate thresholds, rejection logic, and retraining loops
Ensure data meets client-facing standards without threshold dilution
Track and optimize cost-per-approved submission
Forecast fulfillment timelines based on early signal velocity
Prevent margin leakage through structural discipline
Build Plan A/B/C routing for all major deployments
Mitigate risks related to geography gaps, contributor churn, or platform failures
Reduce late-stage surprises through early signal detection
Align Operations with Sales timelines and client SLAs
Collaborate with Engineering to strengthen execution tooling
Partner with Community to sustain contributor engagement
Hire, train, and manage regional operations leads
Define performance standards and accountability structures
Build a culture of execution discipline and ownership