Field Marketing Intern - Summer 2027

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: "About Out Summer Internship Program" (typo). There's description about program. Then "Your Role As a Field Marketing Intern..." then "Key Responsibilities" list. Then "Qualifications". Then "Benefits". Then pay range: "United States of America Intern Pay Range $20 - $25 USD". Also schedule: program takes place from June – August 2027 (10-week program). That's schedule info. Also maybe "Skills" not explicitly listed; but we have "Proficiency in Microsoft Office Suite (especially Excel and PowerPoint)" etc. Could treat as Skills. However we should not create sections with filler. We have content for About the role? The "About Out Summer Internship Program" could be considered About the role? Actually "About the role" heading is for role description. The posting includes "Your Role As a Field Marketing Intern..." which is role description. So we can put that under

About the role

with paragraph(s). Then Responsibilities: we have "Key Responsibilities" with bullet points. Use

• . Then Qualifications: list. Then Benefits: list. Then Pay: we have pay range. Then Schedule: program dates. Also maybe Skills: we could combine with Qualifications? But we have separate Skills section optional; we could include Skills if we have specific skill list: "Proficiency in Microsoft Office Suite (especially Excel and PowerPoint)", "Strong organizational skills", "Excellent written and verbal communication skills", "Detail-oriented with a proactive, problem-solving mindset", "Comfortable working in a fast-paced, collaborative environment". Those could be skills. However Qualifications already includes many of those. To avoid duplication, we could put Skills separate if we have distinct skill list. But Qualifications includes "Rising Junior or Senior currently pursuing a degree in Marketing, Business, Communications, or related field" plus skills. Might be okay to have Qualifications and Skills separate but risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one Qualifications section. But they asked to use headings for those categories if content exists. We could still include Skills if we have distinct content not already in Qualifications. However Qualifications already includes many skill-like items. To avoid thin sections, maybe omit Skills and put those under Qualifications. Similarly, we have no separate "Requirements" besides Qualifications; but we could treat Qualifications as Requirements. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Requirements if we have content distinct from Qualifications. The posting has "Qualifications" list; we could treat that as Requirements. But they also have Qualifications heading in the posting. So we should follow the posting: they have "Qualifications". So we will output

  Qualifications

  . For Requirements, we could omit if no separate content. The posting does not have a separate "Requirements" section besides Qualifications. So we skip Requirements. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Now we need to preserve all substantive information, remove boilerplate, navigation, legal, EEO, etc. Remove duplicated lines. Also remove "Veeam is the Data and AI Trust Company..." etc? That's company description; is that substantive? It's about company, not role. Might be considered boilerplate? It's not navigation/legal/EEO but it's generic company overview. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company overview might be considered not boilerplate but could be kept? It's not about the role. However we need to preserve ALL substantive information; does company overview count as substantive? It's about the company, not the role. The instruction didn't say to remove company overview. It says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we keep company overview? But we need to output only HTML fragment; we could include a paragraph about company under maybe "About the role"? But they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings. The company overview could be placed under a generic

  before sections? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra paragraphs before headings. However typical approach: we include sections with headings and content. Could include an introductory paragraph about the company under no heading? Might be okay but could be considered filler. The instruction: Prefer a few substantive sections over many thin ones. So maybe we include a brief intro paragraph before first heading? Not sure. Better to follow the structure: start with

  About the role

  containing the role description and maybe company overview? Actually "About the role" should describe the role, not company. The company overview could be placed under a separate

  About Veeam

  but that's not in allowed headings list. So maybe we incorporate company overview into About the role as context. But that may dilute. Given the instruction to preserve ALL substantive information, we should keep the company overview somewhere. Could add a

  before first heading: a brief description of Veeam. That is substantive. It's not a heading, but allowed. Thus output:

  Veeam is the Data and AI Trust Company, specializing in helping organizations ensure their data and AI are fully understood, secured, and resilient to enable the acceleration of safe AI at scale. As the market leader in both data resilience and data security posture management, Veeam is built for the convergence of identity, data, security, and AI risk. Headquartered in Seattle with offices in more than 30 countries, Veeam protects over 550,000 customers worldwide, who trust Veeam to keep their businesses running. Join us as we go fearlessly forward together, growing, learning, and making a real impact for some of the world’s biggest brands.

  Then

  About the role

  with paragraph about Summer Internship Program and role description. But note: "About Out Summer Internship Program" is a heading in the posting; we could treat that as About the role. We'll combine. Thus:

  About the role

  Our Summer Internship Program is designed for students entering their final year of university who are eager to gain meaningful, real-world experience in a fast paced, collaborative, and professional environment. As a Summer Intern, you'll participate in a comprehensive onboarding experience led by our University Relations team to set you up for success from day one. Throughout the program, you'll also have the opportunity to participate in weekly professional development sessions, networking events, social activities, and other engaging experiences designed to support your personal and professional growth. The program takes place from June – August 2027 (10-week program).

  As a Field Marketing Intern, you will support the planning and execution of regional marketing programs that drive pipeline, customer engagement, and sales alignment. This role provides hands-on experience in event marketing, account-based programs, and cross-functional coordination with sales and partner teams. You’ll gain exposure to how marketing directly influences revenue through in-market activities and targeted campaigns.

  Then Responsibilities: list. We need to extract bullet points from "Key Responsibilities". The posting lists: Event & Program Support - Assist in the planning and execution of field marketing programs such as executive dinners, regional events, trade shows, and partner activations - Coordinate logistics including venue research, vendor coordination, attendee tracking, and on-site support - Help manage event timelines, run-of-show documents, and post-event follow-ups Sales & Partner Alignment - Work closely with regional sales teams to support account targeting, invite strategies, and attendee prioritization - Assist in coordinating joint programs with partners to drive pipeline and relationship building - Help track sales follow-up actions and support post-event engagement efforts Campaign & Audience Support - Support development of targeted outreach campaigns tied to regional programs and key accounts - Assist with segmentation lists, invitation tracking, and campaign performance monitoring - Help ensure messaging aligns with regional priorities and audience needs Research & Insights - Conduct research on local markets, industry events, and competitive activity to inform field programs - Help compile attendee insights, event performance metrics, and pipeline influence data - Support preparation of summaries for regional and leadership reviews Content & Asset Support - Assist in creating event briefs, internal planning docs, and presentations for field programs - Help maintain regional marketing assets and ensure materials are current and accessible We need to output as
  • for any list of duties/requirements/benefits. Should we keep subheadings? Could just list all items as
  • . Or we could keep subheadings as

    maybe? But instruction: Use

    • for any list of duties/requirements/benefits. So we can just flatten list. Thus
      • Assist in the planning and execution of field marketing programs such as executive dinners, regional events, trade shows, and partner activations
      ... etc. Now Qualifications: list: - Rising Junior or Senior currently pursuing a degree in Marketing, Business, Communications, or related field - Strong organizational skills with the ability to manage multiple moving pieces - Excellent written and verbal communication skills - Proficiency in Microsoft Office Suite (especially Excel and PowerPoint) - Interest in event marketing, sales alignment, or customer engagement strategies - Comfortable working in a fast-paced, collaborative environment - Detail-oriented with a proactive, problem-solving mindset We'll output as
      • ...
      . Benefits: list: - Paid Company Holidays during your internship - Tech Stipend to help set up your workspace - 8 Hours of Paid Volunteer Time through our Veeam Cares Program - Personal and Professional Development through our Internship Program We'll output as
      • ...
      . Pay: we have "United States of America Intern Pay Range $20 - $25 USD". Also note: "The pay range posted is an hourly rate of base pay. When making an offer of employment, Veeam will take into consideration the candidate’s expectations, experience, education, scope of responsibility for the role, and the current market demands." That's substantive. We'll include that as paragraph(s) under Pay. Thus

      Pay

      The pay range posted is an hourly rate of base pay. When making an offer of employment, Veeam will take into consideration the candidate’s expectations, experience, education, scope of responsibility for the role, and the current market demands.

      United States of America Intern Pay Range $20 - $25 USD

      Schedule: we have program dates: "The program takes place from June – August 2027 (10-week program)." Already included in About the role paragraph. But we could also have a Schedule section with that detail. However we already used it in About the role. To avoid duplication, we could keep schedule info only in About the role and not create a separate Schedule section (since it's duplicate). The instruction: Remove duplicated lines. So we should not repeat same info. So we will not create a Schedule section; we already included schedule in About the role. So we omit Schedule heading. Thus final HTML fragment: opening

      company overview, then sections. Check for any boilerplate: EEO statement at end: "Veeam Software is an equal opportunity employer..." etc. Remove that. Also remove "All your information will be kept confidential..." etc. Remove application instructions? There's none explicit. Also remove "By applying for this position, you consent..." etc