Senior AI and Knowledge Systems Engineer

Chantilly, VA Senior AI/ML Engineer

Interested in this AI/ML Engineer role at GeoYeti, a division of Bcore?

Apply Now →

Skills & Technologies

EmbeddingsPrompt EngineeringPythonRag

About This Role

AI job market dashboard showing open roles by category

Active TS/SCI with CI poly Chantilly, VA At Bcore, our strength comes from how we deliver impact to the mission. Whether it’s architecting critical IT solutions, producing actionable intelligence, or developing cutting edge technology, we succeed because of the expertise, collaboration, and agility of our teams. Our Insight Solutions division delivers intelligence analysis, advanced data science, and strategic decision support. Bcore accelerates decisive advantage for warfighters and intelligence professionals by fusing human insight, rapid-fire engineering, precision-measured outcomes, and relentless grit into mission-ready solutions.

Are you ready to lean into analytic approaches that show customers the power of both technical and methodological innovation? Join our growing team supporting customer missions as a Senior AI and Knowledge Systems Engineer in Chantilly, Virginia. What You’ll Do Enterprise Knowledge Platform Design and build a knowledge system that brings together staff reports, plans, and tracked items that today live in separate places across Jira, Confluence, and SharePoint.

Question Answering Build NLP and LLM-based workflows that let a user ask a plain question, such as “give me a completed trip report” or “show me the burndown from our last trip,” and get an answer written the way the staff would write it.

Staff Validation Put staff in the loop to review outputs against how they would have answered, and use their feedback to tune the system until they trust it.

Controlled Information Testing Release only selected information to the model and observe what it surfaces, so we can measure accuracy, find gaps, and understand how the system behaves.

User Testing Watch users do the task the way they normally would, then test the system’s output against their results and use the differences to guide the next round of work.

Prompt Engineering and Integration Build and refine prompts, APIs, and MCP connections that link the model to Jira, Confluence, SharePoint, and the other data sources staff already use.

Access Control and Need-to-Know Make sure the system never shows a user anything they aren’t cleared or authorized to see. Answers must respect the permissions already set in Jira, Confluence, and SharePoint, along with classification markings, compartments, and need-to-know. This applies to every part of the system, including search indexes, embeddings, prompts, and model outputs. You will also build in audit logging and keep the data on the networks where it belongs.

Working With Real-World Systems Work with the systems as they are, not as the documentation says they should be. Some installations are not on current versions, APIs may be limited or unreliable, and MCP connectors may not exist for what you need. You will find workable paths, such as building your own connectors, adapting to older APIs, or pulling content another way, and document what you learn.

Path to Enterprise Capability Grow the first working version into an enterprise knowledge store, working toward initial and then full operational capability.

Who We’re Looking For

  • A builder who enjoys turning messy, siloed information into something people actually use
  • Someone who learns new tools quickly and wants to work at the frontier of AI
  • Someone who stays productive when the tools are older, the APIs are inconsistent, or the connector they need hasn’t been built yet
  • Someone who spends time with end users and designs around how they really work
  • A self-thinker who is comfortable owning ambiguous problems and moving them forward
  • Someone who treats access control and data protection as part of the design from day one, not something added at the end
  • Someone who takes a human-in-the-loop approach and understands both the strengths and the limits of AI
  • Someone who cares about accuracy and can show how they know an answer is right
  • A clear communicator who can explain technical choices to engineers and to senior non-technical leaders
  • A self-motivated individual who works well on their own and as part of a team

Required Qualifications

  • Active TS/SCI clearance with CI poly required to start
  • Experience building NLP or LLM-based applications, including prompt engineering and working with LLM APIs
  • Experience designing and building APIs and integrating multiple data sources
  • Experience implementing access controls in data or search systems, such as role- or attribute-based access, permission-aware retrieval, and audit logging
  • Experience organizing large collections of documents or data so they can be searched and reused
  • Ability to explain technical work to non-technical users and leadership

