Data Mapping and Schema Analyst

We need to output only HTML fragment, no /. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. The posting includes: Location, Onsite Flexibility, Contract Details (Position Type, Contract Duration, Pay Rate, Shift/Schedule, Work Authorization). Job Summary (description). Key Responsibilities (list). Required Skills (list). Preferred Skills (list). Required Experience (list). Nice-to-Have Experience (list). Education Requirements (list). Benefits (Medical, Vision, Dental Insurance Plans, 401k Retirement Fund). About The Client (description). About GTT (description). Job Number etc (metadata). We need to not repeat job title as heading. We need to not put Job ID as heading; fold minor metadata into short

or drop it. Remove boilerplate: cookie/navigation/legal/EEO etc not present. Remove duplicated lines (Key Responsibilities repeated? Actually they appear both in Job Summary and Key Responsibilities; we need to preserve all substantive info but not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep content but we can avoid repeating identical sentences? The job summary and key responsibilities have overlapping sentences; they are essentially same content but maybe we should keep both? The instruction says remove duplicated lines. So we should deduplicate. We'll need to produce sections: About the role (maybe from Job Summary). Responsibilities (list). Requirements (maybe combine Required Skills, Required Experience, Education). Qualifications maybe not separate; but we could have Skills section (Required Skills + Preferred Skills). Benefits section (Benefits). Pay section (Pay Rate). Schedule section (Shift/Schedule). Also maybe Location and Contract details could be folded into a short

under About the role or separate? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include location, contract details, pay rate, schedule as separate sections if they have specific content. Pay and Schedule we must only include if posting actually states them; they do. So we will have Pay and Schedule sections. Benefits we have. Location maybe not a heading; we could include in a short

under About the role or separate? There's no heading for Location; we could just include a

with location and contract details. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings. We need to decide which sections to include. Likely: About the role (Job Summary). Responsibilities (Key Responsibilities). Requirements (maybe combine Required Experience and Education). Skills (Required Skills + Preferred Skills). Benefits. Pay. Schedule. Possibly Qualifications not needed if covered elsewhere. We'll not create empty sections. We need to format lists with

• . For prose use

  . Ensure we preserve all substantive info. Let's extract content. Job Summary: "Performs detailed analysis of inspection and correction data across multiple source systems, databases, and applications to understand how data is structured, stored, maintained, and used by the business. Researches source databases and system tables to identify table names, field names, relationships, data types, key values, and data dependencies needed to support data conversion and migration work. Creates clear source-to-target data mappings that align legacy inspection and correction data to the new data model, schema, and ingestion requirements for a modernized database environment. Works closely with business stakeholders, application teams, database administrators, data engineers, and project teams to validate data definitions, resolve mapping questions, and ensure data meaning is preserved during conversion. Identifies data gaps, inconsistencies, duplicates, and quality issues that could impact successful ingestion into the new database, and documents recommended remediation steps. Translates business rules and operational inspection/correction processes into technical data requirements, including mapping logic, transformation rules, and validation criteria. Develops and maintains detailed documentation, including data dictionaries, table inventories, mapping workbooks, schema alignment notes, conversion assumptions, and open data issues. Supports data conversion planning, mock loads, validation activities, and issue resolution to help ensure inspection and correction data is accurately prepared for ingestion into the new database. Works independently with strong attention to detail and follows through on complex data research assignments with minimal guidance. Acts as a knowledgeable resource for project team members by explaining source-system data structures, data lineage, table relationships, and conversion impacts." Key Responsibilities list repeats same sentences but each as bullet? Actually they are sentences separated by periods but not bullet. We'll treat as list items. We need to deduplicate: The content is essentially same as job summary. To avoid duplication, we could keep only one set. Since instruction says remove duplicated lines, we should not repeat same sentences. So we will keep either Job Summary or Responsibilities, not both. Which section heading? We have both About the role and Responsibilities. We could put the summary in About the role (prose) and responsibilities as list items (maybe shortened). But they are same content; we could keep responsibilities as list items derived from the sentences, and About the role could be a brief overview? But we need to preserve all substantive info; if we only keep responsibilities list, we still have all info. About the role could be short paragraph summarizing role (maybe from first sentence). But that would be duplicative. Safer: Keep About the role as a brief paragraph (maybe first sentence) and Responsibilities as list of duties (the rest). However that may lose some info. Better: Keep About the role as a short paragraph describing the role (maybe from Job Summary first sentence) and Responsibilities as detailed list (the rest). That preserves all info without duplication. Let's extract first sentence for About the role: "Performs detailed analysis of inspection and correction data across multiple source systems, databases, and applications to understand how data is structured, stored, maintained, and used by the business." Then responsibilities list: each subsequent sentence from Job Summary after first? Actually the Job Summary includes many sentences; we can split them into list items. List items: - Researches source databases and system tables to identify table names, field names, relationships, data types, key values, and data dependencies needed to support data conversion and migration work. - Creates clear source-to-target data mappings that align legacy inspection and correction data to the new data model, schema, and ingestion requirements for a modernized database environment. - Works closely with business stakeholders, application teams, database administrators, data engineers, and project teams to validate data definitions, resolve mapping questions, and ensure data meaning is preserved during conversion. - Identifies data gaps, inconsistencies, duplicates, and quality issues that could impact successful ingestion into the new database, and documents recommended remediation steps. - Translates business rules and operational inspection/correction processes into technical data requirements, including mapping logic, transformation rules, and validation criteria. - Develops and maintains detailed documentation, including data dictionaries, table inventories, mapping workbooks, schema alignment notes, conversion assumptions, and open data issues. - Supports data conversion planning, mock loads, validation activities, and issue resolution to help ensure inspection and correction data is accurately prepared for ingestion into the new database. - Works independently with strong attention to detail and follows through on complex data research assignments with minimal guidance. - Acts as a knowledgeable resource for project team members by explaining source-system data structures, data lineage, table relationships, and conversion impacts. That covers all. Now Requirements section: Could include Required Experience and Education Requirements. We'll combine. Required Experience bullet points: - Typically five or more years of experience working with databases, data analysis, data mapping, data conversion, schema analysis, or application data support. - Experience analyzing relational databases and writing SQL queries to research tables, fields, joins, dependencies, and data quality issues. - Experience creating source-to-target mapping documentation, data dictionaries, table inventories, or conversion specifications. - Experience working across multiple business systems or legacy applications to understand data lineage, operational processes, and system-of-record decisions. Education Requirements: - Bachelor's degree in computer science, information systems, data management, engineering, mathematics, business technology, or a related field, or equivalent experience. We could also include Nice-to-Have Experience but maybe under Skills or separate? The instruction: Prefer a few substantive sections over many thin ones. So we could include Skills section covering Required Skills, Preferred Skills, and Nice-to-Have Experience (maybe as part of Skills). But we also have Required Skills list. Let's create Skills section that includes Required Skills and Preferred Skills (and Nice-to-Have). We'll avoid duplication. Required Skills list: - Advanced attention to detail and ability to work accurately with complex data across multiple systems. - Advanced analytical thinking skills, including the ability to investigate data issues, identify patterns, trace data lineage, and draw clear conclusions from technical research. - Strong knowledge of relational database concepts, including tables, fields, keys, joins, data types, and schema relationships. - Strong SQL skills for querying, profiling, validating, and reconciling data from source systems. - Working knowledge of data modeling, schema design, data transformation, and data ingestion concepts. - Ability to create clear and complete source-to-target mapping documentation that can be used by data engineering, development, and testing teams. - Ability to understand business processes and translate operational rules into data requirements, mapping logic, and validation criteria. - Strong documentation skills, including the ability to maintain data dictionaries, mapping workbooks, table inventories, issue logs, and assumptions. - Strong collaboration skills and ability to work effectively with business users, database administrators, developers, data engineers, testers, and project stakeholders. - Strong communication skills, including the ability to explain technical data findings in a clear, practical way for both technical and nontechnical audiences. - Strong problem-solving skills and persistence in researching unclear, incomplete, or inconsistent data across legacy systems. - Ability to manage competing priorities, follow through on detailed assignments, and raise risks or blockers early. Preferred Skills list: - Experience with inspection, correction, asset management, work management, field operations, or utility data. - Experience with Microsoft SQL Server, Oracle, cloud databases, data integration tools, or reporting/query tools. - Experience with AWS Glue, cloud databases, data integration tools, or reporting/query tools. Nice-to-Have Experience (same as Preferred? Actually they repeat). We'll just include Preferred Skills; Nice-to-Have is duplicate. Now Benefits section: "Medical, Vision, and Dental Insurance Plans 401k Retirement Fund". We'll make list items. Pay section: "$60.00–$70.00 / Hour (USD)". We'll put in

  . Schedule section: "8 AM – 5 PM". Also maybe mention Onsite Flexibility: Hybrid — Monday and Friday remote; Tuesday–Thursday onsite. That's schedule detail. We'll include both. We also have Location: Portland, OR. Could include in a short

  under About the role or separate? Since we have no heading for location, we can add a

  after About the role maybe. Contract Details: Position Type: Contract, Contract Duration: 7 months. Could also be included in a short

  . We need to avoid putting Job ID as heading; we can drop it. Now construct HTML. We'll start with

  About the role

  then

  Location: Portland, OR. Position Type: Contract, Contract Duration: 7 months.

  then

  Performs detailed analysis of inspection and correction data across multiple source systems, databases, and applications to understand how data is structured, stored, maintained, and used by the business.

  Then

  Responsibilities

  with list items. Then

  Requirements

  with experience and education items. Then

  Skills

  with required skills and preferred skills maybe separate subheadings? But we cannot add extra headings beyond allowed? The instruction only says use

  for section headings (list). It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities