Senior Software Engineer (Modeling, Simulation, & Visualization)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe Qualifications), Skills? The posting includes "About The Role", "Primary Responsibilities", "Required Qualifications", "Desired Qualifications", "About Integer Technologies", "Company Benefits", "Company Perks". We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. Pay and Schedule not present, so omit. Benefits present, so include Benefits. Skills maybe not explicit; we could combine qualifications into Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can decide to include About the role, Responsibilities, Requirements (maybe Required Qualifications), Qualifications (maybe Desired Qualifications), Benefits, maybe Skills not present. Could also include Skills if we extract from qualifications? But better to only include sections with real content. We have About the role content, Responsibilities content, Required Qualifications content, Desired Qualifications content, Company Benefits content, Company Perks content (maybe could be under Benefits or separate). The instruction: Prefer a few substantive sections over many thin ones. Could combine Required and Desired Qualifications into a single Qualifications section. Could also put Company Perks under Benefits or as separate? Might be okay to have Benefits and maybe not separate Perks. But we have both Benefits and Perks; we could include Benefits section covering both benefits and perks. Or we could have Benefits and maybe another section like "Company Overview"? Not in list. Probably best to have: About the role, Responsibilities, Qualifications (combining required and desired), Benefits (including perks). No Skills, Pay, Schedule. We must not repeat job title as heading. No metadata like Job ID. Remove boilerplate. We need to preserve all substantive information. So we need to include details from About The Role, Primary Responsibilities, Required Qualifications, Desired Qualifications, Company Benefits, Company Perks. We must format as HTML: use

for section headings,

