Senior Data Migration Consultant
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only sections that have real specific content. We must not repeat job title as heading. We must not put Job ID etc. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc.
We need to decide which sections to include. Likely we have:
- About the role: could be Position Summary (maybe also About Unison? but that's company description; maybe not needed). The instruction says "About the role" heading for section headings. So we can put Position Summary under About the role.
- Responsibilities: Key Responsibilities.
- Requirements: maybe Qualifications? Or Requirements could combine Qualifications, Preferred Experience, Technical Skills, Federal Delivery, Core Skills, Education, Clearance? But we need to follow instruction: Use headings as given; we can have multiple sections like Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content.
We have Compensation Range: $110K - $160K => Pay section.
We have no explicit Benefits or Schedule info (Work Location and Travel mentions travel expectations vary, but not specific schedule). There's "Work location, on-site requirements, and travel expectations vary by program." That's not a specific schedule; also "In-Person Interview Our hiring process requires an in-person meeting, typically the final interview. Travel and accommodations will be provided." That's not schedule. So we should not create Benefits or Schedule sections because they lack specific content.
We have Qualifications section: includes Preferred Experience, Technical Skills And Exposure, Federal Delivery and Data Environment, Core Skills And Abilities, Education and Certifications, Clearance. Could combine into Qualifications? Or we could have separate sections: Qualifications, Skills. The instruction list includes Qualifications and Skills as possible headings. So we could put Qualifications for education/experience/clearance, and Skills for technical skills.
But we must not create thin sections; we need substantive content.
Let's structure:
About the role
Position Summary text...
Responsibilities
- ... each responsibility
Qualifications
Education and Certifications, Clearance, etc? Actually Qualifications could include education, certifications, clearance, maybe also preferred experience? But we have a separate "Preferred Experience" block. Might be better to put Preferred Experience under Qualifications as part of qualifications. However we also have Technical Skills etc. Could put under Skills. Thus:
Qualifications
Bachelor's degree (BA or BS) in Computer Science, Information Systems, Software Engineering, or a related technical field, or equivalent professional experience. Relevant technical certifications in database, cloud, or integration platform technologies are a plus. Applicants may need to be the subject of a security investigation and may need to meet eligibility requirements for access to classified information, to include U.S. Citizenship.
Skills
- Advanced SQL skills and hands-on experience with relational databases
- ETL processes and tools such as Talend Data Services or comparable platforms
- Data profiling, cleansing, deduplication, and data quality analysis techniques
- Data mapping, transformation logic, and crosswalk development between source and target systems
- Oracle databases, PL/SQL, SQL Loader, or comparable bulk data load technologies
- Reconciliation methods, control totals, and validation reporting
- Legacy system data extraction, including flat files, exports, and direct database extraction
- Data modeling concepts and relational database structures
- Handling of sensitive data during conversion, including masking and protection of test and production data sets
- Familiarity with federal acquisition, contract, grants, and financial data structures and the systems that produce them
- Interfaces with federal financial, procurement, personnel, and reporting systems
- Handling of sensitive federal data, including personally identifiable information (PII) and controlled unclassified information (CUI)
- Federal security and compliance requirements, including FISMA, authority to operate (ATO), and Section 508 accessibility
- Working with government technical points of contact, information system security officers, and system owners
- Strong analytical and problem-solving skills, including with ambiguous or poorly documented systems and data
- Ability to explain technical decisions, risks, and tradeoffs clearly to non-technical client stakeholders and program leadership
- Sound technical judgment under delivery pressure, balancing speed against maintainability
- Ability to manage multiple priorities and workstreams in a collaborative, client-facing environment
- Ability to adapt quickly to new technologies and evolving client requirements
under Qualifications summarizing preferred experience. We must preserve all substantive info; we should not lose any. So we need to include that Preferred Experience block as text. Thus Qualifications section could contain multiple paragraphs: education, certifications, clearance, preferred experience. We also have "Work Location and Travel" and "In-Person Interview" but those are not Benefits/Pay/Schedule; we could drop them as they are not requested headings. The instruction says remove boilerplate etc. Those are not boilerplate but they are not requested sections; we could either drop them or include them under maybe a generic section? But we should only output sections from the list; we can omit other info if not fitting headings. However we must preserve ALL substantive information; we cannot drop info just because no heading matches? The instruction: "Prefer a few substantive sections over many thin ones." It also says "include a section ONLY when the posting has real, specific content for it". It does not say we must include all info; but earlier: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep all substantive info somewhere. If we omit a heading, we could still include the info under a relevant heading (like Qualifications or Skills). For Work Location and Travel, we could maybe put under a "Schedule" heading? But schedule is about work hours, not location. There's no heading for location. Could we put under "About the role"? Might be okay to add a paragraph about work location and travel under About the role? But that might mix. Alternatively, we could create a "Schedule" section if we have info about work location/travel expectations? The posting says: "Work location, on-site requirements, and travel expectations vary by program." That's vague; not specific. Also "In-Person Interview Our hiring process requires an in-person meeting, typically the final interview. Travel and accommodations will be provided." That's about interview process, not schedule. Since we should not create Schedule section unless posting actually states them (like specific schedule). It does not state specific schedule, so we should not create Schedule section. However we still need to preserve that info. Where to put? Could incorporate into About the role as a note? Might be acceptable. Similarly, "Why Join Unison" is marketing; could be omitted as boilerplate? It's not boilerplate but it's promotional; maybe we can drop as not required? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Join Unison" is not those; it's more like company selling. Might be considered promotional but not required. However we need to preserve ALL substantive information; that includes why join? It's substantive but maybe not required for job posting? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. Where to put? Could be under About the role as a paragraph? Or maybe under Benefits? But we don't have benefits specifics. Could create a Benefits section if we have content: "Why Join Unison" includes culture, values, mission, etc. That could be considered benefits? Not exactly compensation/benefits but more about company. The instruction list includes Benefits as a possible heading. We could put that under Benefits. However we must not create a Benefits section unless posting actually states them. It does state reasons to join, which could be considered benefits. So we could create Benefits section with that content. Similarly, "Compensation Range" => Pay. Thus we can have sections: About the role (Position Summary), Responsibilities, Qualifications, Skills, Benefits (Why Join Unison), Pay (Compensation Range). Possibly also Schedule? Not needed. We need to ensure we don't create thin sections with filler like "commensurate with experience". We have specific content. Now we need to format. Let's extract the exact text for each. About Unison paragraph: "Unison’s products power the business of government to work smoother and smarter, making critical federal processes and acquisitions simpler and more effective. Trusted by over 200,000 federal employees and government contractors, our AI-infused software and deep domain expertise help contract shops, cost engineers, 1102s, program managers, and budgeting professionals cut through friction, keep compliance airtight, and sharpen decisions. Our federal focus brings efficiency, transparency, and clarity to complex data, regulations, and workflows, empowering agencies and executives to spend more minutes on mission and achieve strategic objectives. Unison is how federal business gets done. Unison is proud to be recognized as a 2026 Quantum Certified Workplace™ in Washington D.C., reflecting our continued focus on building a workplace where people feel supported and teams thrive." Position Summary: "Unison Software is seeking a Senior Data Migration Consultant to serve as the senior technical authority for data conversion across federal programs, owning the migration strategy that moves legacy data into Unison's acquisition, grants management, and contract lifecycle solutions. This is a hands-on senior delivery role. Senior Data Migration Consultants own the conversion approach across all source systems on a program, set data quality and reconciliation standards, serve as the escalation point for the most difficult conversion problems, and provide direction, review, and mentorship to other technical consultants while personally delivering the most complex conversions. Program assignment, data volume and complexity, and team size scale with the engagement and are defined in the specific job posting." We could combine About Unison and Position Summary under About the role. But About the role likely should focus on the role, not company. However we can include both; it's still substantive. Responsibilities list: need to extract each bullet from "Key Responsibilities". The text: "Own the data migration strategy and architecture across the program, including source system inventory, conversion sequencing, target data architecture, and cutover approach Establish and enforce standards for data mapping, transformation logic, cleansing rules, reconciliation, and conversion documentation Provide technical direction to other technical consultants, including task assignment, design guidance, and review of their work products Conduct design and code