Senior Partner Solutions Architect – GSI

We need to output HTML fragment with sections: About the role? Actually the posting includes "About the Job:" which is similar to About the role. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have: - About the Job: content describing role. So we can use

About the role

and put that prose in

. - Responsibilities: list of bullet points. Use

• . - Minimum Qualifications: list of bullet points. Could be Requirements or Qualifications. The instruction says use headings like Requirements, Qualifications, Skills. We have Minimum Qualifications and Preferred Qualifications. Could combine into Requirements (minimum) and Preferred Qualifications maybe as Qualifications? Or we could have two sections: Requirements (minimum) and Preferred Qualifications (maybe as Qualifications). But we need to avoid thin sections; we could combine both into a single Qualifications section with subheadings? But we cannot add extra headings beyond the allowed list? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those. We can have Requirements (minimum) and Qualifications (preferred). Or we could have Requirements covering both minimum and preferred, but better to separate. We also have Compensation + Benefits: includes Pay range and benefits mention. So we can have Pay section with the salary range, and Benefits section with mention of benefits (learn more at Google). However we need to avoid filler like "commensurate with experience". The posting gives specific US base pay range: $189,700—$211,400 USD. Also mentions bonus, equity, benefits. So we can include Pay with that range. Benefits: mention that benefits include ... and link to Google? The posting says "Learn more about benefits at Google." That's vague but still a statement about benefits. We can include Benefits section with that sentence. Schedule: not mentioned, so omit. Skills: maybe we could extract skills from qualifications but we already have Requirements and Qualifications sections; Skills could be omitted if not distinct. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all bullet points from Minimum Qualifications and Preferred Qualifications. Also responsibilities bullet points. Also About the Job paragraph. Also compensation details. Also benefits note. Also maybe note about legal right to work, visa sponsorship, equal opportunity, deadline? Those are boilerplate/legal/EEO etc. According to instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the equal opportunity statement, visa sponsorship note, deadline, etc. Also "Applicants must have the legal right to work..." is legal boilerplate; remove. Also "Wiz is an equal opportunity employer..." remove. Also "By submitting your application..." remove. Also "The application deadline is: 10/31/2026" remove. Also "Compensation + Benefits Compensation for this full-time position includes base salary + bonus + equity + benefits." That's substantive; we keep. Also "Our salary ranges are determined by role, level, and location..." etc. That's substantive about compensation; we can keep in Pay section. Also "Please note that the compensation details listed in US role postings reflect the base salary only, and do not include bonus, equity, or benefits." Keep. Also "Learn more about benefits at Google." Keep in Benefits. Also "US Base Pay Range $189,700—$211,400 USD". Keep. Now we need to format. Structure:

  About the role

  ... (the About the Job paragraph)

  Responsibilities

  • ... each bullet

  Requirements

  • ... Minimum Qualifications bullets

  Qualifications

  • ... Preferred Qualifications bullets

  Pay

  ... compensation details including base salary range, bonus, equity, benefits note.

  Benefits

  Learn more about benefits at Google.

  We must ensure we don't repeat job title as heading. Not include Job ID. Check for duplicated lines: The posting had some duplicated lines? Not obvious. Now we need to extract the About the Job paragraph exactly as given, preserving all info. The About the Job section starts after "About the Job:" and goes until "This role offers a unique opportunity to:"? Actually the text: "About the Job: At Wiz, we move at relentless velocity.... Are you ready for the challenge? This role offers a unique opportunity to:" Then bullet list of opportunities. Those bullet points could be considered part of About the Job or maybe separate? But we have Responsibilities section separate. The "This role offers a unique opportunity to:" list includes items like "Work with Bleeding-Edge Tech:", "Massive Multiplier Effect:" which are more like responsibilities or opportunities. However we already have Responsibilities section with specific items. The "unique opportunity to" list may be considered part of About the role or maybe responsibilities. To avoid duplication, we could incorporate those into About the role paragraph. But we must preserve all substantive information; we can include them in About the role paragraph as part of the description. However we also have a Responsibilities section with specific items. The "unique opportunity to" list is not exactly responsibilities but more like highlights. We could treat them as part of About the role. Let's include them in the About the role paragraph. Thus About the role paragraph will combine the initial description and the opportunity list. Let's copy the text: "At Wiz, we move at relentless velocity. With the explosion of autonomous AI agents, frontier models, and multi-cloud environments, the cloud security landscape is shifting overnight. As a Partner Solutions Architect (GSI), you won't just be supporting deals. You will sit at the absolute bleeding edge, serving as the lead technical strategist co-architecting joint security offerings with top-tier Global Systems Integrators. You will bridge the Wiz Security Graph and our agentless architecture directly into massive digital transformations and emerging AI ecosystems. If you are a high-caliber architect driven to tackle complex technical challenges, work with the most advanced stack in the industry, and build alongside the best GSI team in the world, this is your role. Are you ready for the challenge? This role offers a unique opportunity to: - Work with Bleeding-Edge Tech: Architect solutions spanning AI-SPM, autonomous agentic workflows, Model Context Protocol (MCP), eBPF runtime security, and multi-cloud graph analytics. - Massive Multiplier Effect: Your technical frameworks won't just secure one enterprise. They will become the default reference standard deployed across thousands of client environments by global partner practices." We need to keep the bullet points maybe as
  inside the

  ? But we said use

  for prose. Could embed

  inside

  ? Not typical but allowed. However to keep simple, we could keep them as part of the paragraph with line breaks. But better to keep as

  maybe under About the role? The instruction says use
  • for any list of duties/requirements/benefits. This list is not duties/requirements/benefits but opportunities; still a list. Safer to treat as
    • . But they said use
      • for any list of duties/requirements/benefits. Not explicitly for other lists, but we can still use. However to follow instruction, we could keep them as prose within

        using commas. But we risk losing formatting. I'd keep them as

        • under About the role? Might be okay. But we already have Responsibilities section for duties. The opportunity list is not duties but maybe still okay as
          . I'll include them as
          • inside the About the role section after the paragraph. Thus:

            About the role

            At Wiz, we move at relentless velocity. With the explosion of autonomous AI agents, frontier models, and multi-cloud environments, the cloud security landscape is shifting overnight. As a Partner Solutions Architect (GSI), you won't just be supporting deals. You will sit at the absolute bleeding edge, serving as the lead technical strategist co-architecting joint security offerings with top-tier Global Systems Integrators. You will bridge the Wiz Security Graph and our agentless architecture directly into massive digital transformations and emerging AI ecosystems. If you are a high-caliber architect driven to tackle complex technical challenges, work with the most advanced stack in the industry, and build alongside the best GSI team in the world, this is your role. Are you ready for the challenge?

            • Work with Bleeding-Edge Tech: Architect solutions spanning AI-SPM, autonomous agentic workflows, Model Context Protocol (MCP), eBPF runtime security, and multi-cloud graph analytics.
            • Massive Multiplier Effect: Your technical frameworks won't just secure one enterprise. They will become the default reference standard deployed across thousands of client environments by global partner practices.
            Now Responsibilities: we have list after "Responsibilities:" with bullet points starting with "Architect Next-Gen Joint Offerings:" etc. We'll extract each. Let's copy them: - Architect Next-Gen Joint Offerings: Build scalable technical blueprints for GSI MSP, MDR, and AI threat detection, response, and remediation offerings powered by Wiz. - Embed Security into Enterprise AI & Cloud Blueprints: Partner with GSI practice leads to integrate Wiz as the default security layer in Cloud Migration, App Modernization, and AI transformation reference architectures. - Command Technical & Executive Gravitas: Engage GSI CTOs, CISOs, and Practice Leaders as a trusted peer. Guide executive teams through complex multi-cloud ecosystems (CSPM, DSPM, AI-SPM, CWP) to inspire top-down adoption. - Scale High-Impact Technical Enablement: Move far beyond basic training presentations. Build advanced "train-the-trainer" bootcamps and hands-on technical challenges that empower thousands of GSI architects and consultants to implement and manage Wiz. - Be the Voice of the Ecosystem: Translate the multi-tenancy and massive scale requirements of top GSIs back into actionable product requirements. Partner directly with R&D to push the boundaries of what our platform can do. - Spearhead Industry Thought Leadership: Represent Wiz at key partner summits, lead high-profile technical sessions, and co-author technical whitepapers demonstrating how CNAPP unlocks unprecedented innovation velocity. We'll put each as
          • . Now Requirements (Minimum Qualifications): list: - 5+ Years of Cloud Security Mastery: Deep, hands-on architectural experience across AWS, Azure, GCP, or OCI, with a firm command of cloud-native security paradigms. - GSI DNA & Ecosystem Fluency: Proven experience working inside or alongside Global Systems Integrators. You understand matrixed partner organizations, how practice leads monetize services, and how to build high-level technical champions. - Modern Infrastructure as Code (IaC): Advanced proficiency with tools like Terraform, CloudFormation, or Ansible. You know how to embed security control frameworks directly into IaC deployments. - DevSecOps & Supply Chain Security: Practical experience implementing "Shift Left" guardrails within high-throughput CI/CD pipelines (GitHub Actions, GitLab, Jenkins) to stop risk before code reaches production. - SOC Integration & Telemetry Pipelines: Experience connecting cloud security telemetry into enterprise SIEM/SOAR platforms (Splunk, Cortex XSOAR, Microsoft Sentinel) to streamline incident response and threat detection workflows. - High-Impact Consultative Storytelling: Ability to translate