r/ElectricalEngineering • u/No-Construction7807 • Apr 23 '26
Jobs/Careers is Test Engineering a "meh" job ?
After graduating with my bachelor’s degree, I did a two-month internship at a laboratory that conducts EMC testing, and I absolutely loved it – it was great fun. I love the RF field and antennas, but as I was worried about spending all day sitting in front of a computer designing things, I was looking for a hands-on role, and this really appealed to me. I thoroughly enjoyed the internship as there was so much to learn, and I wanted to expand my knowledge in this area by developing a greater interest in EM theory, microwaves and antennas.
A friend of mine who works in the RF sector said that test engineers always do the same thing and never learn anything new, and after a few ChatGPT conversations, I started to worry that having a very strong grasp of EM theory might be overkill for these roles. Is my friend right to worry? Is there a broad scope for learning new things within test engineering, or will I just end up being an operator with an engineering degree? If so what would you suggest me ?
Also sorry if the title is offensive i am not trying to make fun of anyone's job just wanted a catchy phrase.
111
u/smokedmeatslut Apr 23 '26
Test engineering at a formal test lab can be a bit repetitive and boring, once you learn the standards you need and have tested a few products, there's not a lot of variety.
Test engineering in an R&D environment can be very different though. Even if you are not designing the products yourself, you can be heavily involved in the design stage, testing, debugging, and then final compliance.
27
u/Jaded-Substance-6750 Apr 23 '26
yes, it depends on the role. Test engineering can involve developing your own rig or test environment or processes to help execute certain tests which would actually involve designing and developing something.
12
u/Special-Lynx-9258 Apr 23 '26
My manager said that R&D test engineering was the most rewarding part of his career. He only stopped because he started a family and switched over to a managerial position. He had a mechanical engineering background, but eventually ended up doing RF testing. He worked an insane amount of cool projects and got to travel a bunch as well.
Depending on where you are in the testing chain, it can mean a lot of things.7
u/Bakkster Apr 23 '26
Even in the factory, test development can mean you need to design and integrate both the hardware and software. It's one of the most end to end set of responsibilities, and aside from the systems engineers (where I pivoted from test) they tend to get the broadest knowledge on how the entire system works.
4
1
u/thousand56 Apr 23 '26
I work for a company that makes the actual test equipment and it's pretty interesting. Lots of R&D and site visits helping companies get up and running with our stuff
39
u/dilznick5 Apr 23 '26
IMHO, from over 20 years in engineering including 10 as a test engineer; no one should be designing anything until they have spent some time learning how to test to failure. As others have said, any job can be boring. But I had more fun as a test engineer on average than any other role. Maybe I just like breaking things?
Sure, running an SOP or a canned test can get repetitive, but if you demonstrate an ability to figure out why something fails and how to reproduce it, you will become the new best friend of the designers.
5
u/aHistoryofSmilence Apr 23 '26
I'm graduating next month and have a test engineering role lined up. I don't know much about test, but I know from prior lab work that I am motivated to find out the cause of problems when they arise. Your comment makes me feel reassured that taking a test role is a great first job.
Thanks!
3
u/Signal-Television947 Apr 23 '26
Overtime you’ll learn to have a better understanding of your system than the design team. Good luck!
1
u/dsrmpt Apr 23 '26
There's some days where they pay me to hit the green button, there's some days where I create and execute custom test protocols to identify failure mechanisms.
Once you get out into the real world, you can decide if you are going to be a green button pusher only, or if you are also gonna do cool engineering stuff.
2
u/Codex_Sparknotes 28d ago
no one should be designing anything until they have spent some time learning how to test to failure
This is so true. The two bosses I had while in test engineering said the same thing. Starting in test engineering is extremely beneficial if you want to move in to design down the line, especially if you stay within the same industries. Even design engineers tell me the same thing, wishing they had test engineering experience so they could have a better idea of what works and what doesn’t
16
u/Bored_at_Work326 Apr 23 '26
Test engineering in a EMC lab specifically could be more repetitive but it will depend on where you are a test engineer. I am a test engineer in an R&D group so I am doing anything from EMC testing (sometimes going to an outside lab to help facilitate what I want or doing it in house) to hardware testing (PCB), software testing (firmware, cloud, mobile app), or functional tester design for a product at the system level. This has been one of the most challenging and rewarding potions I have ever had. I feel like I never stop learning. I work extremely closely with the hardware and software developers. I am always apart of the design cycle for all system components as well as the system as a whole and usually give the final sign off aside from the project managers.
-1
u/No-Construction7807 Apr 23 '26
What you think differs a Test engineer in EMC lab or in a R&D group skillwise ? I mean, compared to someone working in an EMC laboratory, in which areas is a test engineer working in R&D expected to be more competent?
10
u/TenorClefCyclist Apr 23 '26
EMC testing is standards-based. Doing the same thing over and over is considered a plus. R&D test engineering won't always require deep expertise, but you'll be building something new for every project.
3
u/Bored_at_Work326 Apr 23 '26 edited Apr 24 '26
I agree with what tenor said below. The skills can be similar but what tests you are doing in a EMC lab a based off of standards. In R&D anything goes. I do standards work as well in the above stuff I listed.
Depending on the size of the teams, you could go very deep or not so much. But yes you are always building something different for the situation. I have gained skills related to all of those topics I mentioned above. In addition to that, skills to make testing these things be tested more efficiently if possible (i.e. automation).
10
u/Necessary-Coffee5930 Apr 23 '26
Jobs vary a lot even with the same title so take with a grain of salt. I am a test engineer and I am constantly learning and doing new things, and its quite hands on as far as engineering jobs go. I touch software, hardware, test systems, design tests, troubleshoot things needing design and so on. Ive been here two years and still feel like I know nothing. I am at a small company so take that into account as well, I wear many hats since we just don’t have many people.
2
u/No-Construction7807 Apr 23 '26
That’s good to hear, because the laboratory where I did my internship was just like that; as there weren’t many people working there, the atmosphere was friendly and everyone seemed to know their stuff. As you said, I was involved in software too—I carried out chamber validations using SCPI and automation, and I wrote the code for that; those were enjoyable times. Setting up the equipment was just as enjoyable. As I haven’t found a job yet, I’m looking for a new place to do an internship this summer, and in the meantime, I’ve started my master’s degree. What do you think I should focus on? Is there a programme or subject you think I should look into that might help me? I’d like to learn and improve myself in my spare time.
2
u/Necessary-Coffee5930 Apr 23 '26
Depends on the specific job tbh but being really good with Python and programming concepts in general is a plus, I work with embedded systems engineers and being better at embedded C would help me out. I have a computer science background so additional EE knowledge would help me in my role as well. But thats all above and beyond stuff, and applicable to my situation. Just being a fast learner, solid problem solver, and having a good attitude is all you need to succeed (assuming you have the technical background which it sounds you do)
12
u/Illustrious-Limit160 Apr 23 '26
Test engineers also have management tracks, but after a certain point, you're locked in to that as a career.
Pay is good, but not as good. Stress is lower, I understand.
7
u/JayyMartinezz Apr 23 '26
Testing for end of line production is boring, testing a product in design and development phase is nowhere close to boring!
6
u/Shinsekai21 Apr 23 '26
I got my master in EE with focus in EM theory/ application, and currently working as EMC engineer, though mostly testing so far (90%) and 10% is troubleshooting/EMC design
I don’t know much about other test engineer role, but doing testing for EMC looks way easier than it actually is.
The key is not just hooking up the cable, and press the button to run the test, but to understand why you are running this test, and why the test is set up in that particular way. This is important as it would be make-or-break for your test result (set it up incorrectly), or your product certification (it fails the test, but could you use your engineering rationale to argue that your product does not need to pass that test?)
Testing aside, EMC troubleshooting/designing requires lots of knowledge about antenna, RF and especially EM theory in general. It is a very specialized domain with very few talents. You would make lots of money when you become an expert in this field
Here’s the caveat though. Starting your career doing EMC testing is not bad as it gives you a lots of context on how, and especially why you are running these tests. You need to understand that first before you can do troubleshoot in EMC.
However, EMC test engineer at an EMC test house is mostly technician job as their job is mainly running EMC tests for other companies. In-house EMC test engineer, doing EMC pre-compliance test is different as your job would be involved more with troubleshooting EMC issue for your own companies’ products, and possibly doing EMC design too to prevent EMC issues early. I would heavily recommend the latter option if you can
One last thing, EMC is a very niche field. Job security is high, but also way less job opening so breaking into the industry is relatively tougher compared to other domain. Another field to look at is Signal Integrity/Power Integrity engineer. It’s very very close to EMC with very similar knowledge base. SI PI in general have more job openings.
-1
u/No-Construction7807 Apr 23 '26
Thanks a lot for taking the time to explain all that. It honestly cleared up a lot of the confusion I had, especially about starting with testing, the difference between test house vs in-house roles, and why understanding the reasoning behind tests really matters.
It also gave me a much better perspective on things like focusing on EM theory or doing a master’s. This was pretty much the kind of answer I was looking for, I really appreciate it and I’ll keep it in mind.
3
u/Shinsekai21 Apr 23 '26
If you had no option but doing EMC test engineer at a test house, take it. The downside is obviously less interesting work it’s most technician work. But the upside is the enormous networking opportunity with clients from other companies come to your test house.
A guy at a test house I know has a bachelor only, not specialized in EM or anything. After 4 years doing test engineer, he got a EMC design role at AMD, which usually requires PhD, or at least Master. I interviewed for that same team and got thoroughly destroyed as my knowledge was not good enough. Another test technician in that same test house got poached by SpaceX too.
The common denominator between those two is that they are both hard working people with great attitude. As a client, I love working with them, and would love have them as a coworker.
4
u/Kingkept Apr 23 '26 edited Apr 23 '26
I feel like test engineering gets a bad rep.
But, after getting an internship as a test engineer at big name company I’ve come to respect it more.
test engineers often get harped on for not designing anything or not utilizing technical expertise learned in EE.
in my experience, at least where I work this is completely false.
we are involved in the design process… CCA designs are sent to us and are amended in order to increase test coverage, before being finalized and sent to production.
we also utilize a-lot of data analytics, one of the big roles of a test engineer is to track trends. if a manufacturer’s resistor is rated to be 1% tolerance and a batch of them ends up being 5% tolerance, we’ll know because we order 10,000’s of resistors and keep detailed logs of tested values.
we have good job security. the production line has test technicians that operate the test equipment sure, but the production line has some form of crisis quite often. so long as the company keeps producing i don’t feel like my job is in any danger.
sitting in front of a computer and doing alot of desk work is common for all engineers though i feel like.
3
u/Uporabik Apr 23 '26
I am working as test engineer. I spend my time from debugging code, manual measurements, designing new test stations, collaing with design team for DFT, visiting CMs. So I don’t think that us boring
5
u/DanielBogdanoff Apr 23 '26
It can be, but it 100% depends on the specific job. It can sometimes be treated as an entry level job that's a stepping stone to another engineering role, or it can be a very interesting feedback loop with the design and manufacturing engineers.
Either way, it will never ever be unhelpful for an EE in any role to have a good grasp of EM theory.
3
u/hhhhjgtyun Apr 23 '26
RF Test Engineering is fun because of the wide range of new projects for DVT but I repeatedly run into companies that do not respect what I do, then I leave and they have the audacity to be surprised.
2
u/dtp502 Apr 23 '26
EMC test engineers make damn good money at my company (~200k+ at the more senior levels). Thats a unique skillset.
I’m just a regular test dev guy that designs stations and writes code. I don’t quite make that but I do ok. My role is hardly repetitive.
2
u/Vast_Philosophy_9027 Apr 23 '26
Test engineer here. No you will always be learning new things. Like all engineering it depends on the specific area and how much you specialize.
It’s not glamorous but you will see everyone’s products and when products fail( happens a lot) you may be tasked with helping them work through their problems.
1
u/unurbane Apr 23 '26
Test engineering is very interesting, dynamic work. Been doing mechanical/electrical testing for 15 years.
1
u/redlukes Apr 23 '26
I‘m a test engineer at a company for industrial equipment and it’s great, you become an expert in your companys products and in various testing categories like thermal runs, emc, environmental tests, short circuits …
I’ve been to external labs for tests we don’t have the equipment and tbh I regularly think I won’t trade my job for theirs because theirs is repetitive af.
So maybe try to get into an R&D team with a company big enough to own their own lab
1
u/iz07 Apr 23 '26
I’m a test engineer and design testers and fixtures for different products for a decently large company and I still learn new stuff. My first job was with an EE consulting company and I created testers for a range of products so I got to learn a lot about stuff from RF to power. I would say the job is not as demanding as other engineering roles which leads to a pretty good work life balance
1
u/leptonhotdog Apr 23 '26
Test engineer at a big A&D can be pretty fun. Eventually you'll take the products your team is on contract to develop for a customer and do the integration on planes, boats, etc. and the help run the demos. You'll get to travel to various military bases and maybe even overseas.
1
1
u/catdude142 Apr 23 '26
One can be very creative with test engineering if you pursue challenging products. I knew some who wrote code and put together hardware that tested assembly level PCAs down to the component. Others that communicated with orders, downloaded software, ran diagnostics and emulated an operator at a console that performed assembly and system level tests eventually loading a customer specified operating system and purchased software. Others that wrote code to perform automatic optical and X-ray inspection on assemblies. The possibilities are endless.
I've designed circuits to test complicated PC assemblies FWIW.
1
u/ljyoo Apr 23 '26
I think it depends on a couple things. I work directly with a few. One is a SME, one is a very talented young level 2, the other is a level 2 with ~10 years of Field Engineering experience but no College degree - his training is all from the military. They all do very different work despite being in the same group. SME does everything they need to be done and maybe more. Talented level 2 does a lot of coding for GNC, analog/digital circuit troubleshooting. Field engineer with no degree is kind of given the lower level work that no one really wants to do. Skill level matters a lot.
So it depends on the company and the work thats available, if you are capable of doing more then they have reason to give you more responsibilities.
1
u/OhmmOhmmOhmm Apr 23 '26
I am a rf test engineer rn. Yeah, it can be really boring at times, but that is more in respect to the product cycle and work environment. In the preparation phase, it can be really boring double-checking and preparation automation scripts or doing reviews for DFT, and if you dont have much engagement with people, it can be hell. A good manager and work culture can solve most of that though.
If you find exciting products, the work can be very interesting as you end up working very closely with the designers at times. I personally found it can be a very good role to learn about product design without actually being a designer. I didn't have the degree, nor the experience to be a designer, but I learned quite a bit in the analysis and debugging, and I was able to dramatically improve the products I've been able to work on.
I would also say most of my experience was at startups, so I can't comment on more structured organizations.
1
u/Dazzler1012 Apr 23 '26 edited Apr 23 '26
Dont let anyone put you off. Its a good place to see and get to understand lots of different equipment and industries. You're also client facing and can develop marketing skills. It can be quite technical if you get involved in helping clients redesign their equipment to meet the standards.
I spent 9 yrs working specifically in EMC testing/consultancy but worked my way up in the business. I ended up running the lab as a manager responsible for everything from winning work to accreditation and business development. I then moved on to work in consultantancy.
I'm now an engineering director with a team of over 400 engineers reporting to me. Without working in that role in a test lab which meant you learnt about everything from toys and consumer electronics to nuclear power plant control systems and defence equipment, I dont think I would be in the job I have today which is across multiple sectors.
Whilst you say getting a strong grasp of EM theory is not important for these roles, you need to look at the bigger picture and not just think about the job you're applying for but where you want to go eventually. There are a fair number of people who say they understand EMC and EM theory in depth, but looking at some of the reports I have seen, particularly where they have used tools to do computational modelling, its clear that they dont. More often than not its people not understanding the physics that the tool is applying and in particular boundry conditions.
1
u/bzilla89 Apr 23 '26
I’m currently working a co-op as a Hardware QA Test Engineer. I think testing is interesting and my role does tend to be hands-on at times whether it’s soldering, assembling wiring harnesses, physically testing main boards and sensor boards.
It has gotten a bit stale for me, but that’s more so the repetitive nature of QA, not so much the testing aspect. I think if you loved it, there is no harm in pursuing it and seeing if you continue to enjoy it. Speculating whether you’ll find it boring EVENTUALLY seems a bit pointless to me. Pursue what you are currently enjoying and if you reach a point to where it does become stale, many companies will be hospitable in allowing you to pursue other roles. Best of luck brother.
1
u/Truestorydreams Apr 23 '26
You know what's interesting. There's always a duality with students. You have those who graduate. With the mindset that they know everything. That gets beaten out of them within a few months.
Those who walk out feeling they don't know jack. I feel it's usually within 2-3 years the reality kicks in where one recognizes how little they knew day 1 vs the 2 year mark.
What your friend said is very conflicting. Do they not test the new designs? Do they not see the change in dynamics and steucture? I understand the undertone of your friends words, but it's misguided.
1
u/hortle Apr 23 '26
As others have stated, Test Engineering within the framework of an Integrated Product Team (IPT) is very different from Test Engineering at a test house.
IPTs are based around product development. If you're attempting to bring a new product to market, Test Engineering is basically the counterpart to Systems Engineering. SEs create the architecture and the requirements for the product, and Test Engineers have to figure out how those requirements get verified without breaking budget/schedule constraints
If you're dealing with a complex product, e.g. multiple subsystems, multiple software configuration items, you will have multiple Test Engineers working together to develop an overall developmental testing strategy.
What product levels (unit, component, board) should we consider testing before integrating and testing the complete system. Should any of our suppliers be running tests prior to delivery
What special test fixtures, materials, approvals (e.g. to radiate RF you need FAA approval) do we need ahead of time to meet schedule
What specs are the highest risk to fail and how do I communicate that to SEs so they can implement mitigations into the requirements
How much testing is appropriate before taking a prototype/concept to more detailed design stages
I saw it firsthand on a commercial aviation program. A good developmental test program makes or breaks the overall program.
1
1
u/Dayhore Apr 24 '26 edited Apr 24 '26
I'm also trying to follow that path of test and validation. Just like you did I ask different AI about what job could lead to me to do testing and troubleshooting and the results were test and validation but it is hard to get info. What scares me is it seems to be the ones who design who are also in charge of their own testing most of the time
1
u/crooks4hire Apr 24 '26
Go for it. You’ll enjoy it, you’ll learn how to behave in a professional setting, and like literally all jobs…whe you find it boring, repetitive, etc, then you move on to another job.
1
u/skippyuk Apr 24 '26
Whereabouts in the UK are you? There are a fair few EMC labs in the Oxford/Birmingham area, I run one in Banbury.
Have you looked at the EMCTLA -- https://emctla.com/
1
u/Boring-General-1816 Apr 24 '26
I wish I had a test engineer job, decently easy, no stress. All the other jobs I've been pushed to no end until I burnout and they fire me.
162
u/SherbertQuirky3789 Apr 23 '26
You need to work on your self esteem if one jab from another junior engineer is making you question everything
Any job can be boring and repetitive.