AI Implementation Engineer - JobID-0245
or drop it." So we can include location and compensation maybe as a short paragraph. The location is given: Department: EngineeringLocation: Mount Laurel, NJCompensation: $114,000 - $231,000 / year Description. We can fold that into a short
maybe after heading? But we shouldn't create a heading for it. Probably we can start with a
containing location and compensation. Then sections. We need to include Pay section only if posting actually states them. It does: Pay Range*: $114,000 - $184,000 or $135,000 - $231,000. Also mention Senate Bill. So we should include Pay section with that info. Also Schedule: they mention "9/80 optional schedule (2nd and 4th Friday off every month)" under benefits. That's schedule info. Should we create a Schedule section? The rule: "Prefer a few substantive sections over many thin ones." Could include schedule within Benefits or separate. Since schedule is a specific benefit, we could keep it under Benefits. But they said include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler. So we can include Benefits section that includes schedule info. Pay section separate. We must not include "commensurate with experience" as filler; but we can include that phrase if it's part of description? It appears in Pay Range*: "more than one pay range has been included, commensurate with experience." That's somewhat filler but it's part of the posting. We can keep it. We must not invent or summarize away detail. Keep all substantive info. We need to use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections we have content for. We have About the role (the paragraph after "Description About The Role:"). We have Responsibilities (list under "Key Responsibilities What You Will Do:"). We have Skills, Knowledge & Expertise (under "Skills, Knowledge & Expertise Who You Are (Required):" and "What Makes You Stand Out:"). We have Benefits (list under "Job Benefits Why Work at Innovative Defense Technologies (IDT):"). We have Pay (the pay range). We might not have a separate Requirements section distinct from Skills; but we could combine qualifications into Skills. The instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Skills, Benefits, Pay. That's 5 sections. Could also include Qualifications but that's overlapping with Skills. We'll skip Requirements and Qualifications. We must not include headings with no content. So we will output:
Department: Engineering. Location: Mount Laurel, NJ. Compensation: $114,000 - $231,000 per year.
Then sections. Now we need to extract content. About the role: The paragraph after "Description About The Role:" up to before "Clearance & Location Requirements:"? Actually "About The Role: Innovative Defense Technologies (IDT), a leading defense technology company, is seeking an AI Implementation Engineer to be part of our Warfare Systems team and based out of our Arlington, VA or Mount Laurel, NJ location. The AI Implementation Engineer will design and deliver engineering-focused AI solutions that move beyond demos into reliable, mission-relevant systems. This role is ideal for an engineer who has extensive experience with commercially available AI tooling/chat, hosting LLM servers and has demonstrated ability to build end-to-end capabilities including MCP integrations, RAG pipelines, tool-using agents, and production-grade AI workflows." We'll keep that as. Clearance & Location Requirements: "All applicants must be able to obtain/maintain an active Secret U.S. Security Clearance. This is an on-site position. Requiring at least 3 days in office, based out of our Arlington, VA location or Mt. Laurel, NJ location." This could be folded into a short paragraph maybe under About the role or separate? But we already have location in the initial paragraph. Could include this as a short
after About the role? But we might incorporate into About the role? The instruction: fold minor metadata into a short
or drop it. This is about clearance and location requirements, which is substantive (clearance requirement). Might be worth its own section? There's no heading for Clearance. Could be part of About the role or a separate section like "Requirements". But we decided not to have Requirements section. Could include a short
after About the role: "
Must be able to obtain/maintain an active Secret U.S. Security Clearance. On‑site position requiring at least 3 days in office at Arlington, VA or Mt. Laurel, NJ.
" That seems fine. Now Responsibilities: list items under "Key Responsibilities What You Will Do:" each bullet starts with a bold phrase? We'll extract each sentence as list item. List: - Design and Build AI Solutions for On-Prem systems in Air-Gapped environment: Design and implement end-to-end agentic AI systems that support planning, reasoning, tool use, and multi-step execution in real-world environments. Build modular, testable components that move from prototype to operational capability. - Integrate Models and Tools for On-Prem systems in Air-Gapped environment: Develop integrations across LLMs, APIs, data sources, and Model Context Protocol (MCP) interfaces to enable intelligent agents to interact with external systems, retrieve context, and take action safely and reliably. - Develop Retrieval Pipelines for On-Prem systems in Air-Gapped environment: Build and optimize Retrieval-Augmented Generation (RAG) pipelines that connect models to live knowledge sources, structured data, and enterprise content to improve factual grounding, contextual relevance, and response quality. - Engineer Conversational and Agentic Interfaces for On-Prem systems in Air-Gapped environment: Create conversational systems and intelligent agents with memory, contextual awareness, adaptive decision-making, and support for multi-turn user and system interactions. - Implement and Evaluate AI Workflows for On-Prem systems in Air-Gapped environment: Translate technical objectives into working pipelines, run experiments, evaluate agent behavior, and iterate on prompts, orchestration logic, retrieval quality, and system performance to improve reliability and usability. - Architect local infrastructure to size, config, and optimize local CPU/GPU workloads, utilizing quantization techniques to maximize throughput, etc. - Orchestrate disconnected environments, design and maintain offline model update pipelines, local package mirrors, etc. - Scope and Define Requirements: Gather, document, and validate technical and functional requirements from project artifacts, stakeholders, and mission needs to ensure feasibility, completeness, and alignment with operational goals. - Collaborate Across Teams: Work closely with engineers, technical leads, and mission stakeholders to integrate AI capabilities into broader software and system architectures. Participate in technical reviews, design discussions, and delivery planning. - Support Technical Quality: Contribute to testing, debugging, and performance optimization of AI-enabled applications, including edge cases involving context management, retrieval failures, tool execution, and orchestration logic. - Learn and Apply Emerging Practices: Stay current on advances in LLMs, agent frameworks, orchestration methods, and applied AI engineering practices, and bring that knowledge into practical system design and implementation. - Communicate Technical Work: Clearly document architectures, workflows, assumptions, and implementation decisions so that solutions are maintainable, explainable, and transferable across teams. We'll put each as