Mostly harmless, conspicuously useful
The Hitchhiker's Guide to Becoming an Analytics Engineer
DON'T PANIC. An Analytics Engineer does not spend the day making charts prettier, although charts do occasionally need saving from themselves. They turn the raw records a business collects—orders, sign-ups, support requests, deliveries, and other digital footprints—into reliable tables and shared definitions that people can use to make decisions. The job is part translator, part builder, and part professional sceptic: make the numbers understandable, reusable, and difficult to accidentally reinterpret on a Monday morning.
Level 1 · Novice
Learn to ask the data a question before asking it to run the company
At the first stop, you discover that data is simply recorded information, that databases are organised places to keep it, and that an Analytics Engineer helps people retrieve it without creating twelve competing versions of “monthly revenue.”
Start with a small business question: “How many customers ordered last week?” The answer usually lives in rows and columns, much like a spreadsheet, except the spreadsheet has become far too large to open without your laptop considering a career change. SQL is the language used to ask a database for those rows. You write a request, the database finds matching information, and you inspect whether the answer makes sense.
The important habit is not memorising every SQL command. It is learning to be precise about what you mean. Does “customer” include cancelled accounts? Does “last week” mean the last seven days or the previous calendar week? A number is only useful when the question behind it is clear. Your first models should therefore be small, visible, and easy for another person to check.
Get comfortable following the path from an event to a table to a question. A purchase event becomes a record; records become a table; a table can answer a question. Once you see that chain, analytics stops being a cloud of mysterious dashboards and becomes a set of understandable building blocks.
Words from the spaceship manual, translated
- Data
- Recorded information about something that happened or exists, such as a customer order, a website visit, or a product. Data becomes useful only when its meaning and context are understood.
- Database
- Software that stores organised information so people and applications can add, change, and retrieve it. It is a managed collection of records, not a giant spreadsheet with a security badge.
- SQL
- A language for asking a database questions and shaping the answer. It lets you select records, combine related tables, calculate totals, and make the logic of an analysis repeatable.