I can probably count on one hand, maybe part of another, how many EE-oriented PEs I met over ~40 years designing circuits. It is more a civil engineer thing, but some gov't positions, universities, and test labs wanted PEs to certify designs and results. I considered getting one a few times, but it is a bit of a PITA with almost zero reward, and opens you up to greater liability. For most engineers in the USA, there is no accreditation, besides that of their tech school or college. It is by degree and experience. Certain jobs do require additional certificates, but the vast majority of those I have seen are SW certs by Microsoft and the like for IT folk and programmers (who may not have degrees). Some states do require a PE to use the title "Consulting Engineer" or even "Consultant" in an engineering firm. I got around that at one point years back when asked to consult in a state with such a requirement, but I think it was because I was not a resident of that state.
Nor would the vast majority, all I think, of the companies I and my friends worked for list the engineers on staff. That was usually considered proprietary information closely guarded by corporate. I am actually on LinkedIn, but many folk are not, as it is often of (very) limited value and leads to a wealth of extra junk emails to wade through. Example: they sent me a job opening for "Retired" as program manager for Netflix. Apparently their algorithm does not know what "retired" means, nor understand that "analog IC design and test" does not qualify me to manage a software team at Netflix. Some companies also enjoin their employees from publicly listing current job info on sites like LinkedIn (some do it anyway, with various repercussions if caught, up to termination).