Solutions Architecture Intern - Summer 2027

We need to output only HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. Remove boilerplate, navigation, EEO, etc. Also remove duplicated lines, application instructions. Keep substantive info. We need to parse the posting. First paragraph: "NVIDIA Solution Architects show partners and customers how to be successful with new NVIDIA technologies. In this role, you will team up with experienced Solution Architects working across our full stack. Internships can involve infrastructure, robotics, agentic AI, machine learning and more." That's about the role. Then "What You’ll Be Doing" list: Collaborating with solution architects, engineering or product teams; Understanding technical needs of partners and customers; Developing proof of concept projects with NVIDIA technologies. Then "What We Need To See": bullet list of qualifications: Pursuing a BS, MS, or PhD in Computer Architecture, Computer Networking, Computer/Electrical Engineering (ECE/ECS), Computer Science, Math, Physics, Data Science, or a related technical field.; Strong skills in one or more programming languages (Python, C, C++, etc.); Excellent presentation, communication and teamwork skills; Ability to work independently and with a cross-functional team; Comfortable multi-tasking in a fast-paced environment with changing requirements; Curiosity about AI infrastructure and the modern AI stack (e.g., LLMs, inference serving, agentic or retrieval workloads) is a plus; Strong analytical and problem-solving skills. Then "Ways To Stand Out From The Crowd": bullet list: Experience with NVIDIA GPUs and software libraries; Work experience within an engineering or research community; A computer architecture, networking, data science, or ML foundation with Linux skills; System administration or hands-on hardware experience at the server/rack level, and/or workload orchestration; Academic or industry familiarity with GPUs, AI, CUDA, or related technologies; Ability and eagerness to dig into unfamiliar territories to tackle problems relying on experience from previous work; Data center infrastructure experience, from hardware up through workloads running on NVIDIA AI Factories. Then "This posting represents multiple Solutions Architecture Internships in Santa Clara, CA. Some examples are listed below. Apply to this job posting if any of the descriptions below suit your background and career aspirations." Then list of internship types with descriptions. We need to decide sections: About the role (intro paragraph). Responsibilities (What You’ll Be Doing). Requirements/Qualifications (What We Need To See). Skills (Ways To Stand Out maybe). Benefits? There's mention: "Our internship hourly rates are a standard pay based on the position, your location, year in school, degree, and experience. The hourly rate for our interns is 20 USD - 71 USD. You will also be eligible for Intern benefits." That's pay and benefits. Also "Applications for this job will be accepted at least until September 15, 2026." That's schedule? Actually deadline. Could be schedule? Not exactly schedule. Could be "Schedule" maybe not. The posting doesn't give work schedule (full-time, part-time). So we should not create Schedule section unless there is specific content. There's no schedule info. So we omit Schedule. Pay: we have hourly rate range. So we can create Pay section with that. Benefits: mention "You will also be eligible for Intern benefits." That's vague but it's a benefit statement. Could include Benefits section with that line. However rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Here "Intern benefits" is vague but it's actual statement. It's not placeholder like "TBD". It says you will also be eligible for Intern benefits. That's substantive enough? Might be considered vague but it's actual info. I'd include Benefits section with that sentence. We also have location: Santa Clara, CA. Could be part of About the role or maybe a separate section? Not in list of headings. Could embed in About the role paragraph. We need to avoid repeating job title as heading. No Job ID/requisition numbers as headings. So we ignore JR2025245. We need to remove duplicated lines, boilerplate like EEO, NVIDIA uses AI tools, etc. Also remove "Applications for this job will be accepted at least until September 15, 2026." That's maybe schedule? Could be considered schedule? Actually it's application deadline, not work schedule. The instruction says to remove application instructions. So we drop that line. Also remove "This posting is for an existing vacancy." etc. Now we need to format lists with

