GRC Data Scientist
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content.
We need to parse the job posting.
Key parts:
- Job Family Data Science & Analysis Travel Required Up to 10% Clearance Required Ability to Obtain Public Trust
- What You Will Do: description of role.
- What You Will Need: requirements.
- What Would Be Nice To Have: nice-to-have.
- The annual salary range for this position is $98,000.00-$163,000.00.
- What We Offer: benefits list.
- About Guidehouse: EEO etc, but we need to remove boilerplate EEO/equal-opportunity etc. Also remove application instructions, legal, etc.
We need to preserve all substantive information, not invent or summarize away detail.
We need to use for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We must 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.
We need to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text.
We need to prefer a few substantive sections over many thin ones.
Thus we can combine sections: maybe "About the role" (What You Will Do), "Responsibilities" could be same as duties? But we have "What You Will Do" describing duties. Could treat that as Responsibilities. Or we could have "About the role" as a short paragraph summarizing role, and then "Responsibilities" as bullet list.
But we must not create sections with filler. So we need to decide which headings to include based on actual content.
We have:
- About the role: we could use the introductory paragraph: "The Guidehouse Technology AI & Data team is seeking a Data Scientist to support the development of analytical and automation solution for clients across our Department of Justice (DOJ) portfolio. This high performing team works with clients to implement the full spectrum of data analytics and data science, from data querying and data wrangling, to data visualization and dashboarding, to predictive analytics, machine learning, and artificial intelligence as well as robotic process automation (RPA). Our services enable our clients to define their information strategy, enable mission critical insights and data-driven decision making, reduce cost and complexity, increase trust, and improve operational effectiveness."
That's substantive.
- Responsibilities: we have bullet-like sentences: "Turn cybersecurity and GRC data into actionable insights that support RMF workflows, continuous monitoring, vulnerability management, and authorization activities. Design and deliver analytics (descriptive, diagnostic, predictive) and ML models that improve risk visibility (e.g., predictive risk scoring, anomaly detection) and inform remediation priorities. Partner with ISSOs, system owners, and Agile delivery teams to define data requirements, curate datasets, and operationalize dashboards for mission decision-making. Operate within CI/CD and DevSecOps practices to version experiments, automate data/feature pipelines, and validate models in controlled environments. Communicate findings in plain language and produce clear visualizations and documentation that align to stakeholder needs."
These are duties; we can put them as
- .
- Requirements: "What You Will Need" includes: Must be able to OBTAIN and MAINTAIN a Federal or DHS "PUBLIC TRUST"; candidates must obtain approved adjudication of their PUBLIC TRUST prior to onboarding with Guidehouse. Candidates with an ACTIVE PUBLIC TRUST or SUITABILITY are preferred. Bachelor’s degree THREE (3) or more years’ experience as a Data Security Analyst or equivalent knowledge. FOUR (4) or more years’ experience in data analytics with large data sets. Experience working on data analytics, modeling, or visualization projects in a consulting or federal environment. Experience working with Python, SQL, and other modern scripting languages used in analytics. Experience working with at least one major BI/data visualization platform (Tableau, Power BI, or Qlik). Ability to support on-site and hybrid projects in the DC metro area.
We can list these as bullet points.
- Qualifications: maybe combine with Requirements? But we could have a separate "Qualifications" heading for education and experience? However we must avoid thin sections. Could combine Requirements and Qualifications into one section "Requirements & Qualifications". But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. If we combine, we might still use a heading like "Requirements" and include both mandatory and nice-to-have? But nice-to-have is separate.
We have "What Would Be Nice To Have": list of nice-to-have items. That could be under "Skills" or "Qualifications". Could treat as "Preferred Qualifications". But we have headings: Skills, Qualifications. Could put nice-to-have under "Skills". Or we could have a separate "Preferred Qualifications" but not in list. Better to put under "Skills" as bullet list.
- Pay: we have salary range. So we need a Pay section with that info.
- Benefits: we have "What We Offer" list of benefits. So Benefits section.
- Schedule: not mentioned besides travel up to 10% and ability to support on-site and hybrid projects. No explicit schedule (full-time, part-time). So we should not create Schedule section.
- Travel: could be included in About the role or Responsibilities? Not needed as separate heading.
Thus sections: About the role (intro paragraph), Responsibilities (bullet list of duties), Requirements (bullet list of mandatory qualifications), Skills (bullet list of nice-to-have), Pay (salary range), Benefits (bullet list of benefits). Possibly also "Qualifications" but we already have Requirements; we could rename Requirements to "Qualifications". But we need to follow instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. Let's include About the role, Responsibilities, Requirements, Skills, Pay, Benefits. That's six sections.
We must not repeat job title as heading. Good.
We must not include boilerplate EEO etc. So we will omit About Guidehouse section.
We must not include application instructions etc.
Now format: Use
for each heading. Then content: either
for prose or
- for lists.
For About the role: we have a few sentences; we can put in
.
For Responsibilities: each duty as
- .
For Requirements: each requirement as
- . Must preserve all detail: include the PUBLIC TRUST requirement verbatim, Bachelor’s degree, etc.
For Skills: nice-to-have items as
- .
For Pay: we have salary range sentence; we can put in
.
For Benefits: list each benefit as
- . The benefits list is long; we need to preserve all. We'll copy them exactly as listed.
Check benefits list: "Medical, Rx, Dental & Vision InsurancePersonal and Family Sick Time & Company Paid HolidaysParental Leave401(k) Retirement PlanGroup Term Life and Travel AssistanceVoluntary Life and AD&D InsuranceHealth Savings Account, Health Care & Dependent Care Flexible Spending AccountsTransit and Parking Commuter BenefitsShort-Term & Long-Term DisabilityTuition Reimbursement, Personal Development, Certifications & Learning OpportunitiesEmployee Referral ProgramCorporate Sponsored Events & Community OutreachCare.com annual membershipEmployee Assistance ProgramSupplemental Benefits via Corestream (Critical Care, Hospital Indemnity, Accident Insurance, Legal Assistance and ID theft protection, etc.)Position may be eligible for a discretionary variable incentive bonus"
Note there is no punctuation between some items; but we should preserve as is. We'll split by maybe commas? But better to keep as a single string? However instruction: use
- for any list of duties/requirements/benefits. So we need to split into items. The original benefits list seems to be a run-on sentence without clear delimiters. We need to infer items: Medical, Rx, Dental & Vision Insurance; Personal and Family Sick Time & Company Paid Holidays; Parental Leave; 401(k) Retirement Plan; Group Term Life and Travel Assistance; Voluntary Life and AD&D Insurance; Health Savings Account, Health Care & Dependent Care Flexible Spending Accounts; Transit and Parking Commuter Benefits; Short-Term & Long-Term Disability; Tuition Reimbursement, Personal Development, Certifications & Learning Opportunities; Employee Referral Program; Corporate Sponsored Events & Community Outreach; Care.com annual membership; Employee Assistance Program; Supplemental Benefits via Corestream (Critical Care, Hospital Indemnity, Accident Insurance, Legal Assistance and ID theft protection, etc.); Position may be eligible for a discretionary variable incentive bonus.
We'll create
- for each.
Now ensure we don't include any filler like "commensurate with experience". Not present.
Now produce HTML fragment.
Let's craft.
We'll start with
About the role
...
Then Responsibilities
- ...
...
Then Requirements
- ...
...
Then Skills
- ...
...
Then Pay
The annual salary range for this position is $98,000.00-$163,000.00.
Then Benefits
- ...
...
Make sure to not include extra whitespace? It's fine.
Now verify we preserved all substantive information.
Check About the role paragraph: we included the first two sentences? Actually we included the paragraph up to "improve operational effectiveness." That's from the "What You Will Do" section. Did we miss any? The "What You Will Do" also includes: "Turn cybersecurity and GRC data into actionable insights..." etc. Those we moved to Responsibilities. Good.
Now Responsibilities list: we need to include each bullet:
- Turn cybersecurity and GRC data into actionable insights that support RMF workflows, continuous monitoring, vulnerability management, and authorization activities.
- Design and deliver analytics (descriptive, diagnostic, predictive) and ML models that improve risk visibility (e.g., predictive risk scoring, anomaly detection) and inform remediation priorities.
- Partner with ISSOs, system owners, and Agile delivery teams to define data requirements, curate datasets, and operationalize dashboards for mission decision-making.
- Operate within CI/CD and DevSecOps practices to version experiments, automate data/feature pipelines, and validate models in controlled environments.
- Communicate findings in plain language and produce clear visualizations and documentation that align to stakeholder needs.
Check if any other duties: The paragraph also mentions "This high performing team works with clients to implement the full spectrum of data analytics and data science, from data querying and data wrangling, to data visualization and dashboarding, to predictive analytics, machine learning, and artificial intelligence as well as robotic process automation (RPA)." That is part of About the role? Actually that is also part of the team description; we could include it in About the role. We included only first two sentences? Let's re-evaluate.
Original "What You Will Do" paragraph:
"The Guidehouse Technology AI & Data team is seeking a Data Scientist to support the development of analytical and automation solution for clients across our Department of Justice (DOJ) portfolio. This high performing team works with clients to implement the full spectrum of data analytics and data science, from data querying and data wrangling, to data visualization and dashboarding, to predictive analytics, machine learning, and artificial intelligence as well
- for any list of duties/requirements/benefits, and
for prose. We must 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. We need to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We need to prefer a few substantive sections over many thin ones. Thus we can combine sections: maybe "About the role" (What You Will Do), "Responsibilities" could be same as duties? But we have "What You Will Do" describing duties. Could treat that as Responsibilities. Or we could have "About the role" as a short paragraph summarizing role, and then "Responsibilities" as bullet list. But we must not create sections with filler. So we need to decide which headings to include based on actual content. We have: - About the role: we could use the introductory paragraph: "The Guidehouse Technology AI & Data team is seeking a Data Scientist to support the development of analytical and automation solution for clients across our Department of Justice (DOJ) portfolio. This high performing team works with clients to implement the full spectrum of data analytics and data science, from data querying and data wrangling, to data visualization and dashboarding, to predictive analytics, machine learning, and artificial intelligence as well as robotic process automation (RPA). Our services enable our clients to define their information strategy, enable mission critical insights and data-driven decision making, reduce cost and complexity, increase trust, and improve operational effectiveness." That's substantive. - Responsibilities: we have bullet-like sentences: "Turn cybersecurity and GRC data into actionable insights that support RMF workflows, continuous monitoring, vulnerability management, and authorization activities. Design and deliver analytics (descriptive, diagnostic, predictive) and ML models that improve risk visibility (e.g., predictive risk scoring, anomaly detection) and inform remediation priorities. Partner with ISSOs, system owners, and Agile delivery teams to define data requirements, curate datasets, and operationalize dashboards for mission decision-making. Operate within CI/CD and DevSecOps practices to version experiments, automate data/feature pipelines, and validate models in controlled environments. Communicate findings in plain language and produce clear visualizations and documentation that align to stakeholder needs." These are duties; we can put them as
- .
- Requirements: "What You Will Need" includes: Must be able to OBTAIN and MAINTAIN a Federal or DHS "PUBLIC TRUST"; candidates must obtain approved adjudication of their PUBLIC TRUST prior to onboarding with Guidehouse. Candidates with an ACTIVE PUBLIC TRUST or SUITABILITY are preferred. Bachelor’s degree THREE (3) or more years’ experience as a Data Security Analyst or equivalent knowledge. FOUR (4) or more years’ experience in data analytics with large data sets. Experience working on data analytics, modeling, or visualization projects in a consulting or federal environment. Experience working with Python, SQL, and other modern scripting languages used in analytics. Experience working with at least one major BI/data visualization platform (Tableau, Power BI, or Qlik). Ability to support on-site and hybrid projects in the DC metro area.
We can list these as bullet points.
- Qualifications: maybe combine with Requirements? But we could have a separate "Qualifications" heading for education and experience? However we must avoid thin sections. Could combine Requirements and Qualifications into one section "Requirements & Qualifications". But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. If we combine, we might still use a heading like "Requirements" and include both mandatory and nice-to-have? But nice-to-have is separate.
We have "What Would Be Nice To Have": list of nice-to-have items. That could be under "Skills" or "Qualifications". Could treat as "Preferred Qualifications". But we have headings: Skills, Qualifications. Could put nice-to-have under "Skills". Or we could have a separate "Preferred Qualifications" but not in list. Better to put under "Skills" as bullet list.
- Pay: we have salary range. So we need a Pay section with that info.
- Benefits: we have "What We Offer" list of benefits. So Benefits section.
- Schedule: not mentioned besides travel up to 10% and ability to support on-site and hybrid projects. No explicit schedule (full-time, part-time). So we should not create Schedule section.
- Travel: could be included in About the role or Responsibilities? Not needed as separate heading.
Thus sections: About the role (intro paragraph), Responsibilities (bullet list of duties), Requirements (bullet list of mandatory qualifications), Skills (bullet list of nice-to-have), Pay (salary range), Benefits (bullet list of benefits). Possibly also "Qualifications" but we already have Requirements; we could rename Requirements to "Qualifications". But we need to follow instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. Let's include About the role, Responsibilities, Requirements, Skills, Pay, Benefits. That's six sections.
We must not repeat job title as heading. Good.
We must not include boilerplate EEO etc. So we will omit About Guidehouse section.
We must not include application instructions etc.
Now format: Use
for each heading. Then content: either
for prose or
- for lists.
For About the role: we have a few sentences; we can put in
. For Responsibilities: each duty as
- . For Requirements: each requirement as
- . Must preserve all detail: include the PUBLIC TRUST requirement verbatim, Bachelor’s degree, etc. For Skills: nice-to-have items as
- .
For Pay: we have salary range sentence; we can put in
. For Benefits: list each benefit as
- . The benefits list is long; we need to preserve all. We'll copy them exactly as listed.
Check benefits list: "Medical, Rx, Dental & Vision InsurancePersonal and Family Sick Time & Company Paid HolidaysParental Leave401(k) Retirement PlanGroup Term Life and Travel AssistanceVoluntary Life and AD&D InsuranceHealth Savings Account, Health Care & Dependent Care Flexible Spending AccountsTransit and Parking Commuter BenefitsShort-Term & Long-Term DisabilityTuition Reimbursement, Personal Development, Certifications & Learning OpportunitiesEmployee Referral ProgramCorporate Sponsored Events & Community OutreachCare.com annual membershipEmployee Assistance ProgramSupplemental Benefits via Corestream (Critical Care, Hospital Indemnity, Accident Insurance, Legal Assistance and ID theft protection, etc.)Position may be eligible for a discretionary variable incentive bonus"
Note there is no punctuation between some items; but we should preserve as is. We'll split by maybe commas? But better to keep as a single string? However instruction: use
- for any list of duties/requirements/benefits. So we need to split into items. The original benefits list seems to be a run-on sentence without clear delimiters. We need to infer items: Medical, Rx, Dental & Vision Insurance; Personal and Family Sick Time & Company Paid Holidays; Parental Leave; 401(k) Retirement Plan; Group Term Life and Travel Assistance; Voluntary Life and AD&D Insurance; Health Savings Account, Health Care & Dependent Care Flexible Spending Accounts; Transit and Parking Commuter Benefits; Short-Term & Long-Term Disability; Tuition Reimbursement, Personal Development, Certifications & Learning Opportunities; Employee Referral Program; Corporate Sponsored Events & Community Outreach; Care.com annual membership; Employee Assistance Program; Supplemental Benefits via Corestream (Critical Care, Hospital Indemnity, Accident Insurance, Legal Assistance and ID theft protection, etc.); Position may be eligible for a discretionary variable incentive bonus. We'll create
- for each.
Now ensure we don't include any filler like "commensurate with experience". Not present.
Now produce HTML fragment.
Let's craft.
We'll start with
About the role
...
ThenResponsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Pay
The annual salary range for this position is $98,000.00-$163,000.00.
ThenBenefits
- ... ...
- for lists.
For About the role: we have a few sentences; we can put in
- .
- Requirements: "What You Will Need" includes: Must be able to OBTAIN and MAINTAIN a Federal or DHS "PUBLIC TRUST"; candidates must obtain approved adjudication of their PUBLIC TRUST prior to onboarding with Guidehouse. Candidates with an ACTIVE PUBLIC TRUST or SUITABILITY are preferred. Bachelor’s degree THREE (3) or more years’ experience as a Data Security Analyst or equivalent knowledge. FOUR (4) or more years’ experience in data analytics with large data sets. Experience working on data analytics, modeling, or visualization projects in a consulting or federal environment. Experience working with Python, SQL, and other modern scripting languages used in analytics. Experience working with at least one major BI/data visualization platform (Tableau, Power BI, or Qlik). Ability to support on-site and hybrid projects in the DC metro area.
We can list these as bullet points.
- Qualifications: maybe combine with Requirements? But we could have a separate "Qualifications" heading for education and experience? However we must avoid thin sections. Could combine Requirements and Qualifications into one section "Requirements & Qualifications". But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. If we combine, we might still use a heading like "Requirements" and include both mandatory and nice-to-have? But nice-to-have is separate.
We have "What Would Be Nice To Have": list of nice-to-have items. That could be under "Skills" or "Qualifications". Could treat as "Preferred Qualifications". But we have headings: Skills, Qualifications. Could put nice-to-have under "Skills". Or we could have a separate "Preferred Qualifications" but not in list. Better to put under "Skills" as bullet list.
- Pay: we have salary range. So we need a Pay section with that info.
- Benefits: we have "What We Offer" list of benefits. So Benefits section.
- Schedule: not mentioned besides travel up to 10% and ability to support on-site and hybrid projects. No explicit schedule (full-time, part-time). So we should not create Schedule section.
- Travel: could be included in About the role or Responsibilities? Not needed as separate heading.
Thus sections: About the role (intro paragraph), Responsibilities (bullet list of duties), Requirements (bullet list of mandatory qualifications), Skills (bullet list of nice-to-have), Pay (salary range), Benefits (bullet list of benefits). Possibly also "Qualifications" but we already have Requirements; we could rename Requirements to "Qualifications". But we need to follow instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. Let's include About the role, Responsibilities, Requirements, Skills, Pay, Benefits. That's six sections.
We must not repeat job title as heading. Good.
We must not include boilerplate EEO etc. So we will omit About Guidehouse section.
We must not include application instructions etc.
Now format: Use