Originally posted by: Tonix
I'd say anyone that gets a degree from an ABET accredited program at a university can be considered as an enginerd
BSME '92
BSCS '03
Getting close Tonix.
If you graduated from an ABET school, you can take the FE (Fundamentals of Engineering) Exam to become an Engineer-In-Training... and then four years later, you can take the PE to become a Professional Engineer. I have a BSME ('99) and a MSME ('01) from an accredited school (NCSU), and I've passed the FE. So I am an EIT. AFTER I finish my PhD (hopefully, HOPEFULLY by May '04) I'm going to take the PE (I could actually take it now, but REALLY don't have time).... THEN I'll be an engineer. I'm NOT now. People forget that an "engineer" is a legal title... just like "lawyer". You gotta have that stamp.
Sorry, but supertool is right. A degree from deVry qualifies you to be an technician, not an engineer.
PE is only recommended for people who dont have a bachelors in engineering right? I dont see the point of taking the PE if you already have a BS of Engineering from a top university.
- Apr 5, 2002
- 24,326
- 68
- 91
Nope. You HAVE to have a PE before you can do ANY work that qualifies for the health and safety of the public. Try to get a good civil engineering job without a PE. All bridges, buildings, roads, etc have to have a PE stamp in order to be built.
Most of the UL-qualified stuff sold on the market (like electrical components) are PE stamped.
I graduated from a good school, with a good GPA. But you still need that stamp.
EDIT: Think of it more this way: a lawyer has to pass the BAR to be a practicing attorney. So if someone goes to law school and fails the BAR, are they an attorney?
Yep. Which means you're a certified engineering technology major. But its not ABET accredited to take the FE (which is a pre-requisite for the PE). Which is why places like DeVry and ITT have co-operatives with large universities--so some of the students can get actual engineering degrees.
My degree is in business, not engineering, but I consider myself an engineer. When I was a playing musician, I started making money as a technician, reparing other musicians' gear for side money. A good enigneer (whose degree was in physics, not engineering) became my mentor in audio circuit design. I kept reading and learning. By the time we had our first patent for analog mulitpliers (U.S. Pat. 4,155,047), a couple of published technical papers and magazine articles, and I was designing successful product and specifiying the design of the individual transistors on our custom IC's, I figured I could call myself an engineer.
I can pull the job and hold my own in discussions with other engineers. It's what you know, not where you learn it, but you do have to know it.
I can pull the job and hold my own in discussions with other engineers. It's what you know, not where you learn it, but you do have to know it.
great but try getting an engineering position (ie software/electrical engineer) with a degree from deVry. I highly doubt anyone will hire you.
Demon-Xanth
Lifer
- Feb 15, 2000
- 20,551
- 2
- 81
/me points to the "Technology" word for a third time.
It's NOT and f'ing engineering degree! It's a technician's degree.
It's NOT and f'ing engineering degree! It's a technician's degree.
For EE's, the PE is still pretty optional. If your product is widespread enough that you are going for UL cert, then it helps to have at least one EE who is a PE... but it definately is not a requirement for the job.
Oh, of course. EE's don't use it so much. But technically, you're not LEGALLY an engineer if you have one. You can still join a union and all that fun stuff (professional engineers can't join a union, btw... if you didn't know).
I don't know why everyone is so title sensitive. They go through this crap all the time at corporations.... who is a "senior technical engineer" and who is a plain engineer and all that crap.
Its like the "secretary" versus "administrative assistant" thing.... who cares what they call you? You're paid the same. You do the same work. Be proud of what you do... what you actually DO, not what someone calls you.
Demon-Xanth
Lifer
- Feb 15, 2000
- 20,551
- 2
- 81
I believe the major distinction is that as an EE, your product can be destructively tested without any danger to people or excessive cost. UL and CSA testing can take place to verify that the engineer didn't seriously screw up. Civil engineers often do not have that luxury, when something fails, people mourn.
Umm, I was lead software engineer for MCI WorldCom at age 20 without any degree. A "software engineer" is just a fanciful name for "software developer"; it's not an engineer like a civil engineer.
I started (and ended) my engineering career as a test engineer. I hated the job, the work was ok (even enjoyable most of the time), but the politics are so screwed up in engineering. You spend the first week doing a basic design and writing up the project bid (usually being told how long it will take you and how much you can spend), knowing full well that the project was already approved and assigned to you, by some manager who most of the time doesn't know the difference between a NAND gate and an OP-Amp. He just knows how much time and money he has already quoted his boss and so forth and so on.
In test engineering that cycle is so much worse as you are usually having to analyse some other engineers work and build a tester for it, when 90% of the time the techs will hot-bed test anyway and your tester just sits there. So you end up looking like a turd in a swimming pool, because the head tech decides your tester is too hard to use, even though a well built one will test to at least sub-circuit level and sometimes to component level depending on what you are building the tester for. All a hot-bed tester gives a tech is a place to provide input and output signals and power. It becomes a function of the tech as to whether or not they can troubleshoot it fast in the hot bed.
(A very large % of the time, a board will fail in one area anyway so really doesn't need a stand alone test bed anyway).
Sorry for the rant, but it was my experience with test engineering and dealing with engineers that made me decide to leave the field. I also have a very low BS threshold and a NO-Buttkissing policy that left me on the outs with most of my "managers" who seemed to actually need their ego's stroked. I never could understand how any self-respecting person could suck up so much, especially my fellow test engineers. I am happy working for myself (as a tech mostly), even though the benefits suck and sometimes the work is slow.
Demon-Xanth
Lifer
- Feb 15, 2000
- 20,551
- 2
- 81
As an engineering tech, I already deal with all the crap as it is. The biggest difference between what I do now and what I'd do as a test engineer would be in the way I get paid. (hourly vs. salary)
Tip: DO NOT enter the medical field unless you have some unusual paperwork fetish.
I would say there is a big difference between engineer (person who applies science to solve a problem) and an @sshat (someone who looks down on my fellow computer people, or assumes himself superior). Hopefully when I finsh 8 years worth of a doctorate degree I am not the latter, but the former. Just my $.02.
Companies will take someone with no degree or a degree from bottom feeder college that has experiance over someone from a good college and no experiance.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 22K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
News NVIDIA and Intel to Develop AI Infrastructure and Personal Computing Products- Started by poke01
- Replies: 410
-
Facebook
Twitter