Jobs · Massachusetts

PRODUCT DESIGN ENGINEERING INTERN OPPORTUNITIES

SharkNinja France · Needham, MA · 1 mo ago
$27–$40/hrVolunteer
We need to output only HTML fragment, with sections for headings where there is real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to preserve all substantive information. Let's parse the posting: - Intro: "Product Design Engineering Intern Opportunities About Us SharkNinja is a global product design and technology company..." This is about company description. Could be "About Us" but we only have headings list; we can put under "About the role"? Actually "About the role" heading is for description of role. The company description may be considered "About Us" but not in list. We could include it under "About the role" maybe? But we should not invent headings not in list. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples; we can use those headings if appropriate. It says "include a section ONLY when the posting has real, specific content for it". So we need to decide which sections have content. We have: - About the role: description of role, what you'll do, etc. Yes. - Responsibilities: list of duties (the "Here are some of the EXCITING things you’ll get to do:" bullet list). So we can put under Responsibilities. - Requirements: maybe education, schedule, CAD experience, prototyping tools, communication, etc. Could be under Requirements or Qualifications. The posting has "Attributes & Skills" with bullet list of education, schedule, CAD, prototyping, communication, intuition, analytical, etc. Also "Experience with rapid prototyping tools like Arduino..." is desirable. So we can put under Requirements or Qualifications. Since we have both Requirements and Qualifications headings, we need to decide which to use. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section, maybe "Requirements". Or we could split: Requirements for mandatory items, Qualifications for desirable/plus. But we need to avoid thin sections. Let's see content: mandatory: Education (current student or graduated within past year), full-time 40-hour week 5 days onsite Needham, MA, strong CAD experience, strong prototyping tools experience, strong communicator, strong intuition for mechanical engineering/physics, analytical/detail-oriented, demonstrates intellectual curiosity, hands-on attitude, skilled at juggling multiple projects, enthusiastic about user-centered design, hands-on experience building physical prototypes, basic understanding of electronics desirable, experience with rapid prototyping tools like Arduino etc is a plus. So we have many mandatory and some desirable. We could have a single "Requirements" section covering all. Or we could have "Requirements" for mandatory and "Qualifications" for desirable. But that might be thin for Qualifications (just a few lines). Better to combine into one section, maybe "Requirements". The instruction says we can use those headings as examples; we are not forced to use all. So we can output only sections we need: About the role, Responsibilities, Requirements, Benefits, Pay. Schedule is mentioned: "Must be able to work a full-time, 40-hour-per-week schedule with 5 days onsite in Needham, MA". That's schedule info; we could include under Requirements or Schedule. Since schedule is explicit, we could create a Schedule section. But we already have schedule info in Requirements; we could still create a Schedule section with that detail. However we must avoid thin sections; schedule is just one line; but it's specific. Could be okay. But we could also incorporate schedule into Requirements to avoid extra section. The instruction: "Prefer a few substantive sections over many thin ones." So better to incorporate schedule into Requirements. Benefits: The posting lists benefits: medical insurance, HSA with company contribution, sick time, company holidays, employee product discount, product testing opportunities, referral bonuses, and more. Also later: "We offer competitive health insurance, retirement plans, paid time off, employee stock purchase options, wellness programs, SharkNinja product discounts, and more." So we have benefits details. Pay: "Hourly Pay Range $27—$40 USD". Also earlier: "Salary and Other Compensation: The hourly salary range for this position is displayed below." So we have Pay. Thus sections: About the role, Responsibilities, Requirements (including education, schedule, skills, etc.), Benefits, Pay. We must not include headings with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

... (company description and role description)

