Where you are, and where you’ll be:
You care about data. You believe in enabling data-driven decisions. You care about accuracy, consistency, cleanliness; you care about reliability. You already care about data enough to be aware of the different categories of concerns around it. Cleanliness of the data itself, the kinds of things that makes access to data slow, and the problems that can prevent access to data (CAP, for example), or, worse, gives you wrong data.
By three months in, you’ve hit your stride, understand our existing data infrastructure, and are on your way to a plan for what’s next. Within a year, we should have a significantly better data infrastructure, and a significantly more data oriented company, with incremental wins along the way.
What we’d like to see accomplished:
One of your first tasks will be to consolidate all our data. Anyone who needs data should be able to focus on asking questions of it, not fetching it and reformatting it. To this end, it’ll be important to, wherever reasonable, minimize disparities in format of data as well as how/where it’s stored. Once you’ve accomplished this, it’ll be important to consider our data and query patterns, and decide where it’s time to break away from uniformity for the sake of ease of use, performance, etc.
Another thing you’ll get to right away will be to help the team learn enough to consider data collection, persistence and analysis concerns during design and development as a result of your joining. We also hope you can teach us how data can inform our development, product decisions, and be used in production, to support students. Basically, we want you to either bring your existing knowledge, or consolidate what you can find by digging through research and industry discussions, and distill it to a consistent approach to data.
Salary and compensation
$100,000 — $175,000/year
Equity
0.03 – 0.1

