Senior Electrical Engineer (On-site)
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content accordingly. The instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should include headings only when there is real specific content. We must not repeat job title as heading. Also we must not put Job ID etc.
We need to decide which sections to include. The posting has: About Standard Bots (intro), What you'll do (role description), Location, Responsibilities, Who You Are (qualifications/requirements), Skills you'll bring (skills), Bonus points for (additional skills/qualifications), Compensation and Benefits (pay and benefits). There's no explicit schedule besides location says On-Site 5 days/week. That could be schedule. So we could have a Schedule section with that info.
We need to preserve all substantive info, not invent. Remove boilerplate etc.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must not create sections with filler like "commensurate with experience". We have actual content for Pay: base salary range $120k-$180k, plus stock options, benefits list. So we can have Pay and Benefits sections, or combine? The instruction says prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one section maybe "Compensation and Benefits". But they gave examples of headings: Benefits, Pay, Schedule. We could have separate Pay and Benefits if content distinct. However we have both pay and benefits details; we could split: Pay section with salary range and stock options; Benefits section with PTO, insurance, 401k. That seems reasonable.
We also need Requirements/Qualifications: The "Who You Are" includes requirements: degree, 5+ years experience, mastery areas, tool fluency, debugging mastery, communication, impact driven, proactive simplicity, growth optimism, excelling in ambitious environments. That's qualifications/requirements. Could split into Requirements (education, experience) and Qualifications (skills). But we also have a separate Skills you'll bring section. So we could have Requirements (education + experience), Qualifications (maybe the mastery areas?), Skills (the bullet list). However the instruction says use headings like Requirements, Qualifications, Skills. We need to decide.
We have "Skills you'll bring:" with bullet list of experience, EE depth, tool fluency, debugging mastery, clarity of communication, impact driven, proactive simplicity, growth + optimism, excelling in ambitious environments. That's a list of skills/attributes. Then "Bonus points for:" is additional skills/qualifications.
Thus we could map:
- About the role: combine "About Standard Bots" and "What you'll do:" and maybe location? But location could be Schedule. However "About the role" could be a brief description of role: we have "What you'll do:" which is responsibilities-ish but we also have separate Responsibilities section. So maybe About the role includes the introductory paragraph about Standard Bots and the "What you'll do:" summary? But we also have Responsibilities separate. To avoid duplication, we could put About the role as the introductory blurb about company and role purpose (the first two paragraphs). Then Responsibilities as the bullet list under "Own the design and validation..." etc. Then Requirements: education + experience (bachelor's or graduate degree and 5+ years). Qualifications: maybe the mastery areas (power electronics, digital, analog) etc? Or we could treat Qualifications as the bullet list under "Skills you'll bring:"? But they'd overlap.
Better: Use sections: About the role (company intro + what you'll do), Responsibilities (the bullet list under "Own the design..."), Requirements (education + experience), Qualifications (the mastery areas: power electronics, digital, analog, tool fluency, debugging, communication, impact driven, proactive simplicity, growth optimism, excelling in ambitious environments), Skills (the bullet list under "Skills you'll bring:"? Actually that is same as Qualifications). Hmm.
Maybe we treat "Skills you'll bring:" as Skills section, and "Bonus points for:" as additional Qualifications (or Skills). And "Who You Are" includes requirements (education, experience) plus some attributes. Could split.
Let's parse the "Who You Are" paragraph:
"We don't require a background in robotics — but we do require deep, hands-on electronics experience. We're looking for engineers who are self-driven, optimistic, creative, and resourceful. We have no requirement for a background in robotics, but find most success with engineers excited by the domain and looking to apply deep electronics expertise — from motor drives, power electronics, embedded compute, automotive, or aerospace — to robots they can watch move. Our ideal candidate will be open to spending roughly 60% of their time on design (architecture, schematics, layout) and 40% on lab, integration, and manufacturing support (bring-up, debug, vendor and production issues), with flexibility to sway more toward one or the other depending on current projects and team needs."
That includes: self-driven, optimistic, creative, resourceful; excitement for domain; time split expectation. That's more like attributes/qualifications.
Then "Skills you'll bring:" bullet list: Experience (degree + 5+ years), EE Depth (mastery of power electronics, digital, analog), Tool Fluency (Altium), Debugging Mastery, Clarity of Communication, Impact Driven, Proactive Simplicity, Growth + Optimism, Excelling in Ambitious Environments.
Thus Skills you'll bring includes both experience and attributes.
Thus we could have:
- About the role: company intro + what you'll do (maybe short paragraph)
- Responsibilities: bullet list under "Own the design..."
- Requirements: education + experience (bachelor's or graduate degree + 5+ years designing PCBAs)
- Qualifications: the mastery areas (power electronics, digital, analog) plus tool fluency, debugging mastery, communication, impact driven, proactive simplicity, growth optimism, excelling in ambitious environments (these are skills/attributes)
- Skills: maybe the bonus points? Or we could combine Bonus points into Qualifications as extra.
But we need to avoid duplication. The "Skills you'll bring:" list includes the experience bullet and the mastery areas etc. So if we put Requirements as education+experience, Qualifications as mastery areas etc, Skills as bonus points? That seems plausible.
Let's decide:
Section headings we will output:
About the role
Standard Bots ... (intro) ... What you'll do: ... (maybe combine)
Responsibilities
- ... each bullet from "Own the design..." etc.
Requirements
Bachelor's or graduate degree in Electrical Engineering (or related field) and 5+ years designing, building, and testing PCBAs, including designs taken through production release.
Qualifications
- Mastery of power electronics (motor drivers and inverter stages, switch-mode supplies, power sequencing and protection)
- Mastery of digital electronics (MCUs, FPGAs, Ethernet, USB, SPI/I2C/UART, signal-integrity fundamentals)
- Mastery of analog electronics (op-amps, filters, ADC/DAC signal chains, precision sensing)
- Proficiency in Altium Designer (or similar EDA tools) for schematic capture and multi-layer layout, including constraint-driven routing for high-speed and high-current designs
- Debugging mastery: ability to attack hardware problems with scope, logic/protocol analyzer, bench instruments, document findings, converge on fix quickly
- Clarity of communication: clear design documentation, crisp trade studies, design reviews that make peers better
- Impact driven: relentlessly seek user impact and value execution over technical idealism; a reliable, manufacturable board that ships beats an elegant one that never leaves the lab
- Proactive simplicity: prioritize simplicity, reliability, and velocity, proactively identify opportunities to improve designs or incumbent hardware
- Growth + optimism: excited by new domains and challenges, eager to pick up new context to accelerate impact
- Excelling in ambitious environments: excel in dynamic and ambitious environments, working with diverse group of individuals and backgrounds
Skills
- High-speed design (PCIe Gen1–5, USB3/4, MIPI, GMSL, 10G Ethernet) with high-current power delivery for compute modules, and working understanding of signal and power integrity (impedance control, crosstalk, PDN) and mitigation
- Camera electronics and image sensor integration (MIPI, GMSL, sensor power and clocking)
- Dense or space-constrained boards (HDI, flex, rigid-flex) and fabrication trade-offs
- Motor electromagnetic design and motor control (FOC, current sensing, encoder interfaces), or control systems for robotic manipulation or locomotion
- Embedded programming of DSPs, MCUs, and FPGAs; LTspice and Python for simulation, analysis, and test automation
- EMC/EMI design and regulatory compliance testing (CE/UL, IEC 61000 series), including pre-compliance debugging
- Real-time industrial fieldbuses (EtherCAT, CAN/CANopen, EtherNet/IP) and safety-rated electronics to ISO 13849 or IEC 61508 (redundant architectures, STO, safety fieldbus)
- Taking products from prototype through NPI to volume manufacturing — DFM/DFT, test fixtures, yield improvement
Pay
The base salary range for this role is $120,000 to $180,000, depending on experience. Base salary is just one part of the overall compensation at Standard Bots. All Full-Time Employees are eligible for Employee Stock Options.
Benefits
- Paid time off
- Medical/dental/vision insurance
- Life insurance
- Disability insurance
- 401(k) plan for regular full-time employees
Schedule
On‑Site 5 days/week at our Glen Cove, NY Factory.
We need to ensure we didn't repeat any content inadvertently. Check that we captured all substantive info:
- About Standard Bots intro: "At Standard Bots, we're revolutionizing real-world automation by making robotic systems accessible to everyone. Our AI-powered platform enables robots to tackle unprecedented challenges through an intuitive instruction interface, bringing the power of software automation to physical spaces." That's included.
- What you'll do: "We're looking for a seasoned electrical engineer to own the electronics at the heart of our robots: motor controllers, power distribution, compute, camera, battery management, and sensing boards. As a Senior Electrical Engineer you will take designs from concept through production release, work hands-on in the lab, and partner with Mechanical, Software, and Functional Safety engineers to ship hardware that is simple, reliable, and manufacturable at scale." We included that in About the role paragraph.
- Location: we put in Schedule.
- Responsibilities: we captured bullet list from "Own the design and validation..." through "Mentor and advise associate and mid-level engineers..." Good.
- Who You Are: we split into Requirements (education+
- for any list of duties/requirements/benefits, and
for prose. We must not create sections with filler like "commensurate with experience". We have actual content for Pay: base salary range $120k-$180k, plus stock options, benefits list. So we can have Pay and Benefits sections, or combine? The instruction says prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one section maybe "Compensation and Benefits". But they gave examples of headings: Benefits, Pay, Schedule. We could have separate Pay and Benefits if content distinct. However we have both pay and benefits details; we could split: Pay section with salary range and stock options; Benefits section with PTO, insurance, 401k. That seems reasonable. We also need Requirements/Qualifications: The "Who You Are" includes requirements: degree, 5+ years experience, mastery areas, tool fluency, debugging mastery, communication, impact driven, proactive simplicity, growth optimism, excelling in ambitious environments. That's qualifications/requirements. Could split into Requirements (education, experience) and Qualifications (skills). But we also have a separate Skills you'll bring section. So we could have Requirements (education + experience), Qualifications (maybe the mastery areas?), Skills (the bullet list). However the instruction says use headings like Requirements, Qualifications, Skills. We need to decide. We have "Skills you'll bring:" with bullet list of experience, EE depth, tool fluency, debugging mastery, clarity of communication, impact driven, proactive simplicity, growth + optimism, excelling in ambitious environments. That's a list of skills/attributes. Then "Bonus points for:" is additional skills/qualifications. Thus we could map: - About the role: combine "About Standard Bots" and "What you'll do:" and maybe location? But location could be Schedule. However "About the role" could be a brief description of role: we have "What you'll do:" which is responsibilities-ish but we also have separate Responsibilities section. So maybe About the role includes the introductory paragraph about Standard Bots and the "What you'll do:" summary? But we also have Responsibilities separate. To avoid duplication, we could put About the role as the introductory blurb about company and role purpose (the first two paragraphs). Then Responsibilities as the bullet list under "Own the design and validation..." etc. Then Requirements: education + experience (bachelor's or graduate degree and 5+ years). Qualifications: maybe the mastery areas (power electronics, digital, analog) etc? Or we could treat Qualifications as the bullet list under "Skills you'll bring:"? But they'd overlap. Better: Use sections: About the role (company intro + what you'll do), Responsibilities (the bullet list under "Own the design..."), Requirements (education + experience), Qualifications (the mastery areas: power electronics, digital, analog, tool fluency, debugging, communication, impact driven, proactive simplicity, growth optimism, excelling in ambitious environments), Skills (the bullet list under "Skills you'll bring:"? Actually that is same as Qualifications). Hmm. Maybe we treat "Skills you'll bring:" as Skills section, and "Bonus points for:" as additional Qualifications (or Skills). And "Who You Are" includes requirements (education, experience) plus some attributes. Could split. Let's parse the "Who You Are" paragraph: "We don't require a background in robotics — but we do require deep, hands-on electronics experience. We're looking for engineers who are self-driven, optimistic, creative, and resourceful. We have no requirement for a background in robotics, but find most success with engineers excited by the domain and looking to apply deep electronics expertise — from motor drives, power electronics, embedded compute, automotive, or aerospace — to robots they can watch move. Our ideal candidate will be open to spending roughly 60% of their time on design (architecture, schematics, layout) and 40% on lab, integration, and manufacturing support (bring-up, debug, vendor and production issues), with flexibility to sway more toward one or the other depending on current projects and team needs." That includes: self-driven, optimistic, creative, resourceful; excitement for domain; time split expectation. That's more like attributes/qualifications. Then "Skills you'll bring:" bullet list: Experience (degree + 5+ years), EE Depth (mastery of power electronics, digital, analog), Tool Fluency (Altium), Debugging Mastery, Clarity of Communication, Impact Driven, Proactive Simplicity, Growth + Optimism, Excelling in Ambitious Environments. Thus Skills you'll bring includes both experience and attributes. Thus we could have: - About the role: company intro + what you'll do (maybe short paragraph) - Responsibilities: bullet list under "Own the design..." - Requirements: education + experience (bachelor's or graduate degree + 5+ years designing PCBAs) - Qualifications: the mastery areas (power electronics, digital, analog) plus tool fluency, debugging mastery, communication, impact driven, proactive simplicity, growth optimism, excelling in ambitious environments (these are skills/attributes) - Skills: maybe the bonus points? Or we could combine Bonus points into Qualifications as extra. But we need to avoid duplication. The "Skills you'll bring:" list includes the experience bullet and the mastery areas etc. So if we put Requirements as education+experience, Qualifications as mastery areas etc, Skills as bonus points? That seems plausible. Let's decide: Section headings we will output:
About the role
Standard Bots ... (intro) ... What you'll do: ... (maybe combine)
Responsibilities
- ... each bullet from "Own the design..." etc.
Requirements
Bachelor's or graduate degree in Electrical Engineering (or related field) and 5+ years designing, building, and testing PCBAs, including designs taken through production release.
Qualifications
- Mastery of power electronics (motor drivers and inverter stages, switch-mode supplies, power sequencing and protection)
- Mastery of digital electronics (MCUs, FPGAs, Ethernet, USB, SPI/I2C/UART, signal-integrity fundamentals)
- Mastery of analog electronics (op-amps, filters, ADC/DAC signal chains, precision sensing)
- Proficiency in Altium Designer (or similar EDA tools) for schematic capture and multi-layer layout, including constraint-driven routing for high-speed and high-current designs
- Debugging mastery: ability to attack hardware problems with scope, logic/protocol analyzer, bench instruments, document findings, converge on fix quickly
- Clarity of communication: clear design documentation, crisp trade studies, design reviews that make peers better
- Impact driven: relentlessly seek user impact and value execution over technical idealism; a reliable, manufacturable board that ships beats an elegant one that never leaves the lab
- Proactive simplicity: prioritize simplicity, reliability, and velocity, proactively identify opportunities to improve designs or incumbent hardware
- Growth + optimism: excited by new domains and challenges, eager to pick up new context to accelerate impact
- Excelling in ambitious environments: excel in dynamic and ambitious environments, working with diverse group of individuals and backgrounds
Skills
- High-speed design (PCIe Gen1–5, USB3/4, MIPI, GMSL, 10G Ethernet) with high-current power delivery for compute modules, and working understanding of signal and power integrity (impedance control, crosstalk, PDN) and mitigation
- Camera electronics and image sensor integration (MIPI, GMSL, sensor power and clocking)
- Dense or space-constrained boards (HDI, flex, rigid-flex) and fabrication trade-offs
- Motor electromagnetic design and motor control (FOC, current sensing, encoder interfaces), or control systems for robotic manipulation or locomotion
- Embedded programming of DSPs, MCUs, and FPGAs; LTspice and Python for simulation, analysis, and test automation
- EMC/EMI design and regulatory compliance testing (CE/UL, IEC 61000 series), including pre-compliance debugging
- Real-time industrial fieldbuses (EtherCAT, CAN/CANopen, EtherNet/IP) and safety-rated electronics to ISO 13849 or IEC 61508 (redundant architectures, STO, safety fieldbus)
- Taking products from prototype through NPI to volume manufacturing — DFM/DFT, test fixtures, yield improvement
Pay
The base salary range for this role is $120,000 to $180,000, depending on experience. Base salary is just one part of the overall compensation at Standard Bots. All Full-Time Employees are eligible for Employee Stock Options.
Benefits
- Paid time off
- Medical/dental/vision insurance
- Life insurance
- Disability insurance
- 401(k) plan for regular full-time employees
Schedule
On‑Site 5 days/week at our Glen Cove, NY Factory.
We need to ensure we didn't repeat any content inadvertently. Check that we captured all substantive info: - About Standard Bots intro: "At Standard Bots, we're revolutionizing real-world automation by making robotic systems accessible to everyone. Our AI-powered platform enables robots to tackle unprecedented challenges through an intuitive instruction interface, bringing the power of software automation to physical spaces." That's included. - What you'll do: "We're looking for a seasoned electrical engineer to own the electronics at the heart of our robots: motor controllers, power distribution, compute, camera, battery management, and sensing boards. As a Senior Electrical Engineer you will take designs from concept through production release, work hands-on in the lab, and partner with Mechanical, Software, and Functional Safety engineers to ship hardware that is simple, reliable, and manufacturable at scale." We included that in About the role paragraph. - Location: we put in Schedule. - Responsibilities: we captured bullet list from "Own the design and validation..." through "Mentor and advise associate and mid-level engineers..." Good. - Who You Are: we split into Requirements (education+