Engineering & Technology Co-op Opportunities

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions. Must not include sections with filler like "commensurate with experience". Must only include sections where posting has real specific content. We need to parse the posting. Key sections: - About Us: description of company, AI at SharkNinja, Early Edge Experience, etc. This could be "About the role"? Actually "About Us" is company overview. Could be placed under "About the role" maybe? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include description of role and maybe company context. The posting includes "About Us" and "AI at SharkNinja", "Join the SharkNinja Early Edge Experience". That's about the program. So we can put that under About the role. - Responsibilities: The bullet list "Here are some of the EXCITING things you’ll get to do:" and then list items. Also "Depending On The Team, Your Day-to-day May Include ..." with subcategories. Those are responsibilities. So we can create a Responsibilities section with

• items. - Requirements: The "Attributes & Skills" section includes Education, Must be able to work full-time, pursuing degree, strong fundamentals, builder's mindset, programming experience, able to read schematics, natural communicator, attention to detail, comfortable multitasking, collaborative, proficient in MS Office, prior internship experience is a strong asset, plus plus items. That's qualifications/skills. We need to separate Requirements vs Qualifications vs Skills? The instruction lists possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have content that fits Requirements (education, work schedule, degree pursuit). Qualifications could be similar. Skills could be technical skills list. We could combine but must not create thin sections. Perhaps we can have Requirements (education, eligibility) and Skills (technical skills, programming, tools). Qualifications maybe not needed if overlapping. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we should maybe have: About the role, Responsibilities, Requirements (including education, eligibility, core qualifications), Skills (technical skills and tools), Benefits, Pay. Schedule: we have "Must be able to work a full-time, 40-hour-per-week schedule" which is schedule info. Could be included in Requirements or Schedule section. Since we have schedule info, we can create a Schedule section with that detail. But we must not create a Schedule section if it's just generic like "full-time, 40-hour-per-week". That's specific enough. So we can have Schedule section. Benefits: The posting mentions benefits: "The Company offers the following benefits for this position, subject to applicable eligibility requirements: medical insurance, health savings account (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 mention salary range may be affected by geography etc. That's specific. Thus we can have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Possibly Qualifications not needed. We must not repeat job title. Must not include boilerplate like EEO, legal, etc. Must not include application instructions. Must not include duplicated lines. We need to preserve all substantive information. So we need to include all bullet points from responsibilities, all attributes, etc. We must not invent or summarize away detail. So we need to keep the exact phrasing? Probably we can keep the substance but not necessarily verbatim; but we should not lose detail. We'll try to keep the key points. We'll output HTML fragment with

  headings and

  • for lists,

    for prose. We need to avoid markdown code fences. Let's craft. First, About the role: combine About Us, AI at SharkNinja, Early Edge Experience, description of co-op, teams, etc. We'll write a few paragraphs. We must not include "About Us" heading; just content under About the role. We'll include:

    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 the Shark and Ninja brands, the company brings disruptive innovation to market across multiple product categories, driving significant growth and market share. Headquartered in Needham, Massachusetts with over 4,100 associates, its products are sold at key retailers, online and offline, and through distributors worldwide.

    At SharkNinja we are building an AI‑native culture; we experiment boldly, adopt new tools, and continuously raise what’s possible to create meaningful impact for consumers. The Early Edge Experience is built for early‑career talent — co‑ops and internships — providing valuable industry exposure, fast‑paced projects, professional development, community events, and a chance to showcase contributions to leaders.

    This posting covers the Engineering & Technology Co‑op across electrical, embedded, software, robotics, digital, quality, test, and safety functions. Depending on the team, you may work on circuit board bring‑up, control algorithm tuning, cloud or mobile code, test rig construction, field‑return investigation, or product safety and compliance.

    That seems good. Now Responsibilities: we need to list the bullet points from "Here are some of the EXCITING things you’ll get to do:" and also the day-to-day specifics per team. We'll combine into a single list maybe grouped but still
    • . We'll preserve each item. List from "EXCITING things you’ll get to do:": - Contribute to the design, development, and validation of next-generation Shark and Ninja products — and the software that powers them - Work hands-on in labs, at the bench, and in code: building prototypes, test fixtures, scripts, and tools that engineers actually use - Support debugging, troubleshooting, root cause analysis, and failure investigation on real products and real consumer data - Develop and execute test plans, document results, and turn data into recommendations that shape design decisions - Participate in design reviews, sprints, stand-ups, and technical discussions alongside experienced engineers - Collaborate cross-functionally with Mechanical Engineering, Industrial Design, Firmware, Quality, Operations, Marketing, and Product Management - Gain exposure to the full product development lifecycle — ideation and prototyping through certification, mass production readiness, and post-market consumer feedback - Own a meaningful project end to end and present your contributions to SharkNinja leaders Then day-to-day per team: we have categories with details. We could break them into sub-items but still list. We could create subheadings? Not allowed; only headings are h3 for sections. Inside we can use

      or

      • . We could keep as
        • with longer text. We'll add items: - Electrical, Embedded & Robotics: designing, simulating, and evaluating analog and digital circuits (power supplies, signal filtering and amplification, motor control, sensor integration, battery management) using tools such as LTSpice and Altium; board bring‑up, debugging, and validation of real‑time embedded electronics (I2C, SPI, UART); writing and debugging firmware in C/C++ for microcontrollers and prototyping on platforms such as Arduino or Raspberry Pi; developing classical (e.g., PID) and advanced (e.g., MPC) control algorithms in Python, MATLAB, or C++ and tuning them on real hardware; working with robotics and navigation technologies such as LiDAR, Time‑of‑Flight sensors, and SLAM/V‑SLAM; supporting EMC, safety, and certification testing, EBOM/CBOM cost analysis, DVT, and DFMEA. - Software, Digital & IT: building and verifying cloud and connected‑product software on AWS IoT using TypeScript and Python; developing cross‑platform mobile apps in React Native, TypeScript, Swift, Kotlin, or Rust that communicate over BLE, Wi‑Fi, MQTT, and RESTful APIs; front‑end and web development, CMS content updates, analytics and performance tracking, and UX audits supporting SharkNinja websites; testing and evaluating AI‑powered digital features such as chatbots, smart search, and content recommendation engines; coordinating technical roadmaps, schedules, dependencies, and risks across hardware, firmware, and app teams using Agile, Scrum, and JIRA; providing first‑level IT support — device setup and imaging, account provisioning, ticket management in tools such as ServiceNow or Zendesk, and meeting room technology. - Quality, Test, Safety & Compliance: designing and building custom electro‑mechanical test rigs and automated test systems that simulate real‑world consumer use; writing automated test scripts in Python or C++ and integrating sensors, microcontrollers, and data acquisition tools into test setups; executing manual and system‑level test protocols for products, robots, and mobile apps, and documenting defects in JIRA or similar tools; tearing down SharkNinja and competitor products, analyzing large data sets with statistical tools, and investigating failure modes; evaluating consumer field returns, star reviews, and call center feedback to drive root cause analysis and corrective actions; supporting product safety and regulatory compliance work, internal audits, risk assessments, EHS inspections, and safety training aligned to standards such as OSHA and EPA. We'll put each as
        • . Now Requirements: we need education, eligibility, degree pursuit, fundamentals, builder's mindset, communication, attention to detail, multitasking, collaborative, prior internship experience is a strong asset, plus plus items? Actually plus items are more skills. We'll separate. Requirements section: education and eligibility. List: - Must be a current student in a related bachelor's, master’s, or PhD program, or have graduated from such a program within the past year. - Must be able to work a full‑time, 40‑hour‑per‑week schedule. - Pursuing a degree in Electrical Engineering, Computer Engineering, Computer Science, Software Engineering, Mechanical Engineering, Robotics or Mechatronics, Quality Engineering, Information Technology, Environmental Health & Safety, or a closely related technical field. - Strong fundamentals in your discipline and the curiosity to apply them to problems you haven’t seen before. - A builder’s mindset: comfortable with lab and test equipment (oscilloscopes, multimeters, power supplies, data loggers), hand tools and prototyping, a code editor, or all of the above, depending on your focus. - Able to read and interpret schematics, technical drawings, and product requirements. - A natural communicator who can explain complex technical topics clearly to both technical and non‑technical stakeholders, in writing and out loud. - Strong attention to detail in testing, documentation, and data analysis; offers data‑backed insights and constructive feedback. - Comfortable multitasking and shifting between immediate tasks and longer‑term projects in a fast‑paced environment, with proactive ownership of your work. - Collaborative, positive, and eager to contribute to an innovation‑driven team. - Proficient in Microsoft 365, particularly Excel and PowerPoint. - Prior internship, co‑op, capstone, club, research, or personal project experience in consumer products, electronics, robotics, software, or quality is a strong asset. We could also include the plus items as Skills. Now Skills section: technical skills and