<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Lola on Medium]]></title>
        <description><![CDATA[Stories by Lola on Medium]]></description>
        <link>https://medium.com/@Lor111?source=rss-105411e1a409------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Lola on Medium</title>
            <link>https://medium.com/@Lor111?source=rss-105411e1a409------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:25:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Lor111/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Top 10 metrics for a Product Team — Castor Blog]]></title>
            <link>https://medium.com/@Lor111/top-10-metrics-for-a-product-team-castor-blog-bccabbab400c?source=rss-105411e1a409------2</link>
            <guid isPermaLink="false">https://medium.com/p/bccabbab400c</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[metrics]]></category>
            <dc:creator><![CDATA[Lola]]></dc:creator>
            <pubDate>Thu, 12 May 2022 10:01:05 GMT</pubDate>
            <atom:updated>2022-05-12T10:01:05.102Z</atom:updated>
            <content:encoded><![CDATA[<h3>Top 10 metrics for a Product Team — Castor Blog</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_O9ir1cdhQHmja5N.png" /></figure><h3>Introduction</h3><p>Metrics are crucial to strategise, take the best decisions, identify risks before they become reality or even just celebrate your team’s success. Tracking the right metrics is becoming harder with too much data to keep a cold head. This reflects directly on the market as we witness a growing demand for data-driven product managers (we even heard the term engineer-PMs…). Why is that? Product managers must constantly find innovative ways to increase revenues, gauge product usability, increase customer loyalty and product performance. With ever-growing data, the need to understand, digest and react quickly on the product data is as critical, as having someone who puts in place the correct KPIs to make sense of this data. On top of that, you need someone capable of bridging the gap between all teams: a product manager which speaks the same language as business, technical and management teams.</p><p>Today, we’ve brought to you the top 10 metrics your data-savvy product team should absolutely track to ensure you are extracting 100% value out of your product, in other words monitoring the success of your company.</p><p>As shown below, those KPIs span the full product production chain.</p><p>‍</p><blockquote><em>Monthly Recurring Revenue</em></blockquote><blockquote><em>Customer Lifetime Value</em></blockquote><blockquote><em>Customer Acquisition Cost</em></blockquote><blockquote><em>On-time Delivery</em></blockquote><blockquote><em>Team Velocity</em></blockquote><blockquote><em>DAU/MAU ratio</em></blockquote><blockquote><em>Session Duration</em></blockquote><blockquote><em>Onboarding Time to Value</em></blockquote><blockquote><em>Churn Rate</em></blockquote><blockquote><em>Net Promoter Score</em></blockquote><p>‍</p><h3>1. Monthly Recurring Revenue (MRR)</h3><h4>What is it?</h4><p>💡 The <strong>Monthly recurring revenue</strong> measures your product’s total revenue over the course of one month.</p><h4>Why is it important?</h4><p>Sometimes deemed to be the most important metric out there for financial growth, the MRR will allow you to gain key insights into the subscription behaviour of your customers. The MRR has gained great popularity because it tracks your business’s performance, it allows for easily planning and forecasting your growth and finally it makes budgeting more transparent: you immediately know what to expect in revenue from your platform at any given month in time.</p><h4>How to calculate it?</h4><p>To measure MRR every month, you should start with the MRR at the end of last month, add the revenue from new subscriptions and subtract the churn from customers lost this month.</p><h4>What does it look like?</h4><p>When looking at the MRR, we should look at its trend over time. This trend will reveal critical information about the health of your product as it is directly related to the amount of revenue coming in. This trend will help management with decision making, scaling the business and predictability.</p><p>‍</p><h3>2. Customer Lifetime Value (CLV)</h3><h4>What is it?</h4><p>💡 The <strong>Customer Lifetime Value </strong>is a metric indicating the total value a business can reasonably expect from a single customer account throughout the business relationship.</p><h4>Why is it important?</h4><p>Measuring Customer Lifetime Value is key, as it allows you to recoup the investment required to earn a new customer. It allows you to predict future revenue and measure long-term business success. This metric is key for acquiring and retaining highly valuable customers. It is also a great metric to compare with <strong>Customer Acquisition cost</strong>. In fact, you better ensure Customer Lifetime Value is higher than Customer Acquisition costs. Otherwise, you might well be wasting your resources.</p><h4>How to calculate it?</h4><p>Customer Lifetime Value is calculated by adding the costs associated with converting prospects into customers (marketing, advertising, sales personnel, and more) and dividing that amount by the number of customers acquired. This is typically figured for a specific time range, such as a year or a fiscal quarter.</p><p>With:</p><ul><li><strong>Average purchase value</strong> — the value of all customer purchases over a particular timeframe (a year is usually easiest), divided by the number of purchases in that period</li><li><strong>Average purchase frequency</strong> — divide the number of purchases in that same time period by the number of individual customers who made a transaction over the same period</li><li><strong>Average customer lifespan</strong> — the average length of time a customer continues buying from you</li></ul><h4>What does it look like?</h4><p>You should be displaying the Customer Lifetime Value as a <strong>trend</strong>. In fact, observing how this trend evolves reveals a lot about your ability to retain customers and exploit existing customer relationships. As mentioned above, it is also interesting to compare the Customer Lifetime Value with other numbers, such as the Customer Acquisition Cost to gauge your profitability.</p><p>‍</p><h3>3. Customer Acquisition Cost (CAC)</h3><h4>What is it?</h4><p>💡The <strong>Customer Acquisition Cost</strong> is the amount of money it costs your company to acquire a new customer.</p><h4>Why is it important?</h4><p>This is one of the first metrics you’ll want to measure. Measuring this metric allows you to make important decisions for keeping your company afloat. For example, you don’t want to be spending too much money on customer acquisition if it doesn’t yield a profit. This metric helps you decide how much money should be spent on attracting customers while keeping your company profitable.</p><h4>How to calculate it?</h4><p>CAC is calculated by adding the costs associated with converting prospects into customers (marketing, advertising, sales personnel, and more) and dividing that amount by the number of customers acquired. This is typically figured for a specific time range, such as a year or a fiscal quarter.</p><h4>What does it look like?</h4><p>When looking at Customer Acquisition Costs, looking at a number at a specific point in time won’t get you far. It should be displayed:</p><ul><li>As a <strong>trend</strong>, allowing to understand the <strong>evolution</strong> of the acquisition cost. It tells you nothing to know that your customer acquisition cost is $10. However, it tells you a lot to know that your CAC is $10 today while it was $5 last year. Analysing this trend allows you to compare your performance over different time periods.</li><li>In constant comparison with the value yielded by customers. If the customer acquisition cost is $10, while each customer brings about a value of $7, you’re clearly doing something wrong.</li></ul><p>‍</p><h3>4. On-Time Delivery</h3><h4>What is it?</h4><p>💡 <strong>Delivery on time</strong> tracks the performance of your product against time commitments, it ensures your team commits to their development timeliness and increases customer loyalty.</p><h4>Why is it important?</h4><p>Measuring on-time delivery of your product is critical to increase your customer retention and revenue. The metric is key to building customer relationships. This metric also reveals bottlenecks in your team’s development process. In general, issues that emulate from on-time delivery problems touch inventory, order supply and delivery issues. Tracking this metrics allows your team to catch gaps, adjust and prevent customer impact.</p><h4>How to calculate it?</h4><p>OTD is often measured within a date range.</p><h4>What does it look like?</h4><p>Again, the on-time delivery metric should be displayed as a trend. In fact, you need to be able to compare the delivery issues or improvements across different time periods to be able to detect for example seasonality patterns and prevent them in the future.</p><p>‍</p><h3>5.Team Velocity</h3><h4>What is it?</h4><p>💡 The <strong>Team Velocity </strong>metric is the average amount of work your product team produces in one sprint. It is what we call an “Agile” work method.</p><h4>Why is it important?</h4><p>Team velocity is used to estimate the amount of work and delivery date of product features/developments. It is useful for planning but should be used with caution. When correctly monitored and reported, the metric allows product managers to validate roadmaps and estimate how much time upcoming projects will take.</p><h4>How to calculate it?</h4><p>We calculate team velocity by counting the total units of work in a certain time period (usually between 1–3 weeks). Velocity is always measured at a team level.</p><p>We must also define story points, which are points allocated to different tasks within a user story.</p><p>An example would be: XYZ product team finished 15 stories during a two-week sprint. The team had previously defined that each story has a value of 4 story points each. Then the team’s velocity is 45 story points/sprint.</p><h4>What does it look like?</h4><p>Again, velocity tends to be displayed as a trend. This allows your team to have an idea of the “historical velocity” i.e. visualise the progress of your team. It sometimes is plotted next to an “ideal” scenario trend to compare performances.</p><p>‍</p><h3>6. DAU / MAU Ratio</h3><h4>What is it?</h4><p>💡 The <strong>Daily Active User (DAU) / Monthly Active User (MAU)</strong>, represents the number of active users/subscribers per day or month. A unique user visits an application or website at least once within a period of time.</p><h4>Why is it important?</h4><p>What really maters here is the active part of DAU or MAU. It is deemed to be, after revenues, the most valuable metric of product growth. The metric is helpful to evaluate the traction of your product by giving context to the level of engagement of your users. It is directly related to user retention. The ratio can be used then to forecast, budget or take decisions to develop new features or cease others in product development.</p><h4>How to calculate it?</h4><p>With:</p><p><strong>Daily Active User (DAU)</strong> — “Active users” are customers who signed on the product and performed tasks. This is, to some extent, subjective to your product and depends on what user actions you consider important on a daily basis.</p><p><strong>Monthly Active User (MAU)</strong> — “Active users” are customers who complete certain tasks per month. This is, to some extent, subjective to your product and depends on what user actions you consider important on a monthly basis.</p><h4>What does it look like?</h4><p>Simply put, the higher the ratio, the sticker the product is. DAU/MAU ratio is one out of many metrics measuring customer activity. It is for that reason, that it is always better to track this ratio alongside other KPIs as user retention, CAC and churn rate. The ratio can also be dependent on industry benchmarks (i.e. social apps are very sticky vs. travelling apps).</p><p>‍</p><h3>7. Session duration</h3><h4>What is it?</h4><p>💡 <strong>Session duration</strong> represents the time a user spends on your product, on average.</p><h4>Why is it important?</h4><p>Session duration is a good kick-start to identify whats works and what doesn’t with your product. It helps you track your customer journey.</p><h4>How to calculate it?</h4><h4>What does it look like?</h4><p>The session duration KPI can be tracked using histograms displaying how much time each cluster of consumers spend on your product. In fact, you need to be able to compare the churn rate across different time periods but also across different groups/types of consumers.</p><p>‍</p><h3>8. Onboarding Time To Value</h3><h4>What is it?</h4><p>💡 The <strong>onboarding time to value </strong>metric is how long it takes for users from inception of onboarding to extract value from your product.</p><h4>Why is it important?</h4><p>This metric is crucial to track as it has a direct impact on your revenues (by reducing redundant/unnecessary onboarding costs) and on your customer retention. The analysis that comes out of this metric will help you increase the frequency of usage of your product as well as increase conversions. Put simply, the sooner your customer feels the value, the less likely is he to abandon your product. A low TTV translates into a faster return on investment.</p><h4>How to calculate it?</h4><p>There are different ways to measure time to value. Of course, it is dependent on your customer’s definition of value and their needs, as well as your business model. Generally speaking, we measure the TTV by:</p><h4>What does it look like?</h4><p>Time to value is complex to compare as it is highly dependent on the industry, the different clusters of your clientele and your product at hand. Product teams usually visualise Time to Value on a dashboard to witness its’ evolution over time.</p><p>‍</p><h3>9. Churn Rate</h3><h4>What is it?</h4><p>💡 <strong>Customer Churn </strong>refers to the number of customers you’re losing in a predetermined time period.</p><h4>Why is it important?</h4><p>Churn rate allows you to know how many customers are deciding to leave the business and helps you understand how this is impacting revenue.</p><h4>How to calculate it?</h4><p>To calculate churn rate, you’ll have to know the number of customers you had at the beginning of the time period and the number you lost over this same time period. You then divide the number of lost customers by the number of total customers at the start of the time period. Finally, multiply this number by 100 to obtain a percentage.</p><p><strong><em>xample:</em></strong> if your business had 250 customers at the beginning of the month and lost 10 customers by the end, you divide 10 by 250. The answer is 0.04. You then multiply 0.04 by 100, resulting in a 4% monthly churn rate.</p><h4>What does it look like?</h4><p>Your churn rate should be displayed as a trend. In fact, you need to be able to compare the churn rate across different time periods. This allows noticing when there is a spike in the churn rate so that you can act quickly upon it.</p><p>‍</p><h3>10. Net Promoter Score</h3><h4>What is it?</h4><p>💡The <strong>Net Promoter Score (NPS) </strong>is for your customers to score the quality of your product’s service. It gives a sense of the number of loyal customers, who recommend your product versus customers who dislike your product.</p><h4>Why is it important?</h4><p>Bain &amp; Co., the initiators of the metric, have established that a good NPS can yield 20–60% of organic growth. This tell us already indicates the importance of being aware of your NPS. But also, there is a strong correlation between your employees’ motivation, reaction and involvement in your product with the NPS. This metric allows companies to constantly build awareness and improve the experience of their customers: it is a good business health indicator.</p><h4>How to calculate it?</h4><ul><li>Promoters: users who score your product and service between 9–10 points</li><li>Detractors: users who score your product and service between 0–6 points</li><li>Others are called neutrals and are users who score your product and service between 7–8 points</li></ul><h4>How does it look like?</h4><p>The NPS score is usually looked at on a scale from -100 to 100. Most frequently, it should be also studied as a trend in order to depict your customer’s satisfaction over time. Bear in mind that it is important to know your industry and its’ benchmark as NPS may vary considerately across industries.</p><h3>About us</h3><p>We write about all the processes involved when leveraging data assets: from the <a href="https://notion.castordoc.com/">modern data stack</a> to data teams composition, to data governance. Our <a href="https://www.castordoc.com/about/blog">blog</a> covers the technical and the less technical aspects of creating tangible value from data. If you’re a data leader and would like to discuss these topics in more depth, join the <a href="https://notion.castordoc.com/unsupervised-leaders">community</a> we’ve created for that!</p><p>At Castor, we are building a data documentation tool for the Notion, Figma, Slack generation.</p><p>Or data-wise for the Fivetran, Looker, Snowflake, DBT aficionados. We designed our catalog software to be <strong>easy to use, delightful and friendly.</strong></p><p>Want to check it out? <a href="https://meetings.hubspot.com/xavier76/trist-xav-calendar">Reach out to us</a> and we will show you a demo.</p><p>‍</p><p><em>Originally published at </em><a href="https://www.castordoc.com/blog/top-10-metrics-for-a-product-team"><em>https://www.castordoc.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bccabbab400c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Analytics Engineering?]]></title>
            <link>https://medium.com/castor-app/what-is-analytics-engineering-467c86e5d45?source=rss-105411e1a409------2</link>
            <guid isPermaLink="false">https://medium.com/p/467c86e5d45</guid>
            <category><![CDATA[analytics-engineer]]></category>
            <category><![CDATA[data-team]]></category>
            <category><![CDATA[analytics-engineering]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Lola]]></dc:creator>
            <pubDate>Mon, 03 Jan 2022 14:06:25 GMT</pubDate>
            <atom:updated>2022-01-10T14:57:17.478Z</atom:updated>
            <content:encoded><![CDATA[<h4>The emergence of a new role at a crossroads between business and engineering</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*S-fM12suzWd6KgIJ.png" /></figure><p>As you read the title, you probably thought: <strong>“Great, and another job hits the stack: what on earth is an Analytics Engineer now?”</strong></p><p>You almost kept scrolling, but if you made it up to here, it’s probably because the weird juxtaposition of “analytics” next to “engineer” caught your attention. And rightly so: for many of us analysts are not exactly highly technical engineering roles and vice versa. But let’s face it: the world has jumped forward and today, Python, R and SQL are basic requirements to many jobs. The worlds of engineering and analytics are slowly merging to become one, and today we want to discuss the intersection of both areas: here sits <strong>the Analytics Engineer.</strong></p><p>And yes, we agree with you, these days it seems that any excuse is a good one to create “new, essential tech jobs”, making it all so overwhelming to keep track of, but more seriously it also gives the impression that these roles are all very much <em>Fugazi, Foogazi</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgfycat.com%2Fifr%2Funrulyethicalarcticseal&amp;display_name=Gfycat&amp;url=https%3A%2F%2Fgfycat.com%2Funrulyethicalarcticseal-the-wolf-of-wallstreet-matthew-mcconaughey&amp;image=https%3A%2F%2Fthumbs.gfycat.com%2FUnrulyEthicalArcticseal-size_restricted.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=gfycat" width="1142" height="474" frameborder="0" scrolling="no"><a href="https://medium.com/media/ed33ddd19ab639807525e64748b8f3b0/href">https://medium.com/media/ed33ddd19ab639807525e64748b8f3b0/href</a></iframe><p>But this time, everything seems to indicate that the Analytics Engineer is here to stay.</p><p><strong>Here is the deal:</strong></p><p>Analytics has developed from a support to an advisory role, taking a driver seat in product innovations (setting and determining product KPIs, roadmaps, etc.). On the other hand, the data engineering role can, to a large extent, be automated.</p><p><strong>Why does it matter?</strong></p><p>Because whether you have a handful of data engineers or only a few data analysts with some coding skills on your team*,* when these worlds converge, you will need Analytics Engineers to act as the bridge between the producers and the consumers of your data.</p><p>In the following article, we’ll cover <strong>the rise of the Analytics Engineer</strong>, we’ll define <strong>the key responsibilities of Analytics Engineers</strong> and guide you in <strong>identifying your next Analytics Engineer.</strong> All of this to ultimately help you understand <strong>whether your organization needs one</strong>.</p><p>‍</p><h3>The rise of the Analytics Engineer: How did it all start?</h3><p>To grasp why Analytics Engineers are here to stay, we must understand where it all started. Originally coined two years ago, by Michael Kaminsky, the term came from the ground-up, when data people experienced a shift in their job: they went from handling data engineer/scientist/analyst’s tasks to spending most of their time fixing, cleaning, and transforming data. And so, they (mainly members of the <a href="https://www.getdbt.com/dbt-labs/about-us/">dbt</a> community) created a terminology to describe this middle seat role: the Analytics Engineer. <strong><em>The real question becomes: How long ago and why did we experience this?</em></strong></p><p>‍</p><p>Three big changes in the data tooling stack are at the core of the development of the Analytics Engineer:</p><ol><li><strong>The emergence of cloud-based data warehouses brought about a shift from the ETL (Extract, Transform, Load) to the ELT (Extract, Load, Transform) model.</strong></li></ol><p><em>What does that mean? Not so long ago, if you wanted to get data into your warehouse, someone had to extract it by writing code to get the API, transform it, and finally load it into the data warehouse. </em>But today, the reality is that modern cloud data warehouses <em>(database services, hosted by public cloud, accessed remote)</em> automate the Extract &amp; Load steps so we can now do everything in SQL. This means ownership went from software engineers to land in the hands of less technical, business-savvy profiles handling simple SQL queries once it has arrived in the warehouse.</p><p>2. Second, the <strong>growth of data pipeline services</strong> (eg. Fivetran or Stitch) means that data integration and extraction were almost automated. The work of a software engineer became less low-level intensive.</p><p>3. Finally, the rise of user-friendly SQL-first BI tools (eg. Looker) enabled analysts to do more, focus on the creation of more complex pipelines all while saving time.</p><p>‍These shifts made access to data easier than ever. Every company now collects, tracks, and reports large amounts of data on everything but also on anything… This explosion of data comes with the cost of extracting the relevant data. To achieve this, companies must be sure to build <strong>the right data teams</strong>.</p><p>The distinct jobs that existed in traditional data teams have converged: the line between the roles of data engineering, data science, and data analysis is blurry. But we cannot expect data scientists or analysts to be great working software engineers and vice-versa. Although this is exactly what we see happening…‍</p><p>Today, most data teams resemble something like this:</p><ul><li><strong>Data analysts</strong> work with business and build reporting dashboards with Tableau, SQL tools, or modern BI tools. <em>While data analysts should be focused on delivering results as quickly as possible, they tend to spend more time searching for the correct data and transforming it than delivering. Their time is also increasingly stretched by requests to build BI tools for each different area of the organization.</em></li><li><strong>Data engineers</strong> are the plumbers responsible for data modeling. They build customer data integrations, all while ensuring a smooth pipeline orchestration and maintenance of the data platform. They are great software engineers, but <em>they are not trained to leverage data effectively nor to apply business science to engineering.</em></li><li><strong>Data scientists</strong> have an in-depth understanding of the “behind the scenes” of the algorithms, their quality, and optimization enabling them to model and infer statistics. <em>But they spend a lot of their time cleaning and orchestrating the data to feed it into the machine learning models, which is far from being their priority.</em></li></ul><p>The gaps mentioned above are exactly where <strong>Analytics Engineers</strong> walk in.‍</p><h3>So… what is an Analytics Engineer?</h3><p>An Analytics Engineer builds, transforms, tests and deploys models that support the queries of the rest of the data team. The objective of the job is to enable data products to talk to data consumers: the Analytics Engineer stands as the technical moderator of business and technical teams. It all comes down to this: Analytics Engineers allow their teams to navigate quickly the modern stack, all while leveraging the right data to answer their needs.‍</p><h3>What responsibilities does an Analytics Engineer have?</h3><p>At the intersection of business, data engineering and analytics, the Analytics Engineer travels back to SQL land to bring data models to life. In their day-to-day job Analytics Engineers will:</p><ul><li>Own and clean the datasets, building quality and performant data models to help other data team members work save time. Basically, they take control of data quality.</li><li>Work closely with product managers, software engineers, and data teams to make sure analytics are seamlessly integrated with products across the organization.</li><li>Validate and reshape datasets, transforming data so it is easily available for analysis. They also work on the design and development of CI/CD pipelines so that data teams can efficiently apply, test, and release analytics.</li><li>Apply and communicate software engineering best practices in their code and to the analysts and data scientists.</li><li>Create and maintain documentation around data to spread data literacy</li><li>Act as facilitators between the business and technical teams: they can translate the strategic needs of the business into specific data models</li></ul><p>‍</p><p>Obviously, as the modern stack continues its development evolve, we are not done figuring out how to use all these new tools, who should use them, how we should report around them, etc. It only makes sense that the exact responsibilities of Analytics Engineers are still in the works. But the skillset required for such a role is straightforward.</p><p>‍</p><h3>All this is great, but so what skills should an Analytics Engineer have?</h3><p>The next Analytics Engineer at your company may have a ton of software engineering skills or may very well be proficient in only one scripting language. What is important is that the Analytics Engineers bring these two worlds together. They won’t be the best software engineer out there, nor will they be the business go-to deal marker. And they really shouldn’t be: all the value they will add comes from their ability to blend technical and domain expertise in their daily tasks.</p><p>So how do you identify a good analytics engineer? Look at the skill sets.</p><p>‍</p><p>Your Analytics Engineer should have:</p><ul><li><strong>Experience working as part of a data team</strong>: they must be aware of the roles and responsibilities of data scientists, engineers, and analysts.</li><li><strong>SQL Wizard:</strong> Analytics Engineers should be fluent in SQL.</li><li><strong>Software Engineering Best practices</strong>: they will be responsible to use the best practices to ensure the whole team perform efficiently and has good quality standards.</li><li><strong>Great communication &amp; interpersonal skills:</strong> they must be real team players to ensure a smooth communication between tech and business role. They will also guide, develop and mentor the data team around the stack, so demonstrating conciseness and clarity to express technical concepts is critical in this role.</li><li><strong>Written skills</strong>: they will be responsible for documenting learnings for the rest of the data team.</li><li>Finally, the Analytics Engineer will most likely work on the tools presented in the Figure below. Therefore, working experience with cloud data warehouses is important and more generally speaking a solid understanding of data engineering tools and their ecosystems is undeniably a plus.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*nwGT7fuMphcwT39D.png" /></figure><p>One interesting point was put forward: <strong>soft skills are almost more looked into than technical skills in this analyst role</strong>. Claire Carroll, a senior Analytics Engineer from <a href="https://www.getdbt.com/dbt-labs/about-us/">dbt Fishtown Analytics</a> developed that from her experience, the best Analytics Engineers she met were “people who do not come from the engineering background but instead from the operations/consulting/financial area”.</p><p>The skills needed to be a great Analytics Engineer spread across a wide spectrum requiring both technical expertise and solid business acumen. A certain level of experience calls for looking for a somewhat senior profile. At first sight, you may think it is impossible to find someone with such qualifications — but for an Analytics Engineer, the importance is to hire someone that will grow in their role, especially as Danielle Leong, Senior Analytics Engineer at Starry said, the role is more about <strong>“the mindset than the skillset”.</strong>‍</p><h3>Do you really need an analytics engineer?</h3><ul><li>First, remember that the Analytics Engineers saw birth naturally out of necessity. Data teams’ scope of work has only increased, and the amount of code they oversee is growing exponentially. So, whether you want it or not, the probability someone on your data team will unknowingly perform the tasks of an analytics engineer is high. Whether it will be your data engineer, scientist, or analyst, having them sit by idly performing tasks that are not theirs, is not be the best use of their time and will only decrease their satisfaction and will for personal development.</li><li>Ultimately, the emergence of Analytics Engineers is about freeing data analysts and engineers to focus on strategic business decisions and to be more creative and specialized in building data processes. By ensuring the platform is scalable and well-maintained, they enable the rest of the team to save time and have only from a far, remote access to the dirty low-level coding work.</li><li>On top of efficiency reasons, an analytics engineer is less expensive than a data engineer and can help shrink the size of your data team by an important factor. Not only will this save on your expenses, but it is also a lot easier to find people with SQL skills than with ML and big data engineering expertise on the market.</li><li>At an organizational level, we see data science and analytics penetrating functional areas that were very low on tech just a while ago. Many of those areas couldn’t afford to have their decisions backed up by the expensive use of analytics. As data paves its way through the organizational structure, more and more companies undergo a structural reshuffling to place what used to be <em>siloed data teams</em> in business functions. Data teams are multiplying and moving in central parts of the organization, stressing the need for well-rounded (business and tech-savvy) profiles, such as Analytics Engineers.</li></ul><p>Since not long ago, companies experience that, thanks to data, the sky is the limit: their business impact is directly correlated to their ability to navigate the modern stack efficiently and make strategic use of the available data. This only stresses the importance of creating the right data team in place. The Analytics Engineer should be an integral part of that team because:‍</p><p>Too often, we tend to see the world as binary: we think a career path is choosing between getting more specialized or going into management. But there are many different paths to seeing birth in the world of data, and Analytics Engineers are just one of the first. The importance of defining key data roles goes far beyond simply saying ‘oh I want someone to do something with my data’ in an organization. Any stakeholder will want to understand the key roles his team players impersonate before building/joining a company. This relates directly to other topics we have already discussed as having <a href="https://www.castordoc.com/blog/what-if-you-had-to-build-a-data-stack-from-scratch">the right data strategy</a>, different tribes of <a href="https://www.castordoc.com/blog/top-5-challenges-of-data-scientists">data scientists</a> and figuring out <a href="https://www.castordoc.com/blog/how-to-build-your-data-team">how to build a great data team</a>.‍</p><h3>About Us</h3><p>We write about all the processes involved when leveraging data assets: from the <a href="https://notion.castordoc.com/">modern data stack</a> to data teams composition, to data governance. Our <a href="https://www.castordoc.com/about/blog">blog</a> covers the technical and the less technical aspects of creating tangible value from data. If you’re a data leader and would like to discuss these topics in more depth, join the <a href="https://notion.castordoc.com/unsupervised-leaders">community</a> we’ve created for that!</p><p>At Castor, we are building a data documentation tool for the Notion, Figma, Slack generation.</p><p>Or data-wise for the Fivetran, Looker, Snowflake, DBT aficionados. We designed our catalog software to be <strong>easy to use, delightful and friendly.</strong></p><p>Want to check it out? <a href="https://meetings.hubspot.com/xavier76/trist-xav-calendar">Reach out to us</a> and we will show you a demo.</p><p>‍</p><p><em>Originally published at </em><a href="https://www.castordoc.com/blog/what-is-analytics-engineering"><em>https://www.castordoc.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=467c86e5d45" width="1" height="1" alt=""><hr><p><a href="https://medium.com/castor-app/what-is-analytics-engineering-467c86e5d45">What is Analytics Engineering?</a> was originally published in <a href="https://medium.com/castor-app">CastorDoc</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>