WEBVTT

00:00:00.076 --> 00:00:01.596 A:middle
>> My name is Trevor Gurgick.

00:00:01.736 --> 00:00:05.836 A:middle
I'm a business analyst for
Huffington Post, now Huff post.

00:00:05.836 --> 00:00:14.376 A:middle
Basically, you know, obviously, as an analyst,
you're doing things like pulling in the numbers

00:00:14.376 --> 00:00:17.556 A:middle
and kind of connecting the
data of the business back

00:00:17.596 --> 00:00:20.686 A:middle
to the actual, you know, business objective.

00:00:20.796 --> 00:00:24.916 A:middle
So it's a really wonky way of saying
you're taking everything we're collecting

00:00:24.916 --> 00:00:30.356 A:middle
on our consumers, and our operations, things of
that nature, and turning that into, you know,

00:00:30.356 --> 00:00:34.526 A:middle
usable insights for various departments.

00:00:34.526 --> 00:00:39.276 A:middle
So, for me, at Huff Post, that's the
product development team, and like,

00:00:39.276 --> 00:00:43.156 A:middle
then helping them figure out what's going to
be a better product for consumers, editorial,

00:00:43.156 --> 00:00:48.466 A:middle
figuring out what might be better content to
provide to our audiences, or to grow audiences.

00:00:48.936 --> 00:00:52.976 A:middle
Or on the business team, maybe looking for
new sponsorships, or a way to, you know,

00:00:52.976 --> 00:00:55.396 A:middle
improve our ad operations and so forth.

00:00:55.806 --> 00:01:00.746 A:middle
It, a lot of it's traffic patterns.

00:01:00.826 --> 00:01:03.966 A:middle
And basically, you know, what
are consumers clicking on,

00:01:03.966 --> 00:01:07.706 A:middle
what are they seeing, what
are they reading more of?

00:01:08.156 --> 00:01:11.736 A:middle
There's also the opportunity of creating
new ways to capture data like that,

00:01:11.736 --> 00:01:15.976 A:middle
so if maybe you're posing a question to a
consumer, as they're reading an article,

00:01:16.096 --> 00:01:19.526 A:middle
you know, what's their response
if you're surveying folks.

00:01:20.526 --> 00:01:25.216 A:middle
I would say, primarily, I'm looking at
trends of our numbers, when they come in,

00:01:25.276 --> 00:01:30.286 A:middle
just getting a sense of, has anything
changed, you know, what are people consuming.

00:01:30.816 --> 00:01:39.636 A:middle
I spend a large chunk of my day taking maybe
certain areas of that data and dicing that up,

00:01:39.736 --> 00:01:43.786 A:middle
maybe clearing it to figure out what we actually
have, what's pulling, what does it look like,

00:01:44.146 --> 00:01:47.106 A:middle
and letting other teams know what
we might be able to do with it,

00:01:47.106 --> 00:01:49.606 A:middle
and what kind of insights we could provide.

00:01:49.646 --> 00:01:56.866 A:middle
So, you know, maybe like writing a python script
to pull, like the Facebook API for instance,

00:01:56.866 --> 00:01:59.556 A:middle
and figure out, you know, all the video content

00:01:59.556 --> 00:02:02.626 A:middle
that might have been shared or
liked, or so on and so forth.

00:02:02.626 --> 00:02:06.176 A:middle
So I might spend, you know, maybe an hour
on that, you know, pump that through,

00:02:06.176 --> 00:02:11.536 A:middle
pull out the data, and start to really
dice that up and make it more, I guess,

00:02:11.536 --> 00:02:14.246 A:middle
usable and insightful for the rest of the team.

00:02:14.246 --> 00:02:19.916 A:middle
So technology wise, it's a combination
of SQL and python, some Excel,

00:02:19.986 --> 00:02:26.676 A:middle
but python being like the coding language, SQL
being more like a query language to, you know,

00:02:26.746 --> 00:02:28.616 A:middle
pull that data out and organize it.

00:02:28.716 --> 00:02:33.856 A:middle
Definitely a lot of Microsoft Office, things
of that nature, so you can package it up

00:02:33.856 --> 00:02:38.736 A:middle
and present it in a more clear way to
folks who don't use python and SQL.