Job Title: System Verification Engineer
Type of Company: My company manufactures and tests telecommunications equipment that can be found in telephone companies central offices as well as cell sites. Some of our customers include AT&T, Verizon, Sprint, etc.
Education: BS, Electrical Engineering, Northeastern University
Previous Experience: I was hired out of college to work as a system verification engineer for a large telecommunications company on a certain product. I then moved on to the customer support group for that product, but later moved back to a system verification position for another of the company's products.
Job Tasks: My job responsibilities mainly include testing software that runs in telecommunications systems. The first step in the testing process is to write a set of requirements for the specific capability that you want to test. This set of requirements is used to create a test plan and the test plan is run on the software, written from the same set of requirements by the Software Development group. Any problems found in the software are then documented. Sometimes a meeting is needed between the System Engineering group, Software Development group, and myself to decide on the best way to resolve the issue. Then the software is fixed by the Software Development group, and has to be tested again.
The actual testing can be done by writing software scripts which automatically execute the commands used to test the capability, but it is possible to enter the commands manually too.
My responsibilities also include acting as the Release Coordinator for the System Verification group. This basically means that I am the lead (head) engineer on the product I work on. I attend weekly project meetings with the different disciplines (system engineering, software development, system verification) so I can keep everyone posted on the work we've been doing. Since my company also has employees in China, India, Italy, etc., I also serve as a liaison with employees around the world.
Best and Worst Parts of the Job: The best part of my job is being able to find the bugs in the software, and then working with a team of people to get them resolved.
The worst part of my job is that sometimes the responsibilities that I have as lead engineer take up most or even all of my time, and I do not have enough time to test the software.
1. Technology changes so fast these days. You need to stay current with the latest technologies. Your education shouldn't end when you graduate from college.
2. Because many companies are global, if you don't already know a second language language, learning one is very useful.
3. Join engineering clubs while in school or even the student chapter of the IEEE organization. Since engineering jobs are very competitive for recent college graduates, it helps to be able to have things like these on your resume.
These schools offer particularly quick info upon request, and we have written detailed profiles for each (click school names to see the profiles).
Request info from multiple schools, by clicking the Request Info links.
Prepare for an exciting new career at the Milan Institute.
The inside stories from people actually working in the field.
Click a story title to show the story, and click the title again to hide it.
Career Stories are concise, real-world career overviews written by people relating their personal career experiences and wisdom. They provide invaluable insights and mentoring advice to students and career changers.
Most stories include:
Please also see our detailed information about Electrical Engineers, including: