Data Scientist (Risk & Compliance) vs Analytics Engineer (dbt / SQL): Salary & Career Benchmarks in Switzerland

In Switzerland, Data Scientist (Risk & Compliance) and Analytics Engineer (dbt / SQL) carry the same median salary in our 2026 live benchmark data: both sit at CHF126K for a mid-level hire. That parity reflects overlapping seniority and market demand for both roles right now, not that the roles are interchangeable.

Seniority, tech stack, and location still move pay within each role's own range. Senior practitioners in either discipline can exceed the upper range through specialist skills. See the skills premium section below for the specific certifications and tools that push offers to the top of the range.

While both positions are vital to a modern tech organisation, Data Scientist (Risk & Compliance) and Analytics Engineer (dbt / SQL) have fundamentally different daily workflows.

Data Scientist (Risk & Compliance) focuses primarily on building statistical and machine-learning models for credit risk, fraud detection, and regulatory compliance monitoring within a bank or fintech. Day-to-day work revolves around building and validating credit-risk or fraud-detection models, running model performance monitoring, documenting models for regulatory review, and working with compliance teams on model explainability requirements.

Analytics Engineer (dbt / SQL) focuses on transforming raw data into trusted, business-ready datasets using dbt modelling layers and semantic logic. Their time is spent writing and testing dbt models, maintaining data catalogues, defining shared metric logic with analysts, and enforcing data quality checks across the warehouse.

Transitioning between these two paths is achievable but requires targeted upskilling.

Moving from Data Scientist (Risk & Compliance) to Analytics Engineer (dbt / SQL): Data analysts with strong SQL and a working knowledge of dbt are the most natural fit, since the role sits at the intersection of engineering and analysis.

Moving from Analytics Engineer (dbt / SQL) to Data Scientist (Risk & Compliance):

Neither path requires starting from scratch. Professionals in both roles share underlying technology fluency; the gap is usually domain knowledge and specific tooling rather than core engineering fundamentals.

In Switzerland in 2026, both roles are seeing demand, but with different drivers.

Data Scientist (Risk & Compliance) demand is very high, particularly in Data Scientist (Risk and Compliance) demand in Switzerland is heavily weighted toward the banks and insurers, where FINMA's model-risk expectations require dedicated quantitative risk teams alongside model validation functions.. Analytics Engineer (dbt / SQL) demand is very high, concentrated in Analytics Engineer demand in Switzerland is spread across Zurich's banking and insurance analytics teams and Google Zurich's internal data platforms, with dbt adoption growing fastest at insurers modernising legacy reporting..

Workspace flexibility significantly impacts total compensation value in Switzerland.

Data Scientist (Risk & Compliance) roles score 45% on our remote-friendliness index (Moderate). This is because model-building and validation work can partly be done remotely between committee reviews. Where in-office attendance is required, it is typically driven by risk committee presentations and model-validation sign-off with FINMA-facing compliance teams keep this role largely on-site or hybrid at the major banks.

Analytics Engineer (dbt / SQL) roles score 68% (High). Dbt modelling and warehouse work is largely asynchronous and tool-driven, which keeps remote and hybrid listings common among Zurich scale-ups is the primary driver of flexibility. When office days are required, it is usually for cross-functional metric alignment with finance and product teams pulls analytics engineers into the office, and Swiss Re and Zurich Insurance formalise this into a fixed hybrid schedule.