Research Scientist

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Team", "What You Will Do", "Required Qualifications", "Benefits", "Salary Range". Also maybe "About The Team" is a section heading. The rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to parse the posting and extract sections. The posting includes: - Intro paragraph about Anduril (mission). This is likely part of "About the role"? Actually "About The Team" is a heading. The intro before "About The Team" could be considered "About the role"? But we can treat "About The Team" as a section heading. The intro before that could be part of "About the role" or maybe we can combine into a single "About the role" section. However the rules say we should use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings if they match content? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, but we can use those headings if appropriate. The posting has "About The Team", "What You Will Do", "Required Qualifications", "Benefits", and also salary range. There's also "US Salary Range $126,000—$167,000 USD". That's pay info. So we should have a Pay section. We need to remove boilerplate: scam warning, data privacy, etc. Also remove "Protecting Yourself from Recruitment Scams", "Data Privacy". Also remove "Explore Our Benefits." maybe keep benefits list. We need to preserve all substantive information: mission description, team description, what you will do bullet points, required qualifications bullet points, benefits list, salary range. We need to format as HTML with

  headings and

  for prose,

  • for lists. We need to decide which sections to include. Potential sections: - About the role (or About the team) - we can combine the introductory paragraphs about Anduril mission and team description. - Responsibilities (What You Will Do) - bullet list. - Qualifications (Required Qualifications) - bullet list. - Benefits - bullet list. - Pay - maybe a paragraph with salary range. We should not include Schedule (not present). Skills maybe not separate; qualifications cover. We need to ensure we don't create empty sections. Let's extract content. Intro paragraphs: "Anduril Industries is a defense technology company with a mission to transform U.S. and allied military capabilities with advanced technology. By bringing the expertise, technology, and business model of the 21st century’s most innovative companies to the defense industry, Anduril is changing how military systems are designed, built and sold. Anduril’s family of systems is powered by Lattice OS, an AI-powered operating system that turns thousands of data streams into a realtime, 3D command and control center. As the world enters an era of strategic competition, Anduril is committed to bringing cutting-edge autonomy, AI, computer vision, sensor fusion, and networking technology to the military in months, not years." Then "About The Team Anduril’s Research Scientists excel at developing state-of-the art algorithms and software that solve scientific problems with real-world applications. Working in small innovative teams, our research scientists build solutions that make a difference. Our research endeavors don’t end once we’ve written a journal or conference paper describing our technology; rather, our work is complete when our technology has been deployed in mission-critical systems and our customers within government and industry are successful. As science fiction writer Arthur Clarke wrote, “Any sufficiently advanced technology is indistinguishable from magic.” Therefore, Anduril is seeking talented “magicians” to join in our common struggle of expanding the boundary of what’s possible." We can combine these into an "About the role" or "About the team" section. Since the heading "About The Team" is present, we could use that as heading. But the rule says use headings like About the role, Responsibilities, etc. It doesn't forbid other headings, but suggests those examples. Safer to use "About the role" as heading and include both the mission and team description. However we might lose the "About The Team" heading which is specific. But the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It doesn't say we cannot use other headings, but to be safe, we should map content to those headings. Thus: -

    About the role

    containing the mission description and team description. -

    Responsibilities

    containing the bullet list from "What You Will Do". -

    Qualifications

    containing the bullet list from "Required Qualifications". Could also split into Requirements and Qualifications but we have only one. -

    Benefits

    containing bullet list from benefits. -

    Pay

    containing salary range paragraph. We need to ensure we don't include filler like "commensurate with experience". Not present. Now extract bullet lists. "What You Will Do" section: "Contribute to the direction of a talented small team with your expertise and ideas; Create mathematically principled solutions to some of the world’s most challenging information science problems; Prototype state-of-the-art algorithms in an agile development environment; Implement high-performance software spanning the spectrum from tactical systems to web applications; Use high-fidelity modeling and simulation environments, innovative analysis tools, and flexible compute clusters to quantify the benefit of our technology; Engage with our customers, to ensure successful outcomes for their mission-critical needs; Help your colleagues and customers understand what you’re doing and why." Each line ends with semicolon. We'll make each a
  • . "Required Qualifications" section: "A Research Scientist at Anduril should possess an M.S. or Ph.D. in Applied or Computational Mathematics, Electrical Engineering, Computer Science, Controls and Dynamical Systems, Aerospace Engineering, Statistics and Probability, or a related field. A Research Scientist should have a record of academic excellence, including demonstrated experience in most of the following areas: Applied Mathematics: differential equations, linear algebra, numerical analysis, and continuous or discrete optimization; Engineering: controls, estimation theory, digital signal processing, and machine learning; Scientific Computing: software design, algorithm implementation, and software analysis, testing, and optimization; Probability: statistics and random processes. A Research Scientist should have effective written and verbal communication skills, with the demonstrated ability to convey salient details about advanced technology in a compelling manner to both experts and non-experts alike. An active U.S. Top Secret security clearance" We need to turn into bullet list. The content includes some sentences that are not bullet-like but we can break into items: maybe each bullet corresponds to each of the areas? However the instruction: Use
    • for any list of duties/requirements/benefits. So we need to make a list. The posting has a list of areas after "including demonstrated experience in most of the following areas:" then bullet-like items separated by semicolons: Applied Mathematics: ...; Engineering: ...; Scientific Computing: ...; Probability: ... . Also there are preceding sentences about degree and record of academic excellence, and communication skills, and clearance. Those are not part of the list but are still requirements. We could treat them as separate list items as well. The rule says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all those statements. We can make each sentence a list item. Thus list items: - Possess an M.S. or Ph.D. in Applied or Computational Mathematics, Electrical Engineering, Computer Science, Controls and Dynamical Systems, Aerospace Engineering, Statistics and Probability, or a related field. - Have a record of academic excellence, including demonstrated experience in most of the following areas: - Applied Mathematics: differential equations, linear algebra, numerical analysis, and continuous or discrete optimization; - Engineering: controls, estimation theory, digital signal processing, and machine learning; - Scientific Computing: software design, algorithm implementation, and software analysis, testing, and optimization; - Probability: statistics and random processes. - Have effective written and verbal communication skills, with the demonstrated ability to convey salient details about advanced technology in a compelling manner to both experts and non-experts alike. - Have an active U.S. Top Secret security clearance. But note the nested list inside the second item. Could flatten: we could make each area as separate list item, but then we lose the grouping. However we can keep the second item as a paragraph containing the sublist? The rule says use
      • for any list of duties/requirements/benefits. It doesn't forbid nested lists? Might be okay but safer to keep flat list. We could break the second item into multiple items: each area as separate list item, and also include the preceding sentence as separate item. That would preserve all info. Thus list: - Possess an M.S. or Ph.D. in Applied or Computational Mathematics, Electrical Engineering, Computer Science, Controls and Dynamical Systems, Aerospace Engineering, Statistics and Probability, or a related field. - Have a record of academic excellence. - Demonstrated experience in Applied Mathematics: differential equations, linear algebra, numerical analysis, and continuous or discrete optimization. - Demonstrated experience in Engineering: controls, estimation theory, digital signal processing, and machine learning. - Demonstrated experience in Scientific Computing: software design, algorithm implementation, and software analysis, testing, and optimization. - Demonstrated experience in Probability: statistics and random processes. - Have effective written and verbal communication skills, with the demonstrated ability to convey salient details about advanced technology in a compelling manner to both experts and non-experts alike. - Have an active U.S. Top Secret security clearance. But we lost the phrase "including demonstrated experience in most of the following areas:" which is now covered by the separate items. That's okay. Now Benefits section: "Additionally, Anduril offers top-tier benefits for full-time employees, including: At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next. For more information, Explore Our Benefits." But the actual benefits list is not explicitly listed; it's just a description. There's no explicit bullet list of benefits. The posting says "At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next." That's not a list. There's no specific benefits enumerated. So we should not create a Benefits section unless there is real, specific content. The rule: never create Pay/Schedule/Benef