Enterprise Data Architect (Mid) (5672) (TS/SCI) (Ft. Belvoir, VA)

We need to output HTML fragment with sections: h3 headings for sections present. Must not repeat job title. Must include only sections with real content. Must not include boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Key content: - Intro paragraph: "SMX is seeking an Enterprise Data Architect (Mid) to develop and maintain enterprise intelligence workflows and tools that directly support global intelligence missions for the U.S. Army. In this critical role, you will be responsible for refining and standardizing cross-domain data services to ensure seamless and secure intelligence sharing from the enterprise to the tactical edge. The ideal candidate is an exceptional communicator who can translate complex military requirements into technical solutions and effectively brief senior leaders on mission-critical capabilities. If you are a results-oriented professional with a passion for solving complex data challenges in a national security environment, we invite you to apply and help us assure mission outcomes." - Location: "This is a full-time onsite position in Ft. Belvoir, VA." - Essential Duties & Responsibilities: with subheadings: Intelligence Workflow & Application Management, Data Architecture, Standards, and Evaluation Support, Documentation & Operational Coordination. Under each, bullet points. - Required Skills, Experience & Education: includes clearance, degree/experience combos, hands-on experience, familiarity with military/IC structures, practical experience with Agile, ability to create documentation. - Professional Core Attributes: list of attributes. - Desired Skills/Experience: includes Specialized Experience bullet points, Relevant Certifications list. - Application Deadline: October 19, 2026 (but we should drop application instructions? The instruction says remove application instructions. Deadline might be considered application instruction? Probably we should drop it as it's part of application instructions. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So deadline is application instruction; remove. - Salary section: "The proposed salary for this position is:: $140,000 USD - $170,000 USD". Also earlier paragraph about compensation and benefits. We need to include Pay section only if posting actually states them. It does state salary range. Also benefits: "Some key components of our robust benefits include health insurance, paid leave, and retirement." Also earlier: "we offer a competitive mix of compensation, learning & development opportunities, and benefits." So we can include Benefits section with those details. Pay section with salary range. - Schedule: Not explicitly stated besides full-time onsite. Could we infer schedule? The posting says full-time onsite position. That's schedule info (full-time, onsite). Should we include Schedule section? The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. "Full-time onsite" is specific content. So we can include Schedule section with that. - However, we must not repeat job title as heading. So no h3 for "Enterprise Data Architect (Mid)". Good. - Must not put Job ID/requisition numbers as headings; none present. - Must not include duplicated lines. - Must not include boilerplate like "SMX is an Equal Opportunity employer..." etc. Remove that. - Also remove lines like "Selected applicant may be subject to a background investigation..." etc. That's boilerplate; remove. - Also remove "SMX does not sponsor a new applicant..." etc. - Also remove the paragraph about SMX vision etc? That's maybe boilerplate but could be considered substantive? It's generic marketing. Might be considered boilerplate; but not explicitly listed as to remove. However it's not specific to the role; it's company description. Might be considered boilerplate but not in list. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company vision paragraph is not those categories. Could keep but it's not essential. However we need to preserve ALL substantive information; not invent or summarize away detail. The vision paragraph is substantive? It's generic but still part of posting. I'd keep it as a

maybe under a generic "About SMX" but we don't have a heading for that. Could just include as a paragraph before sections. But we need to decide sections: we could have an introductory paragraph (the first paragraph) as

. Then maybe a paragraph about SMX vision as another

. But we might combine. Better to keep the initial descriptive paragraph (the first paragraph) as

. Then after that, we have location sentence: "This is a full-time onsite position in Ft. Belvoir, VA." Could be part of same paragraph or separate. We'll structure:

SMX is seeking an Enterprise Data Architect (Mid) to develop and maintain enterprise intelligence workflows and tools that directly support global intelligence missions for the U.S. Army. In this critical role, you will be responsible for refining and standardizing cross-domain data services to ensure seamless and secure intelligence sharing from the enterprise to the tactical edge. The ideal candidate is an exceptional communicator who can translate complex military requirements into technical solutions and effectively brief senior leaders on mission-critical capabilities. If you are a results-oriented professional with a passion for solving complex data challenges in a national security environment, we invite you to apply and help us assure mission outcomes.

This is a full-time onsite position in Ft. Belvoir, VA.

Then sections:

Essential Duties & Responsibilities

• Intelligence Workflow & Application Management
  • Assist in developing, testing, and maintaining intelligence data workflows and processing tools associated with fielded intelligence systems supporting global intelligence missions.
  • Support the refinement and implementation of mission workflows for data intake, processing, and dissemination of published intelligence reporting in accordance with established Intelligence Community (IC) standards.
  • Under the direction of senior technical leads, build and maintain low-code/no-code applications, with supplemental scripting or full-code components as required to streamline data delivery.
  • Provide technical assistance and operational training to CONUS and OCONUS users on newly deployed workflows, baseline tool sets, and updated process procedures.
• Data Architecture, Standards, and Evaluation Support
  • Support Army intelligence staff and senior architects in analyzing, documenting, and validating cross-domain services and data dissemination requirements for secure intelligence sharing.
  • Apply and adhere to plain-text and regular-expression (regex) filtering standards; support the maintenance of security and data-filtering restriction lists (e.g., dirty-word/clear-word lists) to enforce data handling and classification compliance.
  • Participate in test and evaluation (T&E) events for emerging data technologies, commercial tools, and system upgrades; collect performance metrics and draft structured technical findings for senior architect and government review.
  • Assist in mapping data pipelines, evaluating interface controls, and ensuring architectural alignment with overarching Army and DoD data governance frameworks.
• Documentation & Operational Coordination
  • Author and update technical documentation, system interface descriptions, and visual workflow diagrams detailing data lifecycles, pipeline dependencies, and operational data flows.
  • Draft and maintain Standard Operating Procedures (SOPs), user manuals, and technical runbooks to ensure standard execution across production workflows.
  • Prepare briefing slides, technical summaries, and capability overviews for presentation to operational stakeholders and project leadership.
  • Coordinate operational support tasks, including tracking project action items, coordinating technical exchange meetings (TEMs), organizational scheduling, senior leader travel, mission related event coordination, and end-to-end task assignment, tracking, and completion, and facilitating mission-related stakeholder engagements.

But note: The original had repeated line "Coordinate operational support tasks..." appears twice; we should deduplicate. Now Required Skills, Experience & Education: We need to present as list maybe.

Required Skills, Experience & Education

• Active Top Secret (TS) security clearance with eligibility for SCI and NATO read-on before starting work.
• A master’s degree and a minimum of 1 year of relevant experience or a bachelor’s degree and a minimum of 3 years of relevant experience or an associate’s degree (or equivalent college credit) and a minimum of 5 years of relevant experience.
• Hands-on experience supporting technical data workflows, data architecture implementation, or intelligence systems integration.
• Familiarity with military or Intelligence Community organizational structures, operational environments, and planning processes.
• Practical experience working within Agile development methodologies, data engineering teams, or enterprise IT modernization initiatives.
• Demonstrated ability to create structured technical documentation, workflow diagrams, and standard operating procedures.

Professional Core Attributes:

Professional Core Attributes

• Strategic Thinking & Mission Alignment: Ability to connect organizational strategy to tactical execution; understand and articulate leadership intent
• Active Listening & Communication: Exceptional ability to communicate complex concepts to diverse audiences; translate between military operational language and IT technical terminology
• Problem Framing & Solution Development: Analytical mindset with ability to structure ambiguous problems and develop creative solutions
• Stakeholder Management: Build trust and maintain relationships across organizational boundaries; facilitate consensus among diverse stakeholder groups
• Execution and Results Orientation: Demonstrable record of delivering results in complex organizational environments; ability to move from planning to execution
• Risk-Centered Mindset: Proactive identification and management of risks; balance mission needs with security and compliance requirements

Desired Skills/Experience: We have Specialized Experience bullet points and Relevant Certifications. We could combine under Desired Skills/Experience heading.

Desired Skills/Experience

• Prior experience supporting Army, DoD, or IC data dissemination environments, intelligence data flows, or cross-domain solutions.
• Ability to meet requirements for a Privileged User (PU) account on TS/SCI systems (per DoD 8140.01 / 8570 baselines) upon or shortly after hire.
• Exposure to cloud computing environments (AWS, Azure, or GovCloud/C2S) and familiarity with containerized data pipelines or cloud-hosted analytics.
• Foundational exposure to data engineering pipelines, artificial intelligence/machine learning (AI/ML) integration, or Zero Trust architectural principles.
• Familiarity with process maturity models (e.g., CMMI) or continuous process improvement frameworks.

Relevant Certifications

• Certified CompTIA Cloud + Practitioner
• Certified CompTIA Security + Practitioner
• Digital Intelligence Master Gunner Course and/or Master Intelligence Data Strategies Course

Pay section:

Pay

$140,000 USD - $170,000 USD

Benefits section:

Benefits

Health insurance, paid leave, retirement.

Schedule section:

Schedule

Full-time onsite position in Ft. Belvoir, VA.

But we already have location sentence earlier; we could keep schedule separate. We must not duplicate location. We have location in schedule; we could remove the earlier location paragraph. Let's keep schedule section only. Thus we will have introductory paragraph(s) about role, then schedule section. We need to ensure we don't include boilerplate like "At SMX, one of our Core Values is to Invest in Our People..." etc. That's generic benefits description; we already captured benefits. The paragraph about competitive mix etc is also generic; we could keep as part of benefits? But it's not specific. Might be considered boilerplate. Safer to omit. We also need to omit the paragraph about