Solutions Consultant 2 - SLED

We need to output only HTML fragment, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - Mission and Who We Are: This is about company mission, values. Could be "About the role"? Actually "About the role" is typical heading for description of role. The posting includes "Our Mission", "Who We Are", "Job Summary", "The Role", "Your Impact Role". We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content about responsibilities (Your Impact Role bullet list). Also qualifications (Your Experience bullet list). Also maybe skills (some bullet list). Also compensation disclosure (Pay). Benefits: there is a line "A description of our employee benefits may be found here." but no specifics; we should not create Benefits section unless posting actually states them. It only mentions a link, no details. So we should not include Benefits. Pay: there is compensation disclosure with salary range? It says "The compensation offered for this position will depend on qualifications, experience, and work location. For candidates who receive an offer at the posted level, the starting base salary (for non-sales roles) or base salary + commission target (for sales/com-missioned roles) is expected to be the annual range listed below. The offered compensation may also include restricted stock units and a bonus. A description of our employee benefits may be found here. /yr". It seems truncated; there is no actual numbers. It says "annual range listed below" but not provided. So we have no specific pay info. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Since no specific numbers, we should not include Pay. Schedule: not mentioned. So skip. Skills: maybe we can extract from qualifications: technical expertise list: Networking, Network Security, Cybersecurity, Private/Public Cloud Security, SOC/Endpoint, SASE, or AI Security. Also AI fluency. Could be a Skills section. But we need to decide sections: About the role (maybe combine Mission and Who We Are and Job Summary). Responsibilities (Your Impact Role). Qualifications (Your Experience). Skills (technical expertise list). Possibly also "Requirements" could be same as Qualifications? But we have both Qualifications and Requirements headings allowed. We could put Requirements as the bullet list of required experience (6+ years etc). Qualifications could be the preferred or additional qualifications. However the posting lumps them together under "Qualifications Your Experience". It includes both required and preferred. We could split: Requirements = required items (6+ years technical pre-sales experience, consistent history of meeting/exceeding sales targets, proven ability to influence, experience independently creating presentations, pre-sales experience into large enterprises, demonstrated technical expertise in one or more areas, experience partnering with customer success, prior experience architecting solutions, driven by technical curiosity). Qualifications = maybe the "strongly preferred" items? But the posting uses "strongly preferred" for some items. Could treat those as Qualifications. But we must not invent sections with filler. We need to ensure each heading has substantive content. Let's extract: Mission and Who We Are: This is about company mission, values, culture. Could be placed under "About the role"? Actually "About the role" usually describes the role, not company. But we have no separate "About the company" heading allowed. However we could put under "About the role" a paragraph describing the role and company context. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use About the role to include role overview and maybe company mission. That seems acceptable. Responsibilities: The bullet list under "Your Impact Role". We'll list each as

. Requirements: The required items: "6+ years technical pre-sales experience required; demonstrated success selling, implementing, or managing SaaS offerings strongly preferred." Actually that's required? It says required; the SaaS part is strongly preferred. We'll separate. Let's parse the Qualifications section: "Your Experience 6+ years technical pre-sales experience required; demonstrated success selling, implementing, or managing SaaS offerings strongly preferred. Consistent history of meeting or exceeding sales targets, with a track record of executing seven-figure opportunities involving extended sales cycles, multiple buying centers, and multi-product solutions. Proven ability to influence and gain buy-in from key stakeholders in customer-facing engagements. Experience independently creating and delivering customized technical presentations, workshops, or technical validation engagements across varied environments for strategic customer accounts. Pre-Sales experience into large, complex enterprises, typically with multi-billion-dollar revenue and global or multi-regional operations, with a proven ability to manage a targeted number of high-value accounts (typically 10–30). Demonstrated technical expertise or experience in selling, designing, implementing, or managing one or more of the following: Networking, Network Security, Cybersecurity, Private/Public Cloud Security, SOC/Endpoint, SASE, or AI Security. Experience partnering with customer success or support functions to ensure successful implementation and drive solution adoption is strongly preferred. Prior experience in architecting and positioning cybersecurity solutions that address technical challenges and support new business initiatives is strongly preferred. Driven by technical curiosity to self-develop skills in emerging domains, utilizing high AI fluency to elevate work quality and accelerate outcomes." We can treat the first line as requirement (6+ years). The rest could be qualifications (some required, some preferred). But we need to split into Requirements and Qualifications headings. Maybe Requirements: the mandatory items: 6+ years technical pre-sales experience required; consistent history of meeting/exceeding sales targets; proven ability to influence; experience independently creating presentations; pre-sales experience into large enterprises; demonstrated technical expertise in one of the listed areas; (maybe also experience partnering with customer success? It's strongly preferred). Prior experience architecting... strongly preferred. Driven by technical curiosity... maybe required? Not specified. Qualifications: the strongly preferred items: demonstrated success selling SaaS offerings; experience partnering with customer success; prior experience architecting solutions; high AI fluency. But we need to avoid filler. We'll include both sections with substantive bullet lists. Skills: Could be the technical expertise list: Networking, Network Security, Cybersecurity, Private/Public Cloud Security, SOC/Endpoint, SASE, AI Security. Also AI fluency. We'll make a Skills section. Now we need to output HTML fragment only. Structure:

About the role

... paragraph summarizing role and company mission etc.

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Skills

• ...
...

We must not include empty sections. Now craft About the role paragraph: combine mission, who we are, job summary, role description. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the specifics: mission statement, values, hybrid remote, etc. Also the role description: Solutions Consultant evolution of Sales Engineering, drives technical leadership, guides customers, defines technical solutions, end-to-end ownership, evangelizes industry leadership, etc. Also the impact bullet list? Actually that belongs to Responsibilities. So About the role should include the narrative before the bullet list: "Our Mission... Who We Are... This role is remote... You will be part of a culture... Job Summary The Role The Solutions Consultant is the evolution...". We'll combine into a paragraph or multiple paragraphs? Use

for prose. Could have multiple

tags. We must not repeat job title as heading. It's fine. Now Responsibilities: list each bullet from "Your Impact Role". Let's extract them: - Meeting and exceeding sales quotas by building and implementing strategic, technical account plans that target complex, multi-threaded sales engagements involving senior executive stakeholders, technical buyers, and procurement teams. - Conducting advanced discovery using analytical thinking and technical expertise to understand, articulate, and align the technical and operational priorities of your prospects and customers. - Building and leveraging C-level relationships (CIO, CISO, CSO) to establish Palo Alto Networks as a trusted strategic partner and drive a security architecture transformation roadmap. - Using an understanding of key customer business requirements to position, demonstrate, and create high-level designs across the entire PANW portfolio solutions to create business value for large, complex enterprises, typically with multi-billion-dollar revenue and global or multi-regional operations. - Leading successful complex technical validation efforts based on advanced best practices tailored to customer environments to ensure a technical win in assigned and strategic opportunities. - Promoting broad, integrated solutions that include Palo Alto Networks technologies and collaborating with professional services to drive expanded customer outcomes and ensure ongoing platform adoption. - Managing day-to-day technical ownership and serving as the primary technical advisor for assigned accounts, ensuring solution validation, deployment readiness, and expanded solution adoption while maintaining cross-product solution alignment and sustained technical health of the accounts, resulting in a trusted customer partnership. - Proactively supporting customers beyond the sale by monitoring customer usage and outcomes to identify optimization opportunities, emerging needs, and potential risks, partnering with account teams to re-engage customers and guide them toward continued value and expanded platform adoption. - Effectively navigating and influencing the internal cross-functional landscape, collaborating with Professional Services, Customer Success, Specialists, Channel partners, and Support teams to align strategies, remove obstacles, and ensure a one-team approach for a seamless, outcome-driven journey across every stage of the customer lifecycle. - Demonstrating trusted presence and strong communication skills to align customer decision-making through impactful technical engagements, tailored solution briefings, use-case-driven demonstrations, and workshops that translate complex security concepts into clear operational value. - Maintaining broad knowledge of the competitive landscape while validating the value of the Palo Alto Networks platform, clearly differentiating its solutions and aligning customer strategy through situational objection handling and technical advocacy. - Learning continuously to develop technical and professional expertise that drives greater customer impact, while actively contributing to the Solutions Consultant community through knowledge sharing and participation in internal and industry events. We need to keep each as

. Now Requirements: we need to decide which items are required. Let's list required items based on text: - 6+ years technical pre-sales experience required. - Consistent history of meeting or exceeding sales targets, with a track record of executing seven-figure opportunities involving extended sales cycles, multiple buying centers, and multi-product solutions. - Proven ability to influence and gain buy-in from key stakeholders in customer-facing engagements. - Experience independently creating and delivering customized technical presentations, workshops, or technical validation engagements across varied environments for strategic customer accounts. - Pre-Sales experience into large, complex enterprises, typically with multi-billion-dollar revenue and global or multi-regional operations, with a proven ability to manage a targeted number of high-value accounts (typically 10–30). - Demonstrated technical expertise or experience in selling, designing, implementing, or managing one or more of the following: Networking, Network Security, Cybersecurity, Private/Public Cloud Security, SOC/Endpoint, SASE, or AI Security. These seem required (no "strongly preferred"). Now Qualifications (strongly preferred): - Demonstrated success selling, implementing, or managing SaaS offerings. - Experience partnering with customer success or support functions to ensure successful implementation and drive solution adoption. - Prior experience in architecting and positioning cybersecurity solutions that address technical challenges and support new business initiatives. - Driven by technical curiosity to self-develop skills in emerging domains, utilizing high AI fluency to elevate work quality and accelerate outcomes. Also maybe "high AI fluency" is part of that. Now Skills: technical expertise list: Networking, Network