hozah - Senior Data Engineer

• You've owned a data warehouse or platform alone, or as its lead, including being the one who fixes it when it breaks. You can say exactly what you were accountable for and what you personally changed. • You write deep SQL and model data properly on a cloud warehouse such as BigQuery or Snowflake, inside a versioned transformation framework such as Dataform or dbt, with CI around it. You can explain how you turned raw data into measures the business trusts, how a change gets from a branch to production, and what stops a bad one getting there. • You've made a disputed number trusted. You can walk through a specific incident from the last 12 months: how you found it, what the root cause was, and what now stops it happening again. • You work directly with non-technical stakeholders, and you've refused or reshaped a metric definition you thought was wrong. You can say what you said, and what happened next. • You've worked with at least one of change-data-capture or replication, SaaS connectors, or file loads, and know what tends to go wrong. Streaming experience is not required. • You've built the analytics layer yourself for business users (the measures, KPI views and dashboards), not just fed the data underneath it. You can describe something you built that changed a decision. • You've shipped one new data capability end to end, whether that's a machine learning model in production, a near real-time feed or a new data product. You can say who used it and whether it stuck. • You're comfortable setting your own priorities in a fast-moving SME, and you're happy being the only data person in the company. • Experience of GCP itself, Terraform, streaming, Kotlin or another JVM language, or Metabase is welcome, but none of it is required.