>It's a shame there aren't specific software
NCEES tried to have a software PE but it withered on the vine and was only offered for a few years. I suspect the incentives in industry don’t support it and the only way itv would get traction is if it were forced by regulation.
So in that light, I want a software PE to know things like thermodynamics if they are writing controls code for a nuclear reactor or aerodynamics if they’re writing avionics code for an aircraft. In my experience, there’s a lot of problems created when SWEs don’t consider the physical dynamics of the system and having some breadth of engineering knowledge can mitigate some of that. Breath of engineering knowledge is the aim of the FE exam. There are oodles of materials to study specifically to pass the FE, so I don’t think that’s really an hurdle for a properly motivated person. Also in that vein, I want them with real experience under a PE. It’s a hurdle, but there are plenty of PEs in domains like oil & gas, aerospace, automotive etc. to work under. But if you think you’ll can work at a FAANG or adjacent SV role and get a PE, it’s probably harder to find a senior PE. I also don’t know if it adds much benefit to a web developer.
The other aspect that’s interesting to me is that, like “engineer”, the term “expert witness” may be too generic to have much meaning. From the related Oregon case linked elsewhere:
>“Courts have long recognized that the term ‘engineer’ has a generic meaning separate from ‘professional engineer”