Senior Compliance Analyst (MS), AML (Anti-Money Laundering)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when 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 posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Content:
"The Opportunity: ..." paragraph describing role.
"What you’ll do:" bullet list (actually lines with periods). It's a list of duties.
"To Qualify for the role, you will have:" list of qualifications.
"Ideally, you’ll also have:" list of preferred qualifications.
"Skills and Attributes for Success:" list of skills.
"What working at ACA offers:" description of benefits.
"About ACA:" description of company.
"What we commit to:" EEO statement (should be removed as boilerplate).
"Salary Range: $65,000.00" This is pay info.
Then a privacy notice (boilerplate) to remove.
We need sections: About the role (maybe from "The Opportunity:"?), Responsibilities (What you’ll do?), Requirements (To Qualify...), Qualifications (Ideally...), Skills (Skills and Attributes...), Benefits (What working at ACA offers...), Pay (Salary Range...), Schedule (none? Not mentioned, so we should NOT create Schedule section). Also maybe About ACA could be a section but not in list of allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "About ACA" maybe could be considered "About the role"? Actually "About the role" is a heading we can use for the introductory description. The "Opportunity" paragraph is about the role. So we can put that under
About the role
. Then responsibilities under Responsibilities
. Requirements under Requirements
(the "To Qualify for the role, you will have:" list). Qualifications under Qualifications
(the "Ideally, you’ll also have:" list). Skills under Skills
. Benefits under Benefits
. Pay under Pay
. No Schedule.
We must not include filler like "commensurate with experience". Not present.
We need to use - for any list of duties/requirements/benefits. So for responsibilities, requirements, qualifications, skills, benefits we need to use lists. For prose we use
.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep each bullet point exactly as in text (maybe minor punctuation). We must not drop any.
Let's extract each list.
Responsibilities (What you’ll do:):
- Perform investor intake, document collection, review, and verification.
- Execute AML/KYC tasks in accordance with SOPs.
- Handle lower-complexity onboarding or lifecycle cases.
- Clearly document findings and decisions.
- Escalate issues or data gaps following defined guidelines.
- Meet productivity, quality, SLA, and turnaround time targets.
Requirements (To Qualify for the role, you will have:):
- 2–4 years of AML/KYC, compliance, or financial services experience.
- Prior experience supporting onboarding and due diligence workflows.
- Familiar with institutional investor documentation and entity structures.
- Strong attention to detail, file organization discipline, and ability to work in SLA-driven environments.
- Willingness to learn and expand AML/KYC expertise.
Qualifications (Ideally, you’ll also have:):
- Major or concentration in compliance, criminal justice, law, business, accounting, finance, and/or economics preferred.
Skills and Attributes for Success: list:
- Demonstrated professional integrity
- Dependable, flexible, and adaptable to new ACA initiatives and changing client needs
- Ability to exercise discretion and make independent judgments on matters of significance
- Ability to work in a fast-paced, small team environment
- Ability to establish and maintain effective working relationships with colleagues and clients
- Highly motivated and goal oriented; pro-active in one’s own education and career progression; volunteers for and shows initiative on both internal and external projects and tasks
- Dedicated to upholding ACA’s high-quality standards and customer service focus
- Strong organizational and problem-solving skills with attention to detail
- Strong oral and written communication skills
- Proficient with Microsoft Office applications and comfortable working in a tech enabled environment.
Benefits (What working at ACA offers:):
We need to capture the description: "We offer a competitive compensation package where you’ll be rewarded based on your performance and recognized for the value you bring to our business. Our Total Rewards package includes medical and dental coverage and 401(k) plans, and a wide range of paid time off options as well as a flexible work environment. You’ll also be granted time off for designated ACA Paid Holidays, Summer Fridays, Personal/Family Care, and other leaves of absence when needed to support your physical, financial, and emotional well-being. We also offer unique benefits such as Student Debt Forgiveness and Pet Insurance."
We need to decide if we should turn this into a list? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. Benefits could be considered a list? It's more prose. But we could split into list items? The instruction says "any list of duties/requirements/benefits". If the benefits are presented as a list, we should use
- . However the text is not explicitly a list with bullet points; it's a paragraph. We could still treat as prose (
). The instruction says use
- for any list of duties/requirements/benefits. If it's not a list, we can use
. So we will use
for benefits.
Pay: Salary Range: $65,000.00. That's a specific pay. Should we put in
or maybe
- ? It's not a list; it's a single value. Use
.
We must not include boilerplate like EEO statement, privacy notice, etc.
Also we should not include "About ACA" description? The allowed headings do not include "About ACA". Should we include it? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not include About ACA. So we should not create a heading for About ACA. However we need to preserve ALL substantive information. If we omit About ACA, we lose substantive info. But maybe we can incorporate that info under About the role? The About the role heading is for role description, not company. But we could maybe add a paragraph under About the role that includes both role and company? However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't forbid adding extra headings beyond the list? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but likely they want only those headings. The instruction: "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." It doesn't explicitly forbid other headings, but the examples given are those. To be safe, we should stick to those headings. However we need to preserve all substantive information; we could incorporate the About ACA paragraph into the Benefits section? No, that's not appropriate. Could we add a
after the Benefits section without a heading? The instruction says output ONLY the HTML fragment — no /, no markdown code fences. It doesn't say we cannot have untagged paragraphs. But we should follow the pattern of using headings for sections. However we could include a
about ACA after Benefits without a heading; that might be considered stray content. Better to include it under a heading like "About the role"? But that would misrepresent.
Maybe we can treat "About ACA" as part of "About the role"? The heading "About the role" could include both role and company overview. The posting has "The Opportunity:" which is role description, and later "About ACA:" which is company description. We could combine them under About the role heading, but that would mix role and company. However the instruction says "About the role" heading is for section headings e.g. About the role. It didn't forbid adding extra content like company overview under that heading. It might be acceptable.
Alternatively, we could create a heading "About ACA" even though not in examples, but risk being considered not following instruction. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not an exhaustive list. So we could add other headings as needed. However later they say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a heading for About ACA if there is real content. That seems okay.
Thus we will include About ACA
with the paragraph.
We must also remove the EEO statement and privacy notice.
Now we need to ensure we don't include any filler like "commensurate with experience". Not present.
Now construct HTML.
We'll start with About the role
then
containing the Opportunity paragraph.
Then
Responsibilities
then - each duty.
Then
Requirements
then - each qualification.
Then
Qualifications
then - the ideal qualification.
Then
Skills
then - each skill.
Then
Benefits
then containing benefits paragraph.
Then
About ACA
then containing About ACA paragraph.
Then
Pay
then containing Salary Range: $65,000.00.
We should not include Schedule.
Check for any duplicated lines: The posting had some duplicated lines? Not obvious.
Now ensure we preserve all substantive information: Let's copy each piece exactly.
Opportunity paragraph: "The Opportunity: The AML/KYC Senior Analyst supports the day-to-day execution of the investor onboarding and lifecycle due diligence. This role is focused specifically on private fund investor KY
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when 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 posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Content: "The Opportunity: ..." paragraph describing role. "What you’ll do:" bullet list (actually lines with periods). It's a list of duties. "To Qualify for the role, you will have:" list of qualifications. "Ideally, you’ll also have:" list of preferred qualifications. "Skills and Attributes for Success:" list of skills. "What working at ACA offers:" description of benefits. "About ACA:" description of company. "What we commit to:" EEO statement (should be removed as boilerplate). "Salary Range: $65,000.00" This is pay info. Then a privacy notice (boilerplate) to remove. We need sections: About the role (maybe from "The Opportunity:"?), Responsibilities (What you’ll do?), Requirements (To Qualify...), Qualifications (Ideally...), Skills (Skills and Attributes...), Benefits (What working at ACA offers...), Pay (Salary Range...), Schedule (none? Not mentioned, so we should NOT create Schedule section). Also maybe About ACA could be a section but not in list of allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "About ACA" maybe could be considered "About the role"? Actually "About the role" is a heading we can use for the introductory description. The "Opportunity" paragraph is about the role. So we can put that under
About the role
. Then responsibilities underResponsibilities
. Requirements underRequirements
(the "To Qualify for the role, you will have:" list). Qualifications underQualifications
(the "Ideally, you’ll also have:" list). Skills underSkills
. Benefits underBenefits
. Pay underPay
. No Schedule. We must not include filler like "commensurate with experience". Not present. We need to use- for any list of duties/requirements/benefits. So for responsibilities, requirements, qualifications, skills, benefits we need to use lists. For prose we use
. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep each bullet point exactly as in text (maybe minor punctuation). We must not drop any. Let's extract each list. Responsibilities (What you’ll do:): - Perform investor intake, document collection, review, and verification. - Execute AML/KYC tasks in accordance with SOPs. - Handle lower-complexity onboarding or lifecycle cases. - Clearly document findings and decisions. - Escalate issues or data gaps following defined guidelines. - Meet productivity, quality, SLA, and turnaround time targets. Requirements (To Qualify for the role, you will have:): - 2–4 years of AML/KYC, compliance, or financial services experience. - Prior experience supporting onboarding and due diligence workflows. - Familiar with institutional investor documentation and entity structures. - Strong attention to detail, file organization discipline, and ability to work in SLA-driven environments. - Willingness to learn and expand AML/KYC expertise. Qualifications (Ideally, you’ll also have:): - Major or concentration in compliance, criminal justice, law, business, accounting, finance, and/or economics preferred. Skills and Attributes for Success: list: - Demonstrated professional integrity - Dependable, flexible, and adaptable to new ACA initiatives and changing client needs - Ability to exercise discretion and make independent judgments on matters of significance - Ability to work in a fast-paced, small team environment - Ability to establish and maintain effective working relationships with colleagues and clients - Highly motivated and goal oriented; pro-active in one’s own education and career progression; volunteers for and shows initiative on both internal and external projects and tasks - Dedicated to upholding ACA’s high-quality standards and customer service focus - Strong organizational and problem-solving skills with attention to detail - Strong oral and written communication skills - Proficient with Microsoft Office applications and comfortable working in a tech enabled environment. Benefits (What working at ACA offers:): We need to capture the description: "We offer a competitive compensation package where you’ll be rewarded based on your performance and recognized for the value you bring to our business. Our Total Rewards package includes medical and dental coverage and 401(k) plans, and a wide range of paid time off options as well as a flexible work environment. You’ll also be granted time off for designated ACA Paid Holidays, Summer Fridays, Personal/Family Care, and other leaves of absence when needed to support your physical, financial, and emotional well-being. We also offer unique benefits such as Student Debt Forgiveness and Pet Insurance." We need to decide if we should turn this into a list? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. Benefits could be considered a list? It's more prose. But we could split into list items? The instruction says "any list of duties/requirements/benefits". If the benefits are presented as a list, we should use
- . However the text is not explicitly a list with bullet points; it's a paragraph. We could still treat as prose (
). The instruction says use
- for any list of duties/requirements/benefits. If it's not a list, we can use
. So we will use
for benefits. Pay: Salary Range: $65,000.00. That's a specific pay. Should we put in
or maybe
- ? It's not a list; it's a single value. Use
. We must not include boilerplate like EEO statement, privacy notice, etc. Also we should not include "About ACA" description? The allowed headings do not include "About ACA". Should we include it? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not include About ACA. So we should not create a heading for About ACA. However we need to preserve ALL substantive information. If we omit About ACA, we lose substantive info. But maybe we can incorporate that info under About the role? The About the role heading is for role description, not company. But we could maybe add a paragraph under About the role that includes both role and company? However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't forbid adding extra headings beyond the list? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but likely they want only those headings. The instruction: "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." It doesn't explicitly forbid other headings, but the examples given are those. To be safe, we should stick to those headings. However we need to preserve all substantive information; we could incorporate the About ACA paragraph into the Benefits section? No, that's not appropriate. Could we add a
after the Benefits section without a heading? The instruction says output ONLY the HTML fragment — no /, no markdown code fences. It doesn't say we cannot have untagged paragraphs. But we should follow the pattern of using headings for sections. However we could include a
about ACA after Benefits without a heading; that might be considered stray content. Better to include it under a heading like "About the role"? But that would misrepresent. Maybe we can treat "About ACA" as part of "About the role"? The heading "About the role" could include both role and company overview. The posting has "The Opportunity:" which is role description, and later "About ACA:" which is company description. We could combine them under About the role heading, but that would mix role and company. However the instruction says "About the role" heading is for section headings e.g. About the role. It didn't forbid adding extra content like company overview under that heading. It might be acceptable. Alternatively, we could create a heading "About ACA" even though not in examples, but risk being considered not following instruction. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not an exhaustive list. So we could add other headings as needed. However later they say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a heading for About ACA if there is real content. That seems okay. Thus we will include
About ACA
with the paragraph. We must also remove the EEO statement and privacy notice. Now we need to ensure we don't include any filler like "commensurate with experience". Not present. Now construct HTML. We'll start withAbout the role
thencontaining the Opportunity paragraph. Then
Responsibilities
then- each duty.
Then
Requirements
then- each qualification.
Then
Qualifications
then- the ideal qualification.
Then
Skills
then- each skill.
Then
Benefits
thencontaining benefits paragraph. Then
About ACA
thencontaining About ACA paragraph. Then
Pay
thencontaining Salary Range: $65,000.00. We should not include Schedule. Check for any duplicated lines: The posting had some duplicated lines? Not obvious. Now ensure we preserve all substantive information: Let's copy each piece exactly. Opportunity paragraph: "The Opportunity: The AML/KYC Senior Analyst supports the day-to-day execution of the investor onboarding and lifecycle due diligence. This role is focused specifically on private fund investor KY
- each skill.
Then
- the ideal qualification.
Then
- each qualification.
Then
- each duty.
Then
- ? It's not a list; it's a single value. Use
- for any list of duties/requirements/benefits. If it's not a list, we can use
- . However the text is not explicitly a list with bullet points; it's a paragraph. We could still treat as prose (
- for any list of duties/requirements/benefits, and