You can now reuse column aliases. Define an alias once in the SELECT, and use it later in the same SELECT and in WHERE. No more copy-pasting the same expression, and no CTE just to filter on a calculated column.
I've written the "wrap it in a CTE so I can filter on it" pattern more times than I'd like to admit. Turns out a good chunk of my SQL career was moving the same expression from line 4 to line 12.
A few things to know before you get excited:
- It's off by default. An admin has to turn on reusable_column_aliases_mode for the project or the whole organization.
- Table columns win. If your alias has the same name as a real column, BigQuery uses the column, and your query quietly returns something else.
- Aliases built on aggregates or window functions still can't go into WHERE.
First AI started writing our queries. Now the queries don't even need to be long.
Pretty soon the analyst job description will be "knows which flag to turn on". Should I start updating my CV?
Want a stronger data analyst role or a raise? Grab the FREE Product Analyst Playbook and get the exact roadmap to your next offer.




