Lead 3D Geospatial Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to decide which sections to include: About the role? The posting has "About NGS" and "The Role". Could treat "About NGS" as "About the role"? Actually "About the role" is a heading they suggest. But we have "About NGS" describing company. Could we put that under "About the role"? Might be okay. Or we could have separate sections: "About NGS" not in list but we can still use
for any heading; they gave examples but not exclusive. Probably we should follow their examples: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also add other headings if needed? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical but not exclusive; we can use other headings if appropriate. However they say "IMPORTANT: include a section ONLY when the posting has real, specific content for it". So we need to decide which sections have content.
We have content: About NGS (company description). The Role description (overview). Responsibilities (list). Required (list). Preferred (list). Benefits (list). No explicit Pay or Schedule. So we should not add Pay or Schedule sections.
We could have sections: About NGS, The Role, Responsibilities, Required, Preferred, Benefits. Or we could map Required to "Requirements" and Preferred to "Qualifications" or "Skills". The posting says "Required" and "Preferred". Could treat Required as "Requirements", Preferred as "Qualifications". Benefits as "Benefits". The Role overview could be "About the role". About NGS could be maybe a short paragraph under "About the role" or separate "About NGS". Since they said do not repeat job title as heading; but we can have About NGS as a heading? Not in examples but could be okay. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should stick to those headings. So we should map content to those headings.
Thus:
- About the role: combine About NGS and The Role description (company + role overview). Could be two paragraphs.
- Responsibilities: list from Responsibilities section.
- Requirements: list from Required section.
- Qualifications: list from Preferred section (or Skills). Could also have Skills separate but we can put Preferred under Qualifications.
- Benefits: list from Benefits section.
We should not include Pay or Schedule.
We must preserve all substantive information. Ensure we don't lose any details.
Let's extract content.
About NGS paragraph:
"NGS builds modern geospatial and C5ISR software for the U.S. Department of Defense and other federal customers. We've been at this since 2009, and we've supported programs at DIA, NGA, the U.S. Army Geospatial Center, INSCOM, SOCOM, and DHA. We're headquartered in the Charleston, SC area and we hold a GSA Multiple Award Schedule contract. We leverage open-source technology and deep mission expertise to deliver secure, scalable systems that solve real problems for warfighters and government agencies. Our flagship platform, CoreSpatial, is built on GeoServer, PostGIS, GDAL, MapStore2, and CesiumJS. We're serious about open source and contribute upstream. We are a small, focused team with a strong track record of delivering complex solutions under real constraints. Our customers rely on us to cut through the noise, move fast, and deliver results that work. More on who we are, the team, and what we do for government customers."
The Role overview:
"Geographic Information Systems engineer with 3D systems creation and support experience. Experienced in design and delivery of software built on Open Geospatial Consortium specifications and working bodies; examples, 3D Tiles, 3D scenes I3S, 3DPS, WPS, WCPS. Experienced with open source libraries and end products such as GDAL, PDAL, MDAL, GEOS, Open3D, and PostGIS.React front end library experience is preferred but not a hard requirement. Does require fundamental understanding of technologies underpinning Cesium ion, OpenCV, Unreal Engine, or similar applications. This is a senior level role for an engineer who can work independently within an organization, turning a vision for 3D data processing into products.We're hiring a Lead 3D Geospatial Engineer for customers looking to implement 3D data processing, services, and integrations ultimately displayed using popular front end visualizations in CesiumJS, OpenLayers or similar. This is a deep expert level role crafting data pipelines from sources into information that can be conveyed via 3D outputs in GIS systems. Data modeling, systems architecture, services design, specification implementations — this role has it all.The work is primarily done using Golang backends but this is a flexible requirement depending on the stage of processing, or analysis in a pipeline. You will build and maintain services running in containers and orchestrated by Kubernetes; there you will find a team of people to help deploy your solutions continuously and securely.You will be working alongside a distributed development team but as the lead in all 3D subject matter, often independently tasked."
We can combine these into About the role section.
Responsibilities list:
- Design, build, and maintain data pipelines for 3D source or finished products, parsing, routing, translation, display
- Integrate 3D capability from custom code, open source libraries, and partner platform integrations via APIs, message brokers, database
- Build and extend, or recommend for development, front-end components for operator-facing views and configuration of your 3D processing pipelines
- Deploy and troubleshoot your work in containerized environments (Docker, Kubernetes) as you go
- Work day to day with a distributed partner engineering team: sprint planning, code reviews, joint debugging, release coordination
- Support integration events, demos, and test activity, including occasional troubleshooting under time pressure
- Follow secure coding practices and support local security and configuration requirements
Required list:
- Professional software engineering experience building production level GIS services.
- Subject matter expert in GIS: 8+ years.
- Strong Golang or equivalent systems-level experience in C/C++/Java/Rust with demonstrated ability to pick up languages quickly
- Comfort with network programming: TCP/UDP, multicast, binary protocols, byte-level message formats
- Linux, Git, and modern CI/CD workflows
- U.S. citizenship.
- Active Secret or Top Secret clearance preferred, otherwise ability to obtain and maintain one.
Preferred list:
- Full-stack software engineering experience
- Kubernetes and container orchestration in production
- Experience working remotely on a distributed or multi-company development team
- Prior DoD or IC program experience
Benefits list:
- Flexible health insurance. Choose from a range of options that fit your situation.
- Life and short-term disability coverage.
- 401(k) retirement plan with competitive options.
- Four weeks of paid time off, moving to five weeks with tenure.
We must not add Pay or Schedule.
Now produce HTML fragment with headings and
for prose,
- for lists.
We need to ensure we don't include any boilerplate like "More on who we are, the team, and what we do for government customers." That's part of About NGS; we keep it.
We should not duplicate lines.
Let's craft.
HTML:
About the role
NGS builds modern geospatial and C5ISR software for the U.S. Department of Defense and other federal customers. We've been at this since 2009, and we've supported programs at DIA, NGA, the U.S. Army Geospatial Center, INSCOM, SOCOM, and DHA. We're headquartered in the Charleston, SC area and we hold a GSA Multiple Award Schedule contract. We leverage open-source technology and deep mission expertise to deliver secure, scalable systems that solve real problems for warfighters and government agencies. Our flagship platform, CoreSpatial, is built on GeoServer, PostGIS, GDAL, MapStore2, and CesiumJS. We're serious about open source and contribute upstream. We are a small, focused team with a strong track record of delivering complex solutions under real constraints. Our customers rely on us to cut through the noise, move fast, and deliver results that work. More on who we are, the team, and what we do for government customers.
Geographic Information Systems engineer with 3D systems creation and support experience. Experienced in design and delivery of software built on Open Geospatial Consortium specifications and working bodies; examples, 3D Tiles, 3D scenes I3S, 3DPS, WPS, WCPS. Experienced with open source libraries and end products such as GDAL, PDAL, MDAL, GEOS, Open3D, and PostGIS. React front end library experience is preferred but not a hard requirement. Does require fundamental understanding of technologies underpinning Cesium ion, OpenCV, Unreal Engine, or similar applications. This is a senior level role for an engineer who can work independently within an organization, turning a vision for 3D data processing into products. We're hiring a Lead 3D Geospatial Engineer for customers looking to implement 3D data processing, services, and integrations ultimately displayed using popular front end visualizations in CesiumJS, OpenLayers or similar. This is a deep expert level role crafting data pipelines from sources into information that can be conveyed via 3D outputs in GIS systems. Data modeling, systems architecture, services design, specification implementations — this role has it all. The work is primarily done using Golang backends but this is a flexible requirement depending on the stage of processing, or analysis in a pipeline. You will build and maintain services running in containers and orchestrated by Kubernetes; there you will find a team of people to help deploy your solutions continuously and securely. You will be working alongside a distributed development team but as the lead in all 3D subject matter, often independently tasked.
Then Responsibilities:
Responsibilities
- Design, build, and maintain data pipelines for 3D source or finished products, parsing, routing, translation, display
- Integrate 3D capability from custom code, open source libraries, and partner platform integrations via APIs, message brokers, database
- Build and extend, or recommend for development, front-end components for operator-facing views and configuration of your 3D processing pipelines
- Deploy and troubleshoot your work in containerized environments (Docker, Kubernetes) as you go
- Work day to day with a distributed partner engineering team: sprint planning
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include: About the role? The posting has "About NGS" and "The Role". Could treat "About NGS" as "About the role"? Actually "About the role" is a heading they suggest. But we have "About NGS" describing company. Could we put that under "About the role"? Might be okay. Or we could have separate sections: "About NGS" not in list but we can still use
for any heading; they gave examples but not exclusive. Probably we should follow their examples: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also add other headings if needed? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical but not exclusive; we can use other headings if appropriate. However they say "IMPORTANT: include a section ONLY when the posting has real, specific content for it". So we need to decide which sections have content.
We have content: About NGS (company description). The Role description (overview). Responsibilities (list). Required (list). Preferred (list). Benefits (list). No explicit Pay or Schedule. So we should not add Pay or Schedule sections.
We could have sections: About NGS, The Role, Responsibilities, Required, Preferred, Benefits. Or we could map Required to "Requirements" and Preferred to "Qualifications" or "Skills". The posting says "Required" and "Preferred". Could treat Required as "Requirements", Preferred as "Qualifications". Benefits as "Benefits". The Role overview could be "About the role". About NGS could be maybe a short paragraph under "About the role" or separate "About NGS". Since they said do not repeat job title as heading; but we can have About NGS as a heading? Not in examples but could be okay. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should stick to those headings. So we should map content to those headings.
Thus:
- About the role: combine About NGS and The Role description (company + role overview). Could be two paragraphs.
- Responsibilities: list from Responsibilities section.
- Requirements: list from Required section.
- Qualifications: list from Preferred section (or Skills). Could also have Skills separate but we can put Preferred under Qualifications.
- Benefits: list from Benefits section.
We should not include Pay or Schedule.
We must preserve all substantive information. Ensure we don't lose any details.
Let's extract content.
About NGS paragraph:
"NGS builds modern geospatial and C5ISR software for the U.S. Department of Defense and other federal customers. We've been at this since 2009, and we've supported programs at DIA, NGA, the U.S. Army Geospatial Center, INSCOM, SOCOM, and DHA. We're headquartered in the Charleston, SC area and we hold a GSA Multiple Award Schedule contract. We leverage open-source technology and deep mission expertise to deliver secure, scalable systems that solve real problems for warfighters and government agencies. Our flagship platform, CoreSpatial, is built on GeoServer, PostGIS, GDAL, MapStore2, and CesiumJS. We're serious about open source and contribute upstream. We are a small, focused team with a strong track record of delivering complex solutions under real constraints. Our customers rely on us to cut through the noise, move fast, and deliver results that work. More on who we are, the team, and what we do for government customers."
The Role overview:
"Geographic Information Systems engineer with 3D systems creation and support experience. Experienced in design and delivery of software built on Open Geospatial Consortium specifications and working bodies; examples, 3D Tiles, 3D scenes I3S, 3DPS, WPS, WCPS. Experienced with open source libraries and end products such as GDAL, PDAL, MDAL, GEOS, Open3D, and PostGIS.React front end library experience is preferred but not a hard requirement. Does require fundamental understanding of technologies underpinning Cesium ion, OpenCV, Unreal Engine, or similar applications. This is a senior level role for an engineer who can work independently within an organization, turning a vision for 3D data processing into products.We're hiring a Lead 3D Geospatial Engineer for customers looking to implement 3D data processing, services, and integrations ultimately displayed using popular front end visualizations in CesiumJS, OpenLayers or similar. This is a deep expert level role crafting data pipelines from sources into information that can be conveyed via 3D outputs in GIS systems. Data modeling, systems architecture, services design, specification implementations — this role has it all.The work is primarily done using Golang backends but this is a flexible requirement depending on the stage of processing, or analysis in a pipeline. You will build and maintain services running in containers and orchestrated by Kubernetes; there you will find a team of people to help deploy your solutions continuously and securely.You will be working alongside a distributed development team but as the lead in all 3D subject matter, often independently tasked."
We can combine these into About the role section.
Responsibilities list:
- Design, build, and maintain data pipelines for 3D source or finished products, parsing, routing, translation, display
- Integrate 3D capability from custom code, open source libraries, and partner platform integrations via APIs, message brokers, database
- Build and extend, or recommend for development, front-end components for operator-facing views and configuration of your 3D processing pipelines
- Deploy and troubleshoot your work in containerized environments (Docker, Kubernetes) as you go
- Work day to day with a distributed partner engineering team: sprint planning, code reviews, joint debugging, release coordination
- Support integration events, demos, and test activity, including occasional troubleshooting under time pressure
- Follow secure coding practices and support local security and configuration requirements
Required list:
- Professional software engineering experience building production level GIS services.
- Subject matter expert in GIS: 8+ years.
- Strong Golang or equivalent systems-level experience in C/C++/Java/Rust with demonstrated ability to pick up languages quickly
- Comfort with network programming: TCP/UDP, multicast, binary protocols, byte-level message formats
- Linux, Git, and modern CI/CD workflows
- U.S. citizenship.
- Active Secret or Top Secret clearance preferred, otherwise ability to obtain and maintain one.
Preferred list:
- Full-stack software engineering experience
- Kubernetes and container orchestration in production
- Experience working remotely on a distributed or multi-company development team
- Prior DoD or IC program experience
Benefits list:
- Flexible health insurance. Choose from a range of options that fit your situation.
- Life and short-term disability coverage.
- 401(k) retirement plan with competitive options.
- Four weeks of paid time off, moving to five weeks with tenure.
We must not add Pay or Schedule.
Now produce HTML fragment with headings and
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should stick to those headings. So we should map content to those headings.
Thus:
- About the role: combine About NGS and The Role description (company + role overview). Could be two paragraphs.
- Responsibilities: list from Responsibilities section.
- Requirements: list from Required section.
- Qualifications: list from Preferred section (or Skills). Could also have Skills separate but we can put Preferred under Qualifications.
- Benefits: list from Benefits section.
We should not include Pay or Schedule.
We must preserve all substantive information. Ensure we don't lose any details.
Let's extract content.
About NGS paragraph:
"NGS builds modern geospatial and C5ISR software for the U.S. Department of Defense and other federal customers. We've been at this since 2009, and we've supported programs at DIA, NGA, the U.S. Army Geospatial Center, INSCOM, SOCOM, and DHA. We're headquartered in the Charleston, SC area and we hold a GSA Multiple Award Schedule contract. We leverage open-source technology and deep mission expertise to deliver secure, scalable systems that solve real problems for warfighters and government agencies. Our flagship platform, CoreSpatial, is built on GeoServer, PostGIS, GDAL, MapStore2, and CesiumJS. We're serious about open source and contribute upstream. We are a small, focused team with a strong track record of delivering complex solutions under real constraints. Our customers rely on us to cut through the noise, move fast, and deliver results that work. More on who we are, the team, and what we do for government customers."
The Role overview:
"Geographic Information Systems engineer with 3D systems creation and support experience. Experienced in design and delivery of software built on Open Geospatial Consortium specifications and working bodies; examples, 3D Tiles, 3D scenes I3S, 3DPS, WPS, WCPS. Experienced with open source libraries and end products such as GDAL, PDAL, MDAL, GEOS, Open3D, and PostGIS.React front end library experience is preferred but not a hard requirement. Does require fundamental understanding of technologies underpinning Cesium ion, OpenCV, Unreal Engine, or similar applications. This is a senior level role for an engineer who can work independently within an organization, turning a vision for 3D data processing into products.We're hiring a Lead 3D Geospatial Engineer for customers looking to implement 3D data processing, services, and integrations ultimately displayed using popular front end visualizations in CesiumJS, OpenLayers or similar. This is a deep expert level role crafting data pipelines from sources into information that can be conveyed via 3D outputs in GIS systems. Data modeling, systems architecture, services design, specification implementations — this role has it all.The work is primarily done using Golang backends but this is a flexible requirement depending on the stage of processing, or analysis in a pipeline. You will build and maintain services running in containers and orchestrated by Kubernetes; there you will find a team of people to help deploy your solutions continuously and securely.You will be working alongside a distributed development team but as the lead in all 3D subject matter, often independently tasked."
We can combine these into About the role section.
Responsibilities list:
- Design, build, and maintain data pipelines for 3D source or finished products, parsing, routing, translation, display
- Integrate 3D capability from custom code, open source libraries, and partner platform integrations via APIs, message brokers, database
- Build and extend, or recommend for development, front-end components for operator-facing views and configuration of your 3D processing pipelines
- Deploy and troubleshoot your work in containerized environments (Docker, Kubernetes) as you go
- Work day to day with a distributed partner engineering team: sprint planning, code reviews, joint debugging, release coordination
- Support integration events, demos, and test activity, including occasional troubleshooting under time pressure
- Follow secure coding practices and support local security and configuration requirements
Required list:
- Professional software engineering experience building production level GIS services.
- Subject matter expert in GIS: 8+ years.
- Strong Golang or equivalent systems-level experience in C/C++/Java/Rust with demonstrated ability to pick up languages quickly
- Comfort with network programming: TCP/UDP, multicast, binary protocols, byte-level message formats
- Linux, Git, and modern CI/CD workflows
- U.S. citizenship.
- Active Secret or Top Secret clearance preferred, otherwise ability to obtain and maintain one.
Preferred list:
- Full-stack software engineering experience
- Kubernetes and container orchestration in production
- Experience working remotely on a distributed or multi-company development team
- Prior DoD or IC program experience
Benefits list:
- Flexible health insurance. Choose from a range of options that fit your situation.
- Life and short-term disability coverage.
- 401(k) retirement plan with competitive options.
- Four weeks of paid time off, moving to five weeks with tenure.
We must not add Pay or Schedule.
Now produce HTML fragment with headings and
for prose,
- for lists.
We need to ensure we don't include any boilerplate like "More on who we are, the team, and what we do for government customers." That's part of About NGS; we keep it.
We should not duplicate lines.
Let's craft.
HTML:
About the role
NGS builds modern geospatial and C5ISR software for the U.S. Department of Defense and other federal customers. We've been at this since 2009, and we've supported programs at DIA, NGA, the U.S. Army Geospatial Center, INSCOM, SOCOM, and DHA. We're headquartered in the Charleston, SC area and we hold a GSA Multiple Award Schedule contract. We leverage open-source technology and deep mission expertise to deliver secure, scalable systems that solve real problems for warfighters and government agencies. Our flagship platform, CoreSpatial, is built on GeoServer, PostGIS, GDAL, MapStore2, and CesiumJS. We're serious about open source and contribute upstream. We are a small, focused team with a strong track record of delivering complex solutions under real constraints. Our customers rely on us to cut through the noise, move fast, and deliver results that work. More on who we are, the team, and what we do for government customers.
Geographic Information Systems engineer with 3D systems creation and support experience. Experienced in design and delivery of software built on Open Geospatial Consortium specifications and working bodies; examples, 3D Tiles, 3D scenes I3S, 3DPS, WPS, WCPS. Experienced with open source libraries and end products such as GDAL, PDAL, MDAL, GEOS, Open3D, and PostGIS. React front end library experience is preferred but not a hard requirement. Does require fundamental understanding of technologies underpinning Cesium ion, OpenCV, Unreal Engine, or similar applications. This is a senior level role for an engineer who can work independently within an organization, turning a vision for 3D data processing into products. We're hiring a Lead 3D Geospatial Engineer for customers looking to implement 3D data processing, services, and integrations ultimately displayed using popular front end visualizations in CesiumJS, OpenLayers or similar. This is a deep expert level role crafting data pipelines from sources into information that can be conveyed via 3D outputs in GIS systems. Data modeling, systems architecture, services design, specification implementations — this role has it all. The work is primarily done using Golang backends but this is a flexible requirement depending on the stage of processing, or analysis in a pipeline. You will build and maintain services running in containers and orchestrated by Kubernetes; there you will find a team of people to help deploy your solutions continuously and securely. You will be working alongside a distributed development team but as the lead in all 3D subject matter, often independently tasked.
Then Responsibilities:Responsibilities
- Design, build, and maintain data pipelines for 3D source or finished products, parsing, routing, translation, display
- Integrate 3D capability from custom code, open source libraries, and partner platform integrations via APIs, message brokers, database
- Build and extend, or recommend for development, front-end components for operator-facing views and configuration of your 3D processing pipelines
- Deploy and troubleshoot your work in containerized environments (Docker, Kubernetes) as you go
- Work day to day with a distributed partner engineering team: sprint planning