{"id":5,"date":"2023-01-12T04:11:35","date_gmt":"2023-01-12T04:11:35","guid":{"rendered":"https:\/\/blogs.oregonstate.edu\/lyanita\/?p=5"},"modified":"2023-01-12T04:11:35","modified_gmt":"2023-01-12T04:11:35","slug":"how-i-found-my-career-in-analytics-engineering","status":"publish","type":"post","link":"https:\/\/blogs.oregonstate.edu\/lyanita\/2023\/01\/12\/how-i-found-my-career-in-analytics-engineering\/","title":{"rendered":"How I found my career in analytics engineering"},"content":{"rendered":"\n<p>I didn\u2019t know what I wanted to do in my career for the longest time. I studied business in university, flip-flopping between concentrations, and doing multiple internships in various roles. And despite not knowing what I was going to do post-graduation, I still felt hopeful that I would figure it all out along the way.<\/p>\n\n\n\n<p>At my first company, I decided to participate in a rotational program, one that would give new grads the opportunity to try different roles within the organization. I started out working in supply chain management, then revenue management, and finally marketing insights. At the surface, these roles don\u2019t seem to have many common threads, but underlying them was data and lots of it.<\/p>\n\n\n\n<p>I was absorbed by all the data that the company had, and at the same time, frustrated when I felt limited by what I could do. Sometimes I couldn\u2019t make sense of how unruly the data was, how slow it was to run a simple calculation, or how undefined the data was. Despite the frustrations, I was equally if not more passionate to figure out how to make the process better. That\u2019s when I discovered analytics engineering.<\/p>\n\n\n\n<p>Anyone who has worked in a data role like data engineering or data analytics will have experienced some of the same frustrations I have. However, when you get to the root of these issues, these symptoms occur when there aren\u2019t defined processes, communication, or resources to build a strong data foundation. Many companies build processes on top of poor data foundations, leading to insurmountable loads of tech debt, which only gets exasperated by an immature tech stack for data analytics. All that changed a few years ago with the introduction of dbt, springing the role of the analytics engineer.<br><br>An analytics engineer is meant to bridge the gap between data engineering and analytics. Per dbt, analytics engineers provide clean data sets to end users, modeling data to empower end users to answer their own analytics questions<sup>1<\/sup>.<br><br>You\u2019re probably wondering, how does an analytics engineer differ from a data analyst and a data engineer? Any data analyst will tell you they spend way too much time fixing data on an ad-hoc basis, rather than bringing insights to their organization. And any data engineer will tell you they hate pulling data for end users in the requested form when they could be managing data flow processes. With the rise of the analytics engineer, an organization can have a designated individual that transforms, tests, deploys, and documents data. Analytics engineers apply software engineering best practices to the analytics code base<sup>1<\/sup>, giving way for modularity and quality assurance.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"571\" src=\"https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/6416\/files\/2023\/01\/image-1024x571.png\" alt=\"\" class=\"wp-image-6\" srcset=\"https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/6416\/files\/2023\/01\/image-1024x571.png 1024w, https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/6416\/files\/2023\/01\/image-300x167.png 300w, https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/6416\/files\/2023\/01\/image-768x428.png 768w, https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/6416\/files\/2023\/01\/image.png 1130w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\">Source: dbt<\/figcaption><\/figure>\n\n\n\n<p>By this point, I was a few months into OSU\u2019s computer science program. I loved everything that I was learning about software engineering, from version control to CI\/CD, to agile development. And yet, I wasn\u2019t completely drawn into working in software engineering because I still loved working with data.<br><br>I enjoy being able to improve processes to better enable others in their work. I love using the opportunity I have in analytics engineering to educate users on our data models. But above all else, I love how dynamic the role is. Sometimes there isn\u2019t a clear distinction between a data engineer, a data analyst, and an analytics engineer, partly because of how new the role is. And that\u2019s okay for me. Some days I might spend some time retooling a Looker dashboard. On other days I\u2019m code-reviewing Python scripts that extract data from a source. But the best days are when I\u2019m in dbt, automating a series of transformations to help us organize the data.<\/p>\n\n\n\n<p>It took a few years before I found my calling in analytics engineering. And reflecting on the experience, I think it was a necessary one (partly because the role didn\u2019t exist during my first degree). For anyone who is looking for an opportunity to be part of a modern data team, I would 100% recommend the role of analytics engineering. The tech stack is still evolving, and every day presents an opportunity to learn something new.<\/p>\n\n\n\n<p>Sources:<br>1. https:\/\/www.getdbt.com\/what-is-analytics-engineering\/<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I didn\u2019t know what I wanted to do in my career for the longest time. I studied business in university, flip-flopping between concentrations, and doing multiple internships in various roles. And despite not knowing what I was going to do post-graduation, I still felt hopeful that I would figure it all out along the way. [&hellip;]<\/p>\n","protected":false},"author":13098,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.oregonstate.edu\/lyanita\/wp-json\/wp\/v2\/posts\/5","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.oregonstate.edu\/lyanita\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.oregonstate.edu\/lyanita\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/lyanita\/wp-json\/wp\/v2\/users\/13098"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/lyanita\/wp-json\/wp\/v2\/comments?post=5"}],"version-history":[{"count":1,"href":"https:\/\/blogs.oregonstate.edu\/lyanita\/wp-json\/wp\/v2\/posts\/5\/revisions"}],"predecessor-version":[{"id":7,"href":"https:\/\/blogs.oregonstate.edu\/lyanita\/wp-json\/wp\/v2\/posts\/5\/revisions\/7"}],"wp:attachment":[{"href":"https:\/\/blogs.oregonstate.edu\/lyanita\/wp-json\/wp\/v2\/media?parent=5"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/lyanita\/wp-json\/wp\/v2\/categories?post=5"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/lyanita\/wp-json\/wp\/v2\/tags?post=5"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}