Virtual Event Producer Jobs in Wisconsin (NOW HIRING)

The AFSIM Simulation Engineer develops, executes, and analyzes physics-based mission simulations using the Advanced Framework for Simulation and Integration Modeling (AFSIM). This role supports mission effectiveness assessments, experimentation, and Live, Virtual, and Constructive (LVC) events by implementing MBSE-derived SysML views (requirements, functional threads, physical architectures, and interfaces) as AFSIM inputs to evaluate sensor-to-shooter kill chains and operational effects, including EMSO-relevant influences.

• Developing, modifying, and executing AFSIM models derived from MBSE SysML artifacts, including mission threads, functional flows, system architectures, and interface definitions
• Analyzing blue vs. red kill chains, system interactions, and mission-level effects across integrated sensor, shooter, and command elements
• Translating MBSE handoff artifacts (requirements allocations, activity diagrams, block definitions, internal block diagrams) into executable AFSIM entities, behaviors, and interactions
• Integrating sensor, RF, EW, weapon, and platform models consistent with MBSE-defined system boundaries, interfaces, and architectural assumptions
• Supporting experimentation, test events, and LVC exercises focused on validating system architectures, mission threads, and kill-chain performance
• Conducting verification and validation of AFSIM models against MBSE-defined assumptions, constraints, and system definitions
• Performing statistical and analytical assessments of mission outcomes and kill-chain performance drivers, producing analysis products that trace back to system design and architecture decisions
• Collaborating with MBSE, LVC, and other modeling and simulation teams to maintain digital thread continuity from SysML models through AFSIM simulations to analysis reports and T&E artifacts

FILLING THIS POSITION IS CONTINGENT UPON FUNDING

• Bachelor’s degree in engineering, physics, operations research, or related technical field
• Five or more years of modeling and simulation experience supporting system-level or mission-level analysis
• Hands‑on experience developing and executing AFSIM models
• Strong understanding of mission-level analysis, system architectures, and kill‑chain dynamics
• Ability to interpret and analyze large simulation datasets and trace results back to system requirements and architecture drivers

• Experience supporting DoD platforms or hardware‑centric mission systems within an MBSE‑driven development environment
• Experience executing sensor‑to‑shooter or effects‑based kill‑chain analysis tied directly to system architecture trades
• Experience supporting DoD test, evaluation, or experimentation activities using MBSE‑informed scenarios and architectures
• Programming experience in Python, C++, or MATLAB

SRC IS A CONTRACTOR FOR THE U.S. GOVERNMENT, THIS POSITION WILL REQUIRE U.S. CITIZENSHIP AS WELL AS A U.S. GOVERNMENT SECURITY CLEARANCE AT THE SECRET LEVEL WITH TOP SECRET / SCI ELIGIBILITY

• No travel required

Medical, dental, and vision plans; 401(k) with a company match; life insurance; vacation and sick paid time off accruals starting at 10 days of vacation and 5 days of sick leave annually; 11 paid holidays; tuition reimbursement; and a work environment that encourages excellence.

Scientific Research Corporation is an equal opportunity employer that does not discriminate in employment.

All qualified applicants will receive consideration for employment without regard to their race, color, religion, sex, age, sexual orientation, gender identity, national origin, disability, protected veteran status, or any other protected characteristic under federal, state or local law.

Scientific Research Corporation endeavors to make www.scires.com accessible to any and all users. If you would like to contact us regarding the accessibility of our website or need assistance completing the application process, please contact jobs@scires.com for assistance. This contact information is for accommodation requests only and cannot be used to inquire about the status of applications.