Manager Customer Success Engineering
Free to start · No card · 5 credits the moment you sign up
Job description
Requirements
- 10-15 years in SecOps: SOC analysis, incident response, threat detection, or security engineering
- Background in an MDR or MSSP strongly preferred - you understand what it means to manage security outcomes for multiple customers simultaneously
- Hands-on with SIEM, EDR, SOAR, and cloud security tooling (Splunk, CrowdStrike, Sentinel, Palo Alto, or equivalent)
- Comfortable running executive-level conversations - QBRs, roadmap discussions, escalation calls - without losing the technical thread
- Experience managing or mentoring junior security analysts or engineers
- Strong written and verbal communication: you can explain a detection gap to a CISO and a playbook fix to an analyst in the same day - Comfortable working in an early-stage environment where the process doesn't exist yet - you build it
- Prior experience in a CSE, TAM, or Solutions Engineering role at a security vendor
Benefits
- Direct line to product - your customer insights shape what we build next
- Build and own a function from the ground up - Remote-first, high-trust culture
- Competitive comp + equity at an early-stage AI security company
- Work with customers who are genuinely trying to solve hard security problems, not just check compliance boxes
Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for Simbian. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.