<?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 Likhita Bathineni on Medium]]></title>
        <description><![CDATA[Stories by Likhita Bathineni on Medium]]></description>
        <link>https://medium.com/@likhita.bathineni?source=rss-cd67b5bf274b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EXrNBh7NjJKmXS2VirTJkQ@2x.jpeg</url>
            <title>Stories by Likhita Bathineni on Medium</title>
            <link>https://medium.com/@likhita.bathineni?source=rss-cd67b5bf274b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:16:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@likhita.bathineni/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[A beginner’s guide to growth engineering]]></title>
            <link>https://medium.com/@likhita.bathineni/a-beginners-guide-to-growth-engineering-f8e9a6f4aaa6?source=rss-cd67b5bf274b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8e9a6f4aaa6</guid>
            <category><![CDATA[growth-engineer]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[a-b-testing]]></category>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[growth-engineering]]></category>
            <dc:creator><![CDATA[Likhita Bathineni]]></dc:creator>
            <pubDate>Sun, 19 Jul 2020 23:20:08 GMT</pubDate>
            <atom:updated>2020-07-21T16:44:39.047Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="growth" src="https://cdn-images-1.medium.com/max/1024/0*7LKe6Row5_zIUe0q" /><figcaption>Photo by <a href="https://unsplash.com/@jeremybishop?utm_source=medium&amp;utm_medium=referral">Jeremy Bishop</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>What is growth engineering?</strong></h3><p>Let’s talk about the basics. What exactly is growth engineering (GE)? Is it different from software engineering? Why? How different is it to software engineering? I am sure you must have had these questions. This is my honest attempt at answering these questions. Think of a Growth engineer as someone who not only builds systems but also works with data (lots of data ;)). In short, a growth engineer has a data driven approach to solving problems in the user journey. The biggest challenge for a growth engineer is being able to quickly adapt and improve. For example, most of the time, the team may not own the code base of these said systems and we may have to either learn the code base, write prod ready code or find another ingenious way to instrument the system to launch the experiment.</p><p>There are typically two approaches to growth engineering:</p><p><strong>Type 1: </strong>Some teams within companies have dedicated people to perform their respective functions comprising of engineers, data scientists, analysts, PMs, designers.</p><p><em>Pros</em>: Quick turnarounds — experiment fast, fail fast;</p><p><em>Cons</em>: Lack of complete picture leads to problems; Information always gets lost/ diluted.</p><p><strong>Type 2:</strong> The other unconventional approach is to let you delve into everything. Yes, you read that right, everything.</p><p><em>Pros</em>: Ownership; High confidence in instrumenting larger systems; Analysis learnings can lead to better instrumentation in future experiments; Higher quality experiments.</p><p><em>Cons</em>: Slow churn of experiments; Hard to find people who specialize in everything.</p><p>Now, there are people who would want to learn, work and specialize in only one area, be it data analysis, experiment instrumentation, frontend, backend etc. For them companies/teams with a similar approach would be a better fit. On the other hand, there are people like me, who want to learn how everything works. For those with this style, the second approach fits the best. I will be talking more about how life would be in type 2 teams.</p><h3><strong>What to expect?</strong></h3><p>As a growth engineer, expect to work on some really interesting problems. You will be working with designers, data scientists, product managers, marketers etc to solve issues in the user journey or in creating new user journeys which lead to more signups/customers.</p><p>You will be swimming in data and code, so it only makes sense for you to be data driven. In some cases, “Data driven” is usually associated with having an abundance of data, but not understanding it. This shouldn’t be the case. It is important to study and understand the data, which leads to balanced experiments and empathetic results.</p><h3><strong>Qualities that might help you embrace GE</strong></h3><p><strong>Ownership</strong>:</p><ul><li>As a growth engineer, your job is more than just writing the code and closing the Jira tickets. Try to understand who the target audience is and how you intend to implement it. Do you have all the resources to quickly finish the job? Or do you have to unlock some features to make this happen? Do you have enough tracking throughout to track the journey of the user? Before getting started, try to follow the same path as the user and see if you have all the tracking you need or not. If the tracking doesn’t exist, then now you know what extra tracking you need to implement while you are coding. To do all of this, keeping in mind the holistic view of the system, you are in an ideal position to take ownership.</li><li>And if you are doing your own analysis, then think about the different ways you can be analyzing your data. Don’t be waiting for the analyst to do that for you. I know this is kind of controversial. Some say a growth engineer should be focused on only building experiments and pushing them out asap and let the analyst take care of analysis. My personal opinion is you should always be self-sufficient. There is absolutely nothing wrong in building an experiment by yourself and also analyzing your own experiment’s data. Yes, this is not a highly scalable option as not everyone wants to do them both. But at-least being involved to some extent with the data is always good.</li></ul><p><strong>Always ask ‘why’</strong></p><ul><li>Always question the logic. Maybe the experiment design might not work. Maybe you can think of a better enrollment logic. Maybe your learnings from a past experiment might help you come up with a new instrumentation plan. Always ask questions. Not everyone knows everything.</li></ul><p><strong>Get your hands dirty</strong></p><ul><li>Be ready to look deep. Sometimes it may look obvious but the deeper, down the funnel metrics might have a different story to tell. For example, an experiment’s day 1 metrics might look amazing, but check if the deeper metrics look good too.</li></ul><p><strong>Be ready for all the twists and turns</strong></p><ul><li>Always code defensively. Especially when you don’t have access to the backend code and their suite of tests. Your experiments will also have to run on multiple browsers at different internet speeds in different devices. Sometimes it is better to stick to the basics to ensure a better quality of user experience with no bugs.</li></ul><p><strong>Be your own person</strong></p><ul><li>I feel a growth engineer has to be independent and innovative to be able to effectively get things done.</li></ul><p><strong>Know the trade offs</strong></p><ul><li>Be ready to trade off some amazing ideas keeping the long term metrics in place. Most of the times obsessing over short term metrics is just not worth it especially if they negatively effect the deeper metrics. You should be either doing equal justice to both above the funnel metrics and deeper metrics or the benefits of one should outweigh the defects of the other. At the end of the day, the funnel health of your product is very important.</li></ul><p>Finally, being a growth engineer is not just about writing code. <strong>It is all about the mindset</strong>. A successful growth engineer IMO is the one who has skills to think about the code, process, user experience, results, long term, short term goals, funnel health, and be able to communicate well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8e9a6f4aaa6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>