Handling workflow rules for a job application process
There is really not enough context here to talk to any performance improvements.  On the surface, there doesn't seem to be any way to optimize on this simple O(n) array iteration. I have no idea what is happening in any of the functions being called though.

You have some room for improvement on coding style IMO.

You understand the continue command but you are not using it effectively.  Consider inverting your conditionals in cases like this to get code structured more like this:

if (!someobj.hasOwnProperty(someProp)) continue;

// some logic

if (!someOthetRule) continue;

// some more logic


This eliminates all those nested ifs.

Your code is also extremely densely packed making it hard to read. You should really try to keep your lines under 80 characters, breaking longer lines across lines. And while I am normally a big proponent of meaningful variable and function names, you seem to almost take it to the extreme, using overly verbose variables when sometimes it does not seem necessary. Take for example how in your for loop you store the array length into conversionsLen when something short and simple like len would be just fine since it is clear what is happening here.