In the US, there are ways to get a software engineering license. Is it worth it? Is it it feasible?1 No! It’s neither worth it nor feasible.
There a many ways to show a product or design meets standards and will not harm people. Engineering licensure is one of those activities in some fields. A Professional Engineering license can be given in the specialization of Electrical and Computer Engineering.2 Every state follows the basic model of engineering licensure, with education, experience, and examination. This is difficult for computing professionals.
Here are the steps and why it’s difficult.
Education – IT and CS degrees are beginning to become accredited by ABET, though through their Computing Accreditation Commission. The education piece requires ABET Engineering Accreditation Commission, so many degrees do not count for the education component. Many of the best programs in our field, like Stanford or MIT, do not have this.
Experience – Four years of experience working under a licensed professional engineer is rare in industries either under the industrial exemption or under federal certification. Defense, aerospace, medical, even electrical other than power have few licensed practicing engineers. There were 13 people passing the Electrical and Computer exam in 2022.3 If you work in computing software or hardware, odds are you do not work directly for one of those 13 people.
Examination – The FE exam is so broad and difficult. And computing has moved so fast that even the foundations targeted in the PE exam are difficult to keep constant and stay relevant. Eight hour exams are always difficult.
The results could be considered underwhelming at best. The exam doesn’t prove you’re good at computing work. The requirements for education and experience aren’t a discriminating factor between other education and other experience that turn out to be just as good as what’s accepted for engineering. There’s no guaranteed or even defined career advancement or PE only work. Just a symbol of professional promise to keep doing continuing education and working ethically.
And so, against all the difficulties, and the almost no payoff, I did it. I got a PE license. And this is how.
I went to college at the University of Florida. I had chosen to graduate through the College of Engineering. And luckily the degree is ABET EAC accredited. No one is choosing computing programs based on this, and I would have happily gone to a school that did not have this feature. Choosing Computer Science or Information Technologies majors would have been a different college than engineering, and would have also worked well for me in every aspect except for this license.
Examination was very difficult. I studied a lot for the FE exam. When I took it in 2008 there was a breadth component that covered all of engineering. Topics range from structural forces to materials to circuits. The PE exam I found easier, but was still only offered once a year in 2023 due to fewer people taking the computing exam.
Experience is basically impossible. But there are exceptions depending on the state board. Alabama will consider whether your supervisor hypothetically could also apply. Washington will consider work for a federal entity or manufacturing as suitable experience (Think of Boeing and Lockheed.). Florida will use a diploma or copy of official transcripts from your supervisor only if your supervisor has a degree in engineering (Think of NASA, Northrop, and L3 Harris). I had no trouble finding PEs in my network of people I know that were willing to recommend me. But I had to rely on Florida’s industrial exemption for my supervisors. If I had lost contact or any of these supervisors were unwilling to help so much or had passed, this would not have been possible.
15 years after I took the FE exam and 4 months after sending in my application, I almost gave up when I had to request an official transcript sent for a retired supervisor who had graduated 50 years prior in another country. I was surprised the university would even do it. University of Alberta was happy to help, but they couldn’t use the newer, faster system. We waited another 3 weeks for that paperwork in the mail.
And there you have it. I can’t recommend anyone else do this. Licensure requires a lot of luck and a lot of following the rules and a lot of waiting. Each of education, experience, and examination excludes too many talented and hard working people for the software field to consider it seriously. On the positive, there are some amazing people working on this behind the scenes. People at state boards, NCEES, IEEE, ABET, and professors at engineering colleges are working hard and doing smart things. They are bringing Professional Engineering forward and making it better for all involved, and including the electronics and computing professionals along the way when they can. Software, hardware, and computing could use some more licensing, or credentialing, or product/process certification than it has today to catch up with other engineering disciplines that are entrusted with safety critical designs and verification, but licensing isn’t ready for that yet.
- Glithero, Jason. “Can we strengthen the Professional Engineer (PE) License.” https://www.linkedin.com/pulse/can-we-strengthen-professional-engineer-pe-license-glithero-p-e-/ ↩︎
- Musselman, Craig, et al. “A Primer on Engineering Licensure in the United States.” https://www.nspe.org/sites/default/files/resources/pdfs/blog/ASEE-A-Primer-on-Engineering-Licensure-in-the-United-States.pdf ↩︎
- NCEES. “Squared.” 2023. https://ncees.org/wp-content/uploads/2024/03/Squared-2023_web-1.pdf ↩︎
