Payne (Pei En) Hwang’s Post

View profile for Payne (Pei En) Hwang, graphic

Revenue Operations, Automations, and Process Optimization Expert | OpenText

So, I have a lot of thoughts about RevOps hiring as a whole, having experienced it now for three years and change. Here are my notes (TL;DR - industry is in its real nascent stages and still kind of figuring out what roles look like, especially outside of the States): 1) If you are the first hire, expect to be asked to do more than what your job title says. See it as a red flag if your pay is still as an entry-level or administrator level IC. 2) This job market has slowed down dramatically, especially outside of the states. We seem to be in a weird little spot where employers don't quite know what they want but have read enough influencer and whitespace literature to see it's a need for their org. 3) Kind of more of a 2a, but because the discipline is so mushy, you have to be the PERFECT hire to be considered beyond the second interview. You have to fit every single checkbox because there are hundreds of candidates, and even then, I'm seeing companies I've applied to and been rejected from still be hiring months down the line. Worse, I've seen the same spots open up only a year down the line. As a wise man once said, Bold Move, Cotton, let's see how this plays out. (Hint: with ballooning TA cost) 4) Guess this is a 2b (nier fans where), but RevOps is a discipline that really requires continuity - for your first hire, unless you're willing to invest in documentation early, that hire's going to be SWAMPED. Turnover at the position is really costly, not just in monetary cost, but in terms of institutional knowledge lost.

To view or add a comment, sign in

Explore topics