They have mostly direct staff involvment.
You send a bug report, the reach out in less than a week. Epic used to do that. They stopped doing that too. The send the automated reply and that’s pretty much it.
You post about an issue with something-say lack of shadows in orthographic view (Silly example).
One of the actual developers will leave a post explaining why the ortho view has no shadows and telling you how to make it have shadows/where to modify source.
Say, that’s an example, but Unity is doing pretty much this for the hdr features…
Well, I did mention a few options. So, sure. It’s possible.
For me,
The best solution of the bunch is to have both an official answer and a community answer.
Say there’s a simple question like…
The character stutters when walking backwards.
There’s about 3 real answer and a cheap trick that works.
The community is using the cheap trick that works - increasing blend times on the animations.
They accepted this as an answer, however it is not an answer.
Once gfx get enough fps, the mesh will likely stutter again.
The proper fix, is to split forward and back movement out and have backwards movement have its own animation blendspace with walking back as the center animation.
You then have to refactor locomotion to walk either forward or back.
Do you think the community would ever go with that answer when increasing a value by a smidge appears to solve their problem?
Never 
And that is the real problem.
The community will not do what is proper if whatever else works.
This is one example of around a thousand actual answers that were in answer hub.
We all try and help when possible - Maybe too much in my case as I’m always reading the forum 
Still, there’s some serious concern about what is “proper” and what the community likes to do that has to be addressed.
I figure the best way is to offer both options/answer with the one posted by Epic being visible before the community solution…