Junior Systems Engineer

Who you are

• You're an early-career engineer who wants to work on the whole product, not one slice of it, and you want your work to end up in the field.
• You like learning new technology. You want to know how a GNSS receiver holds a position fix under jamming, why an antenna design changed and what a test result is really telling you. When something is new to you, you read up and keep asking questions until it makes sense.
• You're hands-on. You'd rather have a unit on the bench than spend all day in documents. You're comfortable with test equipment, cabling and assemblies, and you want to see the hardware your procedures describe.
• You sweat the details. A wrong revision letter or a skipped step in a test procedure becomes a problem on the production floor or at the customer. You catch those before they leave your desk, and you keep your work organized so anyone can find the current version.
• You can work on your own and with a team. You'll take tasks from the Lead Systems Engineer and support engineers on several projects. You can run with an assignment without someone checking in, and you know when to pull in help.
• You adapt when plans change. Priorities shift with customer schedules, test results and design changes. You can move between projects in the same day without losing track of either one.
• You care who's on the other end. Our products go to warfighters who need to know where they are when GPS is jammed or spoofed. A spec you get wrong or a test you rush ends up in their hands. You take that seriously, and it shows in your work.
• Electronics and the design process. You have one to five years of hands-on experience with electronics, assemblies and computer components. You've taken part in a design process from requirements through build and test. Pick a project and you can walk us through it: what it had to do, how you tested it, what failed and what you changed.
• Attention to detail and organization. You keep your work accurate and organized while several tasks are open at once. You can show how you track revisions, manage your files and catch errors before they reach someone else.
• Analytical skills. When a test fails or the data doesn't look right, you work the problem methodically until you find the cause. You can describe a problem you traced and how you knew you'd found the real cause.
• Writing and documentation. Most of this job ends up in a document that someone else builds, tests or buys from. You write procedures and specifications clear enough that a technician can follow them without asking what you meant. You can also explain a technical issue out loud to engineers, technicians and managers. You can show us something you wrote.
• Ability to lift 20 lbs. You'll move units, assemblies and test equipment around the lab and the production floor.
• U.S. person status. This role involves access to technical data controlled under the International Traffic in Arms Regulations (ITAR). You must be a U.S. person as defined in 22 CFR 120.62. That includes U.S. citizens, lawful permanent residents, and certain protected individuals such as refugees and asylees.
• Clearance eligibility. You must be able to obtain and maintain a U.S. government security clearance, which requires U.S. citizenship.

Nice to Haves

Additional information