The RoleThis role exists as a high-leverage force multiplier for our core Computer Vision Machine Learning (CVML) team. You are not building the foundational models for our robotics systems; rather, you own the critical infrastructure, internal tooling, and targeted ML services that enable the CVML team to move fast.
You will own the internal annotation platform used by our labeling team and develop lightweight, high-reliability ML services like our Personal Identifiable Information (PII) blurring pipeline. This is a true hybrid engineering role demanding competence in both deploying practical ML models and writing robust, user-facing full-stack applications.
ResponsibilitiesInternal Tooling & Infrastructure- Own the Annotation Platform (CVA): Build and maintain the web application our labeling team uses daily. You will ship new task types, review workflows, keyboard-driven UI features, and progress dashboards.
- Data Pipelines: Write the glue code to efficiently move video frames, metadata, and JSON payloads between cloud storage, databases, and the client application.
- Quality Measurement: Build tools to track inter-annotator agreement, audit sampling, and dataset health.
Targeted ML Services- PII Blur as a Service: Own the pipeline that detects and blurs faces, screens, and license plates in delivered footage. This is a strict, customer-facing system that must perfectly balance privacy compliance with data preservation.
- Model-Assisted Labeling: Deploy and optimize lightweight detection and segmentation models (e.g., bounding box assists) so annotators correct rather than create from scratch.
- Inference Optimization: Take off-the-shelf or provided PyTorch models, optimize them (e.g., TensorRT, ONNX), and wrap them in fast, concurrent APIs to serve the tooling UI.
Who You AreRequired Skills (The Hard Bar)- Heavy Frontend Engineering: You can confidently build and ship interactive web applications (React, Vue, or modern JS/TS). You understand how to handle complex state, canvas-based rendering, or video playback in the browser without tanking performance.
- Production-Grade Python: You know how to build fast, concurrent APIs (FastAPI, gRPC) that dont choke on high-volume media requests.
- Practical Applied ML: You have experience fine-tuning and deploying detection, segmentation, or tracking models on messy, real-world data. You know how to take a model out of a Jupyter notebook and make it run reliably in a pipeline.
Strong Signals- You have built or heavily customized an annotation UI (handling bounding boxes, polygons, keypoints) and understand the pain points of human-in-the-loop workflows.
- Deep familiarity with video processing pipelines (FFmpeg, frame extraction, codec handling, latency optimization).
- Familiarity with active learning workflows or mining hard negatives to iteratively improve datasets.
- You care deeply about UI/UX and measure your success by the workflow speed of the end-user.
Who Will Not Enjoy This Role- Core ML Architects: If your primary goal is designing novel neural network architectures or working on frontier foundation models, this is the wrong fit. Your ML work here uses established architectures to solve practical pipeline problems (like PII detection).
- Backend-Only Engineers: If you dislike writing TypeScript, debugging CSS, or thinking about UI workflows, you will struggle. You own the frontend annotation product just as much as the ML services.
- Data-Allergic Engineers: If you expect a perfectly clean, balanced dataset handed to you, this isnt the role. You are building the systems that create and sanitize that data.
How to Apply (Proof of Work Requirement)To ensure alignment with the technical realities of this role,
we will only review applications that include a link to your Proof of Work.In your application, you must include a link to
one of the following:
- A personal website or portfolio.
- A GitHub repository showing a non-trivial project you built (no standard bootcamp/tutorial clones).
- A technical blog post or write-up you authored.
- If you do not have public links because your best work is proprietary, include a brief (250 words max) technical description of a complex data pipeline, web application, or ML deployment you personally engineered, focusing on the specific bottlenecks you solved.
