Data Scientist SME
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. Must not invent or summarize away detail. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Pay Range and Benefits description. So we can include Pay and Benefits sections. Schedule not mentioned, so omit Schedule. Also we have location info, clearance level. Those could go under About the role or maybe Requirements? The instructions: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly.
We have description: "Turn complex data into mission advantage..." That's about the role. Could be About the role.
Responsibilities: list of primary responsibilities bullet points.
Requirements: maybe basic qualifications? But they also have Basic Qualifications and Preferred Qualifications. Could treat Basic Qualifications as Requirements, and Preferred Qualifications as Qualifications? Or Skills? The headings list includes Requirements, Qualifications, Skills. We need to decide.
We have: Basic Qualifications (US citizenship, degree, years experience, etc). Preferred Qualifications (certifications, familiarity, etc). Also there is a list of skills: expertise in Python, big data tools, geospatial formats, etc. Those could go under Skills.
We need to preserve all substantive info. So we must include all details from Basic Qualifications, Preferred Qualifications, and the skill bullets.
We must not repeat job title. No mention of Job ID.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning etc. So we need to cut out the sections about Leidos, About Leidos, Pay And Benefits (but we need to keep Pay and Benefits? Actually Pay And Benefits section includes description of benefits; we need to keep Pay and Benefits as per instruction: include Pay and Benefits sections only if posting actually states them. The posting does state Pay Range and a paragraph about Pay and benefits. So we should include Pay and Benefits sections. However the instruction says use headings Pay and Benefits separately? They listed Pay, Benefits as separate possible headings. We could combine? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have separate Pay
and Benefits
. The posting includes Pay Range and a paragraph about benefits. So we need to output both.
We must not include filler like "commensurate with experience". Not present.
We must not include location as heading; we can include location in About the role paragraph or maybe as a
Pay
andBenefits
. The posting includes Pay Range and a paragraph about benefits. So we need to output both. We must not include filler like "commensurate with experience". Not present. We must not include location as heading; we can include location in About the role paragraph or maybe as awithin About the role. Clearance Level Required: could be part of Requirements. We need to ensure we don't create sections with no content. Let's extract content. About the role: The initial description paragraphs up to "If you are energized by applying advanced analytics to real-world mission challenges and want to see your work have a tangible impact, this is an opportunity to make a difference." Also maybe the Leidos National Security Sector paragraph? That is about the team focus. Could be part of About the role. We'll include that. Responsibilities: The list under "Primary Responsibilities". We'll turn each sentence into
About the role
Turn complex data into mission advantage. Join Leidos on the Chinook Program supporting our Intelligence Community customer and play a critical role in transforming massive, complex datasets into actionable intelligence and mission insights. As a Data Scientist SME, you will bring advanced analytical expertise, innovative thinking, and technical leadership to a high performing Agile engineering team delivering next generation capabilities to our Intelligence Community customer. This is an opportunity to work at the intersection of data science, artificial intelligence, machine learning, cloud technology, and national security, where your expertise can directly influence how mission users understand data, identify patterns, and make critical decisions. You will serve as a technical authority while collaborating with software engineers, DevSecOps professionals, system architects, analysts, and mission stakeholders to solve challenging problems that don’t have off-the-shelf answers. If you are energized by applying advanced analytics to real-world mission challenges and want to see your work have a tangible impact, this is an opportunity to make a difference. Leidos National Security Sector combines technology-enabled services and mission software capabilities in the areas of cyber, logistics, security operations, and decision analytics to support our defense and intel customers’ mission to defend against evolving threats around the world. Our team’s focus is to ensure our customers have the right tools, technologies, and tactics to keep pace with an ever-evolving security landscape and succeed in their pursuit to protect people and critical assets. Position may be performed in the following locations: Gaithersburg, MD (primary), Alexandria, VA, Chantilly, VA, Aurora, CO, St. Louis, MO. Clearance Level Required: Active Top Secret/SCI clearance with the ability to successfully pass a Polygraph examination.
But we moved clearance to Requirements maybe. However we included clearance in About the role; but we also need to keep it somewhere. If we put it in About the role, we must not duplicate elsewhere. We could keep it in About the role and not have a separate Requirements for clearance. However Requirements should include education/experience etc. We'll keep clearance in About the role to avoid duplication. But the instruction says we should not invent or summarize away detail; we can place it anywhere as long as it's preserved. So we can keep it in About the role. Now Responsibilities: list each bullet. Let's extract responsibilities sentences: - Serve as the technical SME in data science and geospatial analytics, providing high-level guidance on complex technical problems related to the GEOINT mission. - Lead the design and development of sophisticated data science models and machine learning algorithms to analyze large, multi-source geospatial data sets (e.g., satellite imagery, sensor data, geospatial databases). - Apply deep knowledge of GEOINT, remote sensing, and spatial analysis to develop and implement solutions that enhance data-driven decision-making capabilities. - Provide strategic recommendations for leveraging new and emerging technologies, including machine learning, AI, and cloud platforms, to improve analytical workflows, efficiency, and mission outcomes. - Mentor and train junior data scientists and analysts, ensuring the application of best practices in data science and the development of mission-relevant expertise. - Work closely with GEOINT analysts, program managers, engineers, and other stakeholders to identify critical requirements, define technical approaches, and ensure that solutions align with mission objectives. - Conduct applied research to explore innovative data science techniques and emerging trends (e.g., deep learning, reinforcement learning, advanced geospatial algorithms) that can be applied to solve real-world intelligence problems. - Oversee the deployment and operationalization of data science models, ensuring they are scalable, reliable, and deliver actionable insights to GEOINT decision-makers. - Maintain high-quality documentation