Senior Data Analyst
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have overview and details. No explicit Benefits, Pay, Schedule given. So we should not include those sections. We need sections: About the role (overview), Responsibilities (Key Responsibilities), Requirements (maybe Required Qualifications?), Qualifications (maybe Preferred Qualifications?), Skills (maybe list of technical skills). But we must not repeat job title. We need to preserve all substantive info. We need to decide mapping: The posting includes Overview, Key Responsibilities, Required Qualifications, Preferred Qualifications. Also mentions hybrid, 3 days onsite, contract length, location. That could go under About the role.
We need to avoid filler like "commensurate with experience". Not present.
We need to use - for any list of duties/requirements/benefits. So for responsibilities list, we should create
- . For qualifications also list.
We need to use
for prose.
We must not include boilerplate like NOTE about candidates not meeting qualifications etc. That's a note but it's substantive? It says "NOTE: Candidates who don't meet the required qualifications for this role will NOT be considered at this time." That's a statement but maybe considered boilerplate? It's a note about consideration; could be kept? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This note is not exactly those, but it's a note about consideration. Might be considered part of posting but not essential? It's not duplicated. I'd keep it as a
maybe under Requirements? But it's more like a note. Could be included as a
after Required Qualifications.
We must not invent or summarize away detail. So we need to keep all specifics: VSAM experience, 1-year contract likely to extend, hybrid 3 days onsite Brooklyn, NY, Data Management team, data profiling, cleansing, conversion, migration, validation, field-level analysis, metadata analysis, source-to-target mapping VSAM to relational/dimensional SQL tables, data dictionary, business terms, valid values, definitions, work with SMEs, extract business rules from legacy code, data conversion migration, develop complex SQL validations, transform business rules into ETL and SQL specs, validate data, support processes detect/correct/prevent invalid data, support data integrity/quality initiatives, ETL using IBM DataStage, optimize ETL/SQL, write complex SQL queries/stored procedures, support SSRS report dev, work across IBM Mainframe, Windows Server, SQL Server, extract field references/calculated data from COBOL, analyze mainframe apps COBOL CICS DB2, support pension admin systems, collaborate with technical leads SMEs, identify data quality gaps, work with IT partners to remediate gaps, support defect handling, troubleshooting, root cause analysis, problem resolution, contribute to process improvement programs, recommend solutions, collaborate with data SMEs, technical leads, application teams, IT partners, identify opportunities to improve data quality, streamline validation, strengthen repeatable data management processes.
Required qualifications list: Minimum 5 years source-to-target data mapping experience in mixed mainframe/relational DB; experience creating data dictionary documentation with business terms, valid values, definitions; experience converting/migrating VSAM data to relational/dimensional SQL distributed DB; minimum 3 years recent experience developing applications using IBM DataStage ETL; experience extracting field references and calculated data from COBOL programs; experience with BMC Control-M; experience with Git; minimum 3 years recent experience with pension administration systems; strong SQL knowledge including complex queries and stored procedures; proficiency in SSRS report development; strong analytical skills with ability to receive/analyze requirements and propose suitable solutions aligned with team methodology; ability to work across IBM Mainframe, Windows Server, SQL Server; proficiency with mainframe applications COBOL, CICS, DB2; understanding of data structures and their relationship to ETL applications; ability to develop complex SQL data validations based on source-to-target mappings and target data models; excellent analytical, problem-solving, information-gathering, troubleshooting skills; experience supporting data profiling, cleansing, conversion, migration, validation; ability to collaborate effectively with data SMEs, technical leads, IT partners; ability to support defect handling and problem resolution.
Preferred qualifications: experience extracting business rules from existing legacy code; experience with data quality or data profiling tools; experience with data warehouses and data marts; experience with SQL Server Reporting Services (SSRS); prior experience working in a pension system environment; prior experience working with a New York State or New York City pension system; experience supporting enterprise-wide legacy replacement or modernization initiatives; experience improving data quality processes, validation standards, or ETL performance in complex data environments.
We need to decide sections: About the role (overview + contract/hybrid/location). Responsibilities (Key Responsibilities). Requirements (Required Qualifications). Qualifications (Preferred Qualifications). Skills maybe could be a separate section but we could incorporate skills into Requirements or Qualifications. But we need to follow instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with real content. We have content for About the role, Responsibilities, Requirements, Qualifications. Skills maybe we could extract a list of technical skills from the qualifications but that's overlapping. Could we create a Skills section summarizing technical skills? That would be summarizing, but we must not invent or summarize away detail. However we could list skills as a
derived from the qualifications but that would be repeating content. Might be okay as it's not inventing, just reorganizing. But the instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine Skills into Requirements or Qualifications. Better to have only About the role, Responsibilities, Requirements, Qualifications. That's four sections.
We must not repeat job title as heading. So no heading for Senior Data Analyst.
We need to output only HTML fragment.
Let's craft:
About the role
... overview ...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
We need to ensure we preserve all substantive info. That's a lot; we need to include each bullet point from responsibilities and qualifications. Must not omit any.
Let's extract responsibilities bullets from the text:
Key Responsibilities section includes bullet-like sentences:
- Participate in the identification, inventory, and classification of the agency’s critical data.
- Perform detailed field-level analysis, metadata analysis, data profiling, and data mapping.
- Create source-to-target mappings for VSAM files into relational and dimensional SQL tables.
- Create and maintain data dictionary documentation, including business terms, valid values, and definitions.
- Work with data subject matter experts to document data quality rules, definitions, and business rules.
- Extract business rules from existing legacy code and translate them into source-to-target mappings.
- Support data conversion and migration from VSAM files to relational and dimensional SQL distributed databases.
- Develop complex SQL data validations based on source-to-target mappings and target data models.
- Transform business rules and data quality rules into ETL and SQL technical specifications.
- Validate converted and migrated data to ensure accuracy, completeness, and consistency.
- Support processes that proactively detect, correct, and prevent invalid data values.
- Provide technical and analytical support for agency data integrity and quality initiatives.
- Develop and support ETL processes using IBM DataStage.
- Actively participate in optimization and performance tuning of existing ETL and SQL processes.
- Write and optimize complex SQL queries and stored procedures.
- Support SQL Server Reporting Services (SSRS) report development.
- Apply understanding of data structures and their relationship to ETL applications.
- Work across IBM Mainframe, Windows Server, and SQL Server environments.
- Extract field references and calculated data from COBOL programs.
- Analyze mainframe applications involving COBOL, CICS, and DB2.
- Support data analysis and validation activities related to pension administration systems.
- Collaborate with technical leads and subject matter experts to identify and address data quality gaps.
- Work with IT partners to remediate identified gaps using manual and automated solutions.
- Support defect handling, troubleshooting, root cause analysis, and problem resolution.
- Contribute to ongoing process improvement programs related to data management, quality, profiling, conversion, and validation.
- Recommend solutions based on analyzed requirements and team methodology.
- Collaborate with data SMEs, technical leads, application teams, and IT partners to support legacy replacement objectives.
- Identify opportunities to improve data quality, streamline validation activities, and strengthen repeatable data management processes.
That's many.
Now Required Qualifications bullets:
- Minimum of five (5) years of source-to-target data mapping experience in mixed mainframe and relational database environments.
- Experience creating data dictionary documentation with business terms, valid values, and definitions.
- Experience converting and migrating VSAM data to relational and dimensional SQL distributed databases.
- Minimum of three (3) years of recent experience developing applications using IBM DataStage ETL.
- Experience extracting field references and calculated data from COBOL programs.
- Experience with BMC Control-M workload automation software.
- Experience with Git version control software.
- Minimum of three (3) years of recent experience with pension administration systems.
- Strong SQL knowledge, including experience working with complex queries and stored procedures.
- Proficiency in SSRS report development.
- Strong analytical skills with the ability to receive and analyze requirements and propose suitable solutions aligned with team methodology.
- Ability to work across IBM Mainframe, Windows Server, and SQL Server environments.
- Proficiency with mainframe applications, including COBOL, CICS, and DB2.
- Understanding of data structures and their relationship to ETL applications.
- Ability to develop complex SQL data validations based on source-to-target mappings and target data models.
- Excellent analytical, problem-solving, information-gathering, and troubleshooting skills.
- Experience supporting data profiling, cleansing, conversion, migration, and validation efforts.
- Ability to collaborate effectively with data subject matter experts, technical leads, and IT partners.
- Ability to support defect handling and problem resolution.
Preferred Qualifications bullets:
- Experience extracting business rules from existing legacy code.
- Experience with data quality or data profiling tools.
- Experience with data warehouses and data marts.
- Experience with SQL Server Reporting Services (SSRS).
- Prior experience working in a pension system environment.
- Prior experience working with a New York State or New York City pension system.
- Experience supporting enterprise-wide legacy replacement or modernization initiatives.
- Experience improving data quality processes, validation standards, or ETL performance in complex data environments.
Now About the role content: Overview paragraph plus contract details.
Overview: "A public sector client of ours in NYC is looking for a seasoned Senior Data Analyst with VSAM experience to support a critical Legacy Replacement initiative of theirs for a 1-year contract that is likely to extend. This role will be hybrid with 3 days required onsite in their Brooklyn, NY office. The Senior Data Analyst will join the agency’s Data Management team to support data profiling, cleansing, conversion, migration, and validation activities for an enterprise-wide Legacy Replacement initiative. This role will also contribute to ongoing process improvement efforts focused on data integrity, data quality, and modernization of legacy data environments."
We need to avoid repeating job title as heading but we can mention it in prose. That's fine.
We should not include the NOTE about candidates not meeting qualifications? It's a note but could be considered part of posting. The instruction says remove boilerplate, duplicated lines, and application instructions. This note is not exactly those but could be considered a warning. I'd keep it maybe as a after Requirements? But it's not a requirement. Might be considered boilerplate? It's a statement about consideration. I'd omit it to be safe.
Now produce HTML.
We need to ensure proper nesting:
About the role
...
Responsibilities
...
etc.
Make sure no extra whitespace issues.
Let's
- . For qualifications also list.
We need to use
for prose. We must not include boilerplate like NOTE about candidates not meeting qualifications etc. That's a note but it's substantive? It says "NOTE: Candidates who don't meet the required qualifications for this role will NOT be considered at this time." That's a statement but maybe considered boilerplate? It's a note about consideration; could be kept? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This note is not exactly those, but it's a note about consideration. Might be considered part of posting but not essential? It's not duplicated. I'd keep it as a
maybe under Requirements? But it's more like a note. Could be included as a
after Required Qualifications. We must not invent or summarize away detail. So we need to keep all specifics: VSAM experience, 1-year contract likely to extend, hybrid 3 days onsite Brooklyn, NY, Data Management team, data profiling, cleansing, conversion, migration, validation, field-level analysis, metadata analysis, source-to-target mapping VSAM to relational/dimensional SQL tables, data dictionary, business terms, valid values, definitions, work with SMEs, extract business rules from legacy code, data conversion migration, develop complex SQL validations, transform business rules into ETL and SQL specs, validate data, support processes detect/correct/prevent invalid data, support data integrity/quality initiatives, ETL using IBM DataStage, optimize ETL/SQL, write complex SQL queries/stored procedures, support SSRS report dev, work across IBM Mainframe, Windows Server, SQL Server, extract field references/calculated data from COBOL, analyze mainframe apps COBOL CICS DB2, support pension admin systems, collaborate with technical leads SMEs, identify data quality gaps, work with IT partners to remediate gaps, support defect handling, troubleshooting, root cause analysis, problem resolution, contribute to process improvement programs, recommend solutions, collaborate with data SMEs, technical leads, application teams, IT partners, identify opportunities to improve data quality, streamline validation, strengthen repeatable data management processes. Required qualifications list: Minimum 5 years source-to-target data mapping experience in mixed mainframe/relational DB; experience creating data dictionary documentation with business terms, valid values, definitions; experience converting/migrating VSAM data to relational/dimensional SQL distributed DB; minimum 3 years recent experience developing applications using IBM DataStage ETL; experience extracting field references and calculated data from COBOL programs; experience with BMC Control-M; experience with Git; minimum 3 years recent experience with pension administration systems; strong SQL knowledge including complex queries and stored procedures; proficiency in SSRS report development; strong analytical skills with ability to receive/analyze requirements and propose suitable solutions aligned with team methodology; ability to work across IBM Mainframe, Windows Server, SQL Server; proficiency with mainframe applications COBOL, CICS, DB2; understanding of data structures and their relationship to ETL applications; ability to develop complex SQL data validations based on source-to-target mappings and target data models; excellent analytical, problem-solving, information-gathering, troubleshooting skills; experience supporting data profiling, cleansing, conversion, migration, validation; ability to collaborate effectively with data SMEs, technical leads, IT partners; ability to support defect handling and problem resolution. Preferred qualifications: experience extracting business rules from existing legacy code; experience with data quality or data profiling tools; experience with data warehouses and data marts; experience with SQL Server Reporting Services (SSRS); prior experience working in a pension system environment; prior experience working with a New York State or New York City pension system; experience supporting enterprise-wide legacy replacement or modernization initiatives; experience improving data quality processes, validation standards, or ETL performance in complex data environments. We need to decide sections: About the role (overview + contract/hybrid/location). Responsibilities (Key Responsibilities). Requirements (Required Qualifications). Qualifications (Preferred Qualifications). Skills maybe could be a separate section but we could incorporate skills into Requirements or Qualifications. But we need to follow instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with real content. We have content for About the role, Responsibilities, Requirements, Qualifications. Skills maybe we could extract a list of technical skills from the qualifications but that's overlapping. Could we create a Skills section summarizing technical skills? That would be summarizing, but we must not invent or summarize away detail. However we could list skills as a
- derived from the qualifications but that would be repeating content. Might be okay as it's not inventing, just reorganizing. But the instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine Skills into Requirements or Qualifications. Better to have only About the role, Responsibilities, Requirements, Qualifications. That's four sections.
We must not repeat job title as heading. So no heading for Senior Data Analyst.
We need to output only HTML fragment.
Let's craft:
- ... ...
- ... ...
- ... ...
About the role
... overview ...
Responsibilities
Requirements
Qualifications
after Requirements? But it's not a requirement. Might be considered boilerplate? It's a statement about consideration. I'd omit it to be safe. Now produce HTML. We need to ensure proper nesting:
About the role
...
Responsibilities
- ...