Sr. Analyst, Treasury
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. 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. IMPORTANT: 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to extract substantive content: About Us (company description) maybe not needed? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include sections that have content.
We have:
- About Us: description of Visa. Could be considered "About the role"? Actually "About Us" is company overview. Might be okay to put under
About the role
but that might be inaccurate. However we could treat "About Us" as a short paragraph about the company, maybe not needed. The instruction says we can include sections only when posting has real specific content. The "About Us" is present. Could map to "About the role"? Not exactly but maybe we can use "About the role" heading for the job description summary. The job description paragraph after "Job Description" is: "Join Visa Treasury's Digital Assets and Innovation team to help reshape how money moves with digital assets like stablecoins and next-gen payment rails. In this role, you'll own operations end to end, develop treasury roadmaps, and guide decisions, partnering with Risk, Compliance, Legal, Settlement Ops, Finance, and Product to vet ideas and design and launch pilots with external partners. You'll keep a close pulse on the crypto ecosystem and turn research into clear recommendations. We're looking for someone who brings big ideas and takes ownership, yet stays grounded in treasury fundamentals like liquidity, settlement, reconciliation, and controls. This role is perfect if you're ready to roll up your sleeves, move fast, and help define the next chapter of money movement at Visa."
That's suitable for About the role.
Then we have "Key Responsibilities" list. That's responsibilities.
Then we have "Qualifications" with Basic Qualifications and Preferred Qualifications. That's qualifications.
We also have "Information for US Applicants" includes salary range, benefits, etc. That's Pay and Benefits.
We also have "Work Hours Varies upon the needs of the department." That's schedule info (but it's vague "Varies". The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "Work Hours Varies upon the needs of the department." That's somewhat vague but it's actual statement. However they said never create Schedule section unless posting actually states them. It does state work hours varies. That's not a specific schedule but it's still stating something. However they also said never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Varies" is considered placeholder? They gave "varies" as example of filler. So we should not create a Schedule section because the content is just "Varies". So we skip Schedule.
Travel Requirements: "This position requires travel 5-10% of the time." That's not a standard heading but could be included maybe under a generic section? Not listed. Could be omitted? Might be considered metadata but not required. Probably we can include it as a paragraph under maybe "About the role" or separate? But instruction says prefer few substantive sections. Could add a short paragraph under About the role or maybe a separate section like "Travel". But not in allowed headings list. Probably we should not create a new heading not in list. Could fold into About the role paragraph.
Mental/Physical Requirements: also boilerplate? Might be considered generic but could be omitted.
EEO etc: remove.
Thus sections: About the role (h3), Responsibilities (h3), Qualifications (h3), Pay (h3), Benefits (h3). Possibly also Skills? Not explicitly separate; qualifications cover skills.
We need to use - for any list of duties/requirements/benefits.
Responsibilities list: we have bullet points after "Key Responsibilities". We'll turn each line into
- .
Qualifications: we have Basic Qualifications and Preferred Qualifications. Could combine into a list? Might be two subheadings? But we only allowed h3 headings; we could keep Qualifications as h3 and inside have paragraphs for Basic and Preferred. Or we could make two subsections with
? Not allowed. Better to keep as paragraphs with maybe? But we must not invent headings. Use for prose. So we can have
Basic Qualifications: ...
and similarly for Preferred.
Benefits: list of benefits: Medical, Dental, Vision, 401(k), FSA/HSA, Life Insurance, Paid Time Off, Wellness Program. Use - .
Pay: we have salary range: $129,200.00 to $206,700.00 USD per year, which may include potential sales incentive payments (if applicable). Salary may vary depending on job-related factors which may include knowledge, skills, experience, and location. In addition, this position may be eligible for bonus and equity.
We'll put that in
under Pay.
We also have "Visa requires at least 3 days in office, expectations of these days will be confirmed by your Hiring Manager." That's schedule/office requirement. Could be considered schedule but it's specific: at least 3 days in office. That's not "varies". It's a concrete expectation. So we could include a Schedule section with that info. The instruction says never create Schedule section unless posting actually states them. It does state that. So we can include Schedule heading with that content. However we must avoid filler like "varies". This is specific: at least 3 days in office. So we can include Schedule.
Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits, Schedule.
We must not repeat job title as heading. Not include Job ID.
Now produce HTML fragment.
Structure:
About the role
Join Visa Treasury's Digital Assets and Innovation team to help reshape how money moves with digital assets like stablecoins and next-gen payment rails. In this role, you'll own operations end to end, develop treasury roadmaps, and guide decisions, partnering with Risk, Compliance, Legal, Settlement Ops, Finance, and Product to vet ideas and design and launch pilots with external partners. You'll keep a close pulse on the crypto ecosystem and turn research into clear recommendations. We're looking for someone who brings big ideas and takes ownership, yet stays grounded in treasury fundamentals like liquidity, settlement, reconciliation, and controls. This role is perfect if you're ready to roll up your sleeves, move fast, and help define the next chapter of money movement at Visa.
Responsibilities
- Run daily treasury operations across digital assets and traditional payments, including cash, liquidity, settlement, and reconciliation.
- Execute treasury activities across blockchains, custodians, wallets, banks, exchanges, and payment providers.
- Participate in a rotating weekend and after-hours support model for critical treasury operations and incident response.
- Monitor fiat and digital asset liquidity, funding needs, and operational risk controls.
- Support stablecoin operations, including minting, redemption, custody transfers, wallet funding, and exception management.
- Own settlement, reconciliation, operational controls, audit readiness, and issue resolution processes.
- Improve runbooks, procedures, controls, and escalation frameworks.
- Track KPIs and operational metrics; provide actionable insights to leadership.
- Assess opportunities and risks across digital asset use cases, focusing on liquidity, efficiency, settlement, and working capital impacts.
- Monitor developments across blockchain, stablecoin, custody, payments, and regulatory ecosystems.
- Create executive-ready presentations, strategy memos, and business recommendations.
- Lead pilot execution from planning through launch, including governance, testing, vendor diligence, and operational readiness.
- Partner with Risk, Compliance, Legal, Finance, Product, Engineering, and Operations teams to build scalable solutions.
- Support selection and evaluation of custody, wallet, banking, payment, and blockchain infrastructure providers.
Qualifications
Basic Qualifications: 5 or more years of relevant work experience with a Bachelors Degree or at least 2 years of work experience with an Advanced degree (e.g. Masters, MBA, JD, MD) or 0 years of work experience with a PhD.
Preferred Qualifications: 6 or more years of work experience with a Bachelor's Degree or 4 or more years of relevant experience with an Advanced Degree (e.g. Masters, MBA, JD, MD) or up to 3 years of relevant experience with a PhD. Experience in treasury management systems (TMS). Experience with digital assets: stablecoins, custody, wallets, blockchain networks, transaction fees, and ecosystem participants. Incident management, root-cause analysis, and process improvement. Operational controls, governance, audit readiness, and documentation. Strong project management and cross-functional leadership. High ownership, attention to detail, and ability to balance strategy with execution. Experience in identifying regulatory risks and developing related controls. Experience in preparing and presenting management reports. Experience in process documentation and improvement planning. Experience in reconciliation processes and payment regulations. Experience in treasury, payments, fintech, consulting, strategy, or operations with cross-functional project delivery. Degree in Finance, Economics, Business, Analytics, or a related field (or equivalent experience).
Pay
For roles located in the US, the estimated salary range for this position is $129,200.00 to $206,700.00 USD per year, which may include potential sales incentive payments (if applicable). Salary may vary depending on job-related factors which may include knowledge, skills, experience, and location. In addition, this position may be eligible for bonus and equity.
Benefits
- Medical
- Dental
- Vision
- 401(k)
- FSA/HSA
- Life Insurance
- Paid Time Off
- Wellness Program
Schedule
Visa requires at least 3 days in office, expectations of these days will be confirmed by your Hiring Manager.
We should also maybe include travel? Not required.
Check for any boilerplate leftover: We removed EEO, etc. Also removed "Information for US Applicants" heading; we incorporated salary and benefits.
Check for duplicate lines: none.
Check for
for prose. 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. 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. IMPORTANT: 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to extract substantive content: About Us (company description) maybe not needed? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include sections that have content. We have: - About Us: description of Visa. Could be considered "About the role"? Actually "About Us" is company overview. Might be okay to put under
About the role
but that might be inaccurate. However we could treat "About Us" as a short paragraph about the company, maybe not needed. The instruction says we can include sections only when posting has real specific content. The "About Us" is present. Could map to "About the role"? Not exactly but maybe we can use "About the role" heading for the job description summary. The job description paragraph after "Job Description" is: "Join Visa Treasury's Digital Assets and Innovation team to help reshape how money moves with digital assets like stablecoins and next-gen payment rails. In this role, you'll own operations end to end, develop treasury roadmaps, and guide decisions, partnering with Risk, Compliance, Legal, Settlement Ops, Finance, and Product to vet ideas and design and launch pilots with external partners. You'll keep a close pulse on the crypto ecosystem and turn research into clear recommendations. We're looking for someone who brings big ideas and takes ownership, yet stays grounded in treasury fundamentals like liquidity, settlement, reconciliation, and controls. This role is perfect if you're ready to roll up your sleeves, move fast, and help define the next chapter of money movement at Visa." That's suitable for About the role. Then we have "Key Responsibilities" list. That's responsibilities. Then we have "Qualifications" with Basic Qualifications and Preferred Qualifications. That's qualifications. We also have "Information for US Applicants" includes salary range, benefits, etc. That's Pay and Benefits. We also have "Work Hours Varies upon the needs of the department." That's schedule info (but it's vague "Varies". The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "Work Hours Varies upon the needs of the department." That's somewhat vague but it's actual statement. However they said never create Schedule section unless posting actually states them. It does state work hours varies. That's not a specific schedule but it's still stating something. However they also said never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Varies" is considered placeholder? They gave "varies" as example of filler. So we should not create a Schedule section because the content is just "Varies". So we skip Schedule. Travel Requirements: "This position requires travel 5-10% of the time." That's not a standard heading but could be included maybe under a generic section? Not listed. Could be omitted? Might be considered metadata but not required. Probably we can include it as a paragraph under maybe "About the role" or separate? But instruction says prefer few substantive sections. Could add a short paragraph under About the role or maybe a separate section like "Travel". But not in allowed headings list. Probably we should not create a new heading not in list. Could fold into About the role paragraph. Mental/Physical Requirements: also boilerplate? Might be considered generic but could be omitted. EEO etc: remove. Thus sections: About the role (h3), Responsibilities (h3), Qualifications (h3), Pay (h3), Benefits (h3). Possibly also Skills? Not explicitly separate; qualifications cover skills. We need to use- for any list of duties/requirements/benefits. Responsibilities list: we have bullet points after "Key Responsibilities". We'll turn each line into
- .
Qualifications: we have Basic Qualifications and Preferred Qualifications. Could combine into a list? Might be two subheadings? But we only allowed h3 headings; we could keep Qualifications as h3 and inside have paragraphs for Basic and Preferred. Or we could make two subsections with
? Not allowed. Better to keep as paragraphs with maybe? But we must not invent headings. Use
for prose. So we can have
Basic Qualifications: ...
and similarly for Preferred. Benefits: list of benefits: Medical, Dental, Vision, 401(k), FSA/HSA, Life Insurance, Paid Time Off, Wellness Program. Use- .
Pay: we have salary range: $129,200.00 to $206,700.00 USD per year, which may include potential sales incentive payments (if applicable). Salary may vary depending on job-related factors which may include knowledge, skills, experience, and location. In addition, this position may be eligible for bonus and equity.
We'll put that in
under Pay. We also have "Visa requires at least 3 days in office, expectations of these days will be confirmed by your Hiring Manager." That's schedule/office requirement. Could be considered schedule but it's specific: at least 3 days in office. That's not "varies". It's a concrete expectation. So we could include a Schedule section with that info. The instruction says never create Schedule section unless posting actually states them. It does state that. So we can include Schedule heading with that content. However we must avoid filler like "varies". This is specific: at least 3 days in office. So we can include Schedule. Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits, Schedule. We must not repeat job title as heading. Not include Job ID. Now produce HTML fragment. Structure:
About the role
Join Visa Treasury's Digital Assets and Innovation team to help reshape how money moves with digital assets like stablecoins and next-gen payment rails. In this role, you'll own operations end to end, develop treasury roadmaps, and guide decisions, partnering with Risk, Compliance, Legal, Settlement Ops, Finance, and Product to vet ideas and design and launch pilots with external partners. You'll keep a close pulse on the crypto ecosystem and turn research into clear recommendations. We're looking for someone who brings big ideas and takes ownership, yet stays grounded in treasury fundamentals like liquidity, settlement, reconciliation, and controls. This role is perfect if you're ready to roll up your sleeves, move fast, and help define the next chapter of money movement at Visa.
Responsibilities
- Run daily treasury operations across digital assets and traditional payments, including cash, liquidity, settlement, and reconciliation.
- Execute treasury activities across blockchains, custodians, wallets, banks, exchanges, and payment providers.
- Participate in a rotating weekend and after-hours support model for critical treasury operations and incident response.
- Monitor fiat and digital asset liquidity, funding needs, and operational risk controls.
- Support stablecoin operations, including minting, redemption, custody transfers, wallet funding, and exception management.
- Own settlement, reconciliation, operational controls, audit readiness, and issue resolution processes.
- Improve runbooks, procedures, controls, and escalation frameworks.
- Track KPIs and operational metrics; provide actionable insights to leadership.
- Assess opportunities and risks across digital asset use cases, focusing on liquidity, efficiency, settlement, and working capital impacts.
- Monitor developments across blockchain, stablecoin, custody, payments, and regulatory ecosystems.
- Create executive-ready presentations, strategy memos, and business recommendations.
- Lead pilot execution from planning through launch, including governance, testing, vendor diligence, and operational readiness.
- Partner with Risk, Compliance, Legal, Finance, Product, Engineering, and Operations teams to build scalable solutions.
- Support selection and evaluation of custody, wallet, banking, payment, and blockchain infrastructure providers.
Qualifications
Basic Qualifications: 5 or more years of relevant work experience with a Bachelors Degree or at least 2 years of work experience with an Advanced degree (e.g. Masters, MBA, JD, MD) or 0 years of work experience with a PhD.
Preferred Qualifications: 6 or more years of work experience with a Bachelor's Degree or 4 or more years of relevant experience with an Advanced Degree (e.g. Masters, MBA, JD, MD) or up to 3 years of relevant experience with a PhD. Experience in treasury management systems (TMS). Experience with digital assets: stablecoins, custody, wallets, blockchain networks, transaction fees, and ecosystem participants. Incident management, root-cause analysis, and process improvement. Operational controls, governance, audit readiness, and documentation. Strong project management and cross-functional leadership. High ownership, attention to detail, and ability to balance strategy with execution. Experience in identifying regulatory risks and developing related controls. Experience in preparing and presenting management reports. Experience in process documentation and improvement planning. Experience in reconciliation processes and payment regulations. Experience in treasury, payments, fintech, consulting, strategy, or operations with cross-functional project delivery. Degree in Finance, Economics, Business, Analytics, or a related field (or equivalent experience).
Pay
For roles located in the US, the estimated salary range for this position is $129,200.00 to $206,700.00 USD per year, which may include potential sales incentive payments (if applicable). Salary may vary depending on job-related factors which may include knowledge, skills, experience, and location. In addition, this position may be eligible for bonus and equity.
Benefits
- Medical
- Dental
- Vision
- 401(k)
- FSA/HSA
- Life Insurance
- Paid Time Off
- Wellness Program
Schedule
Visa requires at least 3 days in office, expectations of these days will be confirmed by your Hiring Manager.
We should also maybe include travel? Not required. Check for any boilerplate leftover: We removed EEO, etc. Also removed "Information for US Applicants" heading; we incorporated salary and benefits. Check for duplicate lines: none. Check for
- .
Pay: we have salary range: $129,200.00 to $206,700.00 USD per year, which may include potential sales incentive payments (if applicable). Salary may vary depending on job-related factors which may include knowledge, skills, experience, and location. In addition, this position may be eligible for bonus and equity.
We'll put that in