Career path will vary widely depending on the person. I'll answer this question with the view of "how do I progress my career path in rev ops": 1. Be consistent in your day to day: Build a reputation as a dependable teammate that will get the job done. Do this by hitting timelines, taking ownership of your work, and delivering high quality products. 2. Practice and tailor your communication skills: Be able to inspire confidence from your stakeholders in both verbal and written communications. Do ...Read More
Blake Cummins
Director, Head of Global Sales Strategy & Operations at Wolt
Content
To be successful in revenue operations you must 1. have a data analysis foundation 2. be a strong problem solver and 3. be a good story teller. 1. Data foundation: the requirements will change depending on your company's tech stack (SQL, Tableau, SFDC, etc.), but you must have experience analyzing, visualizing and synthesize takeaways from data. Almost everything you do in rev ops must be data driven, and understanding how to pull actionable takeaways from large data sets is key. 2. Problem solv ...Read More
To justify a promotion you want to be able to show impact, followership and consistency. You want to be able to say 1. this is what I did 2. this is how I did it 3. I'm operating at this level consistently. 1. Impact: show with numbers the impact that your initiatives had on the business, and point to your leadership / actions that enabled it. Quantifying your impact to the business, and leading these types of initiatives is key. 2. Followership: Build a strong followership of teammates and cro ...Read More
I love questions that demonstrate curiosity, scrappiness, operational excellence and enthusiasm for the business. One of my favorite Q/As below Q: Walk me through an example of how you impacted the business? how did you discover the opportunity, execute on it, and ultimately how did it impact the business? A: I want to hear several things in this answer 1. Curiosity for the business and how to make it better--digging into data, talking to stakeholders, etc. 2. Scrappiness on execution--you didn' ...Read More