Senior Government Data Integration Architect / NIEM Architect

• Position Type: Part-Time Consultant / Technical Architecture Specialist
• Target Allocation: 18–22 hours/week average (Note: Workload is heavily concentrated around Deliverable 4, which requires the complex architectural reconciliation of data models across legacy systems including MFMP, FACTS, FLAIR, PALM, and the DFS Data Warehouse).
• Location: Remote (U.S. Based) with periodic travel to Tallahassee, FL as required.
• Technical Reality: Evaluators for this project can easily distinguish between ordinary corporate ETL experience and true standards-based government information exchange. Actual hands-on experience deploying standardized data-exchange models is mandatory.

• NIEM Compliance Ownership: Lead the structural strategy for NIEM compliance and compatibility, detailing exact plans for NIEM conformance levels, component reuse, domain extensibility, and constraint mitigation.
• Canonical Modeling: Define, build, and maintain the platform's canonical data model to standardize information formatting across all ingested state datasets.
• Cross-System Mapping: Develop a unified cross-system mapping and standardization framework to reconcile critical field differences, schema variations, timing misalignments, and data quality gaps across legacy source systems.
• Entity Resolution: Design and implement record-linkage models and identifier normalization logic to accurately track unique vendors and transactions across completely separate agency databases.
• Source Coordination: Act as the primary technical point of contact for source-system data owners across different state departments to resolve field clarifications, mapping guidance, and legacy database nuances.
• Documentation Delivery: Produce comprehensive data dictionaries, transformation documentation, source-to-canonical lineages, and highly detailed data-exchange specifications in open, editable formats.
• Onboarding Optimization: Map out and support the ingestion pipelines for core procurement modules, including invoices, purchase orders, contracts, vendor information portal ledgers, and downstream financial fields.
• Reusable Patterns: Build reusable, automated data-mapping templates to accelerate and standardize the onboarding workflows for the initial wave of 8–10 state agencies.

• Experience Baseline: 8+ years of comprehensive enterprise data integration, data warehousing, or data architecture experience.
• Government Depth: 3+ years of dedicated, hands-on data integration experience working inside a federal, state, or local government framework.
• NIEM Mastery: Documented, verifiable experience designing and executing NIEM-conformant or NIEM-compatible information exchanges.
• Domain Architecture: Advanced structural familiarity with NIEM domains, data components, exchange specifications, and extension rules.
• Mapping Expertise: Extensive background executing complex source-to-target mapping, data profiling, metadata logging, and data-lineage cataloging.
• Exchange Protocols: Proven experience managing both structured and semi-structured data-exchange formats, including JSON, XML, REST APIs, CSV flat files, database views, and automated batch/SFTP pathways.
• Data Quality Engineering: Strong track record establishing automated cross-system data reconciliation scripts and automated validation profiling rules.
• Vetting & Location: Must be a U.S.-based citizen or resident. Must be able to successfully clear an FDLE Level II background screening (including fingerprinting) within 5 business days of contract award.

• Direct experience integrating or mapping data from legacy state financial and procurement architectures.
• Working data domain familiarity regarding procurement workflows, contract activities, purchasing cards, state vendor payments, or grant management ledgers.
• Hands-on data engineering experience leveraging Azure Databricks workspaces and Azure Data Lake Storage Gen2 (ADLS Gen2).
• Deep technical specialization in master data management (MDM) or advanced programmatic entity resolution.
• Working knowledge of secure government interoperability models or federated identity standards beyond basic NIEM implementations.

1. The Government Customer: Explicitly name the agency and the specific interoperability framework utilized (e.g., Department of Justice, State Revenue Office).
2. The Specific NIEM Implementation: Detail exactly how you applied NIEM standards, naming the specific domains, extensions, or information exchange package documentation (IEPD) you personally engineered.
3. System Integration Complexity: Specify the exact systems you connected (e.g., legacy mainframe, REST APIs), data volumes, and precise project duration.
4. Personal Contribution: Detail exactly what you personally built or documented (e.g., "Authored source-to-canonical schema mappings for vendor payments," "Coded entity resolution scripts for transaction matching").
5. Deployment Status: Explicitly state the true production, operational, or steady-state status of the information exchange platform.
6. Quantifiable Results: Include the precise metrics achieved under your guidance, such as data completeness percentages, integration success rates, or volume of record-count variances eliminated.

“We are an equal opportunity employer and all qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, sexual orientation, gender identity, disability or protected veteran status”

Texting Privacy Policy

• Message type: Informational; you will receive text messages regarding your application and potentially regarding interview scheduling.
• No mobile information will be shared with third parties/affiliates for marketing/promotional purposes.
• Message frequency will vary depending on the application process.Msg & data rates may apply.
• OPT out at any time by texting "Stop".