Data Quality Developer - AML
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include Job Number in a short paragraph maybe under About the role? Or we could drop it. The instruction: "fold minor metadata into a short
or drop it." So we can include a short paragraph with Job Number and Industry maybe.
We must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all details from the posting, but we can combine some into paragraphs.
We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit EEO etc. There's work authorization statement which is substantive (must be authorized to work for any employer in US, cannot sponsor visa). That's substantive, keep.
We need to remove duplicated lines: I see "5 years of experience in data analysis, or reporting in a financial or risk-focused environment." appears twice (under Required Skills and Required Experience). We should keep it but not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we remove duplicate, we might be losing info? But it's same info repeated; we could keep one instance. Probably acceptable to deduplicate.
Also "Required Experience: 8 years of overall experience required." plus the 5 years again.
We need to include "Onsite Flexibility: Remote (working East Coast hours; candidates interested in conversion to permanent must be near a TD Hub on the East Coast)". That's substantive.
We need to include "Contract Details Position Type: ContractContract Duration: 6 months (extension possible; conversion to permanent possible)". Actually there is a typo: "ContractContract". We'll parse as Position Type: Contract; Contract Duration: 6 months (extension possible; conversion to permanent possible).
We need to include "Travel Requirements: Not required".
We need to include "Work Environment / Physical Requirements: Role is fully remote; candidates working East Coast hours. Candidate will have access to customer data. Training period of approximately 3 weeks. Approximately 2 hours per day spent in meetings. All interactions are with internal stakeholders."
We need to include "Benefits: Medical, Vision, and Dental Insurance Plans; 401k Retirement Fund".
We need to include "About the Client" paragraph.
We need to include "About GTT" paragraph.
We need to include "Job Number: 26-14453 Industry: Software Engineering". Could be a short paragraph.
Now structure:
We could have sections:
- About the role (Job Summary)
- Responsibilities (Key Responsibilities)
- Requirements (maybe combine Required Skills, Education Requirements, Required Experience, Work Authorization? But we have separate headings: Requirements, Qualifications, Skills. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings appropriately.
We have:
- About the role: Job Summary.
- Responsibilities: Key Responsibilities.
- Requirements: maybe Work Authorization? Or maybe "Work Environment / Physical Requirements"? Actually that could be under Requirements? But we have separate heading for Schedule, Benefits, Pay. Qualifications could cover Education Requirements and Required Experience. Skills could cover Required Skills and Preferred Skills.
Thus:
About the role
Job Summary ...
Responsibilities
- ...
Qualifications
Education Requirements: Degree in computer science or related field required.
Required Experience: 8 years of overall experience required; 5 years of experience in data analysis, or reporting in a financial or risk-focused environment.
Skills
- Required Skills: ...
- Preferred Skills: Power BI, Tableau
But we need to list required skills as items. Could break into - Strong AML background (preferred)
etc. But we need to preserve all substantive information; we can keep as a paragraph or list. The instruction: Use - for any list of duties/requirements/benefits. So for skills we should list each bullet.
Thus we need to extract each required skill bullet:
- Prefer to have a strong AML background.
- 5 years of experience in data analysis, or reporting in a financial or risk-focused environment.
- Proficiency in SQL, Excel.
- Experience with Python, (or similar visualization tools), Jira, and Confluence.
- Preferred knowledge of financial industry's technology controls and security risk issues.
- Strength in prioritizing and managing your own workload to deliver quality results and meet timelines with limited guidance of management.
- Demonstrated ability to participate in complex, comprehensive or large projects and initiatives.
- Business/technology experience with experience collaborating with others in highly matrix, cross-functional environment.
- Problem solver with ability to work independently.
- Must have strong attention to detail.
- Ability to manage multiple efforts simultaneously, strong project management, reporting, and organizational skills.
We also have "Preferred Skills Power BI, Tableau". That's separate.
We also have "Required Skills Prefer to have a strong AML background." Actually the line: "Required Skills Prefer to have a strong AML background." So it's "Prefer to have a strong AML background." (maybe it's preferred but listed under Required Skills). We'll keep as is.
Now for Qualifications we might also include Work Authorization? That could be under Requirements? But we have a heading "Requirements". Could put work authorization, contract details, location, onsite flexibility, travel requirements, etc. However we also have separate headings for Pay, Schedule, Benefits. So we can put other meta under Requirements.
Thus:
Requirements
Location: Mount Laurel, NJ. Onsite Flexibility: Remote (working East Coast hours; candidates interested in conversion to permanent must be near a TD Hub on the East Coast). Contract Type: Contract, 6 months duration (extension possible; conversion to permanent possible). Pay Rate: $80.00–$90.00 per hour (USD). Shift/Schedule: Monday–Friday, core business hours; overtime as needed. Travel Requirements: Not required. Work Authorization: Applicants must be authorized to work for ANY employer in the U.S.; unable to sponsor or take over sponsorship of an employment Visa at this time.
But we have separate Pay and Schedule sections. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should have Pay and Schedule sections. So we should not duplicate pay and schedule in Requirements. Instead we can put location, contract type, onsite flexibility, travel, work authorization under Requirements. Then Pay and Schedule separate.
Thus:
Requirements
Location: Mount Laurel, NJ. Onsite Flexibility: Remote (working East Coast hours; candidates interested in conversion to permanent must be near a TD Hub on the East Coast). Contract Type: Contract, 6 months duration (extension possible; conversion to permanent possible). Travel Requirements: Not required. Work Authorization: Applicants must be authorized to work for ANY employer in the U.S.; unable to sponsor or take over sponsorship of an employment Visa at this time.
Then:
Pay
$80.00–$90.00 per hour (USD)
Schedule
Monday–Friday, core business hours; overtime as needed
Now Benefits:
Benefits
- Medical, Vision, and Dental Insurance Plans
- 401k Retirement Fund
Now About the role (Job Summary) we need to preserve all substantive info: "Reporting to the Risk Reporting Senior Manager for the Enterprise Protect Risk Factory, the candidate will be a member of a high performing team of Technology and Risk professionals utilizing personal experience and knowledge of Business Intelligence expertise. This role is responsible for ensuring data quality, building analytics tools and reports, and supporting risk management initiatives through automation and stakeholder engagement."
We'll put that in .
Now Responsibilities: list each bullet.
Key Responsibilities list:
- Be a part of the risk assessment team.
- Develop and maintain data quality scripts to support the data requirements from enterprise risk assessment stakeholders.
- Maintain regular communication with cross-functional teams to support continuous improvement and data integrity.
- Work with 2nd Line of Defense on all challenges as required.
- Engaging Enterprise Protect stakeholders and data providers, validating the quality and integrity of the data and results of metrics included in all reporting end to end.
- Supporting change awareness activities, providing expertise on KRI design, developing materials and supporting ongoing data analysis requests.
- Demonstrate expert knowledge of all data sources and data lineage for the reporting
for prose. We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include Job Number in a short paragraph maybe under About the role? Or we could drop it. The instruction: "fold minor metadata into a short
or drop it." So we can include a short paragraph with Job Number and Industry maybe. We must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all details from the posting, but we can combine some into paragraphs. We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit EEO etc. There's work authorization statement which is substantive (must be authorized to work for any employer in US, cannot sponsor visa). That's substantive, keep. We need to remove duplicated lines: I see "5 years of experience in data analysis, or reporting in a financial or risk-focused environment." appears twice (under Required Skills and Required Experience). We should keep it but not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we remove duplicate, we might be losing info? But it's same info repeated; we could keep one instance. Probably acceptable to deduplicate. Also "Required Experience: 8 years of overall experience required." plus the 5 years again. We need to include "Onsite Flexibility: Remote (working East Coast hours; candidates interested in conversion to permanent must be near a TD Hub on the East Coast)". That's substantive. We need to include "Contract Details Position Type: ContractContract Duration: 6 months (extension possible; conversion to permanent possible)". Actually there is a typo: "ContractContract". We'll parse as Position Type: Contract; Contract Duration: 6 months (extension possible; conversion to permanent possible). We need to include "Travel Requirements: Not required". We need to include "Work Environment / Physical Requirements: Role is fully remote; candidates working East Coast hours. Candidate will have access to customer data. Training period of approximately 3 weeks. Approximately 2 hours per day spent in meetings. All interactions are with internal stakeholders." We need to include "Benefits: Medical, Vision, and Dental Insurance Plans; 401k Retirement Fund". We need to include "About the Client" paragraph. We need to include "About GTT" paragraph. We need to include "Job Number: 26-14453 Industry: Software Engineering". Could be a short paragraph. Now structure: We could have sections: - About the role (Job Summary) - Responsibilities (Key Responsibilities) - Requirements (maybe combine Required Skills, Education Requirements, Required Experience, Work Authorization? But we have separate headings: Requirements, Qualifications, Skills. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings appropriately. We have: - About the role: Job Summary. - Responsibilities: Key Responsibilities. - Requirements: maybe Work Authorization? Or maybe "Work Environment / Physical Requirements"? Actually that could be under Requirements? But we have separate heading for Schedule, Benefits, Pay. Qualifications could cover Education Requirements and Required Experience. Skills could cover Required Skills and Preferred Skills. Thus:
About the role
Job Summary ...
Responsibilities
- ...
Qualifications
Education Requirements: Degree in computer science or related field required.
Required Experience: 8 years of overall experience required; 5 years of experience in data analysis, or reporting in a financial or risk-focused environment.
Skills
- Required Skills: ...
- Preferred Skills: Power BI, Tableau
- Strong AML background (preferred) etc. But we need to preserve all substantive information; we can keep as a paragraph or list. The instruction: Use
- for any list of duties/requirements/benefits. So for skills we should list each bullet.
Thus we need to extract each required skill bullet:
- Prefer to have a strong AML background.
- 5 years of experience in data analysis, or reporting in a financial or risk-focused environment.
- Proficiency in SQL, Excel.
- Experience with Python, (or similar visualization tools), Jira, and Confluence.
- Preferred knowledge of financial industry's technology controls and security risk issues.
- Strength in prioritizing and managing your own workload to deliver quality results and meet timelines with limited guidance of management.
- Demonstrated ability to participate in complex, comprehensive or large projects and initiatives.
- Business/technology experience with experience collaborating with others in highly matrix, cross-functional environment.
- Problem solver with ability to work independently.
- Must have strong attention to detail.
- Ability to manage multiple efforts simultaneously, strong project management, reporting, and organizational skills.
We also have "Preferred Skills Power BI, Tableau". That's separate.
We also have "Required Skills Prefer to have a strong AML background." Actually the line: "Required Skills Prefer to have a strong AML background." So it's "Prefer to have a strong AML background." (maybe it's preferred but listed under Required Skills). We'll keep as is.
Now for Qualifications we might also include Work Authorization? That could be under Requirements? But we have a heading "Requirements". Could put work authorization, contract details, location, onsite flexibility, travel requirements, etc. However we also have separate headings for Pay, Schedule, Benefits. So we can put other meta under Requirements.
Thus:
Requirements
Location: Mount Laurel, NJ. Onsite Flexibility: Remote (working East Coast hours; candidates interested in conversion to permanent must be near a TD Hub on the East Coast). Contract Type: Contract, 6 months duration (extension possible; conversion to permanent possible). Pay Rate: $80.00–$90.00 per hour (USD). Shift/Schedule: Monday–Friday, core business hours; overtime as needed. Travel Requirements: Not required. Work Authorization: Applicants must be authorized to work for ANY employer in the U.S.; unable to sponsor or take over sponsorship of an employment Visa at this time.
But we have separate Pay and Schedule sections. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should have Pay and Schedule sections. So we should not duplicate pay and schedule in Requirements. Instead we can put location, contract type, onsite flexibility, travel, work authorization under Requirements. Then Pay and Schedule separate. Thus:Requirements
Location: Mount Laurel, NJ. Onsite Flexibility: Remote (working East Coast hours; candidates interested in conversion to permanent must be near a TD Hub on the East Coast). Contract Type: Contract, 6 months duration (extension possible; conversion to permanent possible). Travel Requirements: Not required. Work Authorization: Applicants must be authorized to work for ANY employer in the U.S.; unable to sponsor or take over sponsorship of an employment Visa at this time.
Then:Pay
$80.00–$90.00 per hour (USD)
Schedule
Monday–Friday, core business hours; overtime as needed
Now Benefits:Benefits
- Medical, Vision, and Dental Insurance Plans
- 401k Retirement Fund
. Now Responsibilities: list each bullet. Key Responsibilities list: - Be a part of the risk assessment team. - Develop and maintain data quality scripts to support the data requirements from enterprise risk assessment stakeholders. - Maintain regular communication with cross-functional teams to support continuous improvement and data integrity. - Work with 2nd Line of Defense on all challenges as required. - Engaging Enterprise Protect stakeholders and data providers, validating the quality and integrity of the data and results of metrics included in all reporting end to end. - Supporting change awareness activities, providing expertise on KRI design, developing materials and supporting ongoing data analysis requests. - Demonstrate expert knowledge of all data sources and data lineage for the reporting