Senior Security Sales Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to extract content from posting. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive info. We need to decide sections: Likely "About the role" (intro), "Responsibilities" (What You'll Do), "Requirements" (What You'll Bring), maybe "Qualifications" (maybe same as Requirements). Could combine. Also "Benefits" (Purple Perks). "Pay" section). "Pay" not present. "Schedule" not present (travel approx 25-30% maybe schedule? Not exactly schedule; travel is not schedule. So we should not create Schedule unless posting states schedule. It doesn't. So omit. We need to include "Skills"? Could be part of Requirements. But we can include a Skills section if we have specific skill list. The posting includes many skill items; we could put them under Requirements or Skills. Probably better to have Requirements (including experience, technical skills) and maybe Skills separate? But we should avoid thin sections. Let's combine into one "Requirements" that includes experience, technical skills, etc. Or we could have "Qualifications" for certifications etc. But we need to follow instruction: use headings for those categories if content exists. We can have multiple sections: About the role, Responsibilities, Requirements, Benefits. Possibly also "Skills" if we separate. But we need to avoid filler. Let's extract: About the role: The introductory paragraphs before "What You'll Do". That includes: "Why N-able At N-able, we’re not just helping businesses be secure; we’re redefining what it means to be cyber resilient..." up to "This role needs depth at the endpoint and enough range across the rest to carry the conversation alone." That's the role description. Responsibilities: The bullet list under "What You'll Do". It's a series of paragraphs each starting with a bold phrase? Actually it's sentences: "Own the technical win Take technical ownership..." etc. We need to convert each duty into

. We'll need to parse. Responsibilities content: - Own the technical win: Take technical ownership of security opportunities in your region and build territory strategy with your Account Executives. - Run discovery that gets past the feature checklist: how the partner delivers security today, where they are exposed, and what their clients are being asked for by insurers and auditors. - Lead demos, evaluations and proof-of-value engagements from scoping through to sign-off. - Handle objections and position against competing endpoint and MDR products in head-to-head evaluations. - Go deep on endpoint and AI security: Master the SentinelOne engine as we deliver it: static and behavioural detection, autonomous response, storyline correlation, rollback, isolation and deep visibility telemetry. - Build the same depth in our AI security capabilities as they reach market, across both AI-assisted analysis and the discovery and control of AI use in client environments. - Map detections and demos to MITRE ATT&CK, and be straight with partners about what the product does not do. - Cover the wider SentinelOne portfolio: Build working fluency across the rest of the range as we expand it: cloud and workload protection, identity, attack surface visibility and extended telemetry. - Run first and second technical conversations in those areas without a specialist present, and know when to bring one in. - Grow the installed base: Create expansion by assessing where a partner’s security offering is exposed, using recognised control frameworks rather than a product pitch. - Move partners up the EDR tiers and attach adjacent capability where it solves a problem they already feel. - Help partners who have never sold managed detection understand what delivering it takes. - Be the SME, and enable others to do the job: Serve as the subject matter expert for endpoint and AI security across the sales organisation, supporting Account Executives, Customer Success and the wider SE team on deals, technical questions and escalations. - Equip partner trainers, account managers and SEs to run endpoint and AI security sessions themselves rather than routing every one through you. - Train partners to sell, deploy and support the portfolio through workshops and hands-on sessions, and onboard new partners including demo environments and their first customer deployments. - Build reusable assets the wider team uses: demo scripts, POV workflows, competitive battle cards. That's many items. Requirements/Qualifications: Under "What You'll Bring". Contains bullet-like paragraphs. We need to extract each requirement. Let's list: - Endpoint and AI security depth. This is the core requirement. - >5 years in cyber security, with substantial time in endpoint defence across EDR, XDR, NGAV or MDR. - Hands-on SentinelOne, or comparable depth on CrowdStrike Falcon, Microsoft Defender for Endpoint, Sophos Intercept X or Huntress, and the ability to get fluent on SentinelOne quickly. - Strong Windows and macOS fundamentals: process behaviour, persistence mechanisms, and what normal looks like on an endpoint. - Working fluency in MITRE ATT&CK, and real experience tuning policy and handling false positives at scale. - Enough grounding in AI security to hold the conversation credibly now and become expert quickly: where AI-assisted analysis genuinely helps an analyst, and what the exposure looks like when a partner’s clients adopt AI tools without oversight. - Range across the portfolio: Enough working knowledge to hold a technical conversation unaided in most of the following: cloud and workload security on AWS, Azure or GCP; Microsoft 365, Entra ID and identity as an attack surface; asset and attack surface visibility; security operations, telemetry and retention; and the compliance drivers behind SMB security spend, from CIS and NIST CSF to HIPAA, PCI DSS, CMMC and cyber insurance. - Coverage of most of these, not mastery of all of them. - A record of getting hands on with new technology quickly, and the confidence to say when something sits outside your depth. - Sales engineering: Pre-sales experience carrying technical responsibility for a quota-bearing territory. - Ability to scope and run proof-of-value engagements against agreed success criteria. - Experience selling with or through MSPs, MSSPs or VARs, and a working understanding of how a managed service provider makes money. - Communication: Able to translate technical detail into business value, and to move between a technician and an executive audience in the same meeting. - Credible with senior stakeholders, and calm under pressure when handling escalations. - Preferred: SentinelOne or comparable platform certification; Security+, CySA+, SC-200, AZ-500 or GIAC; a cloud security certification; time inside an MSP, MSSP or SOC; incident response or threat hunting background; experience with Adlumin or another channel-sold MDR/XDR platform; a structured sales methodology such as MEDDICC. - Travel: approximately 25–30%. Travel is not schedule but maybe we could include under "Schedule"? Not exactly. Travel percentage is not schedule. We could omit travel or include under Requirements as a note. Probably include as a bullet under Requirements. Benefits: Under "Purple Perks". List: - Medical, dental and vision – for employee, partner, and children! - Generous PTO and observed holidays - 2 Paid Volunteer Days per year - Pension Plan with company-contribution - Employee Stock Purchase Program - Discounted gym access at several local facilities - Fun-raising opportunities as part of our giving program - N-ablite Learning – custom learning experience as part of our investment in you We need to output HTML fragment with sections. We'll have:

About the role

... (the intro paragraph(s) )

Responsibilities

• ... each duty

Requirements

• ... each requirement

Benefits

• ... each benefit

We should not include Pay or Schedule. Make sure we preserve all substantive info. No extra fluff. We need to ensure we don't include boilerplate like "Why N-able At N-able, we’re not just helping businesses be secure; we’re redefining what it means to be cyber resilient." That's part of About the role. We need to combine the intro paragraphs into a single

maybe multiple

but we can just one. Let's craft About the role paragraph: "Why N-able At N-able, we’re not just helping businesses be secure; we’re redefining what it means to be cyber resilient. Our end-to-end platform blends AI-powered capabilities and flexible tech stacks, so customers can manage, secure, and recover with confidence. But the real power behind it all? Our people. We’re a global crew of N-ablites, who love solving complex problems, sharing knowledge, and delivering solutions that actually make a difference. If you're into meaningful work, fast growth, and a team that’s got your back, you’ll be surrounded by people who believe in what they do, and in you. Our endpoint security is powered by SentinelOne and built for the way MSPs work: multi-tenant, integrated into N-central and N-sight RMM, and available standalone for partners on a different RMM. AI security sits next to it, and it means two things here: the AI-assisted detection and analysis now built into the products, and the newer problem of finding and controlling how AI is being used across a partner’s client estates. Expect it to be a growing part of the conversation. The rest of the portfolio is widening too. We are taking more of the SentinelOne range to market alongside Adlumin, our own MDR/XDR platform, so conversations that start at the endpoint increasingly finish somewhere else. This role needs depth at the endpoint and enough range across the rest to carry the conversation alone." That seems fine. Now Responsibilities list items as above. Now Requirements list items. We need to ensure we include all items from "What You'll Bring". Let's enumerate clearly: 1. Endpoint and AI security depth. This is the core requirement. 2. >5 years in cyber security, with substantial time in endpoint defence across EDR, XDR, NGAV or MDR. 3. Hands-on SentinelOne, or comparable depth on CrowdStrike Falcon, Microsoft Defender for Endpoint, Sophos Intercept X or Huntress, and the ability to get fluent on SentinelOne quickly. 4. Strong Windows and macOS fundamentals: process behaviour, persistence mechanisms, and what normal looks like on an endpoint. 5. Working fluency in MITRE ATT&CK, and real experience tuning policy and handling false positives at scale. 6. Enough grounding in AI security to hold the conversation credibly now and become expert quickly: where AI-assisted analysis genuinely helps an analyst, and what the exposure looks like when a partner’s clients adopt AI tools without oversight. 7. Range across the portfolio: Enough working knowledge to hold a technical conversation unaided in most of the following: cloud and workload security on AWS, Azure or GCP; Microsoft 365, Entra ID and identity as an attack surface; asset and attack surface visibility; security operations, telemetry and retention; and the compliance drivers behind SMB security spend, from CIS and NIST CSF to HIPAA, PCI DSS, CMMC and cyber insurance. 8. Coverage of most of these, not mastery of all of them. 9. A record of getting hands on with new technology quickly, and the confidence to say when something sits outside your depth. 10. Sales engineering: Pre-sales experience carrying technical responsibility for a quota-bearing territory. 11. Ability to scope and run proof-of-value engagements against agreed success criteria. 12. Experience selling with or through MSPs, MSSPs or VARs, and a working understanding of how a managed service provider makes money. 13. Communication: Able to translate technical detail into business value, and to move between a technician and an executive audience