AI Domain Solution Architect

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us" then "AI Domain Solution Architect Job Description". We need to reformat into semantic HTML using

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - About Us (company description) – could be "About the role"? Actually "About Us" is company description, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map sections accordingly. We have: - Job Description: includes description of role, responsibilities, etc. - Key Responsibilities (list) - Skills & Experience (list of skills/experience) - Success in This Role (maybe could be part of responsibilities or separate? Might be considered "Qualifications"? Actually "Success in This Role" describes how success measured; could be considered part of responsibilities or maybe "Qualifications"? But we can treat as "Qualifications" maybe? However we have "Skills & Experience" already. The "Success in This Role" is more about performance expectations; could be considered part of "Responsibilities"? But we already have responsibilities list. Could combine. - Pay: there is a US Pay Transparency Disclaimer with base pay range min & max: 99,000 329,000. Also mention commission plan, benefits. So we have Pay and Benefits sections. - Benefits: described: comprehensive medical coverage, life and disability insurance, a 401(k) plan, an Employee Assistance Program, generous paid time off and leave policies. - Schedule: not mentioned. - About the role: we have a paragraph describing role: "We are seeking an AI-focused Domain Solution Architect (DSA) to join our North America team. This role requires deep technical expertise...". That's about the role. - About Us: company description could be considered "About the role"? Actually "About Us" is company overview. Could be placed as a short paragraph before role description. The instruction says do NOT repeat the job title as a heading. It didn't forbid having a section about company. But the headings list includes "About the role". We could use that for the role description paragraph. The "About Us" could be considered part of "About the role"? Might be okay to include as a

  before the role heading? But we need to follow headings list. Probably we should include an "About the role" section containing the description of the role (the paragraph after "AI Domain Solution Architect Job Description"). We also have "About Us" which is company description; we could include that as a

  before the role heading, but not as a heading. The instruction says "fold minor metadata into a short

  or drop it". Company description is not minor metadata; it's substantive. But we don't have a heading for company. Could we treat it as part of "About the role"? Might be okay to include it as a

  under "About the role". However the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have those headings. We can also have other headings if needed? It says "e.g." implying those are examples, but we should prefer those. Probably we should stick to those headings. Thus we will produce sections: -

  About the role

  containing paragraph(s) describing the role and maybe company overview. -

  Responsibilities

  with
  • list of responsibilities. -

    Skills & Experience

    (or maybe "Qualifications"? The posting has "Skills & Experience". We'll use that heading exactly? The instruction says use headings like Skills. So we can use

    Skills & Experience

    (maybe keep the ampersand). Or we could use

    Skills

    . But better to match the posting: "Skills & Experience". We'll use that. -

    Pay

    with paragraph about base pay range and commission eligibility. -

    Benefits

    with
    • list of benefits. We should not include Schedule as not present. We need to preserve all substantive information: include details like "Drive Technical Architecture & Solution Design:" etc. We'll convert each bullet into
    • . We need to remove boilerplate: background check statement, US Pay Transparency Disclaimer? Actually we need to keep pay info but can drop the boilerplate about background check? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The background check statement is legal; we should remove it. Also the "US Pay Transparency Disclaimer" includes some legal text; we need to keep the pay range but can drop the surrounding boilerplate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The pay range is substantive. The surrounding text about commission plan, benefits, etc is also substantive. The "US Pay Transparency Disclaimer" sentence is somewhat boilerplate but includes info about US only. Might be considered legal? It's about pay transparency; maybe we keep it as part of Pay section? But we can keep the essential info: base salary range, commission plan, benefits. The instruction says remove legal boilerplate; the disclaimer might be considered legal. However the pay range is substantive; we can keep that and maybe a short sentence: "If this role is filled in the United States of America, the starting base salary will be within the applicable pay range displayed below. In addition to base salary, this position may be eligible for a commission plan and a competitive benefits package." That's not purely legal; it's informational. We'll keep that. We also need to remove duplicated lines: there may be duplicates like "We empower you to be bold..." etc under "What We Offer". That's marketing fluff; maybe we should keep? It's substantive? It's more about company culture; could be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "What We Offer" section is promotional; not explicitly listed to remove, but could be considered boilerplate? It's not legal/EEO. It's about culture; maybe we keep as part of "About the role"? But we already have role description. Could include as a paragraph under About the role? However the instruction says prefer a few substantive sections over many thin ones. The "What We Offer" is fluffy; maybe we can drop it as it's not specific to role. The instruction says preserve ALL substantive information; does "We empower you to be bold..." count as substantive? It's more generic marketing. Might be considered boilerplate. Safer to drop it. Also the "SUSE Values" section is definitely boilerplate; remove. Also "Success in This Role" is substantive; we could incorporate into Responsibilities or Qualifications. But we have Skills & Experience already. Could treat "Success in This Role" as a separate section maybe "Qualifications"? But we already have Skills & Experience. Might be better to merge Success in This Role into Responsibilities or Skills & Experience? It describes how success measured; could be considered part of Responsibilities (outcomes). We'll add as a
      under Responsibilities? Actually Responsibilities already list duties; success metrics could be separate. But we can add a

      after responsibilities describing success metrics. That's okay. We need to ensure we don't create empty sections. Now let's extract content. About the role paragraph: "We are seeking an AI-focused Domain Solution Architect (DSA) to join our North America team. This role requires deep technical expertise in AI infrastructure, accelerated computing, Kubernetes, and enterprise AI platforms, combined with the ability to translate that expertise into solutions for complex customer environments. As a Domain Solution Architect, you will be a technical specialist embedded within the sales organization, working alongside Account Executives, Solution Architects, partners, and customers to architect and validate enterprise AI solutions. You will focus on helping customers move AI workloads from experimentation into secure, scalable, production-ready environments. The ideal candidate combines strong Kubernetes, Linux, and infrastructure architecture skills with hands-on knowledge of GPU-accelerated computing and the NVIDIA AI ecosystem." That's the role description. We could also include the "About Us" paragraph before that? Might be considered company overview; we could prepend a short paragraph: "SUSE is a global leader of enterprise open source software..." etc. That's substantive about company. Could be included under About the role as well. But the heading is About the role, not About the company. However we can include both paragraphs under that heading. Now Responsibilities list: From "Key Responsibilities" we have bullet points each starting with a bold phrase. We'll extract each as

      • . List: - Drive Technical Architecture & Solution Design: Lead discovery sessions, technical evaluations, architecture workshops, and infrastructure sizing for complex customer AI environments—translating enterprise workloads such as LLM inference, fine-tuning, and RAG into scalable architectures built on SUSE AI Factory, Rancher Prime, and the NVIDIA accelerated computing stack. - Deliver Technical Validation & Field Sales Execution: Partner with Account Executives and field Solution Architects throughout the sales cycle to lead technical qualification, build targeted PoCs, deliver hands-on demonstrations, and develop technical proposals and RFI/RFP responses. - Guide Agentic AI Architecture: Help customers understand the infrastructure, integration, security, and governance requirements for agentic AI, multi-agent systems, and Model Context Protocol (MCP) integrations in enterprise production environments. - Collaborate Across the AI Ecosystem: Jointly architect customer solutions with strategic ecosystem partners—including hardware vendors, systems integrators, and cloud providers—to optimize AI compute, high-speed networking, storage, and overall platform architecture. - Build Field Capability & Repeatable Assets: Develop reusable reference architectures, solution blueprints, demonstrations, and technical enablement materials that scale AI expertise across regional and global field teams. - Act as the Voice of the Customer: Capture technical feedback and emerging platform requirements from customer environments and communicate them to SUSE Product Management and Engineering to help inform product direction. - Serve as an AI Infrastructure SME: Translate complex topics—including GPU architecture and partitioning, workload scheduling, multi-tenancy, high-performance networking, storage, and air-gapped operations—into clear technical and business value for audiences ranging from platform engineers to C-suite technology executives. Now Skills & Experience list: From "Skills & Experience" heading, we have bullet points each with a bold label. We'll extract each as
      • . List: - Presales Architecture Experience: Proven track record translating deep technical expertise into effective customer solutions, proposals, presentations, demonstrations, RFP responses, and hands-on workshops in a presales, solution architecture, or technical consulting role. - Technical Communication & Leadership: Ability to simplify complex AI and infrastructure concepts for both technical and executive audiences, connecting technical architecture to business outcomes.