Data Analyst (Journeyman)
. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove Job ID, Job Code, Location maybe? They said do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include location etc in a short paragraph maybe under About the role? But they said do NOT repeat the job title as a heading (the page already shows it). So we can include a short paragraph with location, reports to, etc. But we need to preserve all substantive information. The location, reports to, FLSA status, supervisory, prepared date maybe minor metadata; we can fold into a short
after the position summary? Probably better to include a
with that info.
We must not include sections like "About the role" if we have position summary; we can use that as heading. The position summary is a paragraph; we can put under
About the role
then ... (the position summary text). Then Responsibilities
Responsibilities
then with each duty as - . Requirements
Requirements
then with each bullet (education, experience, etc). Benefits Benefits
then with each benefit.
We must not include headings for sections that have only placeholder/filler. Benefits we have concrete list, so include.
We need to ensure we don't include duplicated lines. Also remove legal disclaimer, EEO statement, etc.
Let's extract content.
Position Summary: "Extracts, validates, analyzes, and consolidates facilities, financial, project, engineering, and execution data to support MCICOM portfolio management. Produces reliable data products, dashboards, reports, and decision-support analyses for enterprise planning and execution. At MCB Quantico, this position provides data analysis and reporting support for MCINCR Regional Support under PWS Task 4.7, with primary responsibility for analytical support to Program Management & Data Analytics under Task 4.7.1. Cherokee Strategic Solutions (CSS) performs assigned services as a subcontractor to Current Technologies Corporation (CTC). The Data Analyst supports the Program Manager with validated data for the local Integrated Master Schedule (IMS) and Monthly Status Reports (MSRs); other analytical assignments remain within the assigned Quantico subcontract scope. This position requires an active Secret clearance."
We could also include location etc separately but it's okay to include in summary? Might be duplication. Better to have a short paragraph for metadata: "Marine Corps Base Quantico, VA (On-site). Reports to: Program Manager. FLSA Status: Exempt. Supervisory: No supervisory/management authority. Prepared Date: 9/25/2026." This is minor metadata; we can put in a after the summary or before. The instruction: "fold minor metadata into a short
or drop it." So we can create a
with that.
Now Responsibilities: list each duty from "Essential Functions, Duties & Responsibilities:" bullet points. Let's extract them:
- Extract and consolidate data from Government systems of record, regional submissions, project schedules, facilities databases, and financial-execution sources.
- Validate data for completeness, accuracy, consistency, timeliness, and alignment with established business rules.
- Identify data discrepancies, outdated records, missing fields, duplications, and conflicting project or funding information.
- Develop and maintain data models, trackers, dashboards, reports, and analytical tools that provide visibility into portfolio health and execution.
- Analyze trends related to project schedules, funding, obligations, expenditures, milestones, risks, and performance measures.
- Prepare clear data visualizations, summary products, and briefing materials for Government decision-makers.
- Document data sources, transformation methods, assumptions, validation results, and corrective actions to maintain auditability and traceability.
- Collect, validate, and reconcile Quantico project milestones, schedule progress, and execution data to support continuous weekly maintenance of the local IMS under the Program Manager’s direction.
- Identify missing or inconsistent inputs and coordinate corrections with the responsible personnel. (PWS 4.7.1)
- Prepare consolidated data, trend analyses, charts, and narrative inputs for 12 Quantico MSRs annually to provide comprehensive program visibility to Government leadership.
- Support CSS and CTC review and submission by the 15th day of each month. This reporting cadence applies to the Quantico team’s deliverable. (PWS 4.7.1; Section 8, DEL-02)
- When assigned, compile and validate historical cost data and market research reports to support the Government’s development of Independent Government Cost Estimates (IGCEs).
- Maintain source references and assumptions for review. The task’s ceiling of up to 120 IGCEs per consecutive 12-month period applies to the contractor team. (Support to PWS 4.7.4.2; DEL-20)
- When assigned, analyze third-party facility support service provider execution metrics and technical compliance data, maintain equipment warranty tracking data, and provide analytical inputs for draft service contract compliance evaluations and Preventive Maintenance work plans. (Support to PWS 4.7.5–4.7.5.2; DEL-23)
- Provide advisory analytical products through CSS and CTC for Government review. Acquisition-support products do not authorize signing contracts, obligating funds, or negotiating with vendors. Compliance evaluations are strictly advisory to the COR and do not authorize direct supervision, oversight, or contractual direction of third-party contractor personnel.
- Comply with applicable organizational conflict of interest restrictions. (PWS 4.7.4, 4.7.5.2, and Section 15)
- Protect Government data, working files, schedules, and analytical deliverables as required by the contract, including applicable Controlled Unclassified Information (CUI) handling requirements, and maintain documented sources and methods for review and transition. (PWS Sections 11–14)
- Perform other job-related duties as assigned.
We need to keep all substantive info; we can keep the parenthetical references as part of the li.
Now Requirements: Education, Experience, Knowledge, Skills and Abilities Required: (Basic Qualifications)
List:
- Bachelor’s degree in data analytics, business analytics, information systems, finance, statistics, engineering, or a related field.
- At least 5 years of experience in data analysis, data management, financial analysis, portfolio analysis, or performance reporting.
- Demonstrated experience extracting, cleansing, validating, and reconciling data from multiple systems or sources.
- Advanced proficiency in Microsoft Excel, including formulas, pivot tables, charts, data validation, and reporting tools.
- Experience developing dashboards, reports, data visualizations, or management-information products.
- Strong analytical skills and attention to detail, with the ability to identify and resolve complex data discrepancies.
- Ability to obtain and maintain Government access, suitability, and any contract-required credentials; ability to handle CUI in accordance with applicable requirements.
- Must possess and maintain a Secret security clearance in accordance with PWS 11.1, which requires the clearance at proposal submission and maintenance of the required security level throughout contract performance.
- Must be eligible to receive and maintain a Common Access Card (CAC) and execute the required nondisclosure agreement before commencing work or accessing Government information, facilities, systems, or data. (PWS Sections 11–13)
- Prolonged periods of sitting at a desk and working on a computer; may occasionally require standing or moving about the office for extended periods.
- Must pass pre-employment qualifications of Cherokee Federal.
Preferred Qualifications (we can include as part of Requirements maybe as a sublist? The instruction: Use
- for any list of duties/requirements/benefits. So we can include both basic and preferred as separate lists? Could combine but better to separate with headings? But we only have one heading "Requirements". Could include two sub-lists: Basic Qualifications and Preferred Qualifications. But we need to keep structure simple; maybe we can include all as one list, but we risk mixing basic and preferred. However we can include a note: "Preferred Qualifications:" as a inside a
- ? That might be okay. But better to keep as separate
under same heading? The instruction says use - for any list of duties/requirements/benefits. It doesn't forbid multiple lists under same heading. We'll do:
Requirements
Basic Qualifications
maybe but they said use for section headings only. So we cannot use . We could just have a
with "Basic Qualifications:" then a
. Or we could incorporate basic and preferred as separate with a preceding . That's acceptable.
We'll do:
Requirements
Basic Qualifications:
...
Preferred Qualifications:
...
Now Benefits: list from "Benefits That Set Us Apart" highlights:
- Up to a 6% 401(k) company match to help you build long-term financial security
- Paid time off as part of our comprehensive benefits package, so you have the flexibility to rest, recharge, and enjoy what matters most
- Medical, dental, and vision insurance, plus prescription drug coverage
- Basic life and AD&D insurance, with supplemental life options
- Short-term and long-term disability coverage
- Paid holidays
- Employee Assistance Program (EAP)
- Flexible Spending Account (FSA) and Health Savings Account (HSA) options
- Professional development, training, and certification support
- Voluntary benefits including accident, critical illness, and identity theft protection
We should keep the sentences as is.
Now we need to output only HTML fragment, no /, no markdown.
Let's craft.
First, a short paragraph for metadata: maybe after the position summary? We'll do:
About the role
Extracts, validates, analyzes, and consolidates facilities, financial, project, engineering, and execution data to support MCICOM portfolio management. Produces reliable data products, dashboards, reports, and decision-support analyses for enterprise planning and execution. At MCB Quantico, this position provides data analysis and reporting support for MCINCR Regional Support under PWS Task 4.7, with primary responsibility for analytical support to Program Management & Data Analytics under Task 4.7.1. Cherokee Strategic Solutions (CSS) performs assigned services as a subcontractor to Current Technologies Corporation (CTC). The Data Analyst supports the Program Manager with validated data for the local Integrated Master Schedule (IMS) and Monthly Status Reports (MSRs); other analytical assignments remain within the assigned Quantico subcontract scope. This position requires an active Secret clearance.
Location: Marine Corps Base Quantico, VA (On-site). Reports to: Program Manager. FLSA Status: Exempt. Supervis
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove Job ID, Job Code, Location maybe? They said do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include location etc in a short paragraph maybe under About the role? But they said do NOT repeat the job title as a heading (the page already shows it). So we can include a short paragraph with location, reports to, etc. But we need to preserve all substantive information. The location, reports to, FLSA status, supervisory, prepared date maybe minor metadata; we can fold into a short
after the position summary? Probably better to include a
with that info. We must not include sections like "About the role" if we have position summary; we can use that as heading. The position summary is a paragraph; we can put under
About the role
then... (the position summary text). Then Responsibilities
Responsibilities
then- with each duty as
- . Requirements
Requirements
then- with each bullet (education, experience, etc). Benefits
- for any list of duties/requirements/benefits. So we can include both basic and preferred as separate lists? Could combine but better to separate with headings? But we only have one heading "Requirements". Could include two sub-lists: Basic Qualifications and Preferred Qualifications. But we need to keep structure simple; maybe we can include all as one list, but we risk mixing basic and preferred. However we can include a note: "Preferred Qualifications:" as a inside a
- ? That might be okay. But better to keep as separate
- under same heading? The instruction says use
- for any list of duties/requirements/benefits. It doesn't forbid multiple lists under same heading. We'll do:
Requirements
Basic Qualifications
maybe but they said usefor section headings only. So we cannot use
. We could just have a
with "Basic Qualifications:" then a
- . Or we could incorporate basic and preferred as separate
- with a preceding
. That's acceptable. We'll do:
Requirements
Basic Qualifications:
- ...
Preferred Qualifications:
- ...
About the role
Extracts, validates, analyzes, and consolidates facilities, financial, project, engineering, and execution data to support MCICOM portfolio management. Produces reliable data products, dashboards, reports, and decision-support analyses for enterprise planning and execution. At MCB Quantico, this position provides data analysis and reporting support for MCINCR Regional Support under PWS Task 4.7, with primary responsibility for analytical support to Program Management & Data Analytics under Task 4.7.1. Cherokee Strategic Solutions (CSS) performs assigned services as a subcontractor to Current Technologies Corporation (CTC). The Data Analyst supports the Program Manager with validated data for the local Integrated Master Schedule (IMS) and Monthly Status Reports (MSRs); other analytical assignments remain within the assigned Quantico subcontract scope. This position requires an active Secret clearance.
Location: Marine Corps Base Quantico, VA (On-site). Reports to: Program Manager. FLSA Status: Exempt. Supervis
- ? That might be okay. But better to keep as separate
Benefits
then- with each benefit.
We must not include headings for sections that have only placeholder/filler. Benefits we have concrete list, so include.
We need to ensure we don't include duplicated lines. Also remove legal disclaimer, EEO statement, etc.
Let's extract content.
Position Summary: "Extracts, validates, analyzes, and consolidates facilities, financial, project, engineering, and execution data to support MCICOM portfolio management. Produces reliable data products, dashboards, reports, and decision-support analyses for enterprise planning and execution. At MCB Quantico, this position provides data analysis and reporting support for MCINCR Regional Support under PWS Task 4.7, with primary responsibility for analytical support to Program Management & Data Analytics under Task 4.7.1. Cherokee Strategic Solutions (CSS) performs assigned services as a subcontractor to Current Technologies Corporation (CTC). The Data Analyst supports the Program Manager with validated data for the local Integrated Master Schedule (IMS) and Monthly Status Reports (MSRs); other analytical assignments remain within the assigned Quantico subcontract scope. This position requires an active Secret clearance."
We could also include location etc separately but it's okay to include in summary? Might be duplication. Better to have a short paragraph for metadata: "Marine Corps Base Quantico, VA (On-site). Reports to: Program Manager. FLSA Status: Exempt. Supervisory: No supervisory/management authority. Prepared Date: 9/25/2026." This is minor metadata; we can put in a
after the summary or before. The instruction: "fold minor metadata into a short
or drop it." So we can create a
with that. Now Responsibilities: list each duty from "Essential Functions, Duties & Responsibilities:" bullet points. Let's extract them: - Extract and consolidate data from Government systems of record, regional submissions, project schedules, facilities databases, and financial-execution sources. - Validate data for completeness, accuracy, consistency, timeliness, and alignment with established business rules. - Identify data discrepancies, outdated records, missing fields, duplications, and conflicting project or funding information. - Develop and maintain data models, trackers, dashboards, reports, and analytical tools that provide visibility into portfolio health and execution. - Analyze trends related to project schedules, funding, obligations, expenditures, milestones, risks, and performance measures. - Prepare clear data visualizations, summary products, and briefing materials for Government decision-makers. - Document data sources, transformation methods, assumptions, validation results, and corrective actions to maintain auditability and traceability. - Collect, validate, and reconcile Quantico project milestones, schedule progress, and execution data to support continuous weekly maintenance of the local IMS under the Program Manager’s direction. - Identify missing or inconsistent inputs and coordinate corrections with the responsible personnel. (PWS 4.7.1) - Prepare consolidated data, trend analyses, charts, and narrative inputs for 12 Quantico MSRs annually to provide comprehensive program visibility to Government leadership. - Support CSS and CTC review and submission by the 15th day of each month. This reporting cadence applies to the Quantico team’s deliverable. (PWS 4.7.1; Section 8, DEL-02) - When assigned, compile and validate historical cost data and market research reports to support the Government’s development of Independent Government Cost Estimates (IGCEs). - Maintain source references and assumptions for review. The task’s ceiling of up to 120 IGCEs per consecutive 12-month period applies to the contractor team. (Support to PWS 4.7.4.2; DEL-20) - When assigned, analyze third-party facility support service provider execution metrics and technical compliance data, maintain equipment warranty tracking data, and provide analytical inputs for draft service contract compliance evaluations and Preventive Maintenance work plans. (Support to PWS 4.7.5–4.7.5.2; DEL-23) - Provide advisory analytical products through CSS and CTC for Government review. Acquisition-support products do not authorize signing contracts, obligating funds, or negotiating with vendors. Compliance evaluations are strictly advisory to the COR and do not authorize direct supervision, oversight, or contractual direction of third-party contractor personnel. - Comply with applicable organizational conflict of interest restrictions. (PWS 4.7.4, 4.7.5.2, and Section 15) - Protect Government data, working files, schedules, and analytical deliverables as required by the contract, including applicable Controlled Unclassified Information (CUI) handling requirements, and maintain documented sources and methods for review and transition. (PWS Sections 11–14) - Perform other job-related duties as assigned. We need to keep all substantive info; we can keep the parenthetical references as part of the li. Now Requirements: Education, Experience, Knowledge, Skills and Abilities Required: (Basic Qualifications) List: - Bachelor’s degree in data analytics, business analytics, information systems, finance, statistics, engineering, or a related field. - At least 5 years of experience in data analysis, data management, financial analysis, portfolio analysis, or performance reporting. - Demonstrated experience extracting, cleansing, validating, and reconciling data from multiple systems or sources. - Advanced proficiency in Microsoft Excel, including formulas, pivot tables, charts, data validation, and reporting tools. - Experience developing dashboards, reports, data visualizations, or management-information products. - Strong analytical skills and attention to detail, with the ability to identify and resolve complex data discrepancies. - Ability to obtain and maintain Government access, suitability, and any contract-required credentials; ability to handle CUI in accordance with applicable requirements. - Must possess and maintain a Secret security clearance in accordance with PWS 11.1, which requires the clearance at proposal submission and maintenance of the required security level throughout contract performance. - Must be eligible to receive and maintain a Common Access Card (CAC) and execute the required nondisclosure agreement before commencing work or accessing Government information, facilities, systems, or data. (PWS Sections 11–13) - Prolonged periods of sitting at a desk and working on a computer; may occasionally require standing or moving about the office for extended periods. - Must pass pre-employment qualifications of Cherokee Federal. Preferred Qualifications (we can include as part of Requirements maybe as a sublist? The instruction: Use
- for any list of duties/requirements/benefits. So we can include both basic and preferred as separate lists? Could combine but better to separate with headings? But we only have one heading "Requirements". Could include two sub-lists: Basic Qualifications and Preferred Qualifications. But we need to keep structure simple; maybe we can include all as one list, but we risk mixing basic and preferred. However we can include a note: "Preferred Qualifications:" as a inside a