This is a software engineering and architecture role first.You’llwrite and ship production code, own the tests and CI around it, andoperatewhat you build — designing the interfaces, libraries, and primitives other teams build on, with the versioning, backward-compatibility, and reliability guarantees that implies. Your first six months should produce running systems, not documents. If your recent work has been mostly diagrams, roadmaps, and specs, thisisn’tthe right fit.

You’llwork horizontally across Data Engineering, Analytics, Cloud Infrastructure, and Enterprise Applications as the technical reference point for howteamsmodel, catalog, and expose data, andyou’llregularly leadcross-team technical initiatives.

WhatYou’llOwn

• Treat the platform as a product.Know your consumers — analysts, engineers, applications, AI tools — and where today’s experience falls short. Drive a roadmap measured on adoption, trust, and time-to-answer, and make the case for foundational investment with evidence of consumer need. Ship the sharedprimitivesother teams build on top of — not one-off deliverables, and not starter kits that fork and diverge.

• ML and AI asa capabilityShip the first governed features analysts can apply to trusted data products themselves: anomaly detection over metrics, forecasting, segmentation, natural-language query against the semantic layer. Build them as repeatable capabilities with evaluation, monitoring,driftand cost visibility from day one — not a portfolio of bespoke models. Design how AI tools and agents reach the platform (MCP or comparable) as a core interface held to the same query-safety and permission guarantees as any other consumer — not a side channel around the controls.

• Solve the cross-store problem.Arlo’s data lives in systems that were never designed to be joined — DynamoDB for operational and device data, Databricks for analytics, plus Oracle EBS, Amplitude, andKlaviyo Design the identity resolution, referential integrity, and consistency semantics that let a consumer trust a join across them. Define query-safe access patterns so a dashboard, application, or agentcan’toverwhelm an operational store or quietly return a wrong answer — and a permission model that holds across systems with entirely different native access controls.

• Architecture.On that foundation, design Arlo’s semantic and metric layer and the catalog, so business terms, metric definitions, and ownership are consistent, discoverable, and reusable. Define data product contracts — schemas, ownership, freshness and quality SLAs, access patterns — includingwhat’ssafe to expose to dashboards, applications, and AI tools.

• Governance.Build metadata, lineage, and access-control models into the platform itself, so governance is a property of the system rather than a manual review. Define what “trusted” means for a data product at Arlo, and make that trust visible and checkable. Separate foundational investment from one-off requests, and partner with Data Engineering, Analytics, and AI engineering leadership on build-vs-buy and sequencing.

WhatYou’llBring

• AI and LLM systems.Production experience building with LLMs — retrieval and natural-language interfaces over structured data, context and prompt design, and the evaluation, guardrail, and cost controls that make them safe to put in front of non-technical users. Shipped andoperated, not prototyped.

• ML as a platform capability.Stood up from the ground up and made usable by people whoaren’tML engineers — feature definition, training and serving paths, evaluation, and drift and quality monitoring.

• Lakehouse depth in production.Unity Catalog, Delta Lake, medallion architecture, Lakehouse design patterns — with metadata, lineage, and governance designed in rather than bolted on. We run Databricks; deep production experience on a comparable platformtransfers

• Heterogeneous data integration.Production experience reconciling data across stores with different consistency models, key spaces, and access controls — identity resolution and referential integrity without shared keys, and query patterns that protect operational systems from analytical and agent workloads.

• Enterprise data architecture.Dimensional and semantic modeling, master data and ownership models, data contracts, and taxonomy design across multiple business domains and stacks. Not a single-team data mart — something several consuming teams depend on.

• AWSatscale.AWS data services (DynamoDB, Redshift, Glue, or equivalents) in production. Oracle EBS, Amplitude,Klaviyo, or similar enterprise and product-analytics sources are a strong plus.

• Programmatic data access.Access control and audit design for non-human consumers, and familiarity with MCP or comparable tool-callable interfaces.

• Depth and range.10+ years in data engineering or data platform roles, including production ownership ofsystems multiple teamsdependon.

• Coding.Strong SQL and Python (or another general-purpose language), plus the testing, code review, and production ownership that go with shipping code other teams depend on.

• Adoption without authority.A track recordof getting a platform capability adopted by teams thatdon’treport to you.

Nice to Have

• Data catalog and governance tooling (Collibra, Atlan, or similar).

• A regulated or compliance-sensitive data environment.

• Replacing dashboard and reporting sprawl with governed self-service.

Ready to help build the data foundation behind the next generation of smarter, safer homes?We’dlove to hear from you.

The pay range for this position reflects the minimum and maximum target for new hire salaries at commencement of employment and is expected to be between USD$225,000-300,000/year However, base pay offered may vary depending on multiple factors, including role, job-related knowledge, skills, relevant education and experience. The total compensation package for this position may also include other elements, including bonus, equity, and a full range of benefits. Details of all benefits will be provided if an employee receives an offer of employment.