About the Role

We build AI-powered turnaround monitoring for airports. Our cameras are installed across parking stands to detect and classify ground turnaround events — chocks, GPU, doors, fuelling, boarding — displayed live on our mobile app and OCC dashboard used by airline operations teams.

We are seeking a process-driven Operations Supervisor to manage our data annotation team. You will own the operational lifecycle of our data—from planning weekly tasks to performing final quality audits. Your primary objective is to ensure that our ML Engineers receive high-quality, accurately labeled datasets on a predictable schedule, allowing them to focus entirely on model development.

Key Responsibilities

• Operational Planning: Breakdown project requirements into daily/weekly annotation tasks. Manage the team's workload to ensure no "idle time" and 100% deadline adherence.

Requirements

Must Have

• 3–5 years in Operations Management: Experience as a Supervisor, Team Lead, or Quality Lead in a process-heavy environment (e.g., Data Ops, Content Moderation, or Back-office BPO).
• Proficient Digital Literacy: You must be comfortable working entirely within web-based software applications. You don't need to code, but you should be able to navigate new platforms and troubleshoot basic settings independently.
• Strong Process Orientation: Proven experience in managing workflows, creating trackers, and driving team productivity.

Good to Have

• Prior experience with image/video annotation or data labeling projects.
• Experience using project management tools (Jira, Trello, or similar).
• Experience in a Quality Control (QC) or Quality Assurance (QA) focused role.

What Success Looks Like

• Predictable Delivery: Annotation projects are completed on a clear, measurable weekly cadence.
• High Quality Bar: Data rejection rates from the engineering team drop significantly because your internal QA process is robust.
• Developer Freedom: Our developers no longer spend time managing annotators or checking basic labels; they only interact with you for high-level requirements.
• Clear Documentation: There is a clear "source of truth" for how each event should be labeled, reducing team confusion.