But we need to preserve all substantive information. The company description is about SharkNinja; we can include that in About the role paragraph. Let's extract substantive paragraphs: - "Product Design Engineering Intern Opportunities About Us SharkNinja is a global product design and technology company, with a diversified portfolio of 5-star rated lifestyle solutions that positively impact people’s lives in homes around the world. Powered by two trusted, global brands, Shark and Ninja, the company has a proven track record of bringing disruptive innovation to market and developing one consumer product after another has allowed SharkNinja to enter multiple product categories, driving significant growth and market share gains. Headquartered in Needham, Massachusetts with more than 4,100 associates, the company’s products are sold at key retailers, online and offline, and through distributors around the world." - "AI at SharkNinja At SharkNinja, we’re building an AI-native culture. We’re not waiting for the future; we’re creating it. Our people are expected to experiment boldly, adopt new tools, and continuously raise what’s possible to create meaningful impact for our consumers. If you believe the best way to do your job hasn’t been invented yet, you’ll fit right in." - "Join the SharkNinja Early Edge Experience: Built for early career talent. Geared toward impact. Driven by speed. Whether you're in a co-op or internship, our early talent program is designed to provide valuable exposure to the industry and a fast-paced professional environment. You’ll dive into meaningful projects and tasks that sharpen your skills and deepen your knowledge. Along the way, you’ll benefit from professional development opportunities, community events, and connections that make your experience well-rounded and enriching. Your time with us will culminate in an opportunity to showcase your contributions and learnings to SharkNinja leaders because this is a program for those ready to shape what’s next — fast." - "This role: Are you excited by the idea of building the future of home innovation? Do you thrive at the intersection of creativity and engineering? Are you ready to bring bold ideas to life through hands-on prototyping, user-first thinking, and technical problem-solving? If so, you could be a great fit for the Product Design Engineering Intern at SharkNinja. As a Product Design Engineering Intern, you’ll join a passionate group of hybrid thinkers working at the earliest stages of product innovation. Sitting between Industrial Design and Mechanical Engineering, this role is perfect for those who love to sketch, build, test, and iterate with the consumer always top of mind. You’ll collaborate with cross-functional teams to imagine what’s next for SharkNinja, transforming insights into elegant, viable, and exciting product solutions. If you’re a creative thinker, curious builder, and motivated problem solver who enjoys translating real-world challenges into tangible design opportunities, we want to hear from you!" That's a lot of prose. We'll combine into a couple paragraphs. Then Responsibilities: list bullet points: - Generate new product concepts with a user-centered approach, focusing on ergonomics, aesthetics, and functional innovation. - Collaborate closely with cross-functional teams to define solutions that meet functional requirements while enhancing the user experience. - Lead and participate in design studies to solve technical and user-experience challenges. - Build and test quick turnaround, low fidelity prototypes, and be able to build key findings on user testing with them. - Approach everyday design challenges with curiosity and resilience, driven to rethink and innovate We need to preserve exactly as given; maybe keep the bullet points. Then Requirements: includes education, schedule, CAD, prototyping tools, communication, intuition, analytical, curiosity, hands-on, juggling projects, enthusiasm, hands-on prototype experience, basic electronics desirable, Arduino/Raspberry Pi plus. We should preserve all details. We'll format as
  • for each bullet. We need to decide grouping: maybe separate mandatory vs desirable? But we can just list all as bullet points. Let's extract bullet list from "Attributes & Skills": Education: Current student in a related bachelor's or master’s or PhD program or has graduated from such a program within the past year Must be able to work a full-time, 40-hour-per-week schedule with 5 days onsite in Needham, MA Must have strong experience with CAD software (SolidWorks, Creo, or Rhino) Must have strong experience using basic prototyping tools (3D printing, shop competency) Strong communicator who can convey ideas, concepts, and solutions effectively to both technical and non-technical audiences Strong intuition for mechanical engineering and physics principles, with an emphasis on applying this in product design, ergonomics, and human-centered engineering Analytical and detail-oriented, with a creative approach to identifying and addressing potential issues Demonstrates intellectual curiosity, a hands-on attitude, and commitment to developing elegant, innovative solutions that balance technical and user-focused design principles Skilled at juggling multiple projects, with flexibility to pivot as needed while keeping sight of broader design objectives Enthusiastic about user-centered product design, form, and function Hands-on experience building physical prototypes in various materials (e.g., plastic, metal) and familiarity with machine shop equipment Basic understanding of electronics and components commonly used in small appliances (motors, sensors, PCBAs) is desirable Experience with rapid prototyping tools like Arduino, Raspberry Pi, or other developer kits is a plus. We'll turn each line into
  • . Note that some lines have "is desirable" or "is a plus." We'll keep that text. Then Benefits: list: - medical insurance - health savings account (HSA) with company contribution - sick time - company holidays - employee product discount - product testing opportunities - referral bonuses - and more (maybe we keep "and more" as part of last bullet? Could be separate bullet "and more". But we can incorporate as part of last bullet: "and more". Also later: "We offer competitive health insurance, retirement plans, paid time off, employee stock purchase options, wellness programs, SharkNinja product discounts, and more." This seems like additional benefits. We should combine all benefits. Let's compile benefits list: From first benefits paragraph: medical insurance, health savings account (HSA) with company contribution, sick time, company holidays, employee product discount, product testing opportunities, referral bonuses, and more. From second benefits paragraph: competitive health insurance, retirement plans, paid time off, employee stock purchase options, wellness programs, SharkNinja product discounts, and more. We need to avoid duplication: medical insurance vs health insurance similar. We'll keep both but maybe combine. But we must preserve all substantive information; we can list both but note overlap. Could list as separate bullets: medical insurance, health savings account (HSA) with company contribution, sick time, company holidays, employee product discount, product testing opportunities, referral bonuses, competitive health insurance, retirement plans, paid time off, employee stock purchase options, wellness programs, SharkNinja product discounts, and more. That's a bit redundant but preserves. We could combine similar items: "medical insurance" and "competitive health insurance" maybe same; but we keep both as they appear. Pay: Hourly Pay Range $27—$40 USD. We'll output as

    Hourly

Similar jobs