Electrical Engineering Co-Op
About the role
with its content. - Responsibilities: The bullet list after "In the day-to-day, you will be responsible for..." and later "In this role, you will:" list. So we need to extract responsibilities. - Requirements / Qualifications / Skills: The posting includes "To be eligible for this role..." and "An ideal candidate has:" and then list of qualifications. Also "You should apply if:" includes motivations but those are not requirements. We need to decide sections: maybe combine Requirements and Qualifications? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple if content exists. We need to avoid thin sections. We have content for: - About the role: includes description of role, location, schedule (co-op Tue-Thu in office, remote Mon-Fri), relocation/housing support, duration Jan-Jun 2027, eligibility (must be attending university supporting full-time work as part of 6-month co-op OR allow 2 quarters or one semester off), not accepting first-year co-op, ideally junior year, previous internship/co-op experience. - Responsibilities: list of duties: Contribute to shipping successful product lines; Conduct research; Know the system; Prototype; Design; Test; Failure analysis; Manage; Champion cultural principles. - Requirements / Qualifications: The "An ideal candidate has:" list includes Bachelor's degree in progress in EE or related technical field; looking for second or third-time co-op or Master level co-op; not considering first-time co-ops; target graduation timeline May-June 2026; must commit to minimum 6 months full-time co-op and have university that supports co-op experience; prior intern/co-op experience on high-volume hardware programs; solid fundamentals in digital, analog, mixed-signal circuits; schematic and layout knowledge in Altium or Cadence or CAD/Allegro; ability to navigate tradeoffs; hands-on experience with test instruments; knowledge of cameras, sensors, WiFi, LTE, Bluetooth, GPS, antennas, batteries; strong ability to collaborate; excellent written and verbal communication skills in English. - Skills: Could be overlapping with qualifications; but we could treat the list as Skills. However we already have qualifications. Maybe we separate: Requirements (eligibility, commitment, graduation timeline) and Qualifications (education, experience) and Skills (technical skills). But we need to avoid thin sections. Let's see if we have enough for each. We have: - Requirements: eligibility (university support, commitment duration, not first-year, etc). Could be a section. - Qualifications: education, graduation timeline, prior experience. - Skills: technical fundamentals, tools, knowledge, collaboration, communication. But the instruction says prefer a few substantive sections over many thin ones. Might be better to combine Requirements and Qualifications into one "Requirements" section, and Skills into another "Skills". Or combine all into "Requirements". However they gave examples of headings; we can include multiple if substantive. We also have Benefits: mention relocation and housing support, maybe also total rewards? There's a paragraph about total rewards, base salary range, RSU grant, etc. That's Benefits and Pay. Pay: Annual Base Salary $35—$58 USD. Also mention RSU grant, performance-based bonus/variable pay, equity. So we can have Pay section with base salary range and mention equity/bonus. Schedule: Co-ops required to be in office Tuesdays to Thursdays and remote work days on Mondays and Fridays. Also mention relocation/housing support. So schedule section. Benefits: relocation and housing support, flexible working model, professional development stipend, health and parental leave plans, etc. Also mention total rewards: flexible remote model, professional development stipend, comprehensive health and parental leave plans, etc. So we can have Benefits. We must not include boilerplate like EEO, accommodations, fraud detection, etc. We must not include repeated lines. We must preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. Let's extract exact sentences. We'll craft sections:About the role
We’re looking for an Electrical Engineer co‑op to join our team. In the day‑to‑day, you will be responsible for working on the EE aspects of the design of products based on thorough feasibility, design, and cost studies encompassing key component selection, thermals, antenna, etc. We have a tremendous amount of telemetry and access to customers that help guide our design process. You will work directly with our customers to ensure we lead the industry with our product design. We run a collaborative process working closely with Product Management, PD, FW, EPM, NPI, and Hardware leadership to make excellent tradeoffs and choices. Throughout this process, you’ll share your expertise with other engineers. The US and Taiwan EE teams are supported by the Supply Chain team, laboratories, JDM design resources, and a growing supply base. You will work closely with these internal and external partners to achieve our objectives. This role will be held at our San Francisco office. Co‑ops are required to be in the office Tuesdays to Thursdays and remote work days on Mondays and Fridays. As part of the co‑op program, we do provide relocation and housing support for the duration of the co‑op. To be eligible for this role, you must be attending a university that supports full‑time work as part of a 6‑month co‑op OR attend a university that will allow you to take 2 quarters or one semester off to work a co‑op. Please do not apply if you are unable to commit to the full duration of this co‑op. We are looking for this co‑op to join us from January - June 2027. At this time, we are not accepting first‑year co‑op students. Ideally, this student is in their junior year of school as an undergraduate student and has previous internship and/or co‑op experience.
That covers About the role. Now Responsibilities: we have bullet list after "In this role, you will:" plus earlier "In the day-to-day, you will be responsible for..." but we already used that in About the role. To avoid duplication, we could keep responsibilities separate: maybe combine the earlier sentence into About the role and then responsibilities list. Let's extract responsibilities list: - Contribute to shipping successful product lines. - Conduct research: Stay informed of the latest silicon possibilities from all the top semiconductor companies. - Know the system: Evaluate system feature tradeoffs and create the system specifications for development with product management and cross‑functional engineering teams. - Prototype: Assemble EVKs, board hacks, or quick‑turn fabrication for evaluating concepts or jump‑starting firmware development. - Design: Take a concept from block diagram to schematics and through layout; either on your own or navigate the process with JDM resources. - Test: Create a validation plan for each phase of the product development through PVT and characterize the full electrical system for function, power, and use‑cases. - Failure analysis: Find the root cause of design inefficiencies and field failures, and improve design to meet performance and quality requirements. - Manage: We bolster our internal development team with top JDM companies to design, validate, certify and manufacture quality products, certification labs and other external consultants. - Champion, role model, and embed Samsara’s cultural principles (Focus on Customer Success, Build for the Long Term, Adopt a Growth Mindset, Be Inclusive, Win as a Team) as we scale globally and across new offices. We'll put these in- .
Now Requirements/Qualifications/Skills.
We could have a single "Requirements" section that includes eligibility, education, experience, technical skills. But we might split into Requirements and Skills.
Let's decide: We'll have:
Requirements
Must be attending a university that supports full‑time work as part of a 6‑month co‑op OR attend a university that will allow you to take 2 quarters or one semester off to work a co‑op. Must be able to commit to a minimum of 6 months of full‑time co‑op employment. Not accepting first‑year co‑op students. Ideally a junior‑year undergraduate with previous internship and/or co‑op experience. Target graduation timeline May‑June 2026.
That covers eligibility and timeline. Now Skills:Skills
- Bachelor’s degree in progress in Electrical Engineering or a related technical field.
- Second or third‑time co‑op or Master level co‑op students (first‑time co‑ops not considered).
- Prior intern or co‑op experience working on high‑volume hardware programs.
- Solid fundamentals in digital, analog, and mixed‑signal circuits.
- Schematic and layout knowledge in Altium, Cadence, or CAD/Allegro.
- Ability to navigate tradeoffs between design, manufacturability, schedule, and cost.
- Hands‑on experience with test instruments such as oscilloscopes, signal generators, spectrum analyzers.
- Knowledge of cameras, sensors, Wi‑Fi, LTE, Bluetooth, GPS, antennas, and batteries.
- Strong ability to collaborate with cross‑functional teams and drive independent work.
- Excellent written and verbal communication skills in English.
- .
Now Pay:
Annual Base Salary $35—$58 USD. Also mention RSU grant, performance‑based bonus/variable pay, equity.
We'll put:
Annual base salary range: $35–$58 USD. Eligible for an initial RSU grant with no vesting cliff and ongoing refresh opportunities tied to performance, plus performance‑based bonus/variable pay and equity (for eligible roles).
Now Schedule: We already mentioned schedule in About the role (Tue-Thu in office, Mon-Fri remote). But we could also have a Schedule section to avoid duplication? The instruction says do not repeat job title as heading, but repeating info is okay? It says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. We could keep schedule in About the role and not have separate Schedule section. However they expect a Schedule section if we have content. Since we already included schedule in About the role, we could still have a Schedule section but that would repeat. Better to not have a separate Schedule section and rely on About the role containing schedule. But the instruction