MarketVector Marketing Summer Intern
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We need to parse the posting. Key info: - Position: MarketVector Marketing Summer Intern - Legal Entity: MarketVector Indexes - Location: New York, NY - Department: Product Management and Marketing - Reporting to: Head of Product Management and Marketing - FLSA Status: Non-Exempt Full Time Summer (maybe schedule info) - VanEck description: background. - Intern program details: 10 weeks, June 7 – August 13. - MarketVector description. - Joining MarketVector description. - This Internship Is Your Opportunity To ... (list) - What You’ll Do (list of duties) - What We’re Looking For (list of qualifications/skills) - Education: Currently entering junior level (3rd year) or higher within a 4-year college program. Prior corporate or internship experience helpful but not required. - Why Join MarketVector? (list of benefits) - Compensation: The maximum hourly rate for this position is $25 an hour. - EEO boilerplate to remove. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we drop the EEO paragraph. We need to preserve all substantive info. We need to decide sections. Potential sections: - About the role (maybe a brief description) - Responsibilities (What You’ll Do) - Requirements / Qualifications (What We’re Looking For + Education) - Skills (maybe combine with Requirements) - Benefits (Why Join MarketVector? plus intern program details) - Pay (Compensation) - Schedule (program duration: 10 weeks, June 7 – August 13) We must not create sections with filler like "commensurate with experience". We have actual content. We need to avoid repeating job title as heading. We need to output only HTML fragment. Let's craft. First, maybe a short
for metadata: Position, Legal Entity, Location, Department, Reporting to, FLSA Status. Could be in a paragraph. Then sections. About the role: Could be a paragraph summarizing the role: "As a Marketing Intern at MarketVector Indexes, you will work closely with cross-functional teams to bring the MarketVector brand to life..." But we must not invent or summarize away detail; we can paraphrase but must preserve all substantive info. It's okay to combine sentences as long as we don't lose info. Probably safe. But we need to be careful: The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we can't omit details. Summarizing may be okay if we keep all details? Safer to keep bullet points for responsibilities and requirements, and maybe a short intro paragraph that is just a summary but not omitting details. However, we risk losing some detail if we summarize. Better to avoid a separate About the role section if we can just go straight to Responsibilities. But the instruction says we should use headings for sections like About the role, Responsibilities, etc. It doesn't mandate we must include About the role; we include only when posting has real specific content for it. The posting does have a description of the role in "Joining MarketVector" and "This Internship Is Your Opportunity To". That could be considered About the role. We can include that as a
under About the role heading, but we must ensure we don't lose any detail. We could copy the relevant sentences verbatim. Let's extract substantive paragraphs: From "Joining MarketVector Joining MarketVector means joining a fast-paced, global team where finance, marketing, and technology intersect. You’ll collaborate across functions worldwide, partnering with product managers, researchers, and business development professionals, to craft and deliver marketing campaigns that showcase the indexes behind some of the world’s most recognized and innovative Exchange Traded Funds (ETFs). Through educational sessions, mentorship, and networking events, you will gain exposure to senior management, develop an understanding of the financial services industry, and build critical business skills." From "This Internship Is Your Opportunity To Learn how global indexes power investing and drive financial innovation.Get first-hand experience in how marketing and communications are done in financial services.Experiment with content creation across digital, social, and traditional channels.Contribute directly to campaigns that expand MarketVector’s brand and support business growth.Build creative, analytical, and communication skills in a dynamic, entrepreneurial environment. You’ll be part of a small, energetic, global team that values curiosity, creativity, and bold ideas. The work you do will make a tangible impact on how the MarketVector story is told worldwide." These are substantive. We can combine them into a
under About the role. Now Responsibilities: The bullet list under "What You’ll Do". We'll output as
- items.
Now Requirements/Qualifications/Skills: The posting has "What We’re Looking For" list, plus Education bullet. Could split into Requirements (education) and Qualifications/Skills (the list). But we can combine into a single Requirements section with subpoints? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple headings. We need to decide which to include based on content. We have: - Education: Currently entering junior level (3rd year) or higher within a 4-year college program. Prior corporate or internship experience is helpful but not required. - What We’re Looking For list: Strong interest in marketing, media, and visual design. Experience creating or editing content (videos, presentations, newsletters, blogs, podcasts). Familiarity with digital marketing tools (Google Analytics, Canva, SEO, social media). Proficiency with design and presentation tools such as Adobe Creative Suite (InDesign, Photoshop, Illustrator), PowerPoint, Flourish, and Canva. Strong writing and communication skills, with attention to detail. Analytical mindset and proficiency in Excel or similar tools. Knowledge of PowerPoint, Word, HTML basics. Familiarity with AI tools (e.g., ChatGPT, Claude, ElevenLabs) is a plus. Ability to work independently and collaboratively in a fast-paced environment. A second language (especially German, Korean, Portuguese, or Chinese) is a plus. We could treat Education as Requirements, and the list as Qualifications/Skills. Or we could have Requirements (education) and Skills (the list). Let's do: - Requirements (
Requirements
) containing education paragraph. - Skills (Skills
) containing the list from What We’re Looking For. Alternatively, we could combine into Qualifications. But we have both headings available; we can use both. Now Benefits: "Why Join MarketVector?" list plus intern program details (exposure across firm, educational, mentorship, networking events, exposure to senior management, understanding financial services, learn critical business skills, program spans 10 weeks June 7 – August 13). Also maybe "VanEck’s Summer Intern Program includes exposure across the firm through educational, mentorship, and networking events. As an Intern, you will also be exposed to the firm’s senior management, gain an understanding of the financial services industry and learn critical business skills. Our internship program will build more than just your resume — it will challenge your knowledge, build your network and drive your career path. Our program spans 10 weeks and typically runs from June 7 – August 13." That's benefits. We can put that under Benefits heading. Pay: Compensation: maximum hourly rate $25 an hour. Schedule: Could be the program duration (10 weeks, June 7 – August 13). But we already used that in Benefits. However schedule could be separate: The internship runs 10 weeks, June 7 – August 13. Since we already used that info in Benefits, we might duplicate if we also put in Schedule. The instruction: do not repeat duplicated lines. So we should avoid duplicating the same info in two sections. We need to decide where to place schedule info. The schedule is substantive; we could put it under Schedule heading and not repeat in Benefits. But Benefits also includes other items like exposure, mentorship, etc. We could keep schedule under Schedule and keep benefits focusing on other aspects (exposure, mentorship, networking, skill building). However the benefits text includes the program duration; we could split: keep duration under Schedule, and keep other benefits under Benefits. Thus: - Benefits heading: list of benefits: exposure across firm via educational, mentorship, networking events; exposure to senior management; understanding financial services; learn critical business skills; challenge knowledge; build network; drive career path; build more than resume; etc. - Schedule heading: program spans 10 weeks, typically runs from June 7 – August 13. Now Pay heading: maximum hourly rate $25 an hour. Now we need to ensure we don't include boilerplate: EEO paragraph removed. Also "VanEck is committed to treating all applicants..." is EEO; remove. Also "VanEck does not and will not discriminate..." remove. Now we need to ensure we don't include application instructions like "apply now!" etc. The posting includes "If you are looking to gain valuable hands-on experience while working with talented individuals, apply now!" That's application instruction; remove. Also "If you are looking to gain valuable hands-on experience while working with talented individuals, apply now!" appears earlier? Actually near the end of VanEck description: "If you are looking to gain valuable hands-on experience while working with talented individuals, apply now!" That's application instruction; remove. Also "If you are a high-energy individual with a strong work ethic, excellent team skills, and outstanding communication skills, we would like to speak with you." That's not exactly application instruction but maybe a call to action; but it's part of the description; we might keep as it's substantive about desired traits? It's more like a call but could be considered part of What We’re Looking For? It's similar to "Strong interest..." but it's generic. Might be okay to keep but it's somewhat fluff. However it's not boilerplate; it's a statement about desired traits. Could keep under What We’re Looking For? But we already have a list; we could incorporate that sentence as a bullet? But it's not a bullet. Might be okay to keep as a paragraph under About the role? It says "If you are a high-energy individual with a strong work ethic, excellent team skills, and outstanding communication skills, we would like to speak with you." That's more like a call to apply; but it's also describing desired traits. I'd lean to keep it as part of What We’re Looking For? But we already have a list; we could add a bullet: "High-energy individual with strong work ethic, excellent team skills, outstanding communication skills." However the instruction says do not invent or summarize away detail; we can keep it as is. But we need to avoid duplication: The list already includes strong writing and communication skills, attention to detail. The high-energy etc is somewhat similar but not identical. We could keep it as a separate bullet under Skills? Might be okay. But to be safe, we could keep that sentence as a paragraph under About the role or under a general description. However it's not strictly about the role; it's a call. I'd rather omit it to avoid fluff. The instruction says preserve ALL substantive information; is that substantive? It's a statement about desired traits; could be considered substantive. But it's somewhat generic. I'd keep it as part of What We’re Looking For as a bullet. Let's extract the exact sentence: "If you are a high-energy individual with a strong work ethic, excellent team skills, and outstanding communication skills, we would like to speak with you." We'll turn into a bullet: "High-energy individual with strong work ethic, excellent team skills, outstanding communication skills." Now we need to ensure we don't lose any other details. Let's list all substantive content we need to include