I've always said that regulatory affairs is a 100% experiential profession. I know the certificaters and diploma mills would beg to differ, but I'm still firm on that point.
RA is not about the regulations. You can memorize those chapter and verse. It is also not about meeting requirements. It is about, as Ed Panek puts it, implementation. How exactly do the requirements apply to your device, being made by your company, in its particular circumstances, with its business goals? ("It depends.") You won't find that in the regulations. And how can you implement in a business-savvy way (not to be confused with "shortcuts" or "the minimum we can do.")? How do you manage regulatory-related risk? How do you present your data so that the regulators get it?
I would add to Ed's example, "...and what have people found determines if it takes 4 or 40 hours and what approaches have they found to reduce the number of hours it will take?"
Access to other experienced RA professionals, sans trolls, marketeers, and "inspirational" posts per LinkedIn, that is why I come here.