• for any list of duties/requirements/benefits, and

  for prose. We need to decide what is list vs prose. The responsibilities are bullet-like sentences; we can make them

  • . Same for qualifications. Benefits are list-like sentences; we can make
    • . Perks also list. We need to ensure we don't invent or summarize away detail. Keep all details. Let's extract content. About The Role paragraph: "This role will lead the software development and architecture of a digital twin model integrating vehicle dynamics and physics, environmental, and acoustic models with measured and simulated data. The engineer will work closely with academic researchers and domain experts to transition scientific models and algorithms into maintainable software and develop simulation capabilities for evaluating UUV performance, mission concepts, and environmental interactions. The role will also transform complex model outputs and scientific datasets into visual research demonstrations, including acoustic models, mission routes, environmental overlays, trade-space analyses, and interactive model controls. These capabilities will support exploration of mission-planning concepts such as energy efficiency, mission timing, and route optimization, with the intent to transition toward real-time UUV autonomy. The ideal candidate combines strong software engineering with experience in modeling and simulation, scientific computing, and visualization, with additional experience in autonomy, optimization, or AI/ML highly desirable." We'll put that in

      under About the role. Primary Responsibilities list: each sentence starting with a verb. We'll make

      • for each. List them: - Serve as the senior software developer and software architecture lead for a multidisciplinary applied research team. - Lead development of a physics-based digital twin and modeling/simulation framework integrating acoustic, environmental, vehicle, and mission-level models. - Develop and integrate UUV modeling and simulation, including vehicle performance, energy consumption, operating constraints, and mission execution. - Transition research algorithms and prototype code into modular, maintainable software, integrating measured and simulated scientific datasets. - Develop scientific visualizations and interactive research demonstrations to communicate model behavior, mission tradeoffs, and operational implications. - Develop and integrate mission-planning, optimization, and AI/ML capabilities, including hybrid physics-based and data-driven approaches. - Establish software interfaces, APIs, testing, CI/CD, documentation, and other software engineering best practices. - Support the evolution of the architecture from research simulation and pre-mission analysis toward real-time UUV mission adaptation and autonomy. Required Qualifications list: - U.S. Citizen with the ability to obtain and maintain a DoD Secret clearance. - Bachelor’s degree or higher in Computer Science, Software Engineering, Robotics, Engineering, or a related technical field. - 5+ years of professional software development experience in scientific computing, modeling and simulation, robotics, or complex engineering systems. - Strong proficiency in Python and/or C++ with experience developing modular software architectures. - Experience with physics-based modeling, numerical simulation, and scientific datasets. - Ability to transition research algorithms and prototype code into robust, maintainable software. - Experience with scientific visualization and interactive model/data demonstrations. - Familiarity with modern development practices including Git/ADO, testing, CI/CD, code review, and documentation. - Experience with scientific computing tools such as NumPy, SciPy, Xarray, MATLAB, or equivalent frameworks. Desired Qualifications list: - Experience with robotics, autonomous vehicles, UUVs/AUVs, vehicle modeling, ROS/ROS2, or other autonomous-system simulation environments. - Experience with optimization, path planning, mission planning, operations research, or multi-objective decision-making. - Experience with AI/ML, including PyTorch, TensorFlow, scikit-learn, or integration of data-driven models with physics-based simulations. - Experience with digital twins, Monte Carlo simulation, uncertainty analysis, or distributed simulation. - Experience with geospatial data, GIS, environmental modeling, oceanography, underwater acoustics, or acoustic signal processing. - Ability to work effectively in a multidisciplinary applied research environment, translating evolving research concepts into executable software. About Integer Technologies paragraph: "Integer Technologies is an applied research and product development company founded by scientists and engineers with a passion for protecting freedom with innovation. We perform R&D on next-generation systems and technologies for the Department of Defense and other U.S. Government agencies. We are hardware and software developers with experience transforming research into fieldable technology. Our core portfolio of research includes projects in power & energy systems, unmanned systems (with an emphasis on maritime systems), digital engineering, cyber security, and advanced manufacturing. Our mission is to create a safer world by translating scientific discoveries into reliable products that address urgent national security needs… at the speed of relevance." Company Benefits list: - Integer fully covers medical, prescription, vision, and dental insurance costs for the employee and dependents. - Meaning Integer standard plan pays 100% of health insurance premiums for your entire family from a well-known national insurer, saving its employee’s thousands of dollars annually. - Relocation assistance available. - Base salaries which exceed local & national industry averages. - Year-end performance-based bonuses. - 401(k) with company matching that vest immediately; no funny business. - Paid Vacation - Paid Sick Leave - Paid Holidays Company Perks list: - Startup culture with the stability of a large company. - Integer’s business plan has years of time-phased contracted work, alleviating the would-be risk from a traditional small company. - Direct access to company leadership, prioritization of people over process, and a stellar team with a shared desire for personal and professional growth. - Friendly atmosphere where people enjoy not only their work and what they’re creating but enjoy helping each other as well. We need to avoid duplication: The "Meaning Integer standard plan pays..." seems like a continuation of the first benefit; we can keep as separate list item. Now decide sections: About the role, Responsibilities, Qualifications (combining required and desired), Benefits (including perks). Could also include a short "About Integer Technologies" as a section? Not in the heading list but could be under "About the company"? Not listed. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies we should use those headings when appropriate. Could also add a heading like "About Integer Technologies" but not in list; maybe better to incorporate that into About the role? But About the role already covers role description; company description could be separate but not required. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit company description or incorporate into Benefits? Probably better to include a brief "About Integer Technologies" as a paragraph under maybe a heading "About the Company"? Not in list; but we could still use

        for it? The instruction says use those headings for section headings (e.g. ...). It doesn't say we cannot use other headings, but to be safe, we could include it as a

        without heading, or we could incorporate into Benefits? Might be better to include a short paragraph under a heading "About Integer Technologies" as it's substantive. However, the instruction says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, not exhaustive. So we can use other headings if needed. But to follow the spirit, we could include a heading "About Integer Technologies". However, they said "Prefer a few substantive sections over many thin ones." Adding another section increases count. Could we merge company description into Benefits? Not really. Could we put it as a

        before Benefits without heading? That would be a prose section without heading; maybe acceptable. The instruction: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say every prose must be under a heading, but likely they expect sections. Safer to include a heading for company description, maybe "About Integer Technologies". Let's do that. Thus sections: About the role, Responsibilities, Qualifications, About Integer Technologies, Benefits. We need to avoid Pay and Schedule. Now produce HTML fragment. We'll wrap each section in

        heading then content. For lists:

        • ...

        For prose:

        ...

        Make sure to preserve all details. Let's craft. About the role:

        About the role

        This role will lead the software development and architecture of a digital twin model integrating vehicle dynamics and physics, environmental, and acoustic models with measured and simulated data. The engineer will work closely with academic researchers and domain experts to transition scientific models and algorithms into maintainable software and develop simulation capabilities for evaluating UUV performance, mission concepts, and environmental interactions. The role will also transform complex model outputs and scientific datasets into visual research demonstrations, including acoustic models, mission routes, environmental overlays, trade-space analyses, and interactive model controls. These capabilities will support exploration of mission-planning concepts such as energy efficiency, mission timing, and route optimization, with the intent to transition toward real-time UUV autonomy. The ideal candidate combines strong software engineering with experience in modeling and simulation, scientific computing, and visualization, with additional experience in autonomy, optimization, or AI/ML highly desirable.

        Responsibilities:

        Responsibilities

        • Serve as the senior software developer and software architecture lead for a multidisciplinary applied research team.
        • Lead development of a physics-based digital twin and modeling/simulation framework integrating acoustic, environmental, vehicle, and mission-level models.
        • Develop and integrate UUV modeling and simulation, including vehicle performance, energy consumption, operating constraints, and mission execution.
        • Transition research algorithms and prototype code into modular, maintainable software, integrating measured and simulated