Timestamps, Timezones, and AT TIME ZONE

Concepts covered: sqlTimezones

Timezone-aware aggregation is the area where code most often graduates from working-for-the-easy-case to surviving-the-edge-cases. The discipline is consistent: storage is UTC, queries are explicit about which zone they aggregate in, conversions happen at named points in the query. Once you write this consistently, the edge-case bugs stop shipping; until you do, they keep showing up in the dashboards finance reconciles against. The canonical timezone-aware aggregate Reading the conversion The transactions table stores txn_ts as TIMESTAMPTZ in UTC. The regions table has a region_timezone column ('America/Los_Angeles', 'Asia/Tokyo'). The AT TIME ZONE clause converts each transaction's UTC timestamp to the region's local time. DATE_TRUNC then operates on local time, so the day boundaries matc

About This Interactive Section

This section is part of the Date Arithmetic: Intermediate lesson on DataDriven, a free data engineering interview prep platform. Each section includes explanations, worked examples, and hands-on code challenges that execute in real time. SQL queries run against a live database. Python runs in a sandboxed Docker container. Data modeling problems validate against interactive schema canvases. All content is framed around what data engineering interviewers actually test at companies like Meta, Google, Amazon, Netflix, Stripe, and Databricks.

How DataDriven Lessons Work

DataDriven combines four interview rounds (SQL, Python, Data Modeling, Pipeline Architecture) with adaptive difficulty and spaced repetition. Easy problems get harder as you improve. Weak concepts resurface until you master them. Your readiness score tracks progress across every topic interviewers test. Every lesson section ends with problems you solve by writing and running real code, not by picking multiple-choice answers.