Lead Mission Engineer - Full Stack

We need to output HTML fragment with sections: About the Team, The Role, What you will do (maybe Responsibilities), Who You Are (Qualifications/Requirements), Even Better (maybe Preferred Qualifications), Pay Information (Pay). Also maybe Benefits? Not present. Schedule? Not present. Use

for headings. Use

• for lists. Use

  for prose. Remove boilerplate: EEO, equal opportunity, accommodation, export control, etc. Also remove navigation, cookie, legal, duplicated lines. Also remove application instructions (none). Also remove "Visit us at www.str.us for more info." maybe considered boilerplate? It's not required but could be considered promotional; but it's substantive? Might be considered not needed. 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 EEO but maybe considered promotional; but not required to keep. Safer to keep? It's not prohibited. But we can keep as a paragraph? It's not essential but not disallowed. However they said preserve ALL substantive information; do NOT invent or summarize away detail. That line is substantive? It's just a link. Might be considered not essential but still info. I'd keep it as a

  . But we could drop as it's not required. I'd keep it. We need to avoid headings with filler. Ensure each heading has real content. Let's extract sections: About the Team: paragraph(s) about team. The Role: paragraph about role. What you will do: list of duties (Build Prototype Capabilities, Develop and Enhance Features, System Integration, Customer Collaboration, Deployment and Field Testing). Each bullet maybe with sub-bullets? The text includes description after each bullet. We'll treat each as

• with the sentence. Who You Are: list of requirements (Active Secret Security Clearance..., BS..., Experience deploying..., Passion..., Demonstrated strong knowledge..., Knowledge of performance-focused tools..., Demonstrated ability..., Organized..., Demonstrated experience...). We'll put as
  • . Even Better: list of preferred qualifications (Advanced Degree..., Prior US Military Service..., Located in... or willing to relocate). We'll put as
    • . Pay Information: paragraph with salary range and note. We should not include Benefits or Schedule sections. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings (none present). We need to output only HTML fragment. Let's craft. We'll start with

      About the Team

      then

      ... combined paragraphs maybe two paragraphs? The About the Team block has two paragraphs: first about information processing, second about STR’s AC2 Division and MA group. We'll combine into one

      maybe with line breaks? Better to keep as one

      containing both sentences. Could split into two

      but that's okay. We'll keep as one

      . Then

      The Role

      ... paragraph. Then

      Responsibilities

      (or "What you will do") Use heading "What you will do"? The instruction: use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but we can use appropriate heading. Use "Responsibilities". Provide
      • items. Then

        Qualifications

        (or Requirements). Use "Qualifications". Provide
        • . Then

          Preferred Qualifications

          (or Even Better). Use "Preferred Qualifications". Provide
          • . Then

            Pay

            ... salary range and note. We should not include "Skills" separate if covered. Let's extract exact text. About the Team: "Information processing and sense-making systems are the lifeblood of national security efforts, facilitating an understanding of the global situation, strategic planning, and tactical execution. The reliability, accessibility, and sophistication of these systems can determine the outcomes of conflicts before they begin. STR’s Analytics and Command & Control (AC2) Division focuses on developing actionable, advanced technology solutions to provide asymmetric advantages within the information domain. The Mission Applications (MA) Group within the AC2 Division specializes in ensuring the technology that STR creates produces outsized mission impact. Staff within the MA group have a deep understanding of missions and technology needs for national security with skills targeting transition of technology to operational use, including product management, UX Product implementation, software integration & mission engineering, platform engineering, DevOps, and program management. MA staff combine with other science and engineering staff from the various STR research and development groups to form dedicated product teams focused on accelerating the operational transition of cutting-edge software technologies." We'll put that in

            . The Role: "As a Mission Engineer (Full Stack) in the Mission Applications Group, you will develop and deploy software essential for a specific, real-world objective or "mission" in partnership with our customers. You have: 1) expertise in developing and deploying software solutions in complex and high-security environments, 2) deep domain knowledge in the complex missions executed across the Department of Defense, and 3) expertise in modern frameworks, building full stack applications, and integrating APIs for deployment in high-security environments. You will work as a leader of software teams to design, develop, and maintain software systems deployed in operational use. You have experience managing customer relationships while simultaneously leading engineering teams to ensure the delivered product meets the highest standards of quality, reliability, and performance." We'll put in

            . Responsibilities (What you will do): List: - Build Prototype Capabilities: Break down use cases and user-defined problems, build an MVP, and rapidly evolve a solution into a cohesive application - Develop and Enhance Features: Create high-performance, visually appealing frontend solutions that handle complex use cases effectively. Ensure the product is fast, smooth, and intuitive to use, even under heavy load - System Integration: Leading cross functional engineering teams to design, build, and deploy a cohesive system. Integrate independent capabilities into existing solutions - Customer Collaboration: Working closely with end-users and customers, who are typically military or Government operators, to understand their requirements and translate them into software features. You are experienced in product discovery best practices - Deployment and Field Testing: Traveling to integration sites to deploy, test, and triage software in secure operational environments. On average, travel to customer sites should not exceed one week per month We'll put each as

          • . Qualifications (Who You Are): List: - Active Secret Security Clearance with the ability to obtain Top Secret level with SCI Eligibility - BS in Computer Science or related technical field with at least 7 years of work experience. Equivalent experience will be considered - Experience deploying software for DoD or IC missions - A passion for crafting user-centric interfaces and a keen eye for design details - Demonstrated strong knowledge of modern technologies such as React, TypeScript, and Python - Knowledge of performance-focused tools and techniques for rendering large datasets and building responsive, smooth interfaces - A demonstrated ability to adopt new languages, libraries, and technologies - Organized, detail-oriented, and with an ability to work both independently and collaboratively - Demonstrated experience as an effective communicator to both technical and non-technical audiences We'll put each as
          • . Preferred Qualifications (Even Better): List: - Advanced Degree in Computer Science, Information Technology, or related technical field - Prior US Military Service with experience in joint planning, large force battle monitoring, and fluidity with large force debrief best practices - Located in San Diego, CA, Denver, CO, Arlington, VA, or Boston, MA, or willing to relocate We'll put each as
          • . Pay: Paragraph: "Full-Time Salary Range: $175,000 - $240,000 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'll put in

            . We should not include the rest about STR locations, mission, etc. That's boilerplate? It's descriptive of company but maybe considered substantive? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The company description after pay might be considered substantive but could be considered boilerplate? It's about STR's work, locations, mission. It's not required sections but could be kept as a paragraph under maybe "About the Company". However they didn't give a heading for that. But we could include as a

            after Pay? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This company description is not EEO etc. It's substantive about the company. I'd keep it as a

            after Pay maybe under a heading "About STR"? But they didn't list that heading. Could just add a

            without heading? The instruction: use

            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...). It implies we should use headings for sections. Could add a heading "About the Company". Not in examples but could be okay. However they said "Prefer a few substantive sections over many thin ones." Adding another section may be thin. The company description is not essential to the job posting; it's more fluff. I'd consider it boilerplate-ish and could drop. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive but maybe not required for the job. However it's about the company's mission and locations; could be considered relevant. But many job postings include such fluff; but the instruction didn't explicitly say to remove company description. It said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So we should keep it. But we need to decide where to put it. Could add a

            About the Company

            then

            ... but that adds a section. Might be okay. Alternatively we could incorporate it into the About the Team paragraph? Not really. Given the instruction to prefer few substantive sections over many thin ones, adding a thin company section may be against that. I'd lean to omit it as it's not essential to the role. However the instruction says preserve ALL substantive information; but maybe they consider that as not substantive for the job? It's ambiguous. I'd keep it to be safe. Let's include a section "About the Company" with

            About the Company

            and

            containing the remaining paragraphs: "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, though - we need fellow trailblazers. If you are one, join our team and help to keep our society safe! Visit us at www.str.us for more info." We should remove the EEO paragraph and accommodation and export control lines. Also remove "STR is an equal opportunity employer..." etc. Also remove "