Data scientist: A day in the life
Over the last six years, I’ve made a living from modeling, primarily in New York City but also in Seattle and various countries worldwide. While I enjoy dressing up in NYC’s trendiest streetwear, by “modeling,” I mean predictive modeling, a central element of the applied data science I’ve done throughout my career.
I started my data science journey at Custora, a New York-based company that built predictive marketing software for eCommerce businesses. After Custora was acquired by Amperity, I joined their data science team, where I’m now a lead data scientist. Amperity is partially remote, which has allowed me to work from anywhere with solid Wi-Fi and even more solid espresso.
My experience in data science has been focused on building machine-learning pipelines as part of enterprise software. Such work relies more heavily on engineering prowess, infrastructural considerations, and high performance both computationally and efficaciously (I had to look that one up.) It also requires regular coordination between data scientists, machine learning engineers, back-end engineers, and product managers.
Building machine learning pipelines is a large undertaking – I’ve worked on projects that took anywhere from two months to two years from beginning to end. Still, each project follows a similar pattern, from ideation to prototyping to delivery.
The rhythms of data science projects
There is no “typical” day in data science. Yet there are common stages to a project that require me to flex different muscles, take on different responsibilities, and interact with different stakeholders.
Since our work takes place on such a large scale, in the interest of productivity, we must break that work down into more digestible pieces. If we have a two-month goal, we’ll split that into eight two-week sprints, each with its milestones. We then use tickets to break apart those milestones into specific code contributions.
Each data scientist on our team covers an incredibly large surface area – data acquisition and QA, exploratory data analysis, feature engineering, algorithm development, model evaluation, and delivery. In this sense, we often say we’re looking for “unicorns” to join our team, applied data scientists with the skills and interest to excel and bring innovation to the components across that surface area.
When we look for entry-level data scientists, more than anything else, we’re looking for that curiosity and the ability to be a self-starter. If you’re willing to soak up as much information as you can over your first few months, work consistently on your coding skills, and then dive into complicated, interdisciplinary problems, you might be a good fit for a data science team.