Desired Qualifications

  • Experience with retrieval-augmented generation (RAG) and vector or graph-based search
  • Experience with one or more of Jira, Confluence, or SharePoint, including their APIs and how content is structured in them
  • Experience with MCP servers or similar tool-integration approaches for LLMs
  • Experience building custom MCP servers or connectors where no off-the-shelf option exists
  • Experience integrating with older or on-premises software versions and working around limited, inconsistent, or poorly documented APIs
  • Experience with knowledge management, knowledge graphs, or semantic data standards
  • Experience designing ways to test LLM output, including accuracy checks and human review
  • Experience building and deploying tools on JWICS or higher-classification networks
  • Familiarity with IC data handling, including classification markings, compartments, and need-to-know controls
  • Familiarity with how military or command staffs produce reports, plans, and operational products
  • Strong Python skills and experience with modern data and AI tooling
  • Experience working in Agile environments with short, iterative delivery cycles
  • Experience running user research or user testing on analytic or data-driven tools
  • The expected salary range within the Washington, DC metropolitan area is $150,000 - 210,000. Final compensation is unique to each individual and will be determined based on factors such as experience, education, geographic location, and contractual requirements. This is not a guarantee.
  • Benefits include Health/Dental/Vision, 401(k), Paid Time Off, STD/LTD/Life Insurance/Voluntary Life Insurance, Stipends, Referral Bonuses, and more.

BCore is proud to be an equal opportunity workplace. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, disability status, protected veteran status, sexual orientation or any other characteristic protected by law.

Role Details

Title Senior AI and Knowledge Systems Engineer
Location Chantilly, VA
Category AI/ML Engineer
Experience Senior
Salary Not disclosed
Remote No

About This Role

AI/ML Engineers build and deploy machine learning models in production. They work across the full ML lifecycle: data pipelines, model training, evaluation, and serving infrastructure. The role has evolved significantly over the past two years. Where ML Engineers once spent most of their time on model architecture, the job now tilts heavily toward inference optimization, cost management, and integrating LLM capabilities into existing systems. Companies want engineers who can ship production systems, and the experimenter-only role is fading fast.

Day-to-day, you're writing training pipelines, debugging data quality issues, setting up evaluation frameworks, and figuring out why your model performs differently in staging than it did on your dev set. The best ML engineers are obsessive about reproducibility and measurement. They instrument everything. They know that a model is only as good as the data feeding it and the infrastructure serving it.

Across the 10,419 AI roles we're tracking, AI/ML Engineer positions make up 75% of the market. At GeoYeti, a division of Bcore, this role fits into their broader AI and engineering organization.

Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.

What the Work Looks Like

A typical week might include: debugging a data pipeline that's silently dropping 3% of training examples, running A/B tests on a new model version, writing documentation for a feature flag system that lets you roll back model deployments, and reviewing a junior engineer's PR for a new evaluation metric. Meetings tend to be cross-functional since ML touches product, engineering, and data teams.

Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.

Skills Required

Embeddings (3% of roles) Prompt Engineering (5% of roles) Python (23% of roles) Rag (9% of roles)

Python and PyTorch dominate the requirements. Most roles expect experience with cloud platforms (AWS, GCP, or Azure) and familiarity with ML frameworks like TensorFlow or JAX. RAG (Retrieval-Augmented Generation) has become a top-3 skill requirement as companies integrate LLMs into their products. Docker and Kubernetes show up in about a third of postings, reflecting the production focus of the role.

Beyond the core stack, employers increasingly want experience with experiment tracking tools (MLflow, Weights & Biases), feature stores, and vector databases. Fine-tuning experience is valuable but less common than you'd think from reading Twitter. Most production LLM work is RAG and prompt engineering, not fine-tuning. If you have both, you're in a strong position.

Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.

Compensation Benchmarks

AI/ML Engineer roles pay a median of $213,800 based on 16,346 positions with disclosed compensation. Senior-level AI roles across all categories have a median of $230,000.

Across all AI roles, the market median is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. For comparison, the highest-paying categories include AI Safety ($274,500) and Research Engineer ($252,000). By seniority level: Entry: $114,400; Mid: $193,200; Senior: $230,000; Director: $272,100; VP: $235,000.

GeoYeti, a division of Bcore AI Hiring

GeoYeti, a division of Bcore has 1 open AI role right now. They're hiring across AI/ML Engineer. Based in Chantilly, VA.

Location Context

Across all AI roles, 6% (580 positions) offer remote work, while 9,776 require on-site attendance. Top AI hiring metros: New York (3,785 roles, $222,480 median); San Francisco (3,262 roles, $261,300 median); Los Angeles (1,896 roles, $210,000 median).

Career Path

Common paths into AI/ML Engineer roles include Data Scientist, Software Engineer, Research Engineer.

From here, career progression typically leads toward ML Architect, AI Engineering Manager, Principal ML Engineer.

