$125,100–$225,200
Staff Data Engineer, Foundry & Ontology – Clearance Required
$160,000–$180,000Fort Bragg, NCStaff
Builds the data architecture, pipelines, and ontologies that connect Army enterprise information to operational applications and decision-support capabilities.
Nextmove
Find roles that fit you
We find roles for your experience and goals, explain the fit, and help you get introduced to hiring teams.
We never share your profile with employers without your permission.
Try NextmoveCreate an account, then add your resume
View posting at lmi (icims)At a glance
Posted base pay
$160K–$180KBelow the median
Median $193K
This job$160K–$180KTypical US FDE payMiddle 50% of 2,432 postings$160K–$225KThe work
Builds what the customer runs
This posting is new. The rest of the reading appears within a day.
What they ask for
Tools
Less common in FDE jobs
- Individual contributor or manager: Technical lead47%
Share of US FDE postings that state each fact.
What you’ll do
- Design and develop scalable data architectures, pipelines, integrations, and operational data models.
- Lead ontology development for entities and relationships spanning Army data sources.
- Establish data quality, lineage, traceability, and access-control approaches.
- Enable conversational AI and agent workflows using authoritative enterprise data.
What you’ll bring
- Six or more years of experience in data engineering, data architecture, software engineering, or a related discipline.
- Bachelor's degree in a related technical discipline or equivalent practical experience.
- Strong proficiency in Python and SQL.
- Experience building production data pipelines and modeling relationships across multiple data sources.
Similar jobs
CapgeminiBuilds what the customer runs
Capgemini Invent - Senior Consultant, Forward Deployed Engineer
Seattle, WA · New York, NY · +4 moreSeattle, WA +5
$112,600–$212,700
$149,000–$185,000
$140,000–$200,000
Hiring at lmi (icims) and want this page changed or removed? Email info@nextmove.md and we take it down.
Employer postings · How we read postings