Geospatial Engineer, Battle Road

Onebrief
Battle Road DigitalPosted 21 February 2026

Job Description

About OnebriefOnebrief is collaboration and AI-powered workflow software designed specifically for military staffs. By transforming this work, Onebrief makes the staff as a whole superhuman - meaning faster, smarter, and more efficient.We take ownership, seek excellence, and play to win with the seriousness and camaraderie of an Olympic team. Onebrief operates as an all-remote company, though many of our employees work alongside our customers at military commands around the world.Founded in 2019 by a group of experienced planners, today, Onebrief’s team spans veterans from all forces and global organizations, and technologists from leading-edge software companies. We’ve raised $320m+ from top-tier investors, including Battery Ventures, General Catalyst, Sapphire Ventures, Insight Partners, and Human Capital, and today, Onebrief is valued at $2.15B. With this continued growth, Onebrief is able to make an impact where it matters most.Battle Road Digital, part of Onebrief, applies state-of-the-art innovations and experience from the video game industry to build the future of simulations, modeling, and operations with AtomEngine – our proprietary cloud-based game engine that’s making the world playable.About the RoleAs a Geospatial Engineer at Battle Road, you will design, operate, and evolve the geospatial data pipelines and systems that underpin AtomEngine’s simulation runtime. This role sits at the intersection of data engineering, geospatial science, and simulation systems, owning the lifecycle of spatial data from sourcing and integration through processing, storage, and delivery at scale. You will evaluate and onboard new geospatial datasets and data products, translate simulation and runtime requirements into fit-for-purpose geospatial data, and ensure these datasets balance fidelity, performance, and scalability.In addition to data product ownership, you will administer and optimize the geospatial services and infrastructure that deliver this data—including GeoServer and PostGIS-backed systems—while enforcing strong stewardship practices around metadata, provenance, versioning, and quality. You will collaborate closely with engine, simulation, and AI teams to ensure geospatial data is performant, reliable, and directly enables new simulation capabilities, rather than serving as passive infrastructure.What You'll DoDesign, operate, and evolve Battle Road’s geospatial data pipelines, supporting the ingestion, processing, storage, and delivery of data sets used by the simulation.Source, evaluate, and integrate new geospatial datasets and data products (e.g., terrain, land cover, infrastructure, boundaries, mobility-relevant layers) that unlock new simulation features and capabilitiesTranslate simulation and runtime requirements into geospatial data products, ensuring datasets are fit for purpose across scale, performance, and fidelity constraintsAdminister and optimize geospatial services and infrastructure (including GeoServer and related tooling) to ensure reliability, performance, and secure access in both development and production environmentsImplement and enforce geospatial data stewardship best practices, including metadata standards, versioning, provenance, governance, and quality assuranceDesign and maintain PostgreSQL/PostGIS-backed data stores, optimizing schemas, queries, and access patterns for large-scale simulation and analytical workloadsCollaborate with engine, simulation, and AI teams to ensure geospatial data is aligned with runtime needs, performant at scale, and consumable by downstream systemsWhat We Look ForGeoserver Administration – 3 to 5 years experience installing, configuring, tuning, scaling, and securing Geoserver deployments (including cluster/HA setups, REST API usage, user/role configuration, SLD/stylesheet management, and WMS/WFS/WCS endpoint provision)PostgreSQL/PostGIS Expertise - 3 to 5 years experience database administration for spatial workloads, including schema design for raster and v ... (truncated, view full listing at source)