The fastest path into ML engineering is through software engineering with a self-directed ML education. A CS degree helps, but production engineering skills matter more than academic credentials. Build something that works, deploy it, and measure it. That portfolio project is worth more than a Coursera certificate. For career growth, the fork comes around the senior level: go deep on technical complexity (staff/principal track) or move into managing ML teams.

What to Expect in Interviews

Expect system design questions around ML pipelines: how you'd build a training pipeline for a specific use case, handle data drift, or design A/B testing infrastructure for model deployments. Coding rounds typically involve Python, with emphasis on data manipulation (pandas, numpy) and algorithm implementation. Take-home assignments often ask you to build an end-to-end ML pipeline from raw data to deployed model.

When evaluating opportunities: Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.

AI Hiring Overview

The AI job market has 10,419 open positions tracked in our dataset. By seniority: 117 entry-level, 4,975 mid-level, 3,840 senior, and 1,487 leadership roles (Director, VP, C-Level). Remote roles make up 6% of the market (580 positions). The remaining 9,776 roles require on-site or hybrid attendance.

The market median for AI roles is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. Highest-paying categories: AI Safety ($274,500 median, 90 roles); Research Engineer ($252,000 median, 580 roles); AI Engineering Manager ($250,811 median, 72 roles).

Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.

The AI Job Market Today

The AI job market spans 10,419 open positions across 16 role categories. The largest categories by volume: AI/ML Engineer (7,849), AI Product Manager (516), AI Software Engineer (513). These three account for the majority of open positions, though smaller categories often have higher per-role compensation because of specialized skill requirements.

The seniority mix tells a story about where AI teams are in their maturity. Entry-level roles (117) are outnumbered by mid-level (4,975) and senior (3,840) positions, reflecting that most companies are past the 'build a team from scratch' phase and need experienced engineers who can ship production systems. Leadership roles (Director, VP, C-Level) total 1,487 positions, representing the bottleneck between technical execution and organizational strategy.

Remote work availability sits at 6% of all AI roles (580 positions), with 9,776 requiring on-site or hybrid attendance. The remote share has stabilized after the post-pandemic correction. Senior and specialized roles (Research Scientist, ML Architect) are more likely to be remote-eligible than entry-level positions, partly because experienced hires have more negotiating power and partly because these roles require less hands-on mentorship.

AI compensation is structured in clear tiers. The market median sits at $214,834. Top-quartile roles start at $266,000, and the 90th percentile reaches $321,730. These figures include base salary with disclosed compensation. Total compensation (including equity, bonuses, and sign-on) runs 20-40% higher at companies that offer those components.

Category matters for compensation. AI Safety roles lead at $274,500 median, while Prompt Engineer roles sit at $140,000. The spread between highest and lowest-paying categories reflects the premium on specialized technical skills versus broader analytical roles.

The most in-demand skills across all AI postings: Python (2,350 postings), Aws (1,173 postings), Azure (1,030 postings), Rag (986 postings), Gcp (714 postings), Pytorch (649 postings), Kubernetes (583 postings), Claude (581 postings). Python dominates, appearing in the vast majority of role descriptions regardless of category. Cloud platform experience (AWS, GCP, Azure) is the second most common requirement. The newer entrants to the top skills list (RAG, vector databases, LLM APIs) reflect the shift from traditional ML toward generative AI applications.

Frequently Asked Questions

Based on 16,346 roles with disclosed compensation, the median salary for AI/ML Engineer positions is $213,800. Actual compensation varies by seniority, location, and company stage.
Python and PyTorch dominate the requirements. Most roles expect experience with cloud platforms (AWS, GCP, or Azure) and familiarity with ML frameworks like TensorFlow or JAX. RAG (Retrieval-Augmented Generation) has become a top-3 skill requirement as companies integrate LLMs into their products. Docker and Kubernetes show up in about a third of postings, reflecting the production focus of the role.
About 6% of the 10,419 AI roles we track offer remote work. Remote availability varies by company and seniority level, with senior and leadership roles more likely to offer location flexibility.
GeoYeti, a division of Bcore is among the companies actively hiring for AI and ML talent. Check our company profiles for detailed breakdowns of open roles, salary ranges, and hiring trends.
Common next steps from AI/ML Engineer positions include ML Architect, AI Engineering Manager, Principal ML Engineer. Progression depends on whether you lean toward technical depth, people management, or product strategy.

Get Weekly AI Career Intelligence

Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.