Lead Open Software Systems Engineer

We need to output HTML fragment with sections: About the Team? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use appropriate headings based on content. The posting includes "About the Team", "What you will do", "Who you are", "Even Better", "Pay Information". Also location info etc. We must not repeat job title as heading. We must not include boilerplate like EEO, legal, etc. Must preserve all substantive info. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to decide sections: About the Team (maybe as About the role? but they said About the role is example. We can use About the Team as heading? They said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those standard headings, but we can adapt if content matches. However they said "include a section ONLY when the posting has real, specific content for it". So we need to map content to those headings. We have: - About the Team: description of division, RAID group, role purpose. Could be "About the role" or maybe "About the Team". Since they gave example About the role, we could use that heading for the team description. - Responsibilities: "What you will do" list. - Requirements: "Who you are" (basic qualifications) plus maybe "Even Better" as preferred qualifications. - Qualifications: maybe combine with Requirements? But they differentiate Requirements and Qualifications. Usually Requirements are mandatory, Qualifications are preferred. We could put mandatory in Requirements, preferred in Qualifications. - Skills: maybe list specific skills like MBSE, CAMEO, C/C++, etc. Could be separate. - Pay: we have salary range. - Benefits: not mentioned explicitly; there is no benefits info besides maybe location etc. So we should not create Benefits section. - Schedule: not mentioned (full-time implied but not explicit schedule). So we should not create Schedule. We must not create sections with filler like "not specified". So only include sections with real content. Thus sections: About the role (or About the Team), Responsibilities, Requirements, Qualifications, Skills, Pay. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we need
  . For requirements list (mandatory), also
  . For qualifications (preferred) also
  . For skills list also
  . For pay maybe just

  . We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should keep the info, not omit. We can rephrase but must keep meaning. Safer to copy sentences. We need to remove boilerplate: equal opportunity employer, accommodation, legal, etc. Also remove duplicated lines. Also remove "Visit us at www.str.us for more info." maybe considered boilerplate? It's not legal but maybe considered promotional; but it's substantive? Might be considered info about company; but it's not required. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "Visit us at www.str.us for more info." is not those categories; it's just a link. Might be okay to keep? It's not essential but could be considered navigation? Probably safe to keep? However they said "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." That link is minor metadata; we could drop it. Safer to drop. Also remove "STR is an equal opportunity employer..." etc. Also remove "If you need a reasonable accommodation..." etc. Also remove "Pursuant to applicable federal law..." etc. Also remove "STR is a growing technology company with locations near Boston, MA, Arlington, VA, near Dayton, OH, Melbourne, FL, Carlsbad, CA, Atlanta, GA, and Denver, CO." That's location info; could be considered substantive? Might be considered company info but not required for job. Might be considered boilerplate? Not exactly. Might keep as part of About the role? But they didn't ask to keep location. The instruction: "Preserve ALL substantive information". Location could be substantive for candidate. But they didn't list a section for location. Could include in About the role paragraph. We'll include location info in About the role paragraph. Now craft HTML. We'll start with

  About the role

  then

  containing the team description. Team description: "The Sensors Division at STR focuses on technology development for advanced sensor systems, particularly in the areas of airborne/surface-based radar, electronic warfare, underwater acoustics, hyperspectral imaging, and EO/IR sensing. Within this role, we perform work on full system prototypes, experiment campaigns and technology component development. Development roles within the Sensors Division include RF analog/digital hardware, acoustic hardware, signal processing algorithms, machine learning algorithms, tracking/fusion, as well as real-time embedded processor implementation. Within the Sensors Division, the Real-time Architectures, Integration and Demonstration (RAID) Group focuses on transition of algorithms from concept to real-time software, providing open architecture expertise, and facilitating integration of capabilities for experimentation, test, and deployment. The RAID Group is seeking a Lead Systems Engineer with demonstrated expertise in Model Based Systems Engineering (MBSE) to help design, develop, implement, test, and maintain real-time software that controls complex hardware systems while complying with open architecture standards. You will work as part of focused teams to transition software products from internally developed and integrated software into production-quality software that can be transitioned to outside integrators for use on their embedded and distributed computing platforms. You will be responsible for developing best practices and automated processes in coordination with software and system engineers to further integrate MBSE into Agile Software development processes. A successful candidate will have experience working on teams that have developed large scale high-performance C/C++ software for sensor systems. Strong understanding of MBSE practices and how they are compatible with real-time systems developed via an Agile process is essential. Experience with open architecture frameworks and standards is highly desired. Strong technical, interpersonal, and communication skills are important for working in collaborative, multi-disciplinary teams." We need to ensure we didn't miss any detail: also mention "Within this role, we perform work on full system prototypes, experiment campaigns and technology component development." Already included. Now Responsibilities: list from "What you will do:" bullet points. - Collaborate with principal investigators, software engineers, and other system engineers to plan, model, develop, test, and document large scale software/hardware systems - Collaborate with software and system engineers to integrate MBSE artifacts with software development pipelines (code / test generation, large scale code analysis, etc.) - Collaborate with software and system engineers to integrate MBSE processes to streamline software development - Perform requirement extraction, management, and analysis for RF sensor signal processing or equivalent systems - Document (and/or support documentation of) system designs, software designs, APIs, implementation details, and technical reports - Perform peer reviews and suggest next steps for technical work - Support approximately 5% travel for integration events, customer meetings, and field demonstrations Make

  • each. Now Requirements (mandatory): from "Who you are:" bullet points. - Ability to obtain and retain a Secret or Top Secret Security Clearance, for which U.S citizenship is needed by the U.S government - PhD + 2 years, MS + 5 years, or BS + 7 years in Systems Engineering, Computer Science, Computer Engineering, Electrical Engineering, or related field - Experience with Model Based Systems Engineering for medium to large scale agile software development programs - Strong proficiency with CAMEO or other Model Base Systems Engineering tools - Experience working with professional software development teams - Excellent technical writing and communication skills Make
    . Now Qualifications (preferred): from "Even Better:" bullet points. - Active Security Clearance at the Secret or Top Secret level (strongly preferred due to clearance processing time) - Experience developing products / toolkits that are integrated by 3rd parties with various hardware and software subsystems - Proficiency in automated integration of CAMEO or other Model Based Systems engineering tools with Agile development processes - Experience working with signal processing development teams - Experience with open architecture standards and frameworks - Experience with version control systems (Git) and collaborative development practices - Experience with CAMEO plugin development - Understanding of RF sensor system concepts - Familiarity with CI/CD pipelines, and DevOps and integrating MBSE to those systems - Prior contributions to proposal development and technical writing Make
    . Now Skills: maybe we can list specific technical skills not already covered? Could include: MBSE, CAMEO, C/C++, real-time software, open architecture, Agile, Git, CI/CD, DevOps, signal processing, RF sensor, etc. But we already covered many in requirements/qualifications. To avoid duplication, we could create a Skills section summarizing key skills: MBSE, CAMEO, C/C++, real-time embedded software, open architecture standards, Agile, Git, CI/CD, DevOps, signal processing, RF sensor, technical writing, communication. However we must not invent or summarize away detail; we can list them as they appear. But many appear already. Might be okay to have Skills section that consolidates. However instruction: "Prefer a few substantive sections over many thin ones." So maybe we can skip Skills section and incorporate skills into Requirements/Qualifications. But they said use
    • for any list of duties/requirements/benefits. So we already have lists for responsibilities, requirements, qualifications. That's enough. Pay: we have salary range. We need

      Pay

      then

      with the salary range info. Pay Information: "Full-Time Salary Range: $174,000.00 - $225,000.00 The salary range listed is based on external market data. Offers are based on factors, such as but not limited to, the candidate’s experience, education, training, key skills/critical skills, security clearances, and prevailing market and business conditions." We should keep all that. Now we must not include any other sections like Benefits, Schedule. Now ensure we didn't include any boilerplate: we removed EEO, legal, accommodation, etc. Also removed "Visit us at www.str.us for more info." and maybe the company description about locations and mission? That is after Pay Information. That is more company marketing; could be considered boilerplate? Not exactly legal/EEO. It's substantive about company but maybe not needed. The instruction: "Preserve ALL substantive information". That includes company description? It's about STR's work, mission, etc. Might be considered substantive. However they didn't give a section for company overview. Could include in About the role paragraph as extra sentences. But we already have a long paragraph; we could add after that: "STR is a growing technology company with locations near Boston, MA, Arlington, VA, near Dayton, OH, Melbourne, FL, Carlsbad, CA, Atlanta, GA, and Denver, CO. We specialize in advanced research and development for defense, intelligence, and national security in: cyber; next generation sensors, radar, sonar, communications, and electronic warfare; and artificial intelligence algorithms and analytics to make sense of the complexity that is exploding around us. STR is committed to creating a collaborative learning environment that supports deep technical understanding and recognizes the contributions and achievements of all team members. Our work is challenging, and we go home at night knowing that we pushed the envelope of technology and made the world safer. STR is not just any company. Our people, culture, and attitude along with their unique set of skills, experiences, and perspectives put us on a trajectory to change the world. We can't do it alone