Captivation Software
Systems Engineer 2 (Travel Required) - RF/Python
About this role
Captivation Software seeks a mid-level systems engineer with RF and Python expertise to support electromagnetic testing and systems engineering work on government programs. The role requires a Top Secret/SCI clearance and involves 3 trips per year for 7–10 days.
What you'll do
- Conduct EMI testing and emissions analysis across HF, VHF, and UHF frequency bands
- Formulate, document, and execute comprehensive RF test plans
- Develop technical recommendations and formal test reports for system and component performance
- Specify and review technical requirements to meet E3 noise field limits
- Operate and troubleshoot RF instrumentation including network analyzers, spectrum analyzers, and oscilloscopes
- Coordinate with internal and external stakeholders to support program and mission objectives
What they're looking for
- Python programming
- Visual Basic for Applications
- RF testing and EMI analysis
- Network analyzers and spectrum analyzers
- Test plan formulation and documentation
- Electromagnetic compatibility (EMC) principles
- Technical report writing
- RF component knowledge (amplifiers, filters, isolators)
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Captivation Software
Captivation Software builds high-performance computing and secure analytics infrastructure for mission-critical government programs, specializing in HPC testing, enterprise dataflow architectures, and cleared defense systems. The company is hiring senior test engineers, systems engineers, and technical leaders with deep expertise in Linux, cloud infrastructure, and security clearances to validate systems and architect solutions for intelligence community operations.
View all jobs at Captivation SoftwareLikely interview questions
- Describe your experience conducting EMI testing and how you've applied RF theoretical knowledge in real-world scenarios.
- Walk us through a test plan you developed—what were the key considerations and how did you document it?