Senior Talent Acquisition Partner, GTM
h3 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 as a heading? The instructions say we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. About Us is not listed but could be considered maybe "About Us" not required. However we can include a short paragraph about company? The instruction says preserve all substantive information; we can include it's okay to include as
before sections? Probably we can include a
about the company as intro. But they said 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. So we can include a short
for location (Available Locations Austin, US) maybe as metadata.
We need to include sections only when posting has real specific content.
Let's identify sections:
- About the role: present: "We are hiring for a Senior Talent Acquisition Business Partner to join our Americas (AMER) team. In this role, you will act as a true talent advisor and go-to-market specialist, driving the expansion of hiring across the region. You will operate autonomously, utilizing your deep market expertise, AI-driven strategies, and extensive network to hire top-tier talent for Cloudflare."
- Responsibilities: list bullet points (multiple). We'll put
- each.
- Desirable Skills, Knowledge, And Experience: list bullet points.
- Compensation: "Compensation Equity This role is eligible to participate in Cloudflare’s equity plan." That's specific content about equity. So we can have a section maybe "Compensation" with
about equity.
- Benefits: there is a Benefits section with list of benefits. So we include Benefits heading with
- .
- Pay: not specified beyond equity; no salary numbers. So we should NOT create Pay section because no specific pay.
- Schedule: not specified.
- About Us: maybe we can include as a
before sections, not as heading. The instruction says we can use
for section headings (list). It doesn't forbid other headings, but we should follow. Probably we can include a
about company description.
- Available Locations: we can include as a short
maybe "Available Locations: Austin, US". That's minor metadata.
We must remove boilerplate: EEO, equal opportunity, accommodations, legal, export control, etc. Also remove "Please note that applicants who progress..." etc. Also remove "What Makes Cloudflare Special?" maybe that's substantive? It describes projects like Galileo, Athenian Project, 1.1.1.1. That is substantive about company culture/mission. Could be included as a
maybe under About Us or as a separate section? Not in list of headings but we could include as a
under About Us. The instruction says preserve ALL substantive information; we should keep that content. So we need to include the "What Makes Cloudflare Special?" paragraph(s) and bullet-like description of projects. It's not a list but prose. We'll keep as
.
We also need to keep "Available Locations Austin, US". We'll put as
.
Now structure:
About Us paragraph(s) maybe combine the first paragraph about mission etc. Then maybe the "What Makes Cloudflare Special?" paragraph(s). Could combine.
But we need to avoid duplication: The About Us section includes mission description, then later "What Makes Cloudflare Special?" includes more detail. We'll keep both.
We'll output:
About Us: At Cloudflare, we are on a mission to help build a better Internet....
Then maybe another for What Makes Cloudflare Special? content.
Then
Available Locations: Austin, US
Then About the Role
We are hiring for a Senior Talent Acquisition Business Partner...
Then Responsibilities
- ...
...
Then Desirable Skills, Knowledge, And Experience
- ...
...
Then Compensation
This role is eligible to participate in Cloudflare’s equity plan.
Then Benefits
- ...
...
We must not include Pay or Schedule sections.
Check that we didn't include any boilerplate: Remove EEO, accommodations, legal, export control, etc. Also remove "Please note that applicants who progress..." etc. Also remove "More details about this will be available at that stage..." etc. Also remove "This position may require access to information protected under U.S. export control laws..." etc. Also remove "Cloudflare is proud to be an equal opportunity employer..." etc. Also remove "We are an AA/Veterans/Disabled Employer." etc. Also remove accommodation request details.
Also remove "Available Locations Austin, US" maybe we keep as short p.
Now let's extract exact text.
About Us paragraph: "At Cloudflare, we are on a mission to help build a better Internet. Today the company runs one of the world’s largest networks that powers millions of websites and other Internet properties for customers ranging from individual bloggers to SMBs to Fortune 500 companies. Cloudflare protects and accelerates any Internet application online without adding hardware, installing software, or changing a line of code. Internet properties powered by Cloudflare all have web traffic routed through its intelligent global network, which gets smarter with every request. As a result, they see significant improvement in performance and a decrease in spam and other attacks. Cloudflare was named to Entrepreneur Magazine’s Top Company Cultures list and ranked among the World’s Most Innovative Companies by Fast Company. At Cloudflare, we’re not looking for people who wait for a polished roadmap; we’re looking for the builders who see the cracks in the Internet that everyone else has simply learned to live with. We value candidates who have the instinct to spot a "normalized" problem and the AI-native curiosity to create a solution using the latest tools. Our culture is built on iteration, leveraging AI to ship faster today to make it better tomorrow, while ensuring that every improvement, no matter how small, is shared across the team to lift everyone up. If you’re the type of person who values curiosity over bureaucracy, and that AI is a partner in solving tough problems to keep the Internet moving forward, you’ll fit right in."
What Makes Cloudflare Special? paragraph: "We’re not just a highly ambitious, large-scale technology company. We’re a highly ambitious, large-scale technology company with a soul. Fundamental to our mission to help build a better Internet is protecting the free and open Internet. Project Galileo: Since 2014, we've equipped more than 2,400 journalism and civil society organizations in 111 countries with powerful tools to defend themselves against attacks that would otherwise censor their work, technology already used by Cloudflare’s enterprise customers--at no cost. Athenian Project: In 2017, we created the Athenian Project to ensure that state and local governments have the highest level of protection and reliability for free, so that their constituents have access to election information and voter registration. Since the project, we've provided services to more than 425 local government election websites in 33 states. 1.1.1.1: We released 1.1.1.1 to help fix the foundation of the Internet by building a faster, more secure and privacy-centric public DNS resolver. This is available publicly for everyone to use - it is the first consumer-focused service Cloudflare has ever released. Here’s the deal - we don’t store client IP addresses never, ever. We will continue to abide by our privacy commitment and ensure that no user data is sold to advertisers or used to target consumers."
Available Locations: "Available Locations Austin, US"
About the Role: "We are hiring for a Senior Talent Acquisition Business Partner to join our Americas (AMER) team. In this role, you will act as a true talent advisor and go-to-market specialist, driving the expansion of hiring across the region. You will operate autonomously, utilizing your deep market expertise, AI-driven strategies, and extensive network to hire top-tier talent for Cloudflare."
Responsibilities list: Need to extract each bullet.
From text:
"End-to-End Recruitment & Talent Strategy: Build and execute comprehensive talent strategies to help hiring leaders build high-performing teams, functioning similarly to how a salesperson puts together a go-to-market plan.
Proactive Pipeline & Passive Candidate Outreach: Draw upon an extensive network of industry contacts to build proactive pipeline strategies for a variety of roles.
Stakeholder Management & Advising: Build and maintain solid relationships with AMER leadership and cross-functional stakeholders, including Finance, HRBPs, and compensation teams.
AI-Agent Integration & Process Optimization: Partner with internal automated AI agents and generative tools to eliminate legacy manual tasks, optimize administrative outreach workflows at scale, and synthesize complex market data to inform regional talent strategies.
Data Utilization & Analytics: Leverage foundational data layers and recruitment analytics to inform talent strategies, actively analyzing metrics such as time-to-hire and source efficiency to drive optimal operational decisions.
Employer Branding & Market Awareness: Lead and execute strategic employer branding initiatives tailored to the AMER market to elevate Cloudflare's profile as a top destination for talent."
We'll make each as - .
Desirable Skills, Knowledge, And Experience list:
"Strategic Problem Solving: Ability to operate two "plays" ahead, anticipating potential bottlenecks before they materialize, and resolving complex organizational issues with high autonomy.
Negotiation & Closing Skills: Effective negotiation capabilities to secure top-tier candidates, driven by a deep understanding of Cloudflare's unique value proposition.
AI & Ecosystem Proficiency: Demonstrated capability to leverage automated workflows, AI-powered sourcing environments, and LLMs for complex boolean logic, market mapping, and productivity multiplication.
Candidate Experience Focus: Strong organizational skills to eliminate operational friction, ensuring clear communication and proactive engagement throughout the interview lifecycle.
Communication & Feedback: Exceptional written and verbal communication skills with the ability to influence and advise senior stakeholders across the Americas region.
Adaptability & Self-Direction: Comfort thriving in ever-changing environments, taking complete responsibility for outcomes while seamlessly navigating an evolving technological and organizational landscape."
We'll make each
- .
Compensation: "Compensation Equity This role is eligible to participate in Cloudflare’s equity plan." Might need to format as a sentence: "This role is eligible to participate in Cloudflare’s equity plan."
Benefits list: Extract bullet points.
From text:
"Health & Welfare Benefits
Medical/Rx Insurance
Dental Insurance
Vision Insurance
Flexible Spending Accounts
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 as a heading? The instructions say we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. About Us is not listed but could be considered maybe "About Us" not required. However we can include a short paragraph about company? The instruction says preserve all substantive information; we can include it's okay to include as
before sections? Probably we can include a
about the company as intro. But they said 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. So we can include a short
for location (Available Locations Austin, US) maybe as metadata. We need to include sections only when posting has real specific content. Let's identify sections: - About the role: present: "We are hiring for a Senior Talent Acquisition Business Partner to join our Americas (AMER) team. In this role, you will act as a true talent advisor and go-to-market specialist, driving the expansion of hiring across the region. You will operate autonomously, utilizing your deep market expertise, AI-driven strategies, and extensive network to hire top-tier talent for Cloudflare." - Responsibilities: list bullet points (multiple). We'll put
- each.
- Desirable Skills, Knowledge, And Experience: list bullet points.
- Compensation: "Compensation Equity This role is eligible to participate in Cloudflare’s equity plan." That's specific content about equity. So we can have a section maybe "Compensation" with
about equity. - Benefits: there is a Benefits section with list of benefits. So we include Benefits heading with
- .
- Pay: not specified beyond equity; no salary numbers. So we should NOT create Pay section because no specific pay.
- Schedule: not specified.
- About Us: maybe we can include as a
before sections, not as heading. The instruction says we can use
for section headings (list). It doesn't forbid other headings, but we should follow. Probably we can include a
about company description. - Available Locations: we can include as a short
maybe "Available Locations: Austin, US". That's minor metadata. We must remove boilerplate: EEO, equal opportunity, accommodations, legal, export control, etc. Also remove "Please note that applicants who progress..." etc. Also remove "What Makes Cloudflare Special?" maybe that's substantive? It describes projects like Galileo, Athenian Project, 1.1.1.1. That is substantive about company culture/mission. Could be included as a
maybe under About Us or as a separate section? Not in list of headings but we could include as a
under About Us. The instruction says preserve ALL substantive information; we should keep that content. So we need to include the "What Makes Cloudflare Special?" paragraph(s) and bullet-like description of projects. It's not a list but prose. We'll keep as
. We also need to keep "Available Locations Austin, US". We'll put as
. Now structure:
About Us paragraph(s) maybe combine the first paragraph about mission etc. Then maybe the "What Makes Cloudflare Special?" paragraph(s). Could combine. But we need to avoid duplication: The About Us section includes mission description, then later "What Makes Cloudflare Special?" includes more detail. We'll keep both. We'll output:
About Us: At Cloudflare, we are on a mission to help build a better Internet....
Then maybe anotherfor What Makes Cloudflare Special? content. Then
Available Locations: Austin, US
ThenAbout the Role
We are hiring for a Senior Talent Acquisition Business Partner...
ThenResponsibilities
- ... ...
Desirable Skills, Knowledge, And Experience
- ... ...
Compensation
This role is eligible to participate in Cloudflare’s equity plan.
ThenBenefits
- ... ...
- . Desirable Skills, Knowledge, And Experience list: "Strategic Problem Solving: Ability to operate two "plays" ahead, anticipating potential bottlenecks before they materialize, and resolving complex organizational issues with high autonomy. Negotiation & Closing Skills: Effective negotiation capabilities to secure top-tier candidates, driven by a deep understanding of Cloudflare's unique value proposition. AI & Ecosystem Proficiency: Demonstrated capability to leverage automated workflows, AI-powered sourcing environments, and LLMs for complex boolean logic, market mapping, and productivity multiplication. Candidate Experience Focus: Strong organizational skills to eliminate operational friction, ensuring clear communication and proactive engagement throughout the interview lifecycle. Communication & Feedback: Exceptional written and verbal communication skills with the ability to influence and advise senior stakeholders across the Americas region. Adaptability & Self-Direction: Comfort thriving in ever-changing environments, taking complete responsibility for outcomes while seamlessly navigating an evolving technological and organizational landscape." We'll make each
- . Compensation: "Compensation Equity This role is eligible to participate in Cloudflare’s equity plan." Might need to format as a sentence: "This role is eligible to participate in Cloudflare’s equity plan." Benefits list: Extract bullet points. From text: "Health & Welfare Benefits Medical/Rx Insurance Dental Insurance Vision Insurance Flexible Spending Accounts
- .
- Pay: not specified beyond equity; no salary numbers. So we should NOT create Pay section because no specific pay.
- Schedule: not specified.
- About Us: maybe we can include as a