Drimva

Shield AI

Data Engineer, Finance (R6329)

San Diego, California · Full-time · Posted Oct 21, 2026

Experience
Minimum 2 years of related experience.
Education
Bachelor’s degree in computer science or a related technical or quantitative field.

About the job

Builds and operates governed Finance data pipelines, semantic-layer infrastructure, and production services for analytics, planning, and AI-enabled workflows on Databricks.

What you'll do

  • Build and operate scalable data pipelines and integrations for Finance products; develop governed semantic-layer infrastructure.
  • Establish pipeline observability, data-quality controls, and resilient operations; engineer services for Databricks Genie and other AI-enabled workflows.
  • Use AI coding assistants with independent validation, optimize platform costs using FinOps practices, and collaborate on architecture and data ownership.

What they ask for

  • Bachelor’s degree in computer science or a related technical or quantitative field.
  • Minimum 2 years of related experience and hands-on production data engineering experience with SQL and Python or PySpark.
  • Experience with cloud data platforms, orchestration, data modeling, and governed serving patterns; ability to design for observability, recoverability, security, and maintainability.
  • Proficiency with AI coding assistants and practical experience enabling AI capabilities on enterprise data; strong cross-functional collaboration and production ownership.

Nice to have

  • Experience with Databricks, Delta Lake, cloud infrastructure, and deployment automation.
  • Experience developing AI application backends, model integrations, or LLM-based workflows; FinOps, financial data, or enterprise-system integrations.

Tools

Databricks, SQL, Python, PySpark, Snowflake Cortex, Delta Lake

AI focus

Enables AI applications and Finance workflows on enterprise data, including Databricks Genie; uses AI coding assistants and independently validates generated work.

Model-written summary · the original posting is authoritative

First seen Oct 29, 2026 · Last verified Nov 5, 2026 (UTC)