Daylight Security logo

Customer Success Engineer (CSE)

Daylight Security

Remote · USJobPosted 1mo agoStill listed 2 days ago

Most applications go out cold — see where you stand first. No sign-up to start.

Watch jobs like this.

Don't just apply. Show up ready.

Olive works from this exact posting.

At a glance

Compensation
No compensation found
Location
Remote · US
Work Authorization
Not specified

Olive lists jobs from US employers, including remote roles you can work from the United States.

Job overview

Daylight Security provides managed agentic security services, MDR, threat hunting, and a security data lake. The Customer Success Engineer owns the technical relationship with a portfolio of customer security teams, from onboarding through steady-state operation, and serves as their technical partner and first-line response. The role works alongside a Customer Success Manager, who owns the commercial relationship, while the engineer owns the technical one.

Skills & qualifications

RequiredNice to have

Skills

Knowledge ManagementCloud ArchitectureEDRWritten Communication SkillsSoftware as a ServiceTAMOnboardingPrioritization SkillsScriptingComputer SecuritySecurity OperationsCybersecurityDetection and ResponseMDRSIEM/EDR ToolingTechnical ConversationAPIsSaaS IntegrationsLog PipelinesLog AnalysisWorkflow TracingRoot Cause AnalysisClear CommunicationPrioritizationWritten CommunicationStructured OnboardingKnowledge Base Development

Qualifications

4+ Years Customer-Facing Technical ExperienceStartup or High-Growth Experience

Full job description

Daylight delivers Managed Agentic Security Services (MASS), MDR, threat hunting, and a security data lake, through a fundamentally different architecture than traditional security providers.

Our agentic platform runs the full cycle from detection to response, informed by security experts from IR and threat hunting backgrounds. The platform learns your environment and investigates alerts; experts validate decisions, optimize detections, and take over during incidents.

The result: security teams move from firefighting to strategic work.

We're looking for a Customer Success Engineer to own the technical relationship with a portfolio of customer security teams, from onboarding through steady-state operation. You'll be the go-to technical partner for our customers' security engineers, answering most questions on the spot and serving as first-line response across shared channels. This is not a ticket-routing role: every Daylight account is a live integration project. You'll work alongside a Customer Success Manager who owns the commercial relationship, while you own the technical one.

Responsibilities

  • Execute onboarding: run the integration checklist against contracted scope, set up escalation paths and on-demand paging, and drive accounts to silent-mode exit with status visible to the customer

  • Run stale and non-stale activation tracks separately, keeping onboarding moving without CSM follow-up

  • Serve as live first-line technical response in shared Slack or Teams channels and the Pylon queue

  • Confirm integrations are live, sending data, and that the response policy is active; catch expiring tokens, lapsed permissions, and unannounced new tooling

  • Run working sessions with customer security engineers on escalation and response policies, test notification rules end to end, and wire case data into their ticketing until analysts adopt it

  • Tune detections, false escalations, and the end-to-end case experience

  • Explain case dispositions clearly enough to expand response scope from investigations to quarantine and isolation

  • Maintain Pylon knowledge base articles, service differentiator docs, escalation policies, and troubleshooting playbooks

  • File field observations in Linear so Product and the SOC see what you see

  • Deliver QBR technical content to the CSM ahead of the deck

  • Escalate cleanly to the Solutions Architect pool when needed, with the investigation already done

  • Travel roughly quarterly for customer visits, company events, or conferences

Requirements

  • 4+ years in a customer-facing technical role such as CSE, TAM, Solutions Engineer or Architect, or Implementation Engineer

  • Background in cybersecurity, ideally with experience in security operations, detection and response, MDR, or SIEM/EDR tooling

  • Startup or high-growth experience where process is still being built

  • Ability to hold a technical conversation with a customer's security engineer independently

  • Hands-on scripting experience

  • Working knowledge of APIs, SaaS integrations, log pipelines, and modern cloud architecture

  • Ability to read logs, trace a workflow, isolate root causes, and communicate findings clearly

  • Strong prioritization and written communication skills across multiple accounts

  • Experience with structured onboarding and building a customer-facing knowledge base, an advantage

How this job compares

Set against the 2,683 open Security jobs on Olive Jobs, counted October 31, 2026.

Pay
  • This postingNot listed
  • US median$133–219K/yr1,090 salary ranges
  • US median$18–19/hr687 hourly ranges
Openings
Olive Jobs lists 2,683 open Security jobs across the US. 4% of them nationwide are listed as remote or flexible.
Hiring the most across the US
Experience
This posting asks for at least 4 years of experience; Security postings that state a minimum ask for 5 years at the median (1,385 postings).
Education
601 of the 2,683 open Security jobs (22%) ask for a bachelor's degree or higher.

Counted across the open, public US postings on Olive Jobs on October 31, 2026. Pay medians are the middle values of the low ends and of the high ends of postings that list both ends of a range in the same cadence (a yearly salary or an hourly rate); a range's midpoint is halfway between its ends. Pay and experience figures resting on fewer than 20 postings are left out.

You've read the whole posting — now see how you match it.