If you're not embedded in a science R&D group, you will be lumped in with general IT staff where tech support, database management, or software development of products are prized by management, but tackling individual R&D questions is not (though it is tolerated by IT brass since they know investigation is critical to finding & improving drugs).
I found the same limitations when I worked in R&D-based military contracting (or for US gov't FFRDCs for various agencies). There it's more important to develop a strong relationship with the gov't client, irrespective of the academic degree you have.
(I'm not familiar with DoE sites. And I actually had a good experience (other than the pay), as a high-end federal consultant doing challenging technical work, reporting to operations research PhDs at the Director level, who respected what I could do. Where I've seen and heard of problems is other places.)
I guess that's also a solution but you know that you contributed something, right? I believe that even if you ignore it the effect of your actions is your responsibility, even if somebody else told you to do it. And I don't even condemn it per so I just find the ambiguity puzzling.