Payments & Product Partnerships Counsel, Americas
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections where posting has real specific content. We need to parse the posting.
We have:
- About The Team And Role: description of team and role. Could be "About the role" or "About the team". We'll use About the role
maybe.
- Responsibilities: bullet list under "What You’ll Do". That's responsibilities.
- Requirements/Qualifications/Skills: "Who You Are" includes experience, skills, etc. Could be split into Requirements and Qualifications and Skills. But we need to avoid thin sections. Could combine into one section "Requirements" or "Qualifications". The instruction: prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements (covering experience, skills, etc.), Pay (since salary ranges given), Benefits (total rewards includes equity, 401k, health, dental, vision, more), Schedule (in-office expectations: at least 3 days a week). Also maybe "Location" but not required.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO statement, Work Eligibility, Diversity statement, What's next?, etc. Also remove navigation, cookie, legal, etc. So we keep substantive content: team description, responsibilities, who you are (experience/skills), total rewards & compensation (pay + benefits), in-office expectations (schedule). Possibly also "About The Team And Role" as about role.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include the details from each bullet.
Let's extract:
About The Team And Role paragraph:
"Adyen provides payments, data, and financial products in a single solution for customers like Meta, Uber, H&M, and Microsoft - making us the financial technology platform of choice. At Adyen, everything we do is engineered for ambition. For our teams, we create an environment with opportunities for our people to succeed, backed by the culture and support to ensure they are enabled to truly own their careers. We are motivated individuals who tackle unique technical challenges at scale and solve them as a team. Together, we deliver innovative and ethical solutions that help businesses achieve their ambitions faster.
About The Team And Role Adyen’s Payment & Product Partnerships Counsel team is newly chartered within the Regulatory organization to build and scale the legal framework for our most critical financial and technology infrastructure relationships. We are looking for a skilled, business-oriented financial services transactions lawyer to join our team in New York, San Francisco, or Chicago, focusing on partnerships in the Americas region. In this role, you will be a principal advisor to our partnerships, product, risk, and compliance teams, responsible for a broad range of transactions and relationships that span financial services ecosystems, business operations and processes, and technology. Adyen’s Regulatory and Legal teams build and operate at the intersection of global financial services law and regulation, commercial strategy, and product innovation. We’re looking for a lawyer who’s at home leading deals to support highly regulated, complex products, and who’s willing to roll up their sleeves and take on projects large and small. Experience with financial services transactions and a working understanding of market-dominant financial services regulatory models are a must; experience in payments, lending, and fintech are a plus, but not required."
We need to keep that as prose under About the role heading.
Responsibilities (What You’ll Do) bullet list:
- Partner with Adyen’s payment and product partnerships teams to help build, manage, and grow strategic relationships with card networks, payment methods, financial institutions, and other financial and technology partners that support Adyen’s product and technical stack.
- Structure, draft, and negotiate strategic infrastructure partnership agreements to enable and optimize Adyen’s payments and financial products across our North America and Latin America markets.
- Collaborate with product, regulatory, compliance, risk, finance, partnerships, and other cross-functional teams to ensure our partner deals conform to our regulatory positions and support our product development, market expansion, and commercial objectives.
- Counsel stakeholders across the business on operation and interpretation of partner agreements (including scheme, network, and operating rules), partner and regulatory ecosystem interdependencies, and corresponding risks and opportunities affecting Adyen’s product and go-to-market strategies.
- Scale our deal cycles and the products they support by generating and maintaining documents and other resources for working with partners, including form agreements, position guides, and implementation briefs.
- Stay current on laws, regulations, and scheme and network rules governing bank-partner relationships, third-party service providers and outsourcing, privacy, data security, consumer protection in financial services, and marketing.
- Build relationships as a trusted advisor by providing clear, practical, actionable guidance in areas involving significant ambiguity or rapid industry evolution.
We need to output as - each.
Who You Are (requirements/qualifications/skills) bullet list (actually paragraph with semicolons). Let's extract each requirement:
- 6+ years experience as a practicing lawyer across in-house and law firm roles, with a significant portion spent working with financial institutions or technology companies on transactions opposite experienced counsel.
- Working dexterity with financial services partnership transactions, where a regulated financial institution and another party (e.g., a network, a fintech, another financial institution) collaborate to stand up and run a unified financial product or service, preferably a payment, credit, or lending product.
- A capable contract generalist who’s able to spot a broad range of legal issues across disciplines (e.g., contract, regulatory, IP, privacy); an avid drafter with a passion for simple, elegant language and an aversion to gratuitous legalese; and, a seasoned lead negotiator who is able to identify and communicate practical, risk-based solutions to deal points persuasively and on the fly.
- Excellent English-language communication skills, with the capacity to translate complex legal and contractual concepts to technical teams and other non-lawyer audiences.
- Constitutional curiosity and enthusiasm to self-educate quickly on complex business models, technologies, and product use cases.
- Strong, risk-tuned judgment, outstanding project management skills, and the ability to juggle competing priorities under tight deadlines.
- Proficiency in Spanish or Portuguese is a strong plus but not required.
We could format as
- each.
Pay: "Total Rewards & Compensation In Chicago the annual base salary range for this role is $160,000 - $230,000. In New York and San Francisco the annual base salary range for this role is $210,000 - 300,000. Compensation is based on factors including qualifications, experience, and location. Total compensation package includes equity (RSUs), 401(k), health, dental, vision, and more."
We need Pay section: include salary ranges. Benefits section: equity (RSUs), 401(k), health, dental, vision, and more. Could combine Pay and Benefits? The instruction: prefer few substantive sections over many thin ones. But we have both Pay and Benefits distinct. Could we combine into "Compensation & Benefits"? However headings list includes Pay, Benefits, Schedule separate. We could create Pay section with salary ranges, Benefits section with equity etc. That's two sections. That's okay.
Schedule: "In-office expectations This role is based out of our New York, San Francisco, or Chicago office. We're an office-first company and expect employees to work in-office at least 3 days a week on average. This approach helps strike a balance between bringing people together for in-person collaboration and learning from each other, while also supporting flexibility."
We'll output Schedule section.
We must not include EEO statement, Work Eligibility, Diversity, What's next?, etc.
We must not include repeated lines.
Now produce HTML fragment:
About the role
... (the about paragraph)
Responsibilities
- ...
...
Requirements
- ...
...
Pay
In Chicago the annual base salary range for this role is $160,000 - $230,000. In New York and San Francisco the annual base salary range for this role is $210,000 - $300,000. Compensation is based on factors including qualifications, experience, and location.
Benefits
Total compensation package includes equity (RSUs), 401(k), health, dental, vision, and more.
Schedule
This role is based out of our New York, San Francisco, or Chicago office. We're an office-first company and expect employees to work in-office at least 3 days a week on average. This approach helps strike a balance between bringing people together for in-person collaboration and learning from each other, while also supporting flexibility.
Check that we didn't repeat job title. Good.
We need to ensure we didn't include any boilerplate like "EEO statement". We removed.
Check that we preserved all substantive info: The about paragraph includes the initial description about Adyen and team. Did we miss any sentences? The about paragraph includes two paragraphs: first about Adyen general, second about team and role. We combined them into one paragraph? We should preserve both. Could separate into two but it's okay as one paragraph with both. Ensure we didn't lose any detail: The first paragraph: "Adyen provides payments, data, and financial products in a single solution for customers like Meta, Uber, H&M, and Microsoft - making us the financial technology platform of choice. At Adyen, everything we do is engineered for ambition. For our teams, we create an environment with opportunities for our people to succeed, backed by the culture and support to ensure they are enabled to truly own their careers. We are motivated individuals who tackle unique technical challenges at scale and solve them as a team. Together, we deliver innovative and ethical solutions that help businesses achieve their ambitions faster."
Second paragraph: "About The Team And Role Adyen’s Payment & Product Partnerships Counsel team is newly chartered within the Regulatory organization to build and scale the legal framework for our most critical financial and technology infrastructure relationships. We are looking for a skilled, business-oriented financial services transactions lawyer to join our team in New York, San Francisco, or Chicago, focusing on partnerships in the Americas region. In this role, you will be a principal advisor to our partnerships, product, risk, and compliance teams, responsible for a broad range of transactions and relationships that span financial services ecosystems, business operations and processes, and technology. Adyen’s Regulatory and Legal teams build and operate at the intersection of global financial services law and regulation, commercial strategy, and product innovation. We’re looking for a lawyer who’s at home leading deals to support highly regulated, complex products, and who’s willing to roll up their sleeves and take on projects large and small. Experience with financial services transactions and a working understanding of market-dominant financial services regulatory models are a must; experience in payments, lending, and fintech are a plus, but not required."
We should keep both. We'll put them as separate
under About the role.
Now responsibilities list: ensure each bullet matches exactly.
Now requirements list: ensure each bullet matches.
Potential nuance: The "Who You Are" includes semicolons inside a bullet; we can keep as one bullet.
Now Pay: we need to include the exact ranges: Chicago $160,000 - $230,000. New York and San Francisco $210,000 - 300,000 (note missing comma? In original: "$210,000 - 300,000." We'll keep as "$210,000 - $300,000"? The original omitted second dollar sign. Should we preserve exactly? It says "$210,000 - 300,000." We should preserve that exactly.
- each.
Pay: "Total Rewards & Compensation In Chicago the annual base salary range for this role is $160,000 - $230,000. In New York and San Francisco the annual base salary range for this role is $210,000 - 300,000. Compensation is based on factors including qualifications, experience, and location. Total compensation package includes equity (RSUs), 401(k), health, dental, vision, and more."
We need Pay section: include salary ranges. Benefits section: equity (RSUs), 401(k), health, dental, vision, and more. Could combine Pay and Benefits? The instruction: prefer few substantive sections over many thin ones. But we have both Pay and Benefits distinct. Could we combine into "Compensation & Benefits"? However headings list includes Pay, Benefits, Schedule separate. We could create Pay section with salary ranges, Benefits section with equity etc. That's two sections. That's okay.
Schedule: "In-office expectations This role is based out of our New York, San Francisco, or Chicago office. We're an office-first company and expect employees to work in-office at least 3 days a week on average. This approach helps strike a balance between bringing people together for in-person collaboration and learning from each other, while also supporting flexibility."
We'll output Schedule section.
We must not include EEO statement, Work Eligibility, Diversity, What's next?, etc.
We must not include repeated lines.
Now produce HTML fragment:
About the role
... (the about paragraph)
Responsibilities
- ... ...
Requirements
- ... ...
Pay
In Chicago the annual base salary range for this role is $160,000 - $230,000. In New York and San Francisco the annual base salary range for this role is $210,000 - $300,000. Compensation is based on factors including qualifications, experience, and location.
Benefits
Total compensation package includes equity (RSUs), 401(k), health, dental, vision, and more.
Schedule
This role is based out of our New York, San Francisco, or Chicago office. We're an office-first company and expect employees to work in-office at least 3 days a week on average. This approach helps strike a balance between bringing people together for in-person collaboration and learning from each other, while also supporting flexibility.
Check that we didn't repeat job title. Good. We need to ensure we didn't include any boilerplate like "EEO statement". We removed. Check that we preserved all substantive info: The about paragraph includes the initial description about Adyen and team. Did we miss any sentences? The about paragraph includes two paragraphs: first about Adyen general, second about team and role. We combined them into one paragraph? We should preserve both. Could separate into twobut it's okay as one paragraph with both. Ensure we didn't lose any detail: The first paragraph: "Adyen provides payments, data, and financial products in a single solution for customers like Meta, Uber, H&M, and Microsoft - making us the financial technology platform of choice. At Adyen, everything we do is engineered for ambition. For our teams, we create an environment with opportunities for our people to succeed, backed by the culture and support to ensure they are enabled to truly own their careers. We are motivated individuals who tackle unique technical challenges at scale and solve them as a team. Together, we deliver innovative and ethical solutions that help businesses achieve their ambitions faster." Second paragraph: "About The Team And Role Adyen’s Payment & Product Partnerships Counsel team is newly chartered within the Regulatory organization to build and scale the legal framework for our most critical financial and technology infrastructure relationships. We are looking for a skilled, business-oriented financial services transactions lawyer to join our team in New York, San Francisco, or Chicago, focusing on partnerships in the Americas region. In this role, you will be a principal advisor to our partnerships, product, risk, and compliance teams, responsible for a broad range of transactions and relationships that span financial services ecosystems, business operations and processes, and technology. Adyen’s Regulatory and Legal teams build and operate at the intersection of global financial services law and regulation, commercial strategy, and product innovation. We’re looking for a lawyer who’s at home leading deals to support highly regulated, complex products, and who’s willing to roll up their sleeves and take on projects large and small. Experience with financial services transactions and a working understanding of market-dominant financial services regulatory models are a must; experience in payments, lending, and fintech are a plus, but not required." We should keep both. We'll put them as separate
under About the role. Now responsibilities list: ensure each bullet matches exactly. Now requirements list: ensure each bullet matches. Potential nuance: The "Who You Are" includes semicolons inside a bullet; we can keep as one bullet. Now Pay: we need to include the exact ranges: Chicago $160,000 - $230,000. New York and San Francisco $210,000 - 300,000 (note missing comma? In original: "$210,000 - 300,000." We'll keep as "$210,000 - $300,000"? The original omitted second dollar sign. Should we preserve exactly? It says "$210,000 - 300,000." We should preserve that exactly.