Computer Scientist - Sr

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into 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. We need to parse the posting. Key sections: Purpose and Impact: description. Could be "About the role" maybe. Work Schedule: Standard 40-hour work week between 0600 and 1800, Monday through Friday. Ability to work shift work if necessary. Essential Responsibilities: list of bullet points. Minimum Requirements (Knowledge, Skills, And Abilities): list. Security Clearance Required TS/SCI. Ability to take a poly if requested. Minimum Education: Master's degree or Ph.D. in Data Science, Computer Science, Statistics, Mathematics, or related quantitative field. Minimum Years Of Experience: 7-10 years of experience in computer science, software development, or similar technical roles, with at least 3 years supporting intelligence or defense applications. Other Responsibilities: Safety, Quality, Procedure Compliance (these are generic boilerplate maybe but they are part of posting; but they might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Safety, Quality, Procedure Compliance might be considered generic corporate policy but not necessarily EEO. However they are not specific to role; they are generic responsibilities. Might be considered boilerplate? The instruction says remove duplicated lines, but not necessarily all generic policies. However they say "Prefer a few substantive sections over many thin ones." Might combine these into a "Other Responsibilities" section? But they said include a section ONLY when posting has real, specific content for it. The Safety, Quality, Procedure Compliance are generic but still content. Might be okay to include as a section "Other Responsibilities". However they also said "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Safety etc not EEO. Might keep. Compensation Details: 80K to 190K. That's pay range. Benefits Overview: list. Original Posting date etc: maybe minor metadata; we can fold into short

  or drop. Probably drop. We need to decide sections: About the role (Purpose and Impact), Responsibilities (Essential Responsibilities), Requirements (Minimum Requirements plus Minimum Education and Experience?), Qualifications maybe combine? But we have to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: Purpose and Impact paragraph. - Responsibilities: Essential Responsibilities list. - Requirements: Minimum Requirements (Knowledge, Skills, And Abilities) plus Minimum Education and Minimum Years Of Experience? Could be separate but we can combine into Requirements. - Qualifications: maybe Security Clearance Required? Or could be separate but we have limited sections. Could put Security Clearance under Qualifications. - Skills: maybe not needed if we already covered in Requirements. But we could list skills from Minimum Requirements as a separate Skills section. However we need to avoid thin sections. Better to combine. - Benefits: Benefits Overview. - Pay: Compensation Details. - Schedule: Work Schedule. We must not create sections with filler. All these have content. We must not repeat job title. We must not include Job ID etc. We must output only HTML fragment. We need to use

  for each section heading. Inside sections, use

  for prose,

  • for lists. We need to preserve all substantive information. Let's extract content. Purpose and Impact paragraph: "We are seeking a Senior-Level Computer Scientist to support various locations. The ideal candidate will need to do the following. Employs a wide range of computer science disciplines to develop innovative technical solutions that enhance intelligence capabilities across JIOC operations. This position applies advanced scientific methods and technical expertise to design, develop, test, and maintain complex software systems that process, analyze, and visualize large volumes of multi-source intelligence data. The Computer Scientist utilizes industry best practices and modem software development methodologies to create scalable, secure, and efficient solutions that address critical intelligence requirements and challenges. This role requires comprehensive knowledge of computer science principles and practical experience implementing solutions that adhere to DoD cybersecurity requirements while enabling rapid and secure deployment of new capabilities to the operational environment." We can keep as paragraph(s). Could split into multiple

    but okay. Work Schedule: "Standard 40-hour work week between 0600 and 1800, Monday through Friday. Ability to work shift work if necessary." Essential Responsibilities list: each bullet after "Essential Responsibilities". Let's extract: - Apply computer science disciplines including software engineering, algorithms, distributed systems, cloud computing, full-stack development, and database management. - Design and develop technical solutions that meet JIOC mission requirements and close intelligence gaps. - Support the development and optimization of automated intelligence processes and analysis tools. - Investigate, prototype, and evaluate emerging technologies and processes to enhance intelligence capabilities. - Integrate new technologies into existing operational architectures to improve intelligence effectiveness. - Implement and integrate open-source, commercial off-the-shelf (COTS), and government off-the-shelf (GOTS) technologies. - Evaluate the functionality, effectiveness, and suitability of systems and applications to identify and address shortcomings. - Develop technical documentation, conduct code reviews, and provide technical leadership for development efforts. - Collaborate with government, military, and contractors in complementary mission areas to identify and address technical deficiencies. - Recommend process improvements based on operational effectiveness and emerging technologies. - Actively participate in JIOC intelligence planning conferences and exercises, J2 working groups, intelligence system capability development meetings, Joint and national-level intelligence coordination boards, and technical exchange meetings with mission partners. Minimum Requirements (Knowledge, Skills, And Abilities) list: - Master's degree in Computer Science, Software Engineering, or related technical field preferred - Advanced expertise in multiple programming languages, frameworks, and development paradigms - Deep understanding of distributed systems design and implementation - Experience leading software development teams and managing complex projects - Advanced expertise in cloud-native architecture and deployment strategies - Significant experience delivering capability while utilizing DevSecOps practices and CI/CD tools - Experience with system performance optimization and scalability - Knowledge of federal information security requirements and compliance frameworks - Demonstrated ability to translate complex intelligence requirements into technical solutions - Experience mentoring junior developers and providing technical guidance Security Clearance Required TS/SCI. Ability to take a poly if requested. Minimum Education: Master's degree or Ph.D. in Data Science, Computer Science, Statistics, Mathematics, or related quantitative field. Minimum Years Of Experience: 7-10 years of experience in computer science, software development, or similar technical roles, with at least 3 years supporting intelligence or defense applications. Other Responsibilities: Safety, Quality, Procedure Compliance paragraphs. Let's extract: Safety: "Amentum enforces a safety culture whereby all employees have the responsibility for continuously developing and maintaining a safe work environment. As appropriate, each employee is responsible for completing all training requirements and fulfilling all self-aid/buddy aid responsibilities, participating in emergency response tasks and serving on safety committees and teams." Quality: "Quality is the foundation for the management of our business and the keystone to our goal of customer satisfaction. It is our policy to consistently provide services that meet customer expectations. Accordingly, each employee must conform to the Amentum Quality Policy and carry out job activities in compliance with applicable Amentum Quality System documents and customer contracts. Each employee must read and understand his/her Quality Management and Customer Satisfaction responsibilities." Procedure Compliance: "Each employee must read, understand and implement the general and specific operational, safety, quality and environmental requirements of all plans, procedures and policies pertaining to his/her job." These are generic but we can include as a section maybe "Other Responsibilities". However we have limited headings; we could put them under Responsibilities as additional bullets? But they are not specific to role. Might be considered boilerplate; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not EEO. It's internal policy. Might keep. But we prefer few substantive sections. Could combine Safety, Quality, Procedure Compliance into a single "Other Responsibilities" section with

    • each. Compensation Details: "80K to 190K The compensation range or hourly rate listed for this position is provided as a good-faith estimate of what the company intends to offer for this role at the time this posting was issued. Actual compensation may vary based on factors such as job responsibilities, education, experience, skills, internal equity, market data, applicable collective bargaining agreements, and relevant laws." We need to preserve all substantive information. So include that paragraph. Benefits Overview: list: - Health, dental, and vision insurance - Paid time off and holidays - Retirement benefits (including 401(k) matching) - Educational reimbursement - Parental leave - Employee stock purchase plan - Tax-saving options - Disability and life insurance - Pet insurance Note: Benefits may vary based on employment type, location, and applicable agreements. Positions governed by a Collective Bargaining Agreement (CBA), the McNamara-O'Hara Service Contract Act (SCA), or other employment contracts may include different provisions/benefits. We should include that note as prose. Original Posting dates etc: we can drop or fold into short

      . Probably drop as minor metadata. Now construct HTML. We'll have sections:

      About the role

      ... purpose and impact ...

      Responsibilities

      • ... essential responsibilities ...
      Maybe also include Other Responsibilities under same section? Could add another
      after essential responsibilities? But better to keep separate section for Other Responsibilities if we have heading. But we have limited headings; we could add a section "Other Responsibilities". That's allowed as heading? The list of allowed headings includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Other Responsibilities" is not in list. The instruction: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. So we should stick to those. So we cannot add Other Responsibilities heading. We could incorporate safety/quality/procedure into Responsibilities section as additional list items? Might be okay. Thus Responsibilities section will contain both essential responsibilities and safety/quality/procedure items. But we need to preserve all substantive information; we can add them as list items under Responsibilities. Now Requirements section: include Minimum Requirements (Knowledge, Skills, And Abilities) plus Minimum Education and Minimum Years Of Experience. Could be list. Qualifications section: maybe Security Clearance Required. Skills section: maybe we could extract skills from Minimum Requirements but we already have them in Requirements; better to not duplicate.