Senior Lead Management Specialist
Cloudflare · New York, NY · 1 mo ago
Marketing$138k–$190k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the posting.
We have:
- About Us (but we should not repeat job title; we can include About Us? The instruction says use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the posting.
We have:
- About Us (but we should not repeat job title; we can include About Us? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow those examples. Probably we should include sections that match content: About the role (the "About The Role" paragraph), Responsibilities (the "What You'll Do" bullet list), Skills, Knowledge, And Experience (skills), Compensation (Pay), Benefits, maybe "What Makes Cloudflare Special?" but not required. We should not include About Us? Could be considered filler but it's substantive about company. However instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but we should prefer those. Probably include About the role, Responsibilities, Skills, Knowledge, And Experience (maybe as Skills), Compensation (Pay), Benefits. Also maybe "First-Year Outcomes" could be considered Responsibilities? But it's outcomes; maybe we can include under Responsibilities or separate section like "Goals". But not in list; we could omit if not matching. Better to stick to given headings.
We must not repeat job title as heading. The job title is "Senior Lead Management Specialist". Not present.
We must not put Job ID/requisition numbers as headings.
We must remove boilerplate: cookie/navigation/legal/EEO etc. So we need to strip out the EEO statement, accommodation info, etc.
We must preserve all substantive information.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
Sections:
1. About the role: The paragraph after "About The Role". It's multiple sentences. We'll put in
.
2. Responsibilities: The "What You'll Do" section includes bullet points (each line starting with a bold heading? Actually it's like:
Architect & Run the Journey Operations Engine
Own the end-to-end lead lifecycle...
Monitor lead-flow integrity...
Refactor legacy batch campaign...
Drive Automation via Cloudflare OS
...
Own Governance, Lifecycle Logic & Data Architecture
...
Empower Sales Front Lines & Partner Cross-Functionally
...
First-Year Outcomes
...
These are headings with sub-bullets? Actually each heading is a bold phrase then description. We need to treat as list items? The instruction: use
- for any list of duties/requirements/benefits. So we can make each duty as
- . The sub-bullets under each heading are sentences; we can keep them inside the
- as prose.
Thus we can create a
with each duty as - . The duty headings: "Architect & Run the Journey Operations Engine", "Drive Automation via Cloudflare OS", "Own Governance, Lifecycle Logic & Data Architecture", "Empower Sales Front Lines & Partner Cross-Functionally". Then after that there is "First-Year Outcomes" which is a set of outcomes; could be considered responsibilities or separate section. Could be included as duties as well. But maybe better to treat as separate section "Outcomes"? Not in allowed headings. Could include under Responsibilities as part of list.
We'll include all bullet-like items as
- .
Thus Responsibilities
with several - items.
3. Skills, Knowledge, And Experience: This is a list of requirements. We'll make a
- for each bullet.
The bullet list:
- 7–10 years of experience bridging B2B marketing operations with systems engineering, revenue operations, or MarTech architecture.
- Deep mastery of enterprise MarTech and CRM platforms—specifically Marketo, Salesforce, and advanced lead routing engines (e.g., LeanData).
- Strong engineering aptitude with practical experience using APIs (REST/SOAP), Webhooks, SQL, or scripting (Python, JavaScript, or Bash) to interface with platforms and automate data flows.
- Demonstrated ability to design state logic, lifecycle state transitions, and complex routing architectures with software-level change management discipline.
- Proven track record of automating manual MOPs workflows (list imports, campaign provisioning, enrichment) through workflow engines or custom scripts.
- Strong command of data governance, SLA monitoring, data layer schema, and account-to-lead matching models.
- Experience partnering directly with Field Marketing, BDR/SDR managers, Sales Ops, BizApps, and Data Engineering teams.
- A systems-thinking mindset—you view marketing operations as an engine of connected microservices and default to automating the repeatable.
Then "Bonus Points" subsection: we could include as part of Skills or separate? It's still skills/bonus. We'll include as
- under Skills as well.
Bonus Points:
- Experience building on internal orchestration platforms, worker nodes (e.g., Cloudflare Workers), or IPaaS environments.
- Exposure to server-side tracking, edge technologies (e.g., Zaraz), CDPs, and account-based intent platforms (Demandbase, 6sense).
- Working knowledge of global compliance frameworks (GDPR, CCPA) implemented programmatically across data pipelines.
We'll include them.
4. Compensation: The "Compensation" section includes location-based salary ranges. We'll make a
with that info. Also mention "Equity This role is eligible to participate in Cloudflare’s equity plan." That's also compensation/benefit. We'll include in same section.
Thus Pay section:
Pay
Compensation may be adjusted depending on work location. For San Francisco Bay Area based hires: Estimated annual salary of $138,000 - $190,000. For New York City based hires: Estimated annual salary of $132,000 - $182,000. Equity: This role is eligible to participate in Cloudflare’s equity plan.
5. Benefits: The Benefits section includes list of benefits. We'll make Benefits
- ... each benefit.
List:
- Health & Welfare Benefits
- Medical/Rx Insurance
- Dental Insurance
- Vision Insurance
- Flexible Spending Accounts
- Commuter Spending Accounts
- Fertility & Family Forming Benefits
- On-demand mental health support and Employee Assistance Program
- Global Travel Medical Insurance
- Financial Benefits
- Short and Long Term Disability Insurance
- Life & Accident Insurance
- 401(k) Retirement Savings Plan
- Employee Stock Participation Plan
- Time Off
- Flexible paid time off covering vacation and sick leave
- Leave programs, including parental, pregnancy health, medical, and bereavement leave
We could flatten into a single list or nested. Simpler: each bullet as
- with the benefit description. We'll keep as flat list.
Thus Benefits
with items: Medical/Rx Insurance, Dental Insurance, Vision Insurance, Flexible Spending Accounts, Commuter Spending Accounts, Fertility & Family Forming Benefits, On-demand mental health support and Employee Assistance Program, Global Travel Medical Insurance, Short and Long Term Disability Insurance, Life & Accident Insurance, 401(k) Retirement Savings Plan, Employee Stock Participation Plan, Flexible paid time off covering vacation and sick leave, Leave programs, including parental, pregnancy health, medical, and bereavement leave.
We could also include the introductory sentence: "Cloudflare offers a complete package of benefits and programs to support you and your family. Our benefits programs can help you pay health care expenses, support caregiving, build capital for the future and make life a little easier and fun! The below is a description of our benefits for employees in the United States, and benefits may vary for employees based outside the U.S." That's prose; we can put as before the list.
Thus Benefits section:
Benefits
Cloudflare offers a complete package of benefits and programs to support you and your family. Our benefits programs can help you pay health care expenses, support caregiving, build capital for the future and make life a little easier and fun! The below is a description of our benefits for employees in the United States, and benefits may vary for employees based outside the U.S.
...
Now we need to ensure we don't include sections with placeholder content. All sections have real content.
We should not include About Us? It's not in the list but could be included as a section but not required. Safer to omit.
We also need to remove EEO boilerplate etc. We'll strip those paragraphs.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- Architect & Run the Journey Operations Engine: Own the end-to-end lead lifecycle, routing algorithms, and queue architecture, ensuring 100% of qualified leads and intent signals are processed without delay or data drop. Monitor lead-flow integrity continuously across platforms (Marketo, Salesforce, LeanData), writing automated health checks, error logging, and alert triggers to resolve bottlenecks before they impact sales. Refactor legacy batch campaign operations into automated, real-time, event-driven routing logic.
- Drive Automation via Cloudflare OS: Treat operational tech debt as bugs to be resolved through code, API integrations, webhooks, or programmatic rules engine builds. Design extensible routing frameworks that give regional field marketing teams the agility to run local campaigns while maintaining strict global system standards.
- Own Governance, Lifecycle Logic & Data Architecture: Own the lead scoring, account-to-lead matching, lifecycle states, and routing logic as a version-controlled source of truth. Partner with Data Engineering and BI teams to optimize schema, identity resolution at the web edge, and account telemetry hygiene across the MarTech stack. Define and govern logic change controls, API integration standards, and SLA tracking across marketing and sales systems.
- Empower Sales Front Lines & Partner Cross-Functionally: Automate the delivery of buyer intent telemetry (e.g., intent topics, event participation) directly into sales-facing views to accelerate sales outreach. Serve as the senior systems counterpart to Field Marketing leaders, Sales Development (BDR/SDR), Sales Operations, and BizApps to streamline GTM handoffs. Establish a continuous feedback loop with Sales to measure lead quality, velocity, and stage conversion performance.
- First-Year Outcomes: Zero Lead Leakage & Sub-15 Minute Routing: Eliminate dropped, stuck, or misrouted leads across regional queues, ensuring 100% of qualified leads and intent signals reach the correct rep within 15 minutes. Context-Rich Handoffs for Reps: Automate the delivery of buyer intent telemetry to increase initial sales engagement and conversion rates. Rapid Campaign Processing & SLA Enforcement: Achieve a 24-hour processing standard for all regional events, webinars, and field campaign lists through Cloudflare OS automation workflows. Transparent Account Journey Visibility: Deploy clear, self-serve account-level engagement tracking within Salesforce so sales teams can identify active, high-intent target accounts prior to formal form fills. Shorter Sales Cycles & Increased Pipeline Velocity: Measurably reduce conversion timelines through automated lead prioritization and streamlined handoff workflows.
Skills
- 7–10 years of experience bridging B2B marketing operations with systems engineering, revenue operations, or MarTech
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but we should prefer those. Probably include About the role, Responsibilities, Skills, Knowledge, And Experience (maybe as Skills), Compensation (Pay), Benefits. Also maybe "First-Year Outcomes" could be considered Responsibilities? But it's outcomes; maybe we can include under Responsibilities or separate section like "Goals". But not in list; we could omit if not matching. Better to stick to given headings.
We must not repeat job title as heading. The job title is "Senior Lead Management Specialist". Not present.
We must not put Job ID/requisition numbers as headings.
We must remove boilerplate: cookie/navigation/legal/EEO etc. So we need to strip out the EEO statement, accommodation info, etc.
We must preserve all substantive information.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
Sections:
1. About the role: The paragraph after "About The Role". It's multiple sentences. We'll put in
.
2. Responsibilities: The "What You'll Do" section includes bullet points (each line starting with a bold heading? Actually it's like:
Architect & Run the Journey Operations Engine
Own the end-to-end lead lifecycle...
Monitor lead-flow integrity...
Refactor legacy batch campaign...
Drive Automation via Cloudflare OS
...
Own Governance, Lifecycle Logic & Data Architecture
...
Empower Sales Front Lines & Partner Cross-Functionally
...
First-Year Outcomes
...
These are headings with sub-bullets? Actually each heading is a bold phrase then description. We need to treat as list items? The instruction: use
- for any list of duties/requirements/benefits. So we can make each duty as
- . The sub-bullets under each heading are sentences; we can keep them inside the
- as prose.
Thus we can create a
with each duty as - . The duty headings: "Architect & Run the Journey Operations Engine", "Drive Automation via Cloudflare OS", "Own Governance, Lifecycle Logic & Data Architecture", "Empower Sales Front Lines & Partner Cross-Functionally". Then after that there is "First-Year Outcomes" which is a set of outcomes; could be considered responsibilities or separate section. Could be included as duties as well. But maybe better to treat as separate section "Outcomes"? Not in allowed headings. Could include under Responsibilities as part of list.
We'll include all bullet-like items as
- .
Thus Responsibilities
with several - items.
3. Skills, Knowledge, And Experience: This is a list of requirements. We'll make a
- for each bullet.
The bullet list:
- 7–10 years of experience bridging B2B marketing operations with systems engineering, revenue operations, or MarTech architecture.
- Deep mastery of enterprise MarTech and CRM platforms—specifically Marketo, Salesforce, and advanced lead routing engines (e.g., LeanData).
- Strong engineering aptitude with practical experience using APIs (REST/SOAP), Webhooks, SQL, or scripting (Python, JavaScript, or Bash) to interface with platforms and automate data flows.
- Demonstrated ability to design state logic, lifecycle state transitions, and complex routing architectures with software-level change management discipline.
- Proven track record of automating manual MOPs workflows (list imports, campaign provisioning, enrichment) through workflow engines or custom scripts.
- Strong command of data governance, SLA monitoring, data layer schema, and account-to-lead matching models.
- Experience partnering directly with Field Marketing, BDR/SDR managers, Sales Ops, BizApps, and Data Engineering teams.
- A systems-thinking mindset—you view marketing operations as an engine of connected microservices and default to automating the repeatable.
Then "Bonus Points" subsection: we could include as part of Skills or separate? It's still skills/bonus. We'll include as
- under Skills as well.
Bonus Points:
- Experience building on internal orchestration platforms, worker nodes (e.g., Cloudflare Workers), or IPaaS environments.
- Exposure to server-side tracking, edge technologies (e.g., Zaraz), CDPs, and account-based intent platforms (Demandbase, 6sense).
- Working knowledge of global compliance frameworks (GDPR, CCPA) implemented programmatically across data pipelines.
We'll include them.
4. Compensation: The "Compensation" section includes location-based salary ranges. We'll make a
with that info. Also mention "Equity This role is eligible to participate in Cloudflare’s equity plan." That's also compensation/benefit. We'll include in same section.
Thus Pay section:
Pay
Compensation may be adjusted depending on work location. For San Francisco Bay Area based hires: Estimated annual salary of $138,000 - $190,000. For New York City based hires: Estimated annual salary of $132,000 - $182,000. Equity: This role is eligible to participate in Cloudflare’s equity plan.
5. Benefits: The Benefits section includes list of benefits. We'll make Benefits
- ... each benefit.
List:
- Health & Welfare Benefits
- Medical/Rx Insurance
- Dental Insurance
- Vision Insurance
- Flexible Spending Accounts
- Commuter Spending Accounts
- Fertility & Family Forming Benefits
- On-demand mental health support and Employee Assistance Program
- Global Travel Medical Insurance
- Financial Benefits
- Short and Long Term Disability Insurance
- Life & Accident Insurance
- 401(k) Retirement Savings Plan
- Employee Stock Participation Plan
- Time Off
- Flexible paid time off covering vacation and sick leave
- Leave programs, including parental, pregnancy health, medical, and bereavement leave
We could flatten into a single list or nested. Simpler: each bullet as
- with the benefit description. We'll keep as flat list.
Thus Benefits
with items: Medical/Rx Insurance, Dental Insurance, Vision Insurance, Flexible Spending Accounts, Commuter Spending Accounts, Fertility & Family Forming Benefits, On-demand mental health support and Employee Assistance Program, Global Travel Medical Insurance, Short and Long Term Disability Insurance, Life & Accident Insurance, 401(k) Retirement Savings Plan, Employee Stock Participation Plan, Flexible paid time off covering vacation and sick leave, Leave programs, including parental, pregnancy health, medical, and bereavement leave.
We could also include the introductory sentence: "Cloudflare offers a complete package of benefits and programs to support you and your family. Our benefits programs can help you pay health care expenses, support caregiving, build capital for the future and make life a little easier and fun! The below is a description of our benefits for employees in the United States, and benefits may vary for employees based outside the U.S." That's prose; we can put as before the list.
Thus Benefits section:
Benefits
Cloudflare offers a complete package of benefits and programs to support you and your family. Our benefits programs can help you pay health care expenses, support caregiving, build capital for the future and make life a little easier and fun! The below is a description of our benefits for employees in the United States, and benefits may vary for employees based outside the U.S.
...
Now we need to ensure we don't include sections with placeholder content. All sections have real content.
We should not include About Us? It's not in the list but could be included as a section but not required. Safer to omit.
We also need to remove EEO boilerplate etc. We'll strip those paragraphs.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- Architect & Run the Journey Operations Engine: Own the end-to-end lead lifecycle, routing algorithms, and queue architecture, ensuring 100% of qualified leads and intent signals are processed without delay or data drop. Monitor lead-flow integrity continuously across platforms (Marketo, Salesforce, LeanData), writing automated health checks, error logging, and alert triggers to resolve bottlenecks before they impact sales. Refactor legacy batch campaign operations into automated, real-time, event-driven routing logic.
- Drive Automation via Cloudflare OS: Treat operational tech debt as bugs to be resolved through code, API integrations, webhooks, or programmatic rules engine builds. Design extensible routing frameworks that give regional field marketing teams the agility to run local campaigns while maintaining strict global system standards.
- Own Governance, Lifecycle Logic & Data Architecture: Own the lead scoring, account-to-lead matching, lifecycle states, and routing logic as a version-controlled source of truth. Partner with Data Engineering and BI teams to optimize schema, identity resolution at the web edge, and account telemetry hygiene across the MarTech stack. Define and govern logic change controls, API integration standards, and SLA tracking across marketing and sales systems.
- Empower Sales Front Lines & Partner Cross-Functionally: Automate the delivery of buyer intent telemetry (e.g., intent topics, event participation) directly into sales-facing views to accelerate sales outreach. Serve as the senior systems counterpart to Field Marketing leaders, Sales Development (BDR/SDR), Sales Operations, and BizApps to streamline GTM handoffs. Establish a continuous feedback loop with Sales to measure lead quality, velocity, and stage conversion performance.
- First-Year Outcomes: Zero Lead Leakage & Sub-15 Minute Routing: Eliminate dropped, stuck, or misrouted leads across regional queues, ensuring 100% of qualified leads and intent signals reach the correct rep within 15 minutes. Context-Rich Handoffs for Reps: Automate the delivery of buyer intent telemetry to increase initial sales engagement and conversion rates. Rapid Campaign Processing & SLA Enforcement: Achieve a 24-hour processing standard for all regional events, webinars, and field campaign lists through Cloudflare OS automation workflows. Transparent Account Journey Visibility: Deploy clear, self-serve account-level engagement tracking within Salesforce so sales teams can identify active, high-intent target accounts prior to formal form fills. Shorter Sales Cycles & Increased Pipeline Velocity: Measurably reduce conversion timelines through automated lead prioritization and streamlined handoff workflows.
Skills
- 7–10 years of experience bridging B2B marketing operations with systems engineering, revenue operations, or MarTech
for prose. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Sections: 1. About the role: The paragraph after "About The Role". It's multiple sentences. We'll put in
. 2. Responsibilities: The "What You'll Do" section includes bullet points (each line starting with a bold heading? Actually it's like: Architect & Run the Journey Operations Engine Own the end-to-end lead lifecycle... Monitor lead-flow integrity... Refactor legacy batch campaign... Drive Automation via Cloudflare OS ... Own Governance, Lifecycle Logic & Data Architecture ... Empower Sales Front Lines & Partner Cross-Functionally ... First-Year Outcomes ... These are headings with sub-bullets? Actually each heading is a bold phrase then description. We need to treat as list items? The instruction: use
- for any list of duties/requirements/benefits. So we can make each duty as
- . The sub-bullets under each heading are sentences; we can keep them inside the
- as prose.
Thus we can create a
- with each duty as
- . The duty headings: "Architect & Run the Journey Operations Engine", "Drive Automation via Cloudflare OS", "Own Governance, Lifecycle Logic & Data Architecture", "Empower Sales Front Lines & Partner Cross-Functionally". Then after that there is "First-Year Outcomes" which is a set of outcomes; could be considered responsibilities or separate section. Could be included as duties as well. But maybe better to treat as separate section "Outcomes"? Not in allowed headings. Could include under Responsibilities as part of list. We'll include all bullet-like items as
- .
Thus Responsibilities
- with several
- items.
3. Skills, Knowledge, And Experience: This is a list of requirements. We'll make a
- for each bullet. The bullet list: - 7–10 years of experience bridging B2B marketing operations with systems engineering, revenue operations, or MarTech architecture. - Deep mastery of enterprise MarTech and CRM platforms—specifically Marketo, Salesforce, and advanced lead routing engines (e.g., LeanData). - Strong engineering aptitude with practical experience using APIs (REST/SOAP), Webhooks, SQL, or scripting (Python, JavaScript, or Bash) to interface with platforms and automate data flows. - Demonstrated ability to design state logic, lifecycle state transitions, and complex routing architectures with software-level change management discipline. - Proven track record of automating manual MOPs workflows (list imports, campaign provisioning, enrichment) through workflow engines or custom scripts. - Strong command of data governance, SLA monitoring, data layer schema, and account-to-lead matching models. - Experience partnering directly with Field Marketing, BDR/SDR managers, Sales Ops, BizApps, and Data Engineering teams. - A systems-thinking mindset—you view marketing operations as an engine of connected microservices and default to automating the repeatable. Then "Bonus Points" subsection: we could include as part of Skills or separate? It's still skills/bonus. We'll include as
- under Skills as well.
Bonus Points:
- Experience building on internal orchestration platforms, worker nodes (e.g., Cloudflare Workers), or IPaaS environments.
- Exposure to server-side tracking, edge technologies (e.g., Zaraz), CDPs, and account-based intent platforms (Demandbase, 6sense).
- Working knowledge of global compliance frameworks (GDPR, CCPA) implemented programmatically across data pipelines.
We'll include them.
4. Compensation: The "Compensation" section includes location-based salary ranges. We'll make a
with that info. Also mention "Equity This role is eligible to participate in Cloudflare’s equity plan." That's also compensation/benefit. We'll include in same section. Thus Pay section:
Pay
Compensation may be adjusted depending on work location. For San Francisco Bay Area based hires: Estimated annual salary of $138,000 - $190,000. For New York City based hires: Estimated annual salary of $132,000 - $182,000. Equity: This role is eligible to participate in Cloudflare’s equity plan.
5. Benefits: The Benefits section includes list of benefits. We'll makeBenefits
- ... each benefit. List: - Health & Welfare Benefits - Medical/Rx Insurance - Dental Insurance - Vision Insurance - Flexible Spending Accounts - Commuter Spending Accounts - Fertility & Family Forming Benefits - On-demand mental health support and Employee Assistance Program - Global Travel Medical Insurance - Financial Benefits - Short and Long Term Disability Insurance - Life & Accident Insurance - 401(k) Retirement Savings Plan - Employee Stock Participation Plan - Time Off - Flexible paid time off covering vacation and sick leave - Leave programs, including parental, pregnancy health, medical, and bereavement leave We could flatten into a single list or nested. Simpler: each bullet as
- with the benefit description. We'll keep as flat list.
Thus Benefits
- with items: Medical/Rx Insurance, Dental Insurance, Vision Insurance, Flexible Spending Accounts, Commuter Spending Accounts, Fertility & Family Forming Benefits, On-demand mental health support and Employee Assistance Program, Global Travel Medical Insurance, Short and Long Term Disability Insurance, Life & Accident Insurance, 401(k) Retirement Savings Plan, Employee Stock Participation Plan, Flexible paid time off covering vacation and sick leave, Leave programs, including parental, pregnancy health, medical, and bereavement leave.
We could also include the introductory sentence: "Cloudflare offers a complete package of benefits and programs to support you and your family. Our benefits programs can help you pay health care expenses, support caregiving, build capital for the future and make life a little easier and fun! The below is a description of our benefits for employees in the United States, and benefits may vary for employees based outside the U.S." That's prose; we can put as
- Architect & Run the Journey Operations Engine: Own the end-to-end lead lifecycle, routing algorithms, and queue architecture, ensuring 100% of qualified leads and intent signals are processed without delay or data drop. Monitor lead-flow integrity continuously across platforms (Marketo, Salesforce, LeanData), writing automated health checks, error logging, and alert triggers to resolve bottlenecks before they impact sales. Refactor legacy batch campaign operations into automated, real-time, event-driven routing logic.
- Drive Automation via Cloudflare OS: Treat operational tech debt as bugs to be resolved through code, API integrations, webhooks, or programmatic rules engine builds. Design extensible routing frameworks that give regional field marketing teams the agility to run local campaigns while maintaining strict global system standards.
- Own Governance, Lifecycle Logic & Data Architecture: Own the lead scoring, account-to-lead matching, lifecycle states, and routing logic as a version-controlled source of truth. Partner with Data Engineering and BI teams to optimize schema, identity resolution at the web edge, and account telemetry hygiene across the MarTech stack. Define and govern logic change controls, API integration standards, and SLA tracking across marketing and sales systems.
- Empower Sales Front Lines & Partner Cross-Functionally: Automate the delivery of buyer intent telemetry (e.g., intent topics, event participation) directly into sales-facing views to accelerate sales outreach. Serve as the senior systems counterpart to Field Marketing leaders, Sales Development (BDR/SDR), Sales Operations, and BizApps to streamline GTM handoffs. Establish a continuous feedback loop with Sales to measure lead quality, velocity, and stage conversion performance.
- First-Year Outcomes: Zero Lead Leakage & Sub-15 Minute Routing: Eliminate dropped, stuck, or misrouted leads across regional queues, ensuring 100% of qualified leads and intent signals reach the correct rep within 15 minutes. Context-Rich Handoffs for Reps: Automate the delivery of buyer intent telemetry to increase initial sales engagement and conversion rates. Rapid Campaign Processing & SLA Enforcement: Achieve a 24-hour processing standard for all regional events, webinars, and field campaign lists through Cloudflare OS automation workflows. Transparent Account Journey Visibility: Deploy clear, self-serve account-level engagement tracking within Salesforce so sales teams can identify active, high-intent target accounts prior to formal form fills. Shorter Sales Cycles & Increased Pipeline Velocity: Measurably reduce conversion timelines through automated lead prioritization and streamlined handoff workflows.
- 7–10 years of experience bridging B2B marketing operations with systems engineering, revenue operations, or MarTech
before the list. Thus Benefits section:
Benefits
Cloudflare offers a complete package of benefits and programs to support you and your family. Our benefits programs can help you pay health care expenses, support caregiving, build capital for the future and make life a little easier and fun! The below is a description of our benefits for employees in the United States, and benefits may vary for employees based outside the U.S.
- ...
About the role
...
Responsibilities
Skills
- items.
3. Skills, Knowledge, And Experience: This is a list of requirements. We'll make a