DirectJobHub
Jobs · Sales

Solutions Consultant 2 - Federal

Palo Alto Networks · District of Columbia, United States · 1 mo ago
RemoteRemoteSales$206k–$284k/yrFull-time
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. Must not repeat job title. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. Content: - Mission statement etc. Might be "About the role"? Actually we have "Our Mission", "Who We Are", "Job Summary", "Your Career", "Your Impact", "Qualifications", "Your Experience", "Qualifications Compensation Disclosure", "Our Commitment". We need to map to sections. We need to produce headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: Could be "Job Summary" and "Your Career" and "Your Impact". So we can put description under About the role. - Responsibilities: The bullet list under "Your Impact" includes many responsibilities. So we can put those as
  • . - Requirements: Could be "Qualifications" and "Your Experience". Those list experience requirements. - Qualifications: Might be overlapping with Requirements. But we need to decide: maybe Requirements = mandatory experience, Qualifications = preferred? The posting has "Qualifications Your Experience" list with many items, some "preferred". Could treat as Requirements. - Skills: Could be extracted from responsibilities like influencing, communication, technical presentations, etc. Might be separate. - Benefits: Not explicitly listed besides compensation disclosure and benefits link. There's a line: "A description of our employee benefits may be found here." No specifics. So we should not create Benefits section because no specific content. - Pay: There is compensation disclosure with salary range: $206,400.00 - $283,800.00/yr. Also mention restricted stock units and bonus. So we can include Pay section with that. - Schedule: Not mentioned. No schedule info. So omit. Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Pay. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info, not invent. Let's extract text. About the role: combine "Our Mission", "Who We Are", "Job Summary", "Your Career". But we should not repeat mission statement maybe as prose. We'll produce a

    summarizing? But we must not summarize away detail; we need to preserve all substantive information. That means we should include the sentences as they are, not paraphrase. However we can combine multiple paragraphs into one

    maybe but that would be summarizing? Actually we can keep them as separate

    elements under the heading. That's fine. We need to avoid boilerplate like "Our Mission At Palo Alto Networks®, we’re united by a shared mission—to protect our digital way of life..." That's substantive? It's about company mission, maybe not role-specific but still part of posting. Should we include? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it. However we need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The mission statement is not boilerplate; it's part of the posting. So we keep. Similarly "Who We Are" etc. Thus About the role section will contain multiple

    elements with those paragraphs. Responsibilities: list from "Your Impact". Let's extract each bullet line (starting with "Meeting and exceeding sales quotas..." etc). We'll put each as

  • . Requirements: from "Qualifications Your Experience". That's a list of items. We'll put each as
  • . Skills: maybe we can extract skills like "strong communication skills", "influencing through effective presentations", "technical presentations, workshops, or technical validation engagements", "creating and delivering technical presentations", "partnering with Customer Support", etc. But many overlap with responsibilities. Could create a Skills section with items like "Technical presentation and workshop delivery", "Influencing stakeholders", "Cross-functional leadership", "Understanding of data networking and/or modern application design and cloud architectures", "Experience with Network Security, SASE, SaaS, CNAPP and/or SOC Transformation Technologies", "Proficiency in English". However we must not invent; we need to pull from text. The text includes: "Understanding of data networking and/or modern application design and cloud architectures", "Experience in delivering cybersecurity solutions that solve technical challenges and influence new business initiatives is preferred", "Influencing and gaining buy-in from key stakeholders, either in a customer-facing or internal role; prior experience in a pre-sales role is ideal", "Creating and delivering technical presentations, workshops, or technical validation engagements", "Experience in selling, designing, implementing, or managing one or more of the following solutions: Network Security, SASE, SaaS, CNAPP and/or SOC Transformation Technologies", "Partnering with Customer Support functions to ensure successful implementation and adoption of sold solutions", "Experience in complex sales involving long sales processes with multiple buying centers and multi-product solutions are preferred", "Proficient in English". Also "Demonstrating strong communication skills, influencing through effective presentations and customer-specific demos, and conducts technical engagements and workshops that are clear and impactful, simplifying complex ideas for various audiences". That's also a skill. Thus we can create Skills section with those items. Pay: include salary range and mention of RSU and bonus. Now ensure we don't include sections with filler like "commensurate with experience". Not present. We must not include Benefits section because no specifics. Schedule omitted. Now produce HTML:

    About the role

    Our Mission At Palo Alto Networks®, we’re united by a shared mission—to protect our digital way of life. We thrive at the intersection of innovation and impact, solving real-world problems with cutting-edge technology and bold thinking. Here, everyone has a voice, and every idea counts. If you’re ready to do the most meaningful work of your career alongside people who are just as passionate as you are, you’re in the right place.

    Who We Are In order to be the cybersecurity partner of choice, we must trailblaze the path and shape the future of our industry. This is something our employees work at each day and is defined by our values: Disruption, Collaboration, Execution, Integrity, and Inclusion. We weave AI into the fabric of everything we do and use it to augment the impact every individual can have. If you are passionate about solving real-world problems and ideating beside the best and the brightest, we invite you to join us! This role is remote, but distance is no barrier to impact. Our hybrid teams collaborate across geographies to solve big problems, stay close to our customers, and grow together. You will be part of a culture that values trust, accountability, and shared success where your work truly matters.

    Job Summary Your Career The Solutions Consultant is the evolution of the traditional Sales Engineering role, aligning how we best serve our customers in understanding their environment, providing solution guidance and ensuring value realization in their investment with Palo Alto Networks. As a Solutions Consultant you provide technical leadership and expertise and guidance in your customer’s security transformation journey. You will play a key role in defining technical solutions that secure a customer’s key business imperatives and ensuring value realization of their investment with Palo Alto Networks. You evangelize our industry leadership in on-prem, cloud, and security operations services that establish PANW as your customer’s cybersecurity partner of choice.

    Then Responsibilities:

    Responsibilities

    • Meeting and exceeding sales quotas by building and implementing strategic, technical account plans that target cross-platform solutions
    • Understands Key customer business requirements and has the ability to position, demonstrate and create high level designs across the entire PANW portfolio solutions creating business value for customers
    • Ability to drive customer adoption of Palo Alto Networks Platform
    • Building customer relationships by helping customers achieve increased productivity, operational efficiency, security efficacy, and greater flexibility to innovate
    • Conducting discovery to understand and articulate the key technical, operational, and commercial imperatives of your prospects and customers
    • Working closely with Professional Services, Customer Success and Specialist teams to ensure overall customer implementation and adoption of solutions
    • Demonstrating strong communication skills, influencing through effective presentations and customer-specific demos, and conducts technical engagements and workshops that are clear and impactful, simplifying complex ideas for various audiences
    • Leading successful technical validation efforts based on best practices to ensure technical win in assigned opportunities
    • Demonstrates Cross functional leadership driving collaboration and orchestrating supporting resources (Specialists, Channel Resources, Customer Support) to ensure a one-team approach that demonstrates a cohesive strategy
    • Promoting end-to-end solutions that include PANW and/or partner professional services to ensure customers realize business value sooner
    • Understanding the competitive landscape and effectively differentiating PANW's leadership in the cybersecurity space
    • Continuously investing in yourself to develop technical and professional skills that drive your ever-increasing contributions to success of our customers while actively participating within the Solutions Consultant community and at industry events
    • Identifying technical stakeholders and cultivating relationships with key personas to build and drive a security architecture transformation roadmap
    Requirements:

    Requirements

    • 6+ years experience in pre-sales/sales engineering
    • Security Clearance Requirement: Active Top Secret/SCI with Full Scope Polygraph
    • Understanding of data networking and/or modern application design and cloud architectures
    • Experience in delivering cybersecurity solutions that solve technical challenges and influence new business initiatives is preferred
    • Influencing and gaining buy-in from key stakeholders, either in a customer-facing or internal role; prior experience in a pre-sales role is ideal
    • Creating and delivering technical presentations, workshops, or technical validation engagements
    • Experience in selling, designing, implementing, or managing one or more of the following solutions: Network Security, SASE, SaaS, CNAPP and/or SOC Transformation Technologies
    • Partnering with Customer Support functions to ensure successful implementation and adoption of sold solutions
    • Experience in complex sales involving long sales processes with multiple buying centers and multi-product solutions are preferred
    • Proficient in English
    Skills: We could list skills distinct from requirements. But many overlap. Might be okay to have Skills section with items like: - Strong communication skills - Influencing through effective presentations and customer-specific demos - Conducting technical engagements and workshops - Technical validation efforts based on best practices - Cross-functional leadership and collaboration - Understanding of competitive landscape and differentiation - Continuous technical and professional skill development - Identifying and cultivating technical stakeholder relationships But these are basically responsibilities. However we need a Skills section only if posting has real specific content for it. The posting does not have a separate "Skills" heading; but we can infer skills from responsibilities and qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we should not create Skills if it's thin. But we have enough distinct skill items? Might be better to combine Skills into Requirements or Responsibilities. However the instruction says we must use headings only when posting has real, specific content for it. There's no explicit Skills section, but we could argue that the posting includes skill-related statements (like "Understanding of data networking...", "Creating and delivering technical presentations...", "Proficient in English") which are skills. So we could create a Skills section with those. But we already put those in Requirements. Might be duplication. Better to keep Requirements as the qualifications/experience, and Skills as abilities like communication, influencing, presentation, technical validation, cross-functional leadership, stakeholder cultivation, continuous learning, etc. However many of those are also in Responsibilities. To avoid duplication, we could put Skills as a short list

Similar jobs