Enterprise Account Executive, East
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 / requisition 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 decide which sections to include. The posting includes:
- About Ent (company description) – maybe not needed as a section? Could be part of intro but not required headings. We could include a short
about company? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The company description may be considered minor metadata? But it's substantive about the company. However the instruction says we should include sections only when posting has real, specific content for it. The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map content to these.
We have:
- About The Role: description of role (full-cycle, named account list, etc). That's a section.
- What You’ll Achieve: could be considered Responsibilities? Or maybe "Responsibilities". The list of achievements is basically responsibilities. So we could put under
Responsibilities
with - items.
- What You’ll Bring: could be Requirements/Qualifications/Skills. We have Must-haves and Bonus. Could split into Requirements (must-haves) and Qualifications (bonus) or Skills. The instruction says prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But we need to follow headings list; we can choose which to include. Perhaps include
Requirements
for must-haves, and Qualifications
for bonus. Or combine into one Requirements
with both must-haves and bonus? Might be better to separate.
- Benefits: we have Our Benefits section with details. So include Benefits
with - .
- Pay and Schedule: not mentioned, so omit.
- Also we have "How We Work" which describes culture. Could be a section like "About the company" but not in list. Could be omitted or placed as a
before sections. The instruction says we can include other headings only if they match the list? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those.
Thus output:
About the Role
... prose ...
Then maybe Responsibilities
with - for each achievement.
Then
Requirements
with - for must-haves.
Then
Qualifications
with - for bonus.
Then
Benefits
with - for benefits.
We need to preserve all substantive information, not invent or summarize away detail. Must keep details like "5+ years carrying a quota in a full-cycle closing role selling cybersecurity." etc.
We need to remove boilerplate like Diversity & Accommodations, EEO, etc. Also remove "How We Work" maybe? It's not boilerplate but it's cultural description. Could be included as a
before sections? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "How We Work" is not that; it's cultural description. Could be included as a section like "About the Company" but not in list. Might be okay to include as a
before sections. However the instruction says "Prefer a few substantive sections over many thin ones." Could combine "How We Work" into About the Role? Not ideal.
Maybe we can include a
About the Company
but not in list; risk of being considered extra. Safer to include as a before the first heading.
Let's extract content:
Company intro: "About Ent Ent is the intent-aware workspace security platform for securing human and AI-driven work. Built to protect productivity, the new attack surface, Ent understands not just what users and agents do but why, and intervenes at the moment of risk before incidents occur. Where existing tools see events, Ent sees intent, so security teams can step in at the moment of risk instead of investigating days later. Founded by Lou Manousos and Brandon Dixon, co-founders of RiskIQ (acquired by Microsoft) and the team behind Microsoft Security Copilot, Ent is in production with Global 2000 customers across hospitality, financial services, and defense, and backed by Decibel, Sequoia, Crosspoint Capital, Craft Ventures, Shield Capital, Felicis, and In-Q-Tel. We’re now hiring the team that will define this category."
That's substantive; we can keep as a
before sections.
"How We Work" section: bullet points: Customer first..., Humble..., Urgency... Could be kept as a
or
. It's not a list but prose. We'll keep as .
Then About The Role: we need to capture that paragraph.
Then What You’ll Achieve: list of achievements (multiple sentences each starting with "You'll").
Then What You’ll Bring: Must-haves and Bonus.
Then Our Benefits: list.
We must not include "Diversity & Accommodations" etc.
Now craft HTML.
We need to ensure we use
- for any list of duties/requirements/benefits. For prose, use
.
Thus:
About Ent Ent is the intent-aware workspace security platform ...
How We Work Customer first. The product and the business are built around problems we’ve watched real security teams struggle with — not the other way around. Every roadmap conversation starts with what a CISO told us last week. Humble. No drama. We hire people who share the mission and trust each other to deliver. Teamwork over showmanship. Accountability over politics. The work speaks louder than the person doing it. Urgency. The window to build a durable security company in the AI era is open right now and it will not stay open. The shot clock has started. We move at the speed of the people we want to protect.
About the Role
We're hiring Enterprise Account Executives to sell Ent to security teams at organizations of 5,000 employees and up. This is a full-cycle role on a named account list: you'll open doors with security leaders you already know, run a real technical evaluation, build a business case that clears an enterprise budget process, and close it. You'll be selling a new category, which means the conversation starts with the problem rather than a feature comparison, and you'll be doing it early enough that what you learn in the field changes the product and the playbook. We're looking for sellers whose relationships with CISOs are current and real — the kind where the meeting happens because of who's asking.
Responsibilities
- You'll own a quota and hit it, running the full cycle from first conversation to signature to a clean handoff.
- You'll open your accounts on the strength of your own relationships, and build the rest of your pipeline yourself — outbound, your network, events, and partners.
- You'll build account plans worth the name: the org chart, the security priorities, the budget cycle, the incumbents, and a path to the person who can say yes.
- You'll run credible technical evaluations with security teams: scoping the proof of value, working alongside our engineers, and getting to a clear yes or no rather than a stalled pilot.
- You'll multithread — CISO, security architects, IT and identity owners, procurement, legal, and the executive sponsor above them — and build the business case that survives a budget conversation you're not in.
- You'll navigate the enterprise process without losing the deal to it: security review, privacy, legal redlines, and procurement, sequenced early rather than discovered in month five.
- You'll forecast honestly. You'll know where every deal stands, what has to happen next, and you'll call your quarter accurately enough that leadership plans on it.
- You'll bring the field back inside: the objections, the competitive patterns, the gaps. What you hear this month should show up in the roadmap and the pitch next quarter.
- You'll work AI-native by default — account research, prep, follow-up, call review — and raise what's working so the rest of the team gets it too.
Requirements
- 5+ years carrying a quota in a full-cycle closing role selling cybersecurity.
- Endpoint security experience preferred.
- You've sold to CISOs and their teams, and you can hold your own on a call with a security architect without reaching for a sales engineer to answer everything.
- You have existing, current relationships with security leaders you could call this week — and you can speak to how you built them and what they've been worth.
- You've worked the segment: organizations of 5,000 employees and up, multi-stakeholder deals, real evaluations and security reviews, cycles measured in quarters.
- You're a hunter. You've self-sourced a real share of your pipeline and can say what percentage and how you did it.
- You're coachable in the moment. You've had your calls reviewed, taken the note, and changed what you did on the next one — and you treat pitch practice and deal reviews as reps rather than overhead.
Qualifications
- You've been an early seller at a startup, before the playbook existed.
- You've run a formal sales methodology well enough to have opinions about where it helps and where it gets in the way.
- You've sold through partners or resellers alongside a direct motion.
- You've closed a seven-figure deal, or landed a first logo in a regulated industry.
- You've worked a territory outside the US.
- You're genuinely excited about applying AI to how you sell.
Benefits
- Distributed workplace. While we have positions
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition 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 decide which sections to include. The posting includes: - About Ent (company description) – maybe not needed as a section? Could be part of intro but not required headings. We could include a short
about company? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The company description may be considered minor metadata? But it's substantive about the company. However the instruction says we should include sections only when posting has real, specific content for it. The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map content to these. We have: - About The Role: description of role (full-cycle, named account list, etc). That's a section. - What You’ll Achieve: could be considered Responsibilities? Or maybe "Responsibilities". The list of achievements is basically responsibilities. So we could put under
Responsibilities
with- items.
- What You’ll Bring: could be Requirements/Qualifications/Skills. We have Must-haves and Bonus. Could split into Requirements (must-haves) and Qualifications (bonus) or Skills. The instruction says prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But we need to follow headings list; we can choose which to include. Perhaps include
Requirements
for must-haves, andQualifications
for bonus. Or combine into oneRequirements
with both must-haves and bonus? Might be better to separate. - Benefits: we have Our Benefits section with details. So includeBenefits
with- .
- Pay and Schedule: not mentioned, so omit.
- Also we have "How We Work" which describes culture. Could be a section like "About the company" but not in list. Could be omitted or placed as a
before sections. The instruction says we can include other headings only if they match the list? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those. Thus output:
About the Role
... prose ...
Then maybeResponsibilities
with- for each achievement.
Then
Requirements
with- for must-haves.
Then
Qualifications
with- for bonus.
Then
Benefits
with- for benefits.
We need to preserve all substantive information, not invent or summarize away detail. Must keep details like "5+ years carrying a quota in a full-cycle closing role selling cybersecurity." etc.
We need to remove boilerplate like Diversity & Accommodations, EEO, etc. Also remove "How We Work" maybe? It's not boilerplate but it's cultural description. Could be included as a
before sections? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "How We Work" is not that; it's cultural description. Could be included as a section like "About the Company" but not in list. Might be okay to include as a
before sections. However the instruction says "Prefer a few substantive sections over many thin ones." Could combine "How We Work" into About the Role? Not ideal. Maybe we can include a
About the Company
but not in list; risk of being considered extra. Safer to include as abefore the first heading. Let's extract content: Company intro: "About Ent Ent is the intent-aware workspace security platform for securing human and AI-driven work. Built to protect productivity, the new attack surface, Ent understands not just what users and agents do but why, and intervenes at the moment of risk before incidents occur. Where existing tools see events, Ent sees intent, so security teams can step in at the moment of risk instead of investigating days later. Founded by Lou Manousos and Brandon Dixon, co-founders of RiskIQ (acquired by Microsoft) and the team behind Microsoft Security Copilot, Ent is in production with Global 2000 customers across hospitality, financial services, and defense, and backed by Decibel, Sequoia, Crosspoint Capital, Craft Ventures, Shield Capital, Felicis, and In-Q-Tel. We’re now hiring the team that will define this category." That's substantive; we can keep as a
before sections. "How We Work" section: bullet points: Customer first..., Humble..., Urgency... Could be kept as a
or
- . It's not a list but prose. We'll keep as
- for any list of duties/requirements/benefits. For prose, use
. Thus:
About Ent Ent is the intent-aware workspace security platform ...
How We Work Customer first. The product and the business are built around problems we’ve watched real security teams struggle with — not the other way around. Every roadmap conversation starts with what a CISO told us last week. Humble. No drama. We hire people who share the mission and trust each other to deliver. Teamwork over showmanship. Accountability over politics. The work speaks louder than the person doing it. Urgency. The window to build a durable security company in the AI era is open right now and it will not stay open. The shot clock has started. We move at the speed of the people we want to protect.
About the Role
We're hiring Enterprise Account Executives to sell Ent to security teams at organizations of 5,000 employees and up. This is a full-cycle role on a named account list: you'll open doors with security leaders you already know, run a real technical evaluation, build a business case that clears an enterprise budget process, and close it. You'll be selling a new category, which means the conversation starts with the problem rather than a feature comparison, and you'll be doing it early enough that what you learn in the field changes the product and the playbook. We're looking for sellers whose relationships with CISOs are current and real — the kind where the meeting happens because of who's asking.
Responsibilities
- You'll own a quota and hit it, running the full cycle from first conversation to signature to a clean handoff.
- You'll open your accounts on the strength of your own relationships, and build the rest of your pipeline yourself — outbound, your network, events, and partners.
- You'll build account plans worth the name: the org chart, the security priorities, the budget cycle, the incumbents, and a path to the person who can say yes.
- You'll run credible technical evaluations with security teams: scoping the proof of value, working alongside our engineers, and getting to a clear yes or no rather than a stalled pilot.
- You'll multithread — CISO, security architects, IT and identity owners, procurement, legal, and the executive sponsor above them — and build the business case that survives a budget conversation you're not in.
- You'll navigate the enterprise process without losing the deal to it: security review, privacy, legal redlines, and procurement, sequenced early rather than discovered in month five.
- You'll forecast honestly. You'll know where every deal stands, what has to happen next, and you'll call your quarter accurately enough that leadership plans on it.
- You'll bring the field back inside: the objections, the competitive patterns, the gaps. What you hear this month should show up in the roadmap and the pitch next quarter.
- You'll work AI-native by default — account research, prep, follow-up, call review — and raise what's working so the rest of the team gets it too.
Requirements
- 5+ years carrying a quota in a full-cycle closing role selling cybersecurity.
- Endpoint security experience preferred.
- You've sold to CISOs and their teams, and you can hold your own on a call with a security architect without reaching for a sales engineer to answer everything.
- You have existing, current relationships with security leaders you could call this week — and you can speak to how you built them and what they've been worth.
- You've worked the segment: organizations of 5,000 employees and up, multi-stakeholder deals, real evaluations and security reviews, cycles measured in quarters.
- You're a hunter. You've self-sourced a real share of your pipeline and can say what percentage and how you did it.
- You're coachable in the moment. You've had your calls reviewed, taken the note, and changed what you did on the next one — and you treat pitch practice and deal reviews as reps rather than overhead.
Qualifications
- You've been an early seller at a startup, before the playbook existed.
- You've run a formal sales methodology well enough to have opinions about where it helps and where it gets in the way.
- You've sold through partners or resellers alongside a direct motion.
- You've closed a seven-figure deal, or landed a first logo in a regulated industry.
- You've worked a territory outside the US.
- You're genuinely excited about applying AI to how you sell.
Benefits
- Distributed workplace. While we have positions
. Then About The Role: we need to capture that paragraph. Then What You’ll Achieve: list of achievements (multiple sentences each starting with "You'll"). Then What You’ll Bring: Must-haves and Bonus. Then Our Benefits: list. We must not include "Diversity & Accommodations" etc. Now craft HTML. We need to ensure we use
- for any list of duties/requirements/benefits. For prose, use
- for benefits.
We need to preserve all substantive information, not invent or summarize away detail. Must keep details like "5+ years carrying a quota in a full-cycle closing role selling cybersecurity." etc.
We need to remove boilerplate like Diversity & Accommodations, EEO, etc. Also remove "How We Work" maybe? It's not boilerplate but it's cultural description. Could be included as a
- for bonus.
Then
- for must-haves.
Then
- for each achievement.
Then
- .
- Pay and Schedule: not mentioned, so omit.
- Also we have "How We Work" which describes culture. Could be a section like "About the company" but not in list. Could be omitted or placed as a