Marketing Technology & Operations Manager

#TeamNextdoor

Nextdoor (NYSE: NXDR) is the essential neighborhood network. Neighbors, public agencies, and businesses use Nextdoor to connect around local information that matters in more than 340,000 neighborhoods across 11 countries. Nextdoor builds innovative technology to foster local community, share important news, and create neighborhood connections at scale. Download the app and join the neighborhood at nextdoor.com. 

Meet Your Future Neighbors

As the Marketing Technology & Operations Manager, you will own the data, pipelines, and tooling that power our lifecycle, SMB, and Nextdoor Ads Manager marketing programs. You'll work within an established MarTech stack — Segment, Iterable, Salesforce, Databricks, and Workato - helping ensure clean, reliable data flows that Marketing and RevOps teams depend on to drive engagement and revenue.

This is an individual contributor (IC) role - you will be a hands-on practitioner and focused on technical execution. This role combines hands-on MarTech ownership with cross-functional product thinking. You'll translate marketing and GTM use cases into events, traits, and audiences; partner with Data Platform and Customer Experience on Kafka and Databricks-based pipelines; and ensure our CDP and lifecycle platform remain healthy, usable, and compliant at scale.

At Nextdoor, we offer a warm and inclusive work environment that embraces a hybrid employment model, blending an in office presence and work from home experience for our valued employees. The hiring team will go over these expectations with you if you are being considered for a role near one of our offices in San Francisco, Los Angeles, Chicago, Dallas, New York, and London.  

The Impact You’ll Make

You will be a key contributor to our MarTech data and activation work - helping turn signals from product and CRM systems into reliable traits, events, and audiences that support email journeys, advertiser lifecycle programs, and first-party audience products. Your work will directly contribute to reducing time-to-launch for lifecycle campaigns — replacing slow, DS-queue-dependent workflows with faster, self-serve audience activation and enabling the data reliability that underpins measurable revenue and engagement growth.

Event & Data Pipeline Ownership

• Own the end-to-end marketing event path from Flask and other product sources into Segment and downstream tools (Iterable, Workato, and other destinations)
• Maintain and evolve the mapping engine configuration that filters product events into a canonical Segment CDP topic, ensuring only marketing-relevant traffic flows into the MarTech stack
• Build and maintain marketing data pipelines from product events and warehouse models into Segment and Iterable, so lifecycle programs have the right signals for retention, reactivation, and upsell/cross-sell at scale
• Own and operate key reverse ETL / bridge jobs from Databricks to Segment and Iterable, ensuring warehouse models and traits stay aligned with marketing requirements and data retention guidelines

Segment, Iterable & Audience Activation

• Own Segment workspaces, schemas, and destinations for key marketing projects, ensuring events and traits remain organized, documented, and discoverable for marketers and analysts
• Manage Iterable integrations for lifecycle and advertiser journeys, ensuring reliable delivery of both real-time event streams and batch traits to support onboarding, reactivation, and upsell programs
• Partner with CIA, Sales, and Marketing to design and maintain first-party audiences and interest segments exposed across GAM, internal tools, and email programs
• Work with RevOps and DS to replace fragile Salesforce→Iterable syncs with governed Databricks→Iterable datasets — enabling self-serve audience building and reducing manual CSV workflows — including Smart Ingest/Data Sync configurations and governance models for enterprise/NAM accounts

Scheme Governance, Compliance & Hygiene

• Monitor Segment usage (unique event names, schema growth) and drive consolidation, archival, and naming clean-up to keep the system performant and usable
• Ensure identifier co