Skip to main content

Solace Health

Associate Data Engineer (College Grad 2027)

Redwood City, CAfulltimeentryAdded today

About this role

Solace, a Series C healthcare startup, seeks an Associate Data Engineer to join its Redwood City office and build data pipelines powering patient advocacy technology. You'll work with Python, Airflow, dbt, and Snowflake to ship production code from day one, gaining hands-on mentorship from senior engineers while owning the full lifecycle of real data infrastructure.

What you'll do

  • Develop and deploy production ETL pipelines in Python, Airflow, and dbt that process billions of rows monthly
  • Own data pipelines end-to-end, from design through deployment and monitoring in production
  • Debug production data issues, refactor transformations, and improve pipeline reliability
  • Learn and apply infrastructure-as-code practices using Terraform and AWS services
  • Participate in code reviews, architecture discussions, and data modeling decisions
  • Build across the full data platform stack: ingestion, orchestration, transformation, and analytics on Snowflake

What they're looking for

  • Python programming
  • ETL/data pipeline development
  • SQL and data modeling
  • Airflow or workflow orchestration
  • dbt (data build tool)
  • Snowflake or cloud data warehousing
  • AWS services and cloud infrastructure
  • Terraform or infrastructure-as-code
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Solace Health

Solace Health builds data infrastructure and pipelines designed to enhance patient outcomes in healthcare. The company is hiring Data Engineers to architect robust data systems and collaborate across teams to deliver reliable data solutions.

View all jobs at Solace Health

Likely interview questions

  • Walk us through your experience building ETL pipelines or data workflows—what was your process from requirements to production?
  • Tell us about a time you debugged a complex data issue. How did you approach it?