Senior Security Data Engineer

We need to output HTML fragment with sections: About the team? The instruction: 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. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID 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 parse the posting and decide sections. The posting includes: - About The Team At DoorDash... (team description) - About The Role (description) - You’re Excited About This Opportunity Because You Will… (list of responsibilities/duties) - We’re Excited About You Because You Have… (list of qualifications/requirements) - Compensation (pay range, equity, benefits) - Benefits details (benefits) - Paid Time Off details (maybe part of benefits) - About DoorDash (company description) - Our Commitment to Diversity and Inclusion (EEO boilerplate) – should be removed as boilerplate. - Statement of Non-Discrimination (EEO) – remove. - Pursuant to the San Francisco Fair Chance Ordinance... (legal) – remove. - If you need any accommodations... (accommodations) – maybe keep? It's not boilerplate? Might be considered EEO but it's about accommodations; but likely considered legal boilerplate; but instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Accommodations request is part of EEO; likely remove. - Notice to Applicants for Jobs Located in NYC or Remote Jobs Associated With Office in NYC Only (legal) – remove. - Beware of recruitment scams... (scam-warning) – remove. Thus we keep: About The Team, About The Role, You’re Excited About This Opportunity Because You Will… (Responsibilities), We’re Excited About You Because You Have… (Requirements/Qualifications), Compensation (Pay), Benefits (including benefits package details, PTO details), About DoorDash (maybe company overview). The instruction says prefer a few substantive sections over many thin ones. Could combine About The Team and About The Role into one? But they are distinct headings: About the role is a standard heading. About the team maybe could be part of About the role? But we can keep both if they have substantive content. We need to use

  for section headings. Use

  • for any list of duties/requirements/benefits. Use

    for prose. We must not repeat the job title as a heading. Not needed. We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to extract the exact text for each section. Let's extract: **About The Team At DoorDash...** paragraph: "At DoorDash, including international brands Deliveroo and Wolt, we’re building the industry’s most scalable and reliable delivery network to support our three-sided marketplace of consumers, merchants, and Dashers. Global Cyber Defense is a highly talented and globally distributed team that covers response, intelligence, insider risk, threat hunting, automation, and detection engineering. We exist to keep our brands safe for the Dashers, merchants, and consumers who depend on us. Our mission is to detect, investigate, and respond to cyber threats with speed and precision, while continuously hardening our defenses through automation, AI, and cross-regional collaboration." That's prose. **About The Role** paragraph: "Security at DoorDash, Deliveroo, and Wolt runs on telemetry, and our data pipelines team owns all of it. You will own multi-terabyte-per-day ingest across AWS and GCP, including reliability, cost, and schema, so that every detection engineer, threat hunter, and responder across three brands can find what they need. Most of your week goes to code, pipelines, and query performance rather than alert triage. The team spans the US and UK, so you will be in the room (or the thread) with IT, legal, privacy, incident response, insider risk, threat intelligence, and detection engineering on a regular basis. Very little of this work happens in isolation, and that is the fun of it. This role reports to the Senior Manager of Cyber Defense in the United States. The role includes participation in an on-call rotation for pipeline health." That's prose. **You’re Excited About This Opportunity Because You Will…** list: - Own multi-terabyte-per-day log pipelines across AWS and GCP: ingest, routing, enrichment, schema management, and onboarding new sources as the business adds them - Control ingest cost and volume, cutting noise at the edge without dropping the audit logs investigators depend on - Model security data and tune query performance in Snowflake, BigQuery, and Redshift, including the tables detection engineering builds on - Ship production services and integrations that other teams depend on: custom SIEM connectors, API clients, and automation - Set and defend SLOs for log availability and freshness, and build the dashboards and alerting that prove them - Own infrastructure as code and CI/CD for all of the above, including the deployment path that detections-as-code rides on - Build AI agents and automated runbooks that speed up triage and time to fix across cloud infrastructure - Enforce IAM and service account governance for the pipeline's cloud workloads - Lead cross-functional projects spanning infrastructure, platform engineering, and incident response - Create and maintain the standards and documentation that keep the service consistent, and mentor engineers across Cyber Defense These are duties; we should output as

    • each. **We’re Excited About You Because You Have…** list: - 5+ years building and operating high-volume data pipelines in production at multi-terabyte-per-day scale, with tools like Kafka, Cribl, Dataflow, Kinesis, or CloudWatch - 4+ years writing production software in Python, Go, Rust, or Java: services and tooling that other engineers run, beyond one-off scripts - Deep hands-on experience with AWS and GCP, including infrastructure as code and ownership of CI/CD pipelines on GitHub, GitLab, or Bitbucket - Strong SQL and data modeling in a columnar warehouse such as Snowflake, BigQuery, or Redshift, covering partitioning, cost control, and query tuning - A track record owning reliability for a platform other engineers depend on, including on-call - Experience building executive dashboards and engineering metrics that people actually act on - Proven leadership and technical project management across infrastructure, platform engineering, and incident response - Exceptional written and verbal communication, a collaborative instinct, and a habit of continuous learning - Familiarity with an enterprise SIEM as an operator or a consumer (Google SecOps/Chronicle, Splunk, Elastic, CrowdStrike LogScale) is a plus, as is time with Kubernetes, Docker, and runtime security controls - Any hands-on time with security telemetry sources, detections-as-code (YARA-L, Sigma, SPL), LLM-assisted workflows, penetration testing, red teaming, or triaging bug bounty reports is a bonus These are qualifications; output as
      • . **Compensation** section: "The successful candidate’s starting pay will fall within the pay range listed below and is determined based on job-related factors including, but not limited to, skills, experience, qualifications, work location, and market conditions. Base salary is localized according to an employee’s work location. Ranges are market-dependent and may be modified in the future. In addition to base salary, the compensation for this role includes opportunities for equity grants. Talk to your recruiter for more information." Then later: "DoorDash cares about you and your overall well-being. That’s why we offer a comprehensive benefits package to all regular employees, which includes a 401(k) plan with employer matching, 16 weeks of paid parental leave, wellness benefits, commuter benefits match, paid time off and paid sick leave in compliance with applicable laws (e.g. Colorado Healthy Families and Workplaces Act). DoorDash also offers medical, dental, and vision benefits, 11 paid holidays, disability and basic life insurance, family-forming assistance, and a mental health program, among others. To learn more about our benefits, visit our careers page here." Then: "See Below For Paid Time Off Details For salaried roles: flexible paid time off/vacation, plus 80 hours of paid sick time per year.For hourly roles: vacation accrued at about 1 hour for every 25.97 hours worked (e.g. about 6.7 hours/month if working 40 hours/week; about 3.4 hours/month if working 20 hours/week), and paid sick time accrued at 1 hour for every 30 hours worked (e.g. about 5.8 hours/month if working 40 hours/week; about 2.9 hours/month if working 20 hours/week)." Then: "The national base pay range for this position within the United States, including Illinois and Colorado. $159,800—$235,000 USD" Thus we have Pay and Benefits sections. We need to decide headings: Pay, Benefits. Possibly also include a short paragraph about compensation before the range. We should not create Schedule section (none). So we have sections: About the Team, About the Role, Responsibilities (You’re Excited...), Requirements (We’re Excited...), Pay, Benefits, About DoorDash (company overview). Possibly also combine About DoorDash with About the Team? But we can keep separate. We need to ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML fragment. We need to wrap each section in

        heading then content. For lists, use

        • . For prose, use

          . We must not include any extra text outside HTML. Let's craft:

          About the Team

          At DoorDash, including international brands Deliveroo and Wolt, we’re building the industry’s most scalable and reliable delivery network to support our three-sided marketplace of consumers, merchants, and Dashers. Global Cyber Defense is a highly talented and globally distributed team that covers response, intelligence, insider risk, threat hunting, automation, and detection engineering. We exist to keep our brands safe for the Dashers, merchants, and consumers who depend on us. Our mission is to detect, investigate, and respond to cyber threats with speed and precision, while continuously hardening our defenses through automation, AI, and cross-regional collaboration.

          About the Role

          Security at DoorDash, Deliveroo, and Wolt runs on telemetry, and our data pipelines team owns all of it. You will own multi-terabyte-per-day ingest across AWS and GCP, including reliability, cost, and schema, so that every detection engineer, threat hunter, and responder across three brands can find what they need. Most of your week goes to code, pipelines, and query performance rather than alert triage. The team spans the US and UK, so you will be in the room (or the thread) with IT, legal, privacy, incident response, insider risk, threat intelligence, and detection engineering on a regular basis. Very little of this work happens in isolation, and that is the fun of it. This role reports to the Senior