Data Analyst - Senior
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
Content:
- "What You’ll Be Owning" paragraph: description of role. Could be "About the role" or "Responsibilities". Probably "About the role" or "Responsibilities". The posting says: "In this role, you will support mission-critical intelligence operations by managing, structuring, and optimizing geospatial and enterprise data..." That's responsibilities.
- "What Impact You'll Have": description of impact, could be also responsibilities or maybe "Responsibilities". Might combine.
- "What You Must Have": list of requirements/qualifications.
- "What Would Be Nice To Have": nice-to-have qualifications.
- Pay Range: includes pay range $120,000 - $140,000.
- Benefits: description of benefits package.
- "Why Choose GRVTY": maybe not needed; could be considered "About the company" but not required. Could be omitted as not a standard heading.
- EEO statement: boilerplate to remove.
- Application instructions: remove.
We need to avoid repeating job title as heading.
We need to use for each section heading.
We need to use - for any list of duties/requirements/benefits.
We need to use
for prose.
We need to preserve all substantive information, not invent or summarize away detail.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text.
Thus we need sections: About the role (or Responsibilities), Requirements (or Qualifications), Nice-to-have (maybe Skills?), Benefits, Pay.
We need to decide headings: Could use "About the role" for the first two paragraphs combined. Or separate "Responsibilities" and "Impact". But we should prefer few substantive sections over many thin ones. So combine "What You’ll Be Owning" and "What Impact You'll Have" into a single "About the role" or "Responsibilities". Probably "About the role" is appropriate.
Then "Requirements" for "What You Must Have". Could also include "Qualifications". Use "Requirements".
Then "Preferred Qualifications" or "Nice-to-have" maybe "Preferred Skills". Could use "Preferred Qualifications". But we need to decide heading from allowed list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "Requirements" for must-have, "Skills" for nice-to-have? Or "Qualifications" for must-have and "Skills" for nice-to-have. Let's map:
- Must-have: "Requirements" (or "Qualifications").
- Nice-to-have: "Skills" (or "Preferred Qualifications").
We have both "Requirements" and "Skills" as allowed headings. Use "Requirements" for must-have, "Skills" for nice-to-have.
Then "Benefits" for benefits description.
Then "Pay" for pay range.
We should not include "Schedule" as no info.
Now we need to extract content.
First, combine "What You’ll Be Owning" and "What Impact You'll Have" into prose for About the role.
Let's extract:
What You’ll Be Owning:
"In this role, you will support mission-critical intelligence operations by managing, structuring, and optimizing geospatial and enterprise data to ensure accuracy, accessibility, and usability across analytic environments. You will apply your expertise in GIS, data schemas, and georeferencing to organize and maintain spatial data, ensuring alignment with established metadata and extraction standards. Leveraging relational database management systems, you will design, normalize, and optimize data architectures to enhance performance and scalability, while supporting enterprise geodatabases such as Spatial Database Engines (SDEs)."
What Impact You'll Have:
"You will utilize tools including the ArcGIS Suite, ArcGIS Online, Portal, SQL, Oracle, Excel, and Access to store, manage, and maintain high-quality datasets that enable downstream analysis. Additionally, you will collaborate closely with analysts, engineers, and cross-functional mission partners to improve data workflows, enforce data governance best practices, and ensure that data is structured to effectively support GEOINT and multi-INT mission requirements. This role requires a proactive mindset, attention to detail, and a strong commitment to team success in a fast-paced, mission-driven environment."
Combine into a paragraph(s). Could be two
elements.
Now Requirements (What You Must Have):
List:
- Active TS/SCI Clearance is required with the ability to obtain a CI Poly.
- 10+ years of relevant experience. (A combination of years of experience, professional certifications, and education may be used in lieu of years of experience)
- Demonstrated understanding of GIS, data schemas, and the geo-referencing of information
- Knowledge of extraction and metadata specifications
- Knowledge of Relational Database Management System (RDBMS) architectures, best practices for data normalization, and performance tuning/optimization techniques
- Knowledge of enterprise geodatabases, such as Spatial Database Engines (SDEs)
- Knowledge of tools such as the ArcGIS Suite, ArcGIS Online, Portal, Excel, Access, and SQL for the storage, organization, and maintenance of spatial data
- Familiarity with ontology concepts as they relate to information systems, data modeling, and data relationships
- Strong collaboration skills with the ability to work effectively as a team player across technical and mission-focused teams
We need to preserve all substantive information. Use
- for each.
Now Skills (What Would Be Nice To Have):
List:
- Knowledge of scripting languages, such as R or Python
- Demonstrated understanding of cartographic principles
- Knowledge of Tableau or other data visualization tools
- Experience supporting data governance, data stewardship, or data quality initiatives in enterprise environments
- Certifications:
- GEOINT Professional Certification - Fundamentals (F)
- GEOINT Professional Certification – Geospatial Data Management (GDM)
We need to keep the bullet list; maybe treat certifications as sub-items? Could just list them as separate
- .
Now Benefits:
Paragraph: "GRVTY provides competitive pay, comprehensive benefits, and meaningful opportunities for professional growth. Our benefits package is designed to support the well-being of our employees and their families, and includes coverage in areas such as healthcare, financial wellness, retirement planning, family assistance, continued education, and paid time off."
Then list of benefits under "Why Choose GRVTY": Actually there is a separate section "Why Choose GRVTY" with bullet list of benefits: Robust health plan including medical, dental, and vision; Health Savings Account with company contribution; Annual Paid Time Off and Paid Holidays; Paid Parental Leave; 401k with generous company match; Training and Development Opportunities; Award Programs; Variety of Company Sponsored Events.
We should include those as benefits. The earlier benefits paragraph is generic; we can combine.
Thus Benefits section: include prose paragraph plus list.
Now Pay:
We have pay range: "$120,000 - $140,000". Also there is duplicate lines: "Pay Range: At GRVTY, we understand that compensation is influenced by many factors—such as geographic location, federal contract labor categories, wage rates, prior experience, skillsets, education, and certifications. We’re proud to offer a work environment that empowers our team to achieve a strong work-life balance. GRVTY provides competitive pay, comprehensive benefits, and meaningful opportunities for professional growth. Our benefits package is designed to support the well-being of our employees and their families, and includes coverage in areas such as healthcare, financial wellness, retirement planning, family assistance, continued education, and paid time off. The pay range for this position is: $120,000 - $140,000 Pay Range: At GRVTY, we understand that compensation is influenced by many factors—such as geographic location, federal contract labor categories, wage rates, prior experience, skillsets, education, and certifications. We’re proud to offer a work environment that empowers our team to achieve a strong work-life balance. GRVTY provides competitive pay, comprehensive benefits, and meaningful opportunities for professional growth. Our benefits package is designed to support the well-being of our employees and their families, and includes coverage in areas such as healthcare, financial wellness, retirement planning, family assistance, continued education, and paid time off. Virginia Pay Range $120,000—$140,000 USD"
We need to preserve substantive information: pay range $120,000 - $140,000. Also mention that compensation influenced by many factors etc. That's substantive? It's generic but maybe considered boilerplate? It's repeated. The instruction: remove duplicated lines. So we should keep only one instance of the explanatory text? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The duplicated lines are the repeated paragraph about compensation factors. We should keep only one copy. Also we should keep the pay range.
Thus Pay section: maybe a
explaining that compensation is influenced by many factors (geographic location, federal contract labor categories, wage rates, prior experience, skillsets, education, and certifications) and that GRVTY offers competitive pay, comprehensive benefits, etc. Then a
with the pay range: "$120,000 - $140,000". Or combine.
We must not include filler like "commensurate with experience". Not present.
Now we need to output only HTML fragment, no /, no markdown.
Let's construct:
About the role
In this role, you will support mission-critical intelligence operations by managing, structuring, and optimizing geospatial and enterprise data to ensure accuracy, accessibility, and usability across analytic environments. You will apply your expertise in GIS, data schemas, and georeferencing to organize and maintain spatial data, ensuring alignment with established metadata and extraction standards. Leveraging relational database management systems, you will design, normalize, and optimize data architectures to enhance performance and scalability, while supporting enterprise geodatabases such as Spatial Database Engines (SDEs).
You will utilize tools including the ArcGIS Suite, ArcGIS Online, Portal, SQL, Oracle, Excel, and Access to store, manage, and maintain high-quality datasets that enable downstream analysis. Additionally, you will collaborate closely with analysts, engineers, and cross-functional mission partners to improve data workflows, enforce data governance best practices, and ensure that data is structured to effectively support GEOINT and multi-INT mission requirements. This role requires a proactive mindset, attention to detail, and a strong commitment to team success in a fast-paced, mission-driven environment.
Requirements
- Active TS/SCI Clearance is required with the ability to obtain a CI Poly.
- 10+ years of relevant experience. (A combination of years of experience, professional certifications, and education may be used in lieu of years of experience)
- Demonstrated understanding of GIS, data schemas, and the geo-referencing of information
- Knowledge of extraction and metadata specifications
- Knowledge of Relational Database Management System (RDBMS) architectures, best practices for data normalization, and performance tuning/optimization techniques
- Knowledge of enterprise geodatabases, such as Spatial Database Engines (SDEs)
- Knowledge of tools such as the ArcGIS Suite, ArcGIS Online, Portal, Excel, Access, and SQL for the storage, organization, and maintenance of spatial data
- for any list of duties/requirements/benefits.
We need to use
for prose. We need to preserve all substantive information, not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Thus we need sections: About the role (or Responsibilities), Requirements (or Qualifications), Nice-to-have (maybe Skills?), Benefits, Pay. We need to decide headings: Could use "About the role" for the first two paragraphs combined. Or separate "Responsibilities" and "Impact". But we should prefer few substantive sections over many thin ones. So combine "What You’ll Be Owning" and "What Impact You'll Have" into a single "About the role" or "Responsibilities". Probably "About the role" is appropriate. Then "Requirements" for "What You Must Have". Could also include "Qualifications". Use "Requirements". Then "Preferred Qualifications" or "Nice-to-have" maybe "Preferred Skills". Could use "Preferred Qualifications". But we need to decide heading from allowed list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "Requirements" for must-have, "Skills" for nice-to-have? Or "Qualifications" for must-have and "Skills" for nice-to-have. Let's map: - Must-have: "Requirements" (or "Qualifications"). - Nice-to-have: "Skills" (or "Preferred Qualifications"). We have both "Requirements" and "Skills" as allowed headings. Use "Requirements" for must-have, "Skills" for nice-to-have. Then "Benefits" for benefits description. Then "Pay" for pay range. We should not include "Schedule" as no info. Now we need to extract content. First, combine "What You’ll Be Owning" and "What Impact You'll Have" into prose for About the role. Let's extract: What You’ll Be Owning: "In this role, you will support mission-critical intelligence operations by managing, structuring, and optimizing geospatial and enterprise data to ensure accuracy, accessibility, and usability across analytic environments. You will apply your expertise in GIS, data schemas, and georeferencing to organize and maintain spatial data, ensuring alignment with established metadata and extraction standards. Leveraging relational database management systems, you will design, normalize, and optimize data architectures to enhance performance and scalability, while supporting enterprise geodatabases such as Spatial Database Engines (SDEs)." What Impact You'll Have: "You will utilize tools including the ArcGIS Suite, ArcGIS Online, Portal, SQL, Oracle, Excel, and Access to store, manage, and maintain high-quality datasets that enable downstream analysis. Additionally, you will collaborate closely with analysts, engineers, and cross-functional mission partners to improve data workflows, enforce data governance best practices, and ensure that data is structured to effectively support GEOINT and multi-INT mission requirements. This role requires a proactive mindset, attention to detail, and a strong commitment to team success in a fast-paced, mission-driven environment." Combine into a paragraph(s). Could be two
elements. Now Requirements (What You Must Have): List: - Active TS/SCI Clearance is required with the ability to obtain a CI Poly. - 10+ years of relevant experience. (A combination of years of experience, professional certifications, and education may be used in lieu of years of experience) - Demonstrated understanding of GIS, data schemas, and the geo-referencing of information - Knowledge of extraction and metadata specifications - Knowledge of Relational Database Management System (RDBMS) architectures, best practices for data normalization, and performance tuning/optimization techniques - Knowledge of enterprise geodatabases, such as Spatial Database Engines (SDEs) - Knowledge of tools such as the ArcGIS Suite, ArcGIS Online, Portal, Excel, Access, and SQL for the storage, organization, and maintenance of spatial data - Familiarity with ontology concepts as they relate to information systems, data modeling, and data relationships - Strong collaboration skills with the ability to work effectively as a team player across technical and mission-focused teams We need to preserve all substantive information. Use
- for each. Now Skills (What Would Be Nice To Have): List: - Knowledge of scripting languages, such as R or Python - Demonstrated understanding of cartographic principles - Knowledge of Tableau or other data visualization tools - Experience supporting data governance, data stewardship, or data quality initiatives in enterprise environments - Certifications: - GEOINT Professional Certification - Fundamentals (F) - GEOINT Professional Certification – Geospatial Data Management (GDM) We need to keep the bullet list; maybe treat certifications as sub-items? Could just list them as separate
- .
Now Benefits:
Paragraph: "GRVTY provides competitive pay, comprehensive benefits, and meaningful opportunities for professional growth. Our benefits package is designed to support the well-being of our employees and their families, and includes coverage in areas such as healthcare, financial wellness, retirement planning, family assistance, continued education, and paid time off."
Then list of benefits under "Why Choose GRVTY": Actually there is a separate section "Why Choose GRVTY" with bullet list of benefits: Robust health plan including medical, dental, and vision; Health Savings Account with company contribution; Annual Paid Time Off and Paid Holidays; Paid Parental Leave; 401k with generous company match; Training and Development Opportunities; Award Programs; Variety of Company Sponsored Events.
We should include those as benefits. The earlier benefits paragraph is generic; we can combine.
Thus Benefits section: include prose paragraph plus list.
Now Pay:
We have pay range: "$120,000 - $140,000". Also there is duplicate lines: "Pay Range: At GRVTY, we understand that compensation is influenced by many factors—such as geographic location, federal contract labor categories, wage rates, prior experience, skillsets, education, and certifications. We’re proud to offer a work environment that empowers our team to achieve a strong work-life balance. GRVTY provides competitive pay, comprehensive benefits, and meaningful opportunities for professional growth. Our benefits package is designed to support the well-being of our employees and their families, and includes coverage in areas such as healthcare, financial wellness, retirement planning, family assistance, continued education, and paid time off. The pay range for this position is: $120,000 - $140,000 Pay Range: At GRVTY, we understand that compensation is influenced by many factors—such as geographic location, federal contract labor categories, wage rates, prior experience, skillsets, education, and certifications. We’re proud to offer a work environment that empowers our team to achieve a strong work-life balance. GRVTY provides competitive pay, comprehensive benefits, and meaningful opportunities for professional growth. Our benefits package is designed to support the well-being of our employees and their families, and includes coverage in areas such as healthcare, financial wellness, retirement planning, family assistance, continued education, and paid time off. Virginia Pay Range $120,000—$140,000 USD"
We need to preserve substantive information: pay range $120,000 - $140,000. Also mention that compensation influenced by many factors etc. That's substantive? It's generic but maybe considered boilerplate? It's repeated. The instruction: remove duplicated lines. So we should keep only one instance of the explanatory text? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The duplicated lines are the repeated paragraph about compensation factors. We should keep only one copy. Also we should keep the pay range.
Thus Pay section: maybe a
explaining that compensation is influenced by many factors (geographic location, federal contract labor categories, wage rates, prior experience, skillsets, education, and certifications) and that GRVTY offers competitive pay, comprehensive benefits, etc. Then a
with the pay range: "$120,000 - $140,000". Or combine. We must not include filler like "commensurate with experience". Not present. Now we need to output only HTML fragment, no /, no markdown. Let's construct:
About the role
In this role, you will support mission-critical intelligence operations by managing, structuring, and optimizing geospatial and enterprise data to ensure accuracy, accessibility, and usability across analytic environments. You will apply your expertise in GIS, data schemas, and georeferencing to organize and maintain spatial data, ensuring alignment with established metadata and extraction standards. Leveraging relational database management systems, you will design, normalize, and optimize data architectures to enhance performance and scalability, while supporting enterprise geodatabases such as Spatial Database Engines (SDEs).
You will utilize tools including the ArcGIS Suite, ArcGIS Online, Portal, SQL, Oracle, Excel, and Access to store, manage, and maintain high-quality datasets that enable downstream analysis. Additionally, you will collaborate closely with analysts, engineers, and cross-functional mission partners to improve data workflows, enforce data governance best practices, and ensure that data is structured to effectively support GEOINT and multi-INT mission requirements. This role requires a proactive mindset, attention to detail, and a strong commitment to team success in a fast-paced, mission-driven environment.
Requirements
- Active TS/SCI Clearance is required with the ability to obtain a CI Poly.
- 10+ years of relevant experience. (A combination of years of experience, professional certifications, and education may be used in lieu of years of experience)
- Demonstrated understanding of GIS, data schemas, and the geo-referencing of information
- Knowledge of extraction and metadata specifications
- Knowledge of Relational Database Management System (RDBMS) architectures, best practices for data normalization, and performance tuning/optimization techniques
- Knowledge of enterprise geodatabases, such as Spatial Database Engines (SDEs)
- Knowledge of tools such as the ArcGIS Suite, ArcGIS Online, Portal, Excel, Access, and SQL for the storage, organization, and maintenance of spatial data