Leland Teschler, Executive Editor
On Twitter @ DW_LeeTeschler
Engineers who do electrical work may be familiar with Mike Holt whose website (mikeholt.com) specializes in educational material mainly devoted to deciphering the National Electrical Code.
Holt also hosts a forum where someone recently posted this query: Should I get my PE license? I meet all the requirements…The pay bump is tempting but I feel I will be thrown into the deep end and expected to swim….I have four years’ experience in commercial electrical design. However, the most engineering I’ve done is lighting design, voltage drop, space planning, arc flash studies, TCC coordination, IECC code compliance.….I feel like the vast majority of my experience is in drafting and creating construction documents….I guess I’m afraid of the “You’re a PE, what do you mean you don’t know this?!?” conversation….Should I….wait until I’m confident as an engineer?
As you might suspect, the post has received a lot of comments. Most of them have a “just do it” tone to them similar to this one: I got my PE license years ago even though I thought I might never need it because I was working for a huge company with a bazillion engineers. When that company kicked me to the curb I was…glad I had secured my license. It opened doors for me that would have otherwise been closed off. Get it. Get it now. You will always have the option of not using it.
And like this one: I received my license in the mail about 8 weeks ago. I have never felt more accomplished or proud of anything in my life. Take the exam.
The writer’s concerns about the implied competence of a PE license seemed to have hit a particular nerve, judging by the number and tenor of the responses. This is not surprising. A lot of the people I went to school with back in the dark ages hesitated to take the Engineer in Training part of the PE exam for the same reasons. But for us, waffling over the EIT exam involved a lot more than self-doubt about our abilities. At least for some of us, it had to do with the anxiety over the interactions with our more experienced colleagues. Even on this point, responders on Holt’s forum provided good advice.
One put it this way: I try to stay out of conversations that aren’t part of my skill set. When I can’t (sub-consultant coordination meetings), I keep my mouth shut until the topic comes around to my wheelhouse. Otherwise, I never apologize for my ignorance, which is always curable. No one can know everything. “Stupid,” on the other hand, I sometimes have to apologize for.
Another was more succinct: No one, not even a PE, not even me, knows it all. Repeat after me: “I don’t know offhand, but I can probably find out.”
The back-and-forth on the forum also exposed what seems to be an urban myth: That PE’s are basically paper pushers. PEs on the forum were quick to correct this misconception. Said one, There is no “administrative side” to being a PE, per se….It all depends on the road you choose. What you’re thinking of is engineers who have moved into project management….There you have to worry about schedules, budgets, manpower loading, resource availability, etc.…Staying on the design side can have its own stresses, but usually once you hit the door, the day is done.
But the most compelling argument I saw for getting a PE consisted of three short sentences: Having a PE license will open doors that would otherwise be forever closed to you, but which of those doors you pass through is entirely up to you. Picture yourself 20-30 years from now. Are you more likely to regret not getting your license when you had the chance, or (to be glad) that you got it?
True and well said. DW