What do Job Descriptions tell us about Analytics Engineering in 2026?

While reading job postings, I often think about how much they vary from one other. "Do they actually mean this, or is this something everyone writes?". I wanted to quantify these traits, and that's what the talk will share. I've classified hundreds* of European postings for Analytics Engineers. My attempt is to read between the lines of what these job descriptions reveal beneath what is written, and also check, statistically, which of these signals move together.

The strongest pairing in the dataset is also the least disputable: company stage and mission type move together almost deterministically - early-stage teams hand out greenfield builds, mature teams hire almost entirely to fix and scale what already exists. "We're an early-stage startup" is, in practice, a reliable proxy for "you'll be building from scratch." Other pairings are murkier and more interesting: "we care about data quality" shows up almost everywhere - at cautious fintechs and scrappy low-risk startups alike. This signals that at this current point, data quality and trust as a foundation is a universal concern. And one relationship I was confident about early on, between who a role serves and how much autonomy it carries, held at 120 postings and fell apart at 270 - a reminder that a pattern in a small sample can look real right up until it isn't.

For anyone writing a job description or reading one, I intend for this to be a field guide to which lines are worth trusting, which ones every posting says, and how to discern which roles might have a good fit for you based on associated characteristics.