Systems Engineer III - Data Scientist

We need to output HTML fragment with sections: About the role? The posting includes Position Overview, What You Will Do (list of duties), Required Qualifications, Desired Qualifications, Benefits, Salary Range, Location, Travel, Clearance Requirement. We must not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have Position Overview (could be About the role). We have What You Will Do (Responsibilities). We have Required Qualifications (maybe Requirements). Desired Qualifications (maybe Skills). Benefits (Benefits). Salary Range (Pay). Location/Travel/Clearance maybe could be in a short paragraph under About the role or separate? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. Location, Travel, Clearance are metadata; we could include them in a short paragraph under About the role or maybe a separate section like "Details". But we only have allowed headings list; we could create a section "About the role" that includes overview plus location, travel, clearance. Or we could have separate sections for "Pay" and "Benefits". Schedule not present, so omit. We must not create sections with filler like "commensurate with experience". Salary Range is present: $165k - $183k Annually. So we can create Pay section with that. Benefits section present. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the details from Position Overview, What You Will Do (list of duties), Required Qualifications, Desired Qualifications, Benefits, Salary, Location, Travel, Clearance. We must use

• for any list of duties/requirements/benefits. So for responsibilities we need a list. For qualifications maybe list. For benefits list. We need to use

  for prose. We must not include boilerplate like EEO, etc. Remove those. We must not include application instructions. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings (none present). We must output only HTML fragment. Let's craft:

  About the role

  Intelligent Waves is seeking a highly experienced System Engineer Level III – Data Scientist to support our cybersecurity contract in Linthicum Heights, MD. This senior-level position requires 20+ years of relevant systems engineering experience and combines technical leadership with advanced data science expertise supporting complex systems of systems. The role focuses on natural language processing (NLP), machine learning (ML), data extraction and processing, qualitative analysis, and data visualization, including work with unstructured and semi-structured sources such as PDFs, CONOPS, and DoDAF artifacts. Candidates should be proficient in Python and/or R, with experience or familiarity with technologies such as TensorFlow, PyTorch, Apache Tika, and PDFMiner. The position leads requirements analysis, system architecture and design, integration, testing, implementation planning, and technical documentation while working closely with Government stakeholders and senior program leadership to ensure the technical integrity of systems engineering activities and deliverables.

  Location: Linthicum Heights, MD • Travel: None • Clearance Requirement: Active TS/SCI level security clearance (with polygraph conducted within the past 10 years).

  Then Responsibilities:

  Responsibilities

  • Systems Requirements & Requirements Management: Manage system and derived requirements throughout the lifecycle, ensuring alignment with defined architectures, stakeholder needs, functional requirements, and allocated hardware, software, facility, and personnel components; derive and manage lower-level requirements from higher-level requirements, ensuring they are complete, correct, unique, unambiguous, realizable, verifiable, traceable, and aligned with system effectiveness; establish and manage formal requirements-change processes that evaluate impacts, obtain stakeholder approval, maintain traceability, eliminate ambiguity, and track open actions through resolution.
  • System Architecture, DoDAF & SOA: Develop system architectures, physical architectures, system concepts, design solutions, and alternatives that satisfy requirements while considering lifecycle cost, reuse, complexity, risk, expansion, and growth; develop and implement comprehensive Service-Oriented Architecture (SOA) solutions and DoDAF-compliant operational, technical standards, system, and services views; develop operational scenarios, threads, and concepts describing interactions among the system, users, and environment across operational, support, maintenance, and disposal needs.
  • Systems Engineering & Technical Documentation: Develop, review, and approve systems engineering documentation, including Systems Engineering Plans, Initial Capabilities Documents, Requirements Specifications, Interface Control Documents, and JCIDS documentation; review and provide input to program and contract Work Breakdown Structures (WBS), work packages, and Integrated Master Plans (IMP).
  • System Integration & Interface Management: Provide technical direction for the development, engineering, integration, interfacing, and testing of complex hardware/software systems, including requirements elicitation, functional allocation, systems requirements reviews, concepts of operation, interface standards, system architectures, assessments, and end-to-end flow analysis; define, document, and manage hardware and software interfaces throughout the system lifecycle, including origination, destination, stimulus, data characteristics, and applicable electrical and mechanical characteristics; establish formal integration processes across multiple teams, coordinate interface activities, and improve integration strategies based on previous performance and lessons learned.
  • Verification, Testing & Certification: Develop verification methods, processes, evaluation criteria, and written plans to verify systems, subsystems, and work products against established requirements, including early verification planning for new or unproven designs; support system testing, including planning and test analysis for DoD and other Government Certification and Accreditation (C&A) processes.
  • Configuration & Lifecycle Management: Manage system configuration and technical baselines throughout development, deployment, operations, and maintenance; participate in the Configuration Control Board (CCB) and coordinate actions resulting from CCBs, design reviews, program reviews, and test reviews.
  • Risk, Analysis & System Performance: Assess and manage program risks by determining probability and consequences, developing alternative courses of action and fallback positions, monitoring risks at key milestones, and using Earned Value Management (EVM) data where applicable; conduct or approve system trade analyses and quantitative assessments of non-functional performance areas, including reliability, maintainability, vulnerability, survivability, and producibility; use validated models, simulations, and prototyping to reduce system-development risk and cost, including allocation of real-time process and error budgets and development of time-line analysis diagrams; participate in Integrated Product Teams (IPTs) and Analysis of Alternatives (AoA) efforts to evaluate capabilities and recommend solutions based on operational considerations, assumptions, technology limitations, environmental impacts, and lifecycle costs.
  • Information Assurance & Security: Develop Information Assurance requirements addressing confidentiality, integrity, nonrepudiation, availability, identification, authentication, access control, accountability, cryptography, hashing, key management, and other applicable security mechanisms.
  • Standards & Interoperability: Maintain knowledge of applicable agency, national, and international standards and apply appropriate standards to promote consistency and interoperability across system hardware and software.
  Then Requirements/Qualifications: We have Required Qualifications and Desired Qualifications. Could combine into Requirements section with subpoints? But we need to use headings only from list: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could have "Requirements" for required qualifications, "Skills" for desired qualifications (or maybe "Qualifications" for both). Let's decide: Use "Requirements" for required qualifications (education, experience, clearance). Use "Skills" for desired qualifications (TensorFlow, PyTorch, Apache Tika, PDFMiner). Or we could use "Qualifications" for required and "Skills" for desired. Let's follow typical: Requirements (mandatory), Skills (desired). We'll output:

  Requirements

  • Education: Bachelor’s degree in Systems Engineering, Computer Science, Information Systems, Engineering Science, Engineering Management, or a related field. Five (5) additional years of relevant experience may be substituted for the degree.
  • Experience: Twenty (20) years of systems engineering experience with a bachelor’s degree, or twenty-five (25) years without a degree.
  • Large Data Systems: Experience with large data systems, including Natural Language Processing (NLP) and Machine Learning (ML).
  • Data Extraction: Experience extracting and loading data from unstructured and semi-structured sources, including PDFs, CONOPS, and DoDAF.
  • Programming: Experience with Python and/or R.
  • Clearance: Active TS/SCI with polygraph conducted within the past 10 years.
  Then Skills:

  Skills

  • Experience with TensorFlow and/or PyTorch.
  • Experience with Apache Tika and/or PDFMiner.
  Then Benefits:

  Benefits

  • Medical, dental, vision
  • Paid PTO
  • Life and disability insurance
  • Vesting retirement contributions starting from DAY 1
  • Technical training
  • Tuition bonuses
  Then Pay:

  Pay

  Salary Range: $165k - $183k Annually

  Schedule not present, omit. We must ensure we didn't include any boilerplate like EEO, etc. We removed. Check that we preserved all substantive info: Position overview details, responsibilities (we captured each bullet but we condensed some long sentences into list items; we must preserve all detail, not summarize away. We need to ensure we didn't lose any detail. The responsibilities section had many sub-bullets; we turned each major heading into a list item with semicolons separating subpoints. That preserves the content but maybe we lost some nuance? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing away detail would be removing specifics. Our list items still contain the specifics but we combined multiple sentences into one list item separated by semicolons. That is still preserving the detail, not summarizing away. It's okay. Check we didn't miss any details: In responsibilities we covered all sections: Systems Requirements & Requirements Management, System Architecture, DoDAF & SOA, Systems Engineering & Technical Documentation, System Integration & Interface Management, Verification, Testing & Certification, Configuration & Lifecycle Management, Risk, Analysis & System Performance, Information Assurance & Security, Standards & Interoperability. Yes. Check we didn't miss any details from Position Overview: we included overview paragraph plus location/travel/clearance paragraph. Check we didn't miss any details from Required Qualifications: we included education, experience, large data systems, data extraction, programming, clearance. Check we didn't miss Desired Qualifications: we included TensorFlow/PyTorch, Apache Tika/PDFMiner. Check Benefits: we included medical, dental, vision, paid PTO, life and disability insurance, vesting retirement contributions starting from DAY 1, technical training, tuition bonuses. The original said: "Intelligent Waves offers a generous benefits package including medical, dental, vision, paid PTO, life and disability insurance. We invest in our employees’ futures by contributing with vesting starting from DAY 1, technical training, tuition bonuses, and much more." We captured those. Check Pay: we included salary range. Check we didn't include any boilerplate like EEO, etc. Good. Now output only HTML fragment. Let's ensure proper nesting: each

  followed by

  or

  . No extra whitespace issues. We'll output:

  About the role

  Intelligent Waves is seeking a highly experienced System Engineer Level III – Data Scientist to support our cybersecurity contract in Linthicum Heights,