> Markdown version of [/jobs/ext/3973437-staff-ml-data-engineer](https://www.wearedevelopers.com/jobs/ext/3973437-staff-ml-data-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Staff ML Data Engineer - **Company:** LiveView Technologies - **Location:** Seattle, WA, United States - **Experience:** Expert - **Salary:** $171,900.0 - $221,000.0 - **Contract:** Permanent contract - **Skills:** Training Data, Application Programming Interfaces (APIs), Artificial Intelligence, Computer Vision, Data Architecture, Information Engineering, Data Files, Data Governance, Extract Transform Load (ETL), Database Design, Information Lifecycle Management, Python (Programming Language), Machine Learning, Migration Manager, Tensorflow, Azure Machine Learning, Data Streaming, Management of Software Versions, Parquet, Pytorch, Large Language Models, Apache Spark, Generative AI, Agentic-AI, Data Lakes, Information Technology, Apache Kafka, Machine Learning Operations, Software Version Control, Data Pipelines - **Published:** October 27, 2026 - **Apply:** https://www.careerbuilder.com/job-details/staff-ml-data-engineer-seattle-wa--5e52a98b-f3d8-46d8-b7f4-d5ca6442fbd8 ## About the Role Artificial Intelligence (AI), Solar Power, Safety Compliance, Leadership, High Tech Industry, Data Sets, Telemetry, Benchmarking, Database Design, Migration Strategy, * Data Engineering Depth: 8+ years building and operating large-scale data pipelines and data-lake or lakehouse systems in production ingestion, ETL/ELT, partitioning and storage-format decisions, and the reader/writer libraries consumers rely on. * ML Data Specialty: Has built data pipelines for model training and evaluation, labeled data, and evaluation/benchmark sets with a working understanding of how data quality and versioning move model results. * Lakehouse Architecture: Strong experience with medallion-style layered data architectures and modern table/lake formats (e.g. Iceberg, Delta, Parquet, or comparable), including schema evolution and dataset versioning. * Multimodal Data at Scale: Experience with large multimodal data video, image, sensor/telemetry and the storage and access patterns that make it queryable at scale (denesting, repartitioning, binary-inline vs. reference storage). * Framework Integration: Hands-on with the data side of ML frameworks PyTorch/Lightning dataloaders and Spark and strong Python knowledge. * Governance & Provenance: Practical experience enforcing data governance in pipelines classification, access control, lineage and provenance, retention, particularly for privacy sensitive data. * Technical Leadership: A track record of setting data-engineering direction and leveling up engineers (technical leadership; formal management not required). * Education: Bachelors or Masters in Computer Science, Engineering, or a related field, or equivalent practical experience., * Streaming or near-real-time ingestion from edge/IoT sources into a data lake (e.g. Kafka, Lambda, EMR, or similar). * Append-without-rewrite and hash-indexed dataset techniques on open table formats, and dataset/feature-versioning systems. * Generative-AI data work: fine-tuning and evaluation dataset curation for LLMs/VLMs. * Exposing datasets to AI agents through MCP-style query interfaces, with semantic schema and plain-language documentation for retrieval. * Computer-vision / video annotation tooling and workflows (e.g. Encord, Labelbox, or similar). ## Description This is a senior individual-contributor and technical-leadership role; formal people management is not required. You will partner closely with AI/ML research, the ML platform / MLOps function. You own the data side of the contract that defines what a model consumes and emits and annotation, edge, and infrastructure teams. You should be equally comfortable discussing dataset schema design, storage and partitioning trade-offs for multimodal data, versioning and migration strategy, and the governance controls that keep sensitive video and sensor data safe., * Data Flywheel Ownership: Own the end-to-end loop that converts raw edge telemetry and video into labeled training data, frozen evaluation sets and feeds model outputs back into the next round. * Layered Dataset Pipelines: Build and own the pipelines that register raw source data, standardize it into a single well-defined schema, and join and aggregate it into curated datasets so every team trains, validates, and benchmarks from one consistent store through one reader, rather than copying and reformatting data per use case. * Labels & Annotation Data Lifecycle: Own how labels and semantic annotations are appended to datasets without rewriting source data, then versioned, quality-checked, and served, partnering with annotation and data-operations teams on label production and verification while you own the dataset, storage, and serving side. * Evaluation & Benchmark Sets: Own the frozen, versioned validation and benchmark datasets that make model comparisons valid over time stable enough that an accuracy delta reflects the model, not a shifting dataset including the review and scrubbing discipline required before any set is shared externally. * Dataset Versioning: Own schema and content versioning so producers can evolve datasets without breaking consumers opt-in versions, append-without-rewrite for new fields, and the reader/writer indirection that lets data migrate underneath clients on a controlled rollout instead of forced lockstep migrations. * Framework Integration & Self-Serve Access: Own the read/write libraries and integrations researchers depend on PyTorch/Lightning dataloaders, a simple record-level CRUDL API, and Spark/analytics access and self-service so AI teams stay focused on model development. * Governance Enforced: Make governance machine-enforced in the flywheel rather than documented after the fact classification of clips, frames, labels, and embeddings; scrubbing and anonymization in load jobs; and lineage and provenance for every dataset version, annotation campaign, and training input. * Technical Mentorship: Set the data-engineering standards for the flywheel schema conventions, dataset contracts, quality gates and mentor IC work toward them, growing the function as the team forms.