• . For each bullet list. We need to preserve all substantive information; do not invent or summarize away detail. We'll produce sections:

  About the role

  NVIDIA Solution Architects show partners and customers how to be successful with new NVIDIA technologies. In this role, you will team up with experienced Solution Architects working across our full stack. Internships can involve infrastructure, robotics, agentic AI, machine learning and more. This posting represents multiple Solutions Architecture Internships in Santa Clara, CA.

  Maybe include location.

  Responsibilities

  • Collaborating with solution architects, engineering or product teams
  • Understanding technical needs of partners and customers
  • Developing proof of concept projects with NVIDIA technologies

  Requirements

  • Pursuing a BS, MS, or PhD in Computer Architecture, Computer Networking, Computer/Electrical Engineering (ECE/ECS), Computer Science, Math, Physics, Data Science, or a related technical field.
  • Strong skills in one or more programming languages (Python, C, C++, etc.)
  • Excellent presentation, communication and teamwork skills
  • Ability to work independently and with a cross-functional team
  • Comfortable multi-tasking in a fast-paced environment with changing requirements
  • Curiosity about AI infrastructure and the modern AI stack (e.g., LLMs, inference serving, agentic or retrieval workloads) is a plus
  • Strong analytical and problem-solving skills

  Skills

  • Experience with NVIDIA GPUs and software libraries
  • Work experience within an engineering or research community
  • A computer architecture, networking, data science, or ML foundation with Linux skills
  • System administration or hands-on hardware experience at the server/rack level, and/or workload orchestration
  • Academic or industry familiarity with GPUs, AI, CUDA, or related technologies
  • Ability and eagerness to dig into unfamiliar territories to tackle problems relying on experience from previous work
  • Data center infrastructure experience, from hardware up through workloads running on NVIDIA AI Factories
  We could also include specifics from internship examples? The posting includes many specific internship descriptions. Should we include them? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should include the internship descriptions as part of the posting. They are substantive. Where to place them? Could be under a section like "Internship Opportunities" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could maybe put them under Responsibilities? But they are more like specific internship roles. Could be considered part of "About the role" or maybe we could create a section "Internship Descriptions" but not allowed. The instruction says: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we must fit all content under those headings. The internship descriptions could be considered part of "About the role" or "Responsibilities". But they are specific examples of internships. Could be placed under "About the role" as additional detail. However that may become long but okay. We need to avoid creating headings with filler. So we will not add extra headings beyond those. Thus we will incorporate internship descriptions into About the role or maybe Responsibilities. Since they describe what you'll be doing in each internship, they could be under Responsibilities. But Responsibilities already has three bullet points from the generic "What You’ll Be Doing". We could extend Responsibilities with more detailed bullet points from each internship type. That would preserve all detail. Thus we will create Responsibilities section with a comprehensive list of duties from the generic plus each internship description. We need to be careful not to lose any detail. Let's extract each internship description: AI Factory Deployment Internship: - Contributing member of an Infrastructure Specialist team. - Work encompasses MEP (Mechanical Electrical Plumbing), Ethernet and InfiniBand networking, DevOps, HPC/AI workloads, cluster administration, and Site Reliability Engineering. - Gain exposure to many aspects of AI Factory deployments. - May help stand up cluster monitoring and telemetry, track utilization and reliability, or automate parts of the bring-up and health-checking process. - Applicants should be familiar with Linux system administration, Python, and networking concepts. - Working knowledge of Slurm and data sciences is a plus. AI Factory / AI Cloud Internship: - Join the team that helps AI Cloud Providers build efficient, de-risked, stable AI factories: full stack, from the bare-metal rack up through application delivery. - Focus on developing true end-to-end architecture understanding, with specific emphasis on delivering highly performant clouds. - Dynamic space where multiple solutions provide optimal outcomes for cloud partners, where self-directed engineers thrive. - Projects are well-scoped and high-impact. - Examples include building agentic solutions to optimize operations, agentic validation of cloud hosting capacity, optimizing inference platforms on customized AI factory hardware, and agentic automation of workflows like BOM → PO → equipment delivery. - Helpful backgrounds include network engineering and design, server-level infrastructure/systems work, and operations tooling with a focus on automation. AI Factory Networking Internship: - If enthusiastic about accelerated computing (CPU, GPU, DPU) and networking technologies and how they can be applied to the real world. - Apply if you have had hands-on experience with data center architectures and the L2-L7 networking protocol stack. - Experience working with both on-prem and cloud-based infrastructure is a plus, as is system-level experience with both hardware and software. - May troubleshoot network performance, do packet-level debugging, tune InfiniBand or RoCE fabrics for RDMA workloads, or bring up entire network fabrics. - Understanding of how GPUs are clustered, leaf-spine topologies, and concepts like RDMA and RoCE will come in handy. - Should enjoy a fast-paced, “firefighting” environment: diagnosing issues and jumping into the trenches to get systems working, rather than waiting for a fully pre-defined project. AI Factory Operations Internship: - Interact with engineering, product, and business development teams to help partners leverage NVIDIA technologies for training, fine-tuning, and inference, as well as retrieval and agentic workloads. - Opportunity to develop full-stack skills within an interdisciplinary environment, covering everything from GPU and networking systems to cluster orchestration and production-ready deployments for AI Factories. - Understanding of GPU server architecture, containerized (Docker/Kubernetes) and Slurm-based workload orchestration, and modern inference-serving and agentic/LLM frameworks is a plus. - Some projects lean toward AI software