Senior Lead Management Specialist
for each heading. 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. Remove boilerplate etc. Preserve all substantive information. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to parse the posting.
We have sections: About Us (but that's generic company description; maybe not needed? The instruction says we should include sections only when posting has real, specific content for it. About Us is generic but could be considered "About the role"? Actually there is "About The Role" section. We should include that as a heading "About the role". The "About Us" is company overview; maybe we can incorporate into "About the role" or drop? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include those headings if content exists. The posting includes "About The Role" with description. So we will output About the role
with prose.
Then "What You'll Do" is responsibilities. So we will have Responsibilities
with list of duties (the bullet points under "What You'll Do").
Then "Skills, Knowledge, And Experience" is skills/requirements. Could be split into Requirements, Qualifications, Skills. The instruction says we can have sections for Requirements, Qualifications, Skills. We need to decide how to map. The posting includes a list of required experience and skills. Could treat as "Requirements" or "Skills". Since we have both Requirements and Qualifications sections optional, we should only include those that have substantive content. The posting includes "Skills, Knowledge, And Experience" which is basically requirements. We could put that under Skills
as a list. Or we could split into Requirements and Qualifications but we don't have separate qualifiers. Better to just use Skills section.
Then "Compensation" includes pay ranges for locations. So we need a Pay section. The posting includes compensation details: "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." Also mentions equity eligibility. So we can put that in Pay section.
Then "Benefits" section: there is a Benefits paragraph describing health, welfare, financial benefits, time off. So we include Benefits.
Schedule: not mentioned. So we omit Schedule.
Also there is "First-Year Outcomes" which could be considered responsibilities or maybe qualifications? But it's outcomes expected. Could be included under Responsibilities as additional bullet points? Might be better to include under Responsibilities as they are expected outcomes. But we already have responsibilities list; we could add them as part of responsibilities. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include First-Year Outcomes somewhere. Could be a separate section like "Expected Outcomes" but not in allowed headings. We could incorporate into Responsibilities as additional bullet points. That would preserve info.
Also "Available Locations: Austin, TX, or SF Bay Area or NYC" is location info. Could be included under About the role or maybe as a short paragraph. Not a heading. We'll include in About the role paragraph.
Also "Equity This role is eligible to participate in Cloudflare’s equity plan." Could be part of Pay or Benefits. We'll add to Pay section.
Now we need to strip boilerplate: remove About Us? Actually About Us is generic company description; we could drop it because not required heading. But we might keep some of it in About the role? The instruction says preserve ALL substantive information; About Us is substantive but not required heading. However we could incorporate into About the role? The About the role section already has description; we could prepend company mission? But that might be considered adding content not originally under About the role. However we could keep About Us as a separate paragraph before headings? The instruction says output ONLY the HTML fragment, no extra headings besides those specified. It didn't forbid extra paragraphs not under headings? It says use 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. It doesn't say we cannot have other paragraphs outside headings, but likely they expect sections only. Safer to include About Us as a paragraph under a heading? There's no heading for About Us. Could we treat it as part of "About the role"? Might be okay to include as a preamble paragraph before the first heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot have other content outside those headings, but they said "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 have a leading
for About Us before any heading. That would preserve info. However they might expect all content under headings. I'd rather include About Us as a paragraph under a heading like "About the role" but that might misrepresent. However the About the role heading already has its own content; we could combine.
Let's read the About Us paragraph: It's about Cloudflare mission, network, etc. That's generic but still substantive. If we drop it, we lose info. The instruction says preserve ALL substantive information. So we need to keep it somewhere. Could we put it under a heading like "About the role"? That would be mixing but still preserving. I think it's acceptable.
Thus About the role section will contain: the About Us paragraph + the About The Role paragraph.
Now Responsibilities: include What You'll Do bullet points and First-Year Outcomes bullet points.
Now Skills: include the Skills, Knowledge, And Experience bullet points.
Now Benefits: include the Benefits paragraph.
Now Pay: include Compensation paragraph plus equity note.
Now we need to format lists.
Let's extract bullet points.
Under "What You'll Do": there are several paragraphs each starting with a bold heading? Actually they are:
- 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.
Then "First-Year Outcomes" bullet points:
- 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.
We can combine these as list items under Responsibilities.
Now Skills, Knowledge, And Experience bullet points:
- 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.
Bonus Points (these are optional but still substantive). Should we include them? They are under "Bonus Points". They are still substantive. We could include them as part of Skills section as additional bullet points, maybe label as "Bonus". But we can just include them as bullet points.
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.
Now Benefits: The benefits paragraph includes several bullet-like items but not formatted as list. We'll convert to list for clarity? The instruction: Use
- for any list of duties/requirements/benefits. So we should turn benefits into a list. The benefits paragraph includes:
- 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
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Preserve all substantive information. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to parse the posting. We have sections: About Us (but that's generic company description; maybe not needed? The instruction says we should include sections only when posting has real, specific content for it. About Us is generic but could be considered "About the role"? Actually there is "About The Role" section. We should include that as a heading "About the role". The "About Us" is company overview; maybe we can incorporate into "About the role" or drop? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include those headings if content exists. The posting includes "About The Role" with description. So we will output About the role
with prose.
Then "What You'll Do" is responsibilities. So we will have Responsibilities
with list of duties (the bullet points under "What You'll Do").
Then "Skills, Knowledge, And Experience" is skills/requirements. Could be split into Requirements, Qualifications, Skills. The instruction says we can have sections for Requirements, Qualifications, Skills. We need to decide how to map. The posting includes a list of required experience and skills. Could treat as "Requirements" or "Skills". Since we have both Requirements and Qualifications sections optional, we should only include those that have substantive content. The posting includes "Skills, Knowledge, And Experience" which is basically requirements. We could put that under Skills
as a list. Or we could split into Requirements and Qualifications but we don't have separate qualifiers. Better to just use Skills section.
Then "Compensation" includes pay ranges for locations. So we need a Pay section. The posting includes compensation details: "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." Also mentions equity eligibility. So we can put that in Pay section.
Then "Benefits" section: there is a Benefits paragraph describing health, welfare, financial benefits, time off. So we include Benefits.
Schedule: not mentioned. So we omit Schedule.
Also there is "First-Year Outcomes" which could be considered responsibilities or maybe qualifications? But it's outcomes expected. Could be included under Responsibilities as additional bullet points? Might be better to include under Responsibilities as they are expected outcomes. But we already have responsibilities list; we could add them as part of responsibilities. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include First-Year Outcomes somewhere. Could be a separate section like "Expected Outcomes" but not in allowed headings. We could incorporate into Responsibilities as additional bullet points. That would preserve info.
Also "Available Locations: Austin, TX, or SF Bay Area or NYC" is location info. Could be included under About the role or maybe as a short paragraph. Not a heading. We'll include in About the role paragraph.
Also "Equity This role is eligible to participate in Cloudflare’s equity plan." Could be part of Pay or Benefits. We'll add to Pay section.
Now we need to strip boilerplate: remove About Us? Actually About Us is generic company description; we could drop it because not required heading. But we might keep some of it in About the role? The instruction says preserve ALL substantive information; About Us is substantive but not required heading. However we could incorporate into About the role? The About the role section already has description; we could prepend company mission? But that might be considered adding content not originally under About the role. However we could keep About Us as a separate paragraph before headings? The instruction says output ONLY the HTML fragment, no extra headings besides those specified. It didn't forbid extra paragraphs not under headings? It says use 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. It doesn't say we cannot have other paragraphs outside headings, but likely they expect sections only. Safer to include About Us as a paragraph under a heading? There's no heading for About Us. Could we treat it as part of "About the role"? Might be okay to include as a preamble paragraph before the first heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot have other content outside those headings, but they said "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 have a leading
for About Us before any heading. That would preserve info. However they might expect all content under headings. I'd rather include About Us as a paragraph under a heading like "About the role" but that might misrepresent. However the About the role heading already has its own content; we could combine.
Let's read the About Us paragraph: It's about Cloudflare mission, network, etc. That's generic but still substantive. If we drop it, we lose info. The instruction says preserve ALL substantive information. So we need to keep it somewhere. Could we put it under a heading like "About the role"? That would be mixing but still preserving. I think it's acceptable.
Thus About the role section will contain: the About Us paragraph + the About The Role paragraph.
Now Responsibilities: include What You'll Do bullet points and First-Year Outcomes bullet points.
Now Skills: include the Skills, Knowledge, And Experience bullet points.
Now Benefits: include the Benefits paragraph.
Now Pay: include Compensation paragraph plus equity note.
Now we need to format lists.
Let's extract bullet points.
Under "What You'll Do": there are several paragraphs each starting with a bold heading? Actually they are:
- 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.
Then "First-Year Outcomes" bullet points:
- 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.
We can combine these as list items under Responsibilities.
Now Skills, Knowledge, And Experience bullet points:
- 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.
Bonus Points (these are optional but still substantive). Should we include them? They are under "Bonus Points". They are still substantive. We could include them as part of Skills section as additional bullet points, maybe label as "Bonus". But we can just include them as bullet points.
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.
Now Benefits: The benefits paragraph includes several bullet-like items but not formatted as list. We'll convert to list for clarity? The instruction: Use
- for any list of duties/requirements/benefits. So we should turn benefits into a list. The benefits paragraph includes:
- 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
- for any list of duties/requirements/benefits, and
for prose. It doesn't say we cannot have other paragraphs outside headings, but likely they expect sections only. Safer to include About Us as a paragraph under a heading? There's no heading for About Us. Could we treat it as part of "About the role"? Might be okay to include as a preamble paragraph before the first heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot have other content outside those headings, but they said "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 have a leading
for About Us before any heading. That would preserve info. However they might expect all content under headings. I'd rather include About Us as a paragraph under a heading like "About the role" but that might misrepresent. However the About the role heading already has its own content; we could combine. Let's read the About Us paragraph: It's about Cloudflare mission, network, etc. That's generic but still substantive. If we drop it, we lose info. The instruction says preserve ALL substantive information. So we need to keep it somewhere. Could we put it under a heading like "About the role"? That would be mixing but still preserving. I think it's acceptable. Thus About the role section will contain: the About Us paragraph + the About The Role paragraph. Now Responsibilities: include What You'll Do bullet points and First-Year Outcomes bullet points. Now Skills: include the Skills, Knowledge, And Experience bullet points. Now Benefits: include the Benefits paragraph. Now Pay: include Compensation paragraph plus equity note. Now we need to format lists. Let's extract bullet points. Under "What You'll Do": there are several paragraphs each starting with a bold heading? Actually they are: - 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. Then "First-Year Outcomes" bullet points: - 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. We can combine these as list items under Responsibilities. Now Skills, Knowledge, And Experience bullet points: - 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. Bonus Points (these are optional but still substantive). Should we include them? They are under "Bonus Points". They are still substantive. We could include them as part of Skills section as additional bullet points, maybe label as "Bonus". But we can just include them as bullet points. 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. Now Benefits: The benefits paragraph includes several bullet-like items but not formatted as list. We'll convert to list for clarity? The instruction: Use
- for any list of duties/requirements/benefits. So we should turn benefits into a list. The benefits paragraph includes: - 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