We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include boilerplate like EEO, agency policy, etc. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- Summary: "The Menlo Security Sales Engineer is a customer-focused, technical sales professional who provides guidance and support to prospective and current customers across the region. Partnering closely with Regional Sales Managers and channel partners, the Sales Engineer scopes, recommends, and demonstrates security-focused solutions that map to each customer's business needs and budget. Acting in a consultative capacity, they serve as a trusted technical resource for account teams, partners, and customers alike. The team uses AI-assisted tools throughout the sales cycle, from account research and call preparation to drafting technical responses, so more time goes to the customer conversation and less to administration."
That's about the role.
- Outcomes & KPIs: "Key Outcome(s) Owned: Technical wins on regional sales opportunities, from discovery through successful proof of concept to close. Partner technical self-sufficiency across the assigned region. Success Metrics / KPIs: Technical win rate on supported opportunitiesProof of concept conversion rate (POC to closed-won)Average POC cycle time from kickoff to technical decisionNumber of partner engineers enabled/certified per quarterQuality of field feedback delivered to Product Management and Engineering (adoption of submitted insights)". This could be part of Responsibilities or maybe a separate section? The instruction: we have headings like Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Outcomes & KPIs could be under Responsibilities (what they do). We'll include under Responsibilities.
- What You'll Do: bullet list of duties. That's responsibilities.
- Functional Competencies Required: list of required qualifications/experience. That's Requirements/Qualifications.
- Preferred / Nice to Have: list of preferred qualifications.
- Benefits, Pay, Schedule: Not mentioned. So we should not include those sections.
- Also there is "Why Menlo?" culture description. That could be under About the role or maybe a separate section like "About Menlo"? Not in allowed headings. Could be part of About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role (summary), Responsibilities (What You'll Do + Outcomes & KPIs), Requirements (Functional Competencies Required), Qualifications (maybe same as Requirements? but we can separate: Requirements = mandatory, Qualifications = preferred? Actually they said "Preferred / Nice to Have". Could be Qualifications. We'll treat Requirements as mandatory, Qualifications as preferred.
- Skills: maybe we can extract from required: strong knowledge, hands-on experience, excellent communication, etc. Could be a Skills section.
But we need to avoid thin sections. Let's decide:
- About the role: summary paragraph.
- Responsibilities: combine Outcomes & KPIs and What You'll Do (list).
- Requirements: Functional Competencies Required (mandatory).
- Qualifications: Preferred / Nice to Have.
- Skills: maybe we can extract from required: "Strong knowledge and hands-on experience across core areas including web proxy technologies, network security (firewalls, IDS/IPS, HTTP/SSL proxies), network engineering fundamentals (OSI model, IPv4/6, routing, switching, DNS, VLANs and subnetting), and email security and mail flowExcellent written and oral communication skills, with the ability to articulate both the business value and the technical advantages of Menlo Security solutionsA strong sense of accountability and ownership, a proactive, get-it-done attitude, and a passion for continuous learning". That's more like competencies; could be under Requirements. But we can still have Skills section for technical skills: web proxy, network security, etc. However we risk duplication.
Given instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But headings are distinct; we can include both if they have content.
Let's create:
About the role
...
Responsibilities
Requirements
Qualifications
We should not include Benefits, Pay, Schedule.
Now we need to extract content precisely, preserving all substantive info, no invention.
Let's pull the summary paragraph exactly as given:
"The Menlo Security Sales Engineer is a customer-focused, technical sales professional who provides guidance and support to prospective and current customers across the region. Partnering closely with Regional Sales Managers and channel partners, the Sales Engineer scopes, recommends, and demonstrates security-focused solutions that map to each customer's business needs and budget. Acting in a consultative capacity, they serve as a trusted technical resource for account teams, partners, and customers alike. The team uses AI-assisted tools throughout the sales cycle, from account research and call preparation to drafting technical responses, so more time goes to the customer conversation and less to administration."
We'll put that in
.
Now Responsibilities: combine Outcomes & KPIs and What You'll Do.
Outcomes & KPIs list:
- Technical wins on regional sales opportunities, from discovery through successful proof of concept to close.
- Partner technical self-sufficiency across the assigned region.
- Success Metrics / KPIs:
- Technical win rate on supported opportunities
- Proof of concept conversion rate (POC to closed-won)
- Average POC cycle time from kickoff to technical decision
- Number of partner engineers enabled/certified per quarter
- Quality of field feedback delivered to Product Management and Engineering (adoption of submitted insights)
We need to keep as list items.
What You'll Do list (paragraph with sentences). Let's extract each duty:
- Articulate the benefits of Menlo Security solutions to both technical and non-technical audiences, and research the technical requirements of each opportunity to scope and architect a solution that meets the customer's needs.
- Understand the customer's business drivers and map them to a Menlo Security solution that fits both their needs and their budget.
- Lead proof of concept engagements on regional sales opportunities, including deployment and configuration of Menlo Security services or software, training users on the solutions, and acting as the interface between Sales and technical staff to resolve open issues.
- Use AI-assisted tools to prepare for customer engagements (account research, competitive positioning) and to draft and refine technical documentation, RFP responses, and follow-up communications, applying your own judgment for accuracy and fit.
- Work closely with regional Menlo Security partners to build partner self-sufficiency and drive partner-led opportunities.
- Work closely with customers to grow and expand their implementation and integration of Menlo Security products.
- Provide reporting and feedback on customer accounts and field activities to Sales, Product Management, and Engineering, using AI-generated call summaries and CRM enrichment to keep account records current with less manual effort.
We'll make each a
.
Now Requirements (Functional Competencies Required):
List:
- Bachelor's or Master's degree in Computer Science or a related discipline, or equivalent experience
- 4+ years of pre-sales experience in the computer networking or security space
- Strong knowledge and hands-on experience across core areas including web proxy technologies, network security (firewalls, IDS/IPS, HTTP/SSL proxies), network engineering fundamentals (OSI model, IPv4/6, routing, switching, DNS, VLANs and subnetting), and email security and mail flow
- Excellent written and oral communication skills, with the ability to articulate both the business value and the technical advantages of Menlo Security solutions
- A strong sense of accountability and ownership, a proactive, get-it-done attitude, and a passion for continuous learning
We'll put each as .
Now Qualifications (Preferred / Nice to Have):
List:
- Experience with malware analysis (static, delta, and dynamic/runtime approaches), sandboxing solutions, host-based forensics, and Windows internals
- Network forensics experience, including packet capture and analysis
- Incident response experience, including workflow procedures, evidence gathering, and chain of custody handling
- Enterprise architecture familiarity (Active Directory, SCCM, LDAP/RADIUS/TACACS+, two-factor authentication) and virtualization technology (VMware, Citrix, VDI)
- Familiarity with common hacking and exploitation tools and methodologies, malware families, and AV/IDS/IPS evasion techniques
- Working knowledge of Menlo Security competitors, including their solutions, strengths, and weaknesses
- Fluency with AI-assisted sales and productivity tools (LLM-based research, drafting, and summarization) as part of your everyday workflow
- Self-directed, with the ability to prioritize and execute project tasks in a methodical, disciplined manner and set clear expectations with stakeholders and team members
We'll put each as .
Now ensure we didn't include boilerplate: we omitted "Follow us on LinkedIn!", "Why Menlo?" culture description, EEO statement, agency policy, etc.
Check for any leftover like "All qualified applicants will receive consideration..." that's EEO; we removed.
Now output HTML fragment only.
Let's craft:
About the role
The Menlo Security Sales Engineer is a customer-focused, technical sales professional who provides guidance and support to prospective and current customers across the region. Partnering closely with Regional Sales Managers and channel partners, the Sales Engineer scopes, recommends, and demonstrates security-focused solutions that map to each customer's business needs and budget. Acting in a consultative capacity, they serve as a trusted technical resource for account teams, partners, and customers alike. The team uses AI-assisted tools throughout the sales cycle, from account research and call preparation to drafting technical responses, so more time goes to the customer conversation and less to administration.
Responsibilities
- Technical wins on regional sales opportunities, from discovery through successful proof of concept to close.
- Partner technical self-sufficiency across the assigned region.
- Technical win rate on supported opportunities
- Proof of concept conversion rate (POC to closed-won)
- Average POC cycle time from kickoff to technical decision
- Number of partner engineers enabled/certified per quarter
- Quality of field feedback delivered to Product Management and Engineering (adoption of submitted insights)
- Articulate the benefits of Menlo Security solutions to both technical and non-technical audiences, and research the technical requirements of each opportunity to scope and architect a solution that meets the customer's needs.
- Understand the customer's business drivers and map them to a Menlo Security solution that fits both their needs and their budget.
- Lead proof of concept engagements on regional sales opportunities, including deployment and configuration of Menlo Security services or software, training users on the solutions, and acting as the interface between Sales and technical staff to resolve open issues.
- Use AI-assisted tools to prepare for customer engagements (account research, competitive positioning) and to draft and refine technical documentation, RFP responses, and follow-up communications, applying your own judgment for accuracy and fit.
- Work closely with regional Menlo Security partners to build partner self-sufficiency and drive partner-led opportunities.
- Work closely with customers to grow and expand their implementation and integration of Menlo Security products.
- Provide reporting and feedback on customer accounts and field activities to Sales, Product Management, and Engineering, using AI-generated call summaries and CRM enrichment to keep account records current with less manual effort.
Requirements
- Bachelor's or Master's degree in Computer Science or a related discipline, or equivalent experience
- 4+ years of pre-sales experience in the computer networking or security space
- Strong knowledge and hands-on experience across core areas including web proxy technologies, network security (