FOIA Data Migration & Compliance Lead - Government
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive info.
We need to decide which sections to include based on content.
The posting includes: Overview (Job Overview) which is like About the role. Then Job Description and Requirements (which includes responsibilities). Then Minimum Qualifications, Preferred Qualifications, Required Skills. Also mentions compensation: salary range $134,000-$202,000. Also mentions eligibility for total compensation includes base salary, annual performance bonus, long-term incentives. That's Benefits/Pay. Also mentions remote/hybrid? The posting type says Remote/Hybrid Job Overview. So schedule maybe remote/hybrid. There's mention of Public Trust clearance, etc. That's qualifications/requirements.
We need sections: About the role (overview), Responsibilities (from Job Description), Requirements (minimum qualifications?), Qualifications (maybe preferred qualifications?), Skills (required skills), Pay (salary range and total comp), Benefits (maybe mention total comp includes bonus, LTI), Schedule (remote/hybrid). However we should avoid thin sections. We can combine some.
But rules: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID etc. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate.
Important: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them.
We have Pay info: salary range $134k-$202k, plus total comp includes base salary, annual performance bonus, long-term incentives. So we can have Pay section with that.
Benefits: maybe not explicit beyond total comp? The posting says "eligible for total compensation which includes a competitive base salary, an annual performance bonus, and long-term incentives." That's more compensation than benefits. Benefits could be omitted if not explicit. There's no mention of health, 401k, etc. So we should not create Benefits section unless there is real content. So we skip Benefits.
Schedule: posting type Remote/Hybrid Job Overview. So we have schedule info: remote/hybrid. So we can include Schedule section with that.
Now About the role: we have overview paragraph. We'll put that in
.
Responsibilities: from Job Description and Requirements bullet-like paragraphs. We'll extract duties: Lead end-to-end data migration projects, develop and execute migration plans, serve as primary technical point of contact, troubleshoot and resolve migration issues, technical implementation leadership (subject matter expert, product backlog driver, write user stories, acceptance criteria, functional specs, test and validate new utility features, document tool capabilities, configurations, migration best practices), government & FOIA customer enablement (apply deep knowledge of FOIA regulations, partner with TAM and CS, SME on government data handling, represent voice of government agency customers), documentation & continuous improvement (create and maintain technical documentation, migration runbooks, knowledge base, identify and report product defects, tool gaps, process inefficiencies, refine migration methodologies), FedRAMP & government data security context (maybe part of responsibilities). We'll put as
- .
Requirements: Minimum Qualifications bullet list. We'll put as
- .
Qualifications: Preferred Qualifications bullet list. We'll put as
- .
Skills: Required Skills list (Communication, Cybersecurity, Database Management, Government Regulation, Legal Research, Natural Language, Policy Analysis, Report Writing, Stakeholder Management, Strategic Planning). We'll put as
- .
Pay: salary range and total comp description. We'll put as
maybe with
for components? Could be prose.
Schedule: remote/hybrid. We'll put as .
We must not include any markdown fences. Just raw HTML.
Let's craft.
First, About the role: combine overview paragraphs.
Overview text: "Posting Type Remote/Hybrid Job Overview The FOIA Data Migration & Compliance Lead is a technically skilled, government-domain-experienced professional who serves as both a hands-on practitioner and technical lead for Relativity’s FOIA (Freedom of Information Act) Data Migration initiative. This role enables Relativity’s growing portfolio of federal, state, and local government customers to onboard, migrate, and manage their FOIA data within RelativityOne. This individual operates in a dual capacity: defining, documenting, and prioritizing Data Migration tooling requirements in close partnership with engineering, while engaging directly with FOIA agency customers to execute and support migration projects. Because this role handles government data under Relativity’s FedRAMP authorization, familiarity with FedRAMP significant-change processes, FIPS 140-3, and NIST frameworks are expected. Due to specific customer contract requirements, this position requires that the successful candidate be a U.S. citizen. As a condition of your role supporting the RelativityOne Government product, you are required to obtain a Public Trust clearance. The process for obtaining the Public Trust clearance will be handled by the federal government and could include additional background screening regarding criminal history, drug use, financial records, and a character assessment. If you are unable to obtain the Public Trust clearance, you will be unable to work on the RelativityOne Government product, and your employment, if still in effect, may be terminated."
We'll put that in
.
Now Responsibilities: we need to capture all duties from Job Description and Requirements.
Let's list:
- Lead end-to-end data migration projects for new FOIA customers and government agencies, ensuring data is migrated into RelativityOne accurately, securely, and efficiently.
- Develop and execute migration plans — including data mapping, validation, transformation logic, and cutover strategies — tailored to agency-specific requirements.
- Serve as the primary technical point of contact for FOIA agency customers across the migration lifecycle, from pre-migration planning through post-migration validation.
- Troubleshoot and resolve migration issues, data anomalies, and integration challenges in collaboration with engineering.
- Serve as the technical subject matter expert and product backlog driver for the Data Migration Utility.
- Maintain a near-term view of utility enhancement needs, balancing immediate customer delivery against longer-term platform scalability and communicating tradeoffs to engineering and product leadership.
- Write user stories, acceptance criteria, and functional specifications; test and validate new utility features, providing structured feedback and driving iteration.
- Document tool capabilities, configurations, and migration best practices.
- Apply deep knowledge of FOIA regulations, agency data management workflows, and public records requirements to deliver appropriately tailored migration guidance.
- Partner with the broader TAM and Customer Success teams to introduce new FOIA agency customers, establishing repeatable migration playbooks and success criteria.
- Serve as a subject matter expert on government data handling, including data sensitivity classifications, records retention policies, and agency-specific compliance considerations.
- Represent the voice of government agency customers internally, translating their operational realities into actionable product feedback.
- Create and maintain technical documentation, migration runbooks, and knowledge base content that support consistent, scalable migration delivery.
- Identify and report product defects, tool gaps, and process inefficiencies discovered during engagements.
- Continuously refine migration methodologies to improve accuracy, efficiency, and customer experience.
- All FOIA customer data handled in this role is classified DT1 (Data Type 1), the highest sensitivity tier under Relativity’s FedRAMP authorization. Direct access to DT1 data requires Public Trust clearance — a prerequisite for the role.
- The role requires working within pre-approved toolsets and Azure-native capabilities.
We'll put each as
- .
Now Requirements (Minimum Qualifications):
- Bachelor’s degree in computer science, Information Technology, Information Management, or a related field — or equivalent practical experience.
- Proven experience working directly with government agencies, public-sector organizations, or regulated-industry customers in a technical or consulting capacity.
- Demonstrated experience in data migration, data integration, or data engineering, including designing and executing migrations of structured and/or semi-structured data sets.
- Working knowledge of SQL and experience querying and transforming data.
- Hands-on experience with data formats, transformation tools, and scripting languages relevant to migration work (e.g., Python, PowerShell, JSON, XML, CSV processing).
- Strong written and verbal communication skills, with the ability to translate complex technical concepts for technical and non-technical government stakeholders.
- Experience in a product owner or technical lead capacity — capturing requirements, documenting specifications, and driving iterative delivery engineering.
- Ability to obtain and maintain a Public Trust designation as a condition of employment.
- Candidates who currently hold Public Trust or an active federal security clearance (Secret or above) are preferred.
Now Qualifications (Preferred Qualifications):
- Prior experience working with or within federal, state, or local government agencies — particularly in FOIA administration, records management, data governance, or public records compliance.
- Working knowledge of the Freedom of Information Act (5 U.S.C.552), including exemptions, agency request workflows, processing timelines, and high-volume request management.
- Familiarity with government data security frameworks including NIST SP 800-53, FedRAMP, FISMA, and CJIS Security Policy.
- Experience handling government-designated sensitive data categories — Controlled Unclassified Information (CUI), PII, Law Enforcement Sensitive (LES), or similar — per applicable handling requirements.
- Experience navigating government procurement, contracting, or Authority to Operate (ATO) processes.
- Experience building or supporting data migration solutions on extensible SaaS or cloud platforms, with exposure to REST APIs, cloud storage services, and modern integration patterns.
- Familiarity with FOIA-specific platforms (e.g., FOIAXpress, GovQA, Paladin) and how agency FOIA systems structure and export data.
- Familiarity with Relativity or RelativityOne, or Relativity certifications (RCA, Specialist, Expert, or platform-specific credentials).
Now Skills (Required Skills):
List: Communication, Cybersecurity, Database Management, Government Regulation, Legal Research, Natural Language, Policy Analysis, Report Writing, Stakeholder Management, Strategic Planning.
We'll put as
- .
Now Pay:
- The expected salary range for this role is between $134,000 and $202,000.
- The final offered salary will be based on several factors, including but not limited to the candidate's depth of experience, skill set, qualifications, and internal pay equity.
- Hiring at the top end of the range would not be typical, to allow for future meaningful salary growth in this position.
- This position is eligible for total compensation which includes a competitive base salary, an annual performance bonus, and long-term incentives.
We'll put as
maybe with
for components? Could be prose.
Now Schedule:
- Remote/Hybrid (as indicated in posting type).
We'll put as .
Now ensure we don't include any boilerplate like EEO etc. Already removed.
Now produce HTML fragment:
About the role
...overview...
Responsibilities
- ...
...
Requirements
...
Qualifications
...
Skills
...
Pay
...salary range and total comp...
Schedule
Remote/Hybrid
Check that we didn't create Benefits section (good). Ensure we didn't repeat job title. Good.
Now ensure we preserve all substantive info: we included overview, responsibilities, requirements, qualifications, skills, pay, schedule. Did we miss any? The posting
- for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID etc. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate. Important: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. We have Pay info: salary range $134k-$202k, plus total comp includes base salary, annual performance bonus, long-term incentives. So we can have Pay section with that. Benefits: maybe not explicit beyond total comp? The posting says "eligible for total compensation which includes a competitive base salary, an annual performance bonus, and long-term incentives." That's more compensation than benefits. Benefits could be omitted if not explicit. There's no mention of health, 401k, etc. So we should not create Benefits section unless there is real content. So we skip Benefits. Schedule: posting type Remote/Hybrid Job Overview. So we have schedule info: remote/hybrid. So we can include Schedule section with that. Now About the role: we have overview paragraph. We'll put that in
. Responsibilities: from Job Description and Requirements bullet-like paragraphs. We'll extract duties: Lead end-to-end data migration projects, develop and execute migration plans, serve as primary technical point of contact, troubleshoot and resolve migration issues, technical implementation leadership (subject matter expert, product backlog driver, write user stories, acceptance criteria, functional specs, test and validate new utility features, document tool capabilities, configurations, migration best practices), government & FOIA customer enablement (apply deep knowledge of FOIA regulations, partner with TAM and CS, SME on government data handling, represent voice of government agency customers), documentation & continuous improvement (create and maintain technical documentation, migration runbooks, knowledge base, identify and report product defects, tool gaps, process inefficiencies, refine migration methodologies), FedRAMP & government data security context (maybe part of responsibilities). We'll put as
- .
Requirements: Minimum Qualifications bullet list. We'll put as
- .
Qualifications: Preferred Qualifications bullet list. We'll put as
- .
Skills: Required Skills list (Communication, Cybersecurity, Database Management, Government Regulation, Legal Research, Natural Language, Policy Analysis, Report Writing, Stakeholder Management, Strategic Planning). We'll put as
- .
Pay: salary range and total comp description. We'll put as
maybe with
- for components? Could be prose.
Schedule: remote/hybrid. We'll put as
- . Now Requirements (Minimum Qualifications): - Bachelor’s degree in computer science, Information Technology, Information Management, or a related field — or equivalent practical experience. - Proven experience working directly with government agencies, public-sector organizations, or regulated-industry customers in a technical or consulting capacity. - Demonstrated experience in data migration, data integration, or data engineering, including designing and executing migrations of structured and/or semi-structured data sets. - Working knowledge of SQL and experience querying and transforming data. - Hands-on experience with data formats, transformation tools, and scripting languages relevant to migration work (e.g., Python, PowerShell, JSON, XML, CSV processing). - Strong written and verbal communication skills, with the ability to translate complex technical concepts for technical and non-technical government stakeholders. - Experience in a product owner or technical lead capacity — capturing requirements, documenting specifications, and driving iterative delivery engineering. - Ability to obtain and maintain a Public Trust designation as a condition of employment. - Candidates who currently hold Public Trust or an active federal security clearance (Secret or above) are preferred. Now Qualifications (Preferred Qualifications): - Prior experience working with or within federal, state, or local government agencies — particularly in FOIA administration, records management, data governance, or public records compliance. - Working knowledge of the Freedom of Information Act (5 U.S.C.552), including exemptions, agency request workflows, processing timelines, and high-volume request management. - Familiarity with government data security frameworks including NIST SP 800-53, FedRAMP, FISMA, and CJIS Security Policy. - Experience handling government-designated sensitive data categories — Controlled Unclassified Information (CUI), PII, Law Enforcement Sensitive (LES), or similar — per applicable handling requirements. - Experience navigating government procurement, contracting, or Authority to Operate (ATO) processes. - Experience building or supporting data migration solutions on extensible SaaS or cloud platforms, with exposure to REST APIs, cloud storage services, and modern integration patterns. - Familiarity with FOIA-specific platforms (e.g., FOIAXpress, GovQA, Paladin) and how agency FOIA systems structure and export data. - Familiarity with Relativity or RelativityOne, or Relativity certifications (RCA, Specialist, Expert, or platform-specific credentials). Now Skills (Required Skills): List: Communication, Cybersecurity, Database Management, Government Regulation, Legal Research, Natural Language, Policy Analysis, Report Writing, Stakeholder Management, Strategic Planning. We'll put as
- .
Now Pay:
- The expected salary range for this role is between $134,000 and $202,000.
- The final offered salary will be based on several factors, including but not limited to the candidate's depth of experience, skill set, qualifications, and internal pay equity.
- Hiring at the top end of the range would not be typical, to allow for future meaningful salary growth in this position.
- This position is eligible for total compensation which includes a competitive base salary, an annual performance bonus, and long-term incentives.
We'll put as
maybe with
- for components? Could be prose.
Now Schedule:
- Remote/Hybrid (as indicated in posting type).
We'll put as
- ... ...
. Now ensure we don't include any boilerplate like EEO etc. Already removed. Now produce HTML fragment:
About the role
...overview...
Responsibilities
Requirements
- ...
Qualifications
- ...
Skills
- ...
Pay
...salary range and total comp...
Schedule
Remote/Hybrid
Check that we didn't create Benefits section (good). Ensure we didn't repeat job title. Good. Now ensure we preserve all substantive info: we included overview, responsibilities, requirements, qualifications, skills, pay, schedule. Did we miss any? The posting
. We must not include any markdown fences. Just raw HTML. Let's craft. First, About the role: combine overview paragraphs. Overview text: "Posting Type Remote/Hybrid Job Overview The FOIA Data Migration & Compliance Lead is a technically skilled, government-domain-experienced professional who serves as both a hands-on practitioner and technical lead for Relativity’s FOIA (Freedom of Information Act) Data Migration initiative. This role enables Relativity’s growing portfolio of federal, state, and local government customers to onboard, migrate, and manage their FOIA data within RelativityOne. This individual operates in a dual capacity: defining, documenting, and prioritizing Data Migration tooling requirements in close partnership with engineering, while engaging directly with FOIA agency customers to execute and support migration projects. Because this role handles government data under Relativity’s FedRAMP authorization, familiarity with FedRAMP significant-change processes, FIPS 140-3, and NIST frameworks are expected. Due to specific customer contract requirements, this position requires that the successful candidate be a U.S. citizen. As a condition of your role supporting the RelativityOne Government product, you are required to obtain a Public Trust clearance. The process for obtaining the Public Trust clearance will be handled by the federal government and could include additional background screening regarding criminal history, drug use, financial records, and a character assessment. If you are unable to obtain the Public Trust clearance, you will be unable to work on the RelativityOne Government product, and your employment, if still in effect, may be terminated." We'll put that in
. Now Responsibilities: we need to capture all duties from Job Description and Requirements. Let's list: - Lead end-to-end data migration projects for new FOIA customers and government agencies, ensuring data is migrated into RelativityOne accurately, securely, and efficiently. - Develop and execute migration plans — including data mapping, validation, transformation logic, and cutover strategies — tailored to agency-specific requirements. - Serve as the primary technical point of contact for FOIA agency customers across the migration lifecycle, from pre-migration planning through post-migration validation. - Troubleshoot and resolve migration issues, data anomalies, and integration challenges in collaboration with engineering. - Serve as the technical subject matter expert and product backlog driver for the Data Migration Utility. - Maintain a near-term view of utility enhancement needs, balancing immediate customer delivery against longer-term platform scalability and communicating tradeoffs to engineering and product leadership. - Write user stories, acceptance criteria, and functional specifications; test and validate new utility features, providing structured feedback and driving iteration. - Document tool capabilities, configurations, and migration best practices. - Apply deep knowledge of FOIA regulations, agency data management workflows, and public records requirements to deliver appropriately tailored migration guidance. - Partner with the broader TAM and Customer Success teams to introduce new FOIA agency customers, establishing repeatable migration playbooks and success criteria. - Serve as a subject matter expert on government data handling, including data sensitivity classifications, records retention policies, and agency-specific compliance considerations. - Represent the voice of government agency customers internally, translating their operational realities into actionable product feedback. - Create and maintain technical documentation, migration runbooks, and knowledge base content that support consistent, scalable migration delivery. - Identify and report product defects, tool gaps, and process inefficiencies discovered during engagements. - Continuously refine migration methodologies to improve accuracy, efficiency, and customer experience. - All FOIA customer data handled in this role is classified DT1 (Data Type 1), the highest sensitivity tier under Relativity’s FedRAMP authorization. Direct access to DT1 data requires Public Trust clearance — a prerequisite for the role. - The role requires working within pre-approved toolsets and Azure-native capabilities. We'll put each as
- .
Pay: salary range and total comp description. We'll put as
- .
Skills: Required Skills list (Communication, Cybersecurity, Database Management, Government Regulation, Legal Research, Natural Language, Policy Analysis, Report Writing, Stakeholder Management, Strategic Planning). We'll put as
- .
Qualifications: Preferred Qualifications bullet list. We'll put as
- .
Requirements: Minimum Qualifications bullet list. We'll put as