---
title: "Snowflake | Skills We Assign For | Azendo"
description: "Snowflake as a central warehouse — cost control, workload separation, and the Azendo roles assigned for warehouse work."
url: "https://azendo.co/skills/snowflake/"
---

[Skills](https://azendo.co/skills/) Data stores and query 

# Snowflake.

Snowflake is a cloud data warehouse that separates storage from compute, so query capacity can be scaled independently of data volume. It is used as the central analytical store that reporting, BI and data science all read from.

## Where Snowflake fits on a long engagement.

Separating compute from storage solves a real problem: a heavy analytical query no longer competes with everything else for the same resources. It also removes the natural brake on cost. Because capacity is elastic, an inefficient query does not run slowly — it runs fine and produces an invoice, which is a much harder signal to notice.

Well-run Snowflake estates look similar to each other. Separate warehouses per workload, auto-suspend set aggressively, and someone actually reading the query history. None of that is difficult; it just needs an owner, which is precisely what it usually lacks.

## What an assigned team does with Snowflake.

Warehouse cost is the clearest example of something only continuous assignment catches. A query that got slower and more expensive over eighteen months produces no alert and no complaint — it simply appears in a bill that somebody accepts because it grows the way everything grows.

The people who notice are the ones who wrote the model in the first place. That is the argument for assigning warehouse capacity continuously under [managed data services](https://azendo.co/services/data-engineering/) rather than bringing someone in when the invoice becomes a board question.

## What we use Snowflake for.

* One warehouse several teams can share Reporting, data science and application queries isolated from each other, so one heavy job stops blocking the morning dashboard.
* Getting spend under control Query history reviewed and the expensive paths fixed, which frequently costs less than the first month it saves.
* Sharing data without moving it Giving a partner or another team controlled access without building an export pipeline that then needs maintaining.

## How Snowflake capacity is assigned.

Warehouse work is assigned under managed data services, inside your own Snowflake account and under your own billing rather than resold. The reasoning behind delivering this from Thailand is set out in [why we deliver from Thailand](https://azendo.co/why-thailand/).

## Roles we assign Snowflake for

* [Analytics Engineer Data engineering](https://azendo.co/services/data-engineering/analytics-engineer/)
* [Data Engineer Data engineering](https://azendo.co/services/data-engineering/data-engineer/)

## Service lines it sits in

* [Data engineering](https://azendo.co/services/data-engineering/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in data stores and query

* [SQL — skill we assign for](https://azendo.co/skills/sql/)
* [PostgreSQL — skill we assign for](https://azendo.co/skills/postgresql/)
* [MySQL — skill we assign for](https://azendo.co/skills/mysql/)
* [MongoDB — skill we assign for](https://azendo.co/skills/mongodb/)
* [BigQuery — skill we assign for](https://azendo.co/skills/bigquery/)
* [Redis — skill we assign for](https://azendo.co/skills/redis/)
* [Prisma — skill we assign for](https://azendo.co/skills/prisma/)
* [Postgres — skill we assign for](https://azendo.co/skills/postgres/)

## Tell us what your roadmap needs Snowflake for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)