Domain Consultant (AI Security)
Palo Alto Networks · Seattle, WA · 1 mo ago
RemoteRemoteSalesFull-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. We must not repeat job title. Remove boilerplate like mission, who we are? Actually "Our Mission" and "Who We Are" could be considered "About the role"? The job summary includes description. We need to extract substantive info.
Let's parse the posting:
- Mission statement: not needed? It's generic but could be part of About the role? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role, Responsibilities, Qualifications, etc.
We need to preserve all substantive information, not invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to include sections only when posting has real specific content.
Let's identify content:
- About the role: Could be the mission and who we are? But maybe better to put a short paragraph describing the role: "Your Career As a Prisma AIRS business unit aligned Domain Consultant for AI Security, you provide technical expertise and guidance in securing customers' end to end AI adoption. You will define technical solutions that secure customer’s AI controlled autonomous agents, applications, and enterprise data. You evangelize our industry leadership in AI security by means of securing AI traffic, AI supply chain, and AI governance."
That seems like role description.
- Responsibilities: The bullet list under "Your Impact" includes items: Drive Technical Wins & PoVs: Scope, lead, and execute hands-on Proof of Value (PoV) and technical validation projects to demonstrate real-time AI threat prevention, data loss prevention (DLP), agent governance, and supply chain security in customer environments. Executive Storytelling & Demos: Present tailored solutions and interactive demos to audiences ranging from developers and AI practitioners to CISOs and executive leadership. Influence the Product Roadmap: Serve as the strategic voice of the customer, partnering directly with Product Management and Engineering to channel real-world field feedback into future releases of Prisma AIRS. Architect AI Security Solutions: Design solution architectures that provide holistic AI security within the constraints of enterprise requirements. Thought Leadership & RFx Support: Lead discussions on emerging AI threats and model vulnerabilities, serving as a subject matter expert for RFIs/RFPs. Services & Competitive Positioning: Confidently position Prisma AIRS against market alternatives and align Palo Alto Networks or Partner services to ensure long-term value realization.
These are responsibilities.
- Qualifications: The section "Qualifications Your Experience" includes bullet list: 5+ years of pre-sales experience in AI Security, Cloud Security, Application/API Security, or DevSecOps. Hands-on AI Technical Depth: Proven ability to interact directly with LLM APIs, write scripts, and prototype agentic workflows or security routines across cloud-native platforms (AWS, Azure, GCP, K8s) and REST APIs. Domain Expertise in AI Security: Deep knowledge of AI Runtime Security, Generative AI risks (Prompt Injection, Goal Hijacking), AI Agent/MCP governance, and AI-focused Data Loss Prevention (DLP). Executive Storytelling & Stakeholder Management: Exceptional ability to translate complex AI architectures (RAG, agentic workflows, model orchestration) into clear business outcomes for C-level executives and technical practitioners alike. Consultative Problem-Solving: Demonstrated success guiding enterprise customers through complex pre-sales cycles with a results-oriented mindset. Field Sales Readiness: Willingness to travel as needed for key in-person customer meetings and field events. Proficient in English.
These are qualifications/requirements.
- Skills: Could be extracted from qualifications? Might be overlapping. The instruction says we can have Skills section separate if there is specific content. The qualifications list includes skills. Could we put them under Qualifications? Probably yes. But we need to decide sections: About the role, Responsibilities, Qualifications. Possibly also Skills if distinct. But we can combine qualifications and skills into Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So we can have About the role, Responsibilities, Qualifications. Pay, Benefits, Schedule: The posting includes compensation disclosure: "Compensation Disclosure 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 mentions annual range listed below but no actual numbers are shown in the snippet. It says "/yr" maybe placeholder. There's no actual range given. So we cannot create Pay section because no specific numbers. Benefits: mentions "A description of our employee benefits may be found here." No specific benefits listed. So we cannot create Benefits section. Schedule: not mentioned. So we omit Pay, Benefits, Schedule.
We also have "Our Commitment" and EEO etc which are boilerplate to remove.
Also "Is role eligible for Immigration Sponsorship?: Yes" - that's substantive? It's a specific detail about immigration sponsorship. Could be included maybe under About the role or a separate section? The instruction: include a section ONLY when posting has real specific content for it. Immigration sponsorship is a specific detail. Could be placed under About the role or maybe a separate "Additional Info" but not in allowed headings. Allowed headings are limited to those list. We could put it under About the role as a sentence. Or maybe under Qualifications? Not really. Better to add a short paragraph in About the role.
Also remote/hybrid: "This role is remote, but distance is no barrier to impact. Our hybrid teams collaborate across geographies..." That's about work arrangement. Could be in About the role.
Thus final HTML:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role, Responsibilities, Qualifications, etc.
We need to preserve all substantive information, not invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to include sections only when posting has real specific content.
Let's identify content:
- About the role: Could be the mission and who we are? But maybe better to put a short paragraph describing the role: "Your Career As a Prisma AIRS business unit aligned Domain Consultant for AI Security, you provide technical expertise and guidance in securing customers' end to end AI adoption. You will define technical solutions that secure customer’s AI controlled autonomous agents, applications, and enterprise data. You evangelize our industry leadership in AI security by means of securing AI traffic, AI supply chain, and AI governance."
That seems like role description.
- Responsibilities: The bullet list under "Your Impact" includes items: Drive Technical Wins & PoVs: Scope, lead, and execute hands-on Proof of Value (PoV) and technical validation projects to demonstrate real-time AI threat prevention, data loss prevention (DLP), agent governance, and supply chain security in customer environments. Executive Storytelling & Demos: Present tailored solutions and interactive demos to audiences ranging from developers and AI practitioners to CISOs and executive leadership. Influence the Product Roadmap: Serve as the strategic voice of the customer, partnering directly with Product Management and Engineering to channel real-world field feedback into future releases of Prisma AIRS. Architect AI Security Solutions: Design solution architectures that provide holistic AI security within the constraints of enterprise requirements. Thought Leadership & RFx Support: Lead discussions on emerging AI threats and model vulnerabilities, serving as a subject matter expert for RFIs/RFPs. Services & Competitive Positioning: Confidently position Prisma AIRS against market alternatives and align Palo Alto Networks or Partner services to ensure long-term value realization.
These are responsibilities.
- Qualifications: The section "Qualifications Your Experience" includes bullet list: 5+ years of pre-sales experience in AI Security, Cloud Security, Application/API Security, or DevSecOps. Hands-on AI Technical Depth: Proven ability to interact directly with LLM APIs, write scripts, and prototype agentic workflows or security routines across cloud-native platforms (AWS, Azure, GCP, K8s) and REST APIs. Domain Expertise in AI Security: Deep knowledge of AI Runtime Security, Generative AI risks (Prompt Injection, Goal Hijacking), AI Agent/MCP governance, and AI-focused Data Loss Prevention (DLP). Executive Storytelling & Stakeholder Management: Exceptional ability to translate complex AI architectures (RAG, agentic workflows, model orchestration) into clear business outcomes for C-level executives and technical practitioners alike. Consultative Problem-Solving: Demonstrated success guiding enterprise customers through complex pre-sales cycles with a results-oriented mindset. Field Sales Readiness: Willingness to travel as needed for key in-person customer meetings and field events. Proficient in English.
These are qualifications/requirements.
- Skills: Could be extracted from qualifications? Might be overlapping. The instruction says we can have Skills section separate if there is specific content. The qualifications list includes skills. Could we put them under Qualifications? Probably yes. But we need to decide sections: About the role, Responsibilities, Qualifications. Possibly also Skills if distinct. But we can combine qualifications and skills into Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So we can have About the role, Responsibilities, Qualifications. Pay, Benefits, Schedule: The posting includes compensation disclosure: "Compensation Disclosure 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 mentions annual range listed below but no actual numbers are shown in the snippet. It says "/yr" maybe placeholder. There's no actual range given. So we cannot create Pay section because no specific numbers. Benefits: mentions "A description of our employee benefits may be found here." No specific benefits listed. So we cannot create Benefits section. Schedule: not mentioned. So we omit Pay, Benefits, Schedule.
We also have "Our Commitment" and EEO etc which are boilerplate to remove.
Also "Is role eligible for Immigration Sponsorship?: Yes" - that's substantive? It's a specific detail about immigration sponsorship. Could be included maybe under About the role or a separate section? The instruction: include a section ONLY when posting has real specific content for it. Immigration sponsorship is a specific detail. Could be placed under About the role or maybe a separate "Additional Info" but not in allowed headings. Allowed headings are limited to those list. We could put it under About the role as a sentence. Or maybe under Qualifications? Not really. Better to add a short paragraph in About the role.
Also remote/hybrid: "This role is remote, but distance is no barrier to impact. Our hybrid teams collaborate across geographies..." That's about work arrangement. Could be in About the role.
Thus final 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. Your Career As a Prisma AIRS business unit aligned Domain Consultant for AI Security, you provide technical expertise and guidance in securing customers' end to end AI adoption. You will define technical solutions that secure customer’s AI controlled autonomous agents, applications, and enterprise data. You evangelize our industry leadership in AI security by means of securing AI traffic, AI supply chain, and AI governance. Is role eligible for Immigration Sponsorship?: Yes
But we need to avoid duplication: The mission and who we are may be considered boilerplate? It's not exactly boilerplate but it's generic company description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The mission statement is not explicitly listed as boilerplate to remove, but it's generic. However it's part of the posting; we should preserve ALL substantive information. The mission statement is substantive? It's more like company overview. Might be okay to keep. But we might want to trim to avoid too much fluff. However instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep everything that is substantive. The mission statement is substantive? It's describing the company's mission. It's not directly about the role but it's part of posting. I'd keep it. But we also have "Our Commitment" and EEO etc which are boilerplate to remove. So we remove those. Now Responsibilities: we need- for each responsibility.
We have six responsibilities as bullet points.
We need to capture each exactly.
Let's list them:
1. Scope, lead, and execute hands-on Proof of Value (PoV) and technical validation projects to demonstrate real-time AI threat prevention, data loss prevention (DLP), agent governance, and supply chain security in customer environments.
2. Present tailored solutions and interactive demos to audiences ranging from developers and AI practitioners to CISOs and executive leadership.
3. Serve as the strategic voice of the customer, partnering directly with Product Management and Engineering to channel real-world field feedback into future releases of Prisma AIRS.
4. Design solution architectures that provide holistic AI security within the constraints of enterprise requirements.
5. Lead discussions on emerging AI threats and model vulnerabilities, serving as a subject matter expert for RFIs/RFPs.
6. Confidently position Prisma AIRS against market alternatives and align Palo Alto Networks or Partner services to ensure long-term value realization.
We need to keep the headings like "Drive Technical Wins & PoVs:" etc? The original had headings before each bullet. Should we keep them as part of the liability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The headings like "Drive Technical Wins & PoVs:" are part of the content. So we should include them. Could embed them as bold text? But we only have
and
- . We could include the heading inside the
- as plain text. Thus each
- will contain the heading and description.
Similarly for Qualifications: we have headings like "5+ years of pre-sales experience in AI Security, Cloud Security, Application/API Security, or DevSecOps." Actually that's a bullet without a heading label; it's just a statement. Then "Hands-on AI Technical Depth: Proven ability to interact directly with LLM APIs, write scripts, and prototype agentic workflows or security routines across cloud-native platforms (AWS, Azure, GCP, K8s) and REST APIs." etc.
We'll preserve each bullet.
Now we need to output only HTML fragment, no markdown fences.
Let's construct.
We'll have:
About the role
... (the paragraph)
Responsibilities
- Drive Technical Wins & PoVs: Scope, lead, and execute hands-on Proof of Value (PoV) and technical validation projects to demonstrate real-time AI threat prevention, data loss prevention (DLP), agent governance, and supply chain security in customer environments.
- Executive Storytelling & Demos: Present tailored solutions and interactive demos to audiences ranging from developers and AI practitioners to CISOs and executive leadership.
- Influence the Product Roadmap: Serve as the strategic voice of the customer, partnering directly with Product Management and Engineering to channel real-world field feedback into future releases of Prisma AIRS.
- Architect AI Security Solutions: Design solution architectures that provide holistic AI security within the constraints of enterprise requirements.
- Thought Leadership & RFx Support: Lead discussions on emerging AI threats and model vulnerabilities, serving as a subject matter expert for RFIs/RFPs.
- Services & Competitive Positioning: Confidently position Prisma AIRS against market alternatives and align Palo Alto Networks or Partner services to ensure long-term value realization.