Senior Electrical Engineer, Schematic and Circuit Board Design (Remote Eligible | Relocation Assistance Available)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to extract relevant content: The posting includes:
- Intro: "Join Axon and be a Force for Good." etc. That's marketing fluff; maybe we can include as About the role? Actually "About Axon 911" etc. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections have content.
Let's parse:
- About the role: Could be description of role: "We are seeking a Senior Electrical Engineer to own the design, development, and validation of complex electrical systems for mission-critical, connected hardware." Also "As a founding member of our hardware team..." etc. That could be About the role.
- Responsibilities: The "What You’ll Do" bullet list: Electrical & Board Design, RF Integration & Coexistence, Mechanical Integration, Bring-Up & Debugging, Production Readiness, Technical Leadership. Those are responsibilities.
- Requirements: The "What You Bring" bullet list: 7+ years experience, bachelor's degree, demonstrated experience with PCB design, etc. That's requirements/qualifications.
- Qualifications: Might overlap with requirements; but we can combine? The instruction says prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But they ask to use headings for those specific names if content exists. We could have both Requirements and Qualifications if distinct. However the content seems to be qualifications/experience. Could treat "What You Bring" as Requirements. Could also have Skills: maybe list specific skills like Cadence OrCAD, Allegro, oscilloscopes, etc. That could be Skills.
- Benefits: The "Benefits that Benefit You" list: Competitive salary and 401k with employer match, Discretionary paid time off, Paid parental leave, Medical, dental, and vision plans, Fitness Programs, Emotional & Mental Wellness support, Learning & Development programs, snacks. Also note about benefits varying.
- Pay: The "Pay Transparency" section gives base pay range $112,800 - $196,535. Also mentions bonus, equity. So we have Pay.
- Schedule: The "Work Location" mentions hybrid schedule requiring onsite Tuesday-Friday at hubs, relocation assistance, remote eligibility case-by-case. So schedule info: hybrid schedule, onsite Tue-Fri, relocation assistance, remote eligibility.
We need to output only HTML fragment, no markdown fences.
We must not include boilerplate like "Don’t meet every single requirement? That's ok." etc. Also remove EEO, legal, privacy, phishing alert, etc.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific responsibilities bullet points, qualifications bullet points, benefits list, pay range, schedule details.
We must not repeat job title as heading. So no
Senior Electrical Engineer
.
We must not put Job ID/requisition numbers as headings (none present).
We must not include filler like "commensurate with experience". Not present.
We need to decide which sections to include. Likely we include About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly Skills separate? But we could incorporate skills into Requirements or Qualifications. Since they ask for Skills heading if content exists. The "What You Bring" includes skills like PCB design, RF integration, etc. Could be considered Skills. But we already have Requirements. To avoid many thin sections, we could combine Requirements and Skills into one section called Requirements (or Qualifications). But they said use headings for those specific names if content exists. It's ambiguous. I'd include Requirements and Skills separate if both have distinct content. However the content overlaps; we could treat "What You Bring" as Requirements (experience, education) and Skills as technical skills (tools, technologies). Let's extract skills: "Hands-on experience with Cadence OrCAD and Allegro, as well as oscilloscopes, spectrum analyzers, logic analyzers, power supplies, and related electrical and RF test equipment." Also "Experience designing rigid, flex, or rigid-flex PCBs". Also "Experience working with design partners, ODMs, JDMs". Those could be skills.
Thus we can have:
- About the role: prose summarizing role.
- Responsibilities: list of duties from "What You’ll Do".
- Requirements: list of experience/education from "What You Bring" (7+ years, bachelor's degree, demonstrated experience with PCB design, etc.) maybe also include experience across embedded subsystems, proven experience taking electronics from concept through mass production, understanding of RF coexistence, etc.
- Skills: list of specific tools/technologies: Cadence OrCAD, Allegro, oscilloscopes, spectrum analyzers, logic analyzers, power supplies, etc.; experience designing rigid/flex/rigid-flex PCBs; working with design partners/ODMs/JDMs; travel flexibility.
- Benefits: list from "Benefits that Benefit You".
- Pay: paragraph with base pay range.
- Schedule: paragraph about hybrid schedule, onsite Tue-Fri, relocation assistance, remote eligibility.
We need to ensure we don't include filler like "Benefits listed herein may vary depending on the nature of your employment and the location where you work." That's substantive? It's a note about benefits varying; we could include it as part of Benefits section maybe as a sentence.
We must not include application instructions, EEO, legal, etc.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Benefits may vary depending on employment nature and location.
Pay
The starting base annual pay for this role is between $112,800.00 - $196,535.00, excluding annual bonuses and equity, depending on geographic market. Actual base salary varies based on level, function, training, transferable skills, work experience, business needs, and location.
Schedule
This position offers a hybrid schedule requiring onsite work Tuesday through Friday at one of Axon’s regional hubs in New York City, Boston, or Scottsdale, Arizona. Relocation assistance is available for qualified U.S.-based candidates authorized to work for a U.S. employer and open to relocating nearer to a hub. Full‑time remote eligibility is evaluated case‑by‑case to accommodate specific needs.
We need to ensure we didn't repeat any boilerplate. Also ensure we didn't include "About Axon 911" etc. That could be part of About the role? Actually "About Axon 911" is about the product, not the role. Might be considered extraneous. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The "About Axon 911" is substantive about the team/product. Should we include it? It could be part of About the role or maybe a separate section like "About the team". But we only have prescribed headings. Could include it in About the role paragraph as context. Let's incorporate a sentence: "Axon 911 brings together Prepared and Carbyne under Axon, creating a platform that combines modern 911 infrastructure with an AI intelligence layer to help public safety agencies move faster, make better decisions, and deliver better outcomes." That's substantive.
Thus About the role paragraph: combine role description and Axon 911 context.
Now check for any duplicated lines: we must avoid repeating same content. Ensure we don't duplicate bullet points.
Let's extract bullet points precisely.
From "What You’ll Do":
- Electrical & Board Design: Develop mixed-signal schematics and drive PCB layout across application processors, RF transceivers, power management, battery charging, memory, and high-speed digital interfaces.
- RF Integration & Coexistence: Design and validate RF and radio systems across multiple wireless technologies, addressing RF performance, coexistence, interference, isolation, and electromagnetic compatibility.
- Mechanical Integration: Partner closely with Mechanical and Industrial Design to optimize board layout, component placement, antenna integration, and form factor within tight physical constraints.
- Bring-Up & Debugging: Bring up, characterize, and troubleshoot hardware using oscilloscopes, spectrum analyzers, logic analyzers, power supplies, and other electrical and RF test equipment.
- Production Readiness: Drive component selection, Bills of Materials (BOMs), design documentation, verification, and electrical readiness from concept through certification and mass production.
- Technical Leadership: Provide technical direction to electrical engineering team members and external design partners, reviewing designs and driving hardware objectives to completion.
From "What You Bring":
- 7+ years of embedded electronics design experience and a bachelor's degree in electrical engineering or a related discipline, with experience in high-speed, high-density, battery-powered, or low-power systems.
- Demonstrated experience with PCB design and layout, RF integration and coexistence, mechanical integration, and hardware bring-up/debugging for highly integrated devices.
- Experience across embedded subsystems, including application processors, microcontrollers, high-speed memory, power delivery, battery/charging circuitry, wireless/RF integration, and high-speed or wired interfaces.
- Proven experience taking electronics from concept through schematic and PCB design, verification, certification, manufacturing ramp, and mass production.
- Strong understanding of RF coexistence and interference across cellular and regulated frequency bands, along with signal integrity, power integrity, and electromagnetic compatibility considerations.
- Hands-on experience with Cadence OrCAD and Allegro, as well as oscilloscopes, spectrum analyzers, logic analyzers, power supplies, and related electrical and RF test equipment.
- Experience designing rigid, flex, or rigid-flex PCBs and working within tight mechanical and form-factor constraints.
- Experience designing electronics to meet U.S. and international hardware, wireless, and safety standards and regulations.
- Experience working with design partners, Original Design Manufacturers (ODMs), or Joint Design Manufacturers (JDMs) and collaborating effectively across cross-functional and geographically distributed teams.
- Flexibility to travel domestically up to 50% of the time, as needed, to support the team.
Now we need to split into Requirements and Skills.
Requirements could be: education/experience, years, degree, demonstrated experience with PCB design, RF integration, mechanical integration, bring-up/debugging, experience across embedded subsystems, proven experience taking electronics from concept through mass production, strong understanding of RF coexistence, etc. Also maybe experience designing electronics to meet standards.
Skills could be: hands-on experience with Cadence OrCAD and Allegro, oscilloscopes, spectrum analyzers, logic analyzers, power supplies, etc.; experience designing rigid/flex/rigid-flex PCBs; working with design partners/ODMs/JDMs; travel flexibility.
But note that some items overlap; we need to avoid duplication. We'll allocate as best.
Let's define Requirements list:
- 7+ years of embedded electronics design experience
- Bachelor's degree in electrical engineering or related discipline
- Experience in high-speed, high-density, battery-powered, or low-power systems
- Demonstrated experience with PCB design and layout, RF integration and coexistence, mechanical integration, and hardware bring-up/debugging
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to extract relevant content: The posting includes: - Intro: "Join Axon and be a Force for Good." etc. That's marketing fluff; maybe we can include as About the role? Actually "About Axon 911" etc. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. Let's parse: - About the role: Could be description of role: "We are seeking a Senior Electrical Engineer to own the design, development, and validation of complex electrical systems for mission-critical, connected hardware." Also "As a founding member of our hardware team..." etc. That could be About the role. - Responsibilities: The "What You’ll Do" bullet list: Electrical & Board Design, RF Integration & Coexistence, Mechanical Integration, Bring-Up & Debugging, Production Readiness, Technical Leadership. Those are responsibilities. - Requirements: The "What You Bring" bullet list: 7+ years experience, bachelor's degree, demonstrated experience with PCB design, etc. That's requirements/qualifications. - Qualifications: Might overlap with requirements; but we can combine? The instruction says prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But they ask to use headings for those specific names if content exists. We could have both Requirements and Qualifications if distinct. However the content seems to be qualifications/experience. Could treat "What You Bring" as Requirements. Could also have Skills: maybe list specific skills like Cadence OrCAD, Allegro, oscilloscopes, etc. That could be Skills. - Benefits: The "Benefits that Benefit You" list: Competitive salary and 401k with employer match, Discretionary paid time off, Paid parental leave, Medical, dental, and vision plans, Fitness Programs, Emotional & Mental Wellness support, Learning & Development programs, snacks. Also note about benefits varying. - Pay: The "Pay Transparency" section gives base pay range $112,800 - $196,535. Also mentions bonus, equity. So we have Pay. - Schedule: The "Work Location" mentions hybrid schedule requiring onsite Tuesday-Friday at hubs, relocation assistance, remote eligibility case-by-case. So schedule info: hybrid schedule, onsite Tue-Fri, relocation assistance, remote eligibility. We need to output only HTML fragment, no markdown fences. We must not include boilerplate like "Don’t meet every single requirement? That's ok." etc. Also remove EEO, legal, privacy, phishing alert, etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific responsibilities bullet points, qualifications bullet points, benefits list, pay range, schedule details. We must not repeat job title as heading. So no
Senior Electrical Engineer
. We must not put Job ID/requisition numbers as headings (none present). We must not include filler like "commensurate with experience". Not present. We need to decide which sections to include. Likely we include About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly Skills separate? But we could incorporate skills into Requirements or Qualifications. Since they ask for Skills heading if content exists. The "What You Bring" includes skills like PCB design, RF integration, etc. Could be considered Skills. But we already have Requirements. To avoid many thin sections, we could combine Requirements and Skills into one section called Requirements (or Qualifications). But they said use headings for those specific names if content exists. It's ambiguous. I'd include Requirements and Skills separate if both have distinct content. However the content overlaps; we could treat "What You Bring" as Requirements (experience, education) and Skills as technical skills (tools, technologies). Let's extract skills: "Hands-on experience with Cadence OrCAD and Allegro, as well as oscilloscopes, spectrum analyzers, logic analyzers, power supplies, and related electrical and RF test equipment." Also "Experience designing rigid, flex, or rigid-flex PCBs". Also "Experience working with design partners, ODMs, JDMs". Those could be skills. Thus we can have: - About the role: prose summarizing role. - Responsibilities: list of duties from "What You’ll Do". - Requirements: list of experience/education from "What You Bring" (7+ years, bachelor's degree, demonstrated experience with PCB design, etc.) maybe also include experience across embedded subsystems, proven experience taking electronics from concept through mass production, understanding of RF coexistence, etc. - Skills: list of specific tools/technologies: Cadence OrCAD, Allegro, oscilloscopes, spectrum analyzers, logic analyzers, power supplies, etc.; experience designing rigid/flex/rigid-flex PCBs; working with design partners/ODMs/JDMs; travel flexibility. - Benefits: list from "Benefits that Benefit You". - Pay: paragraph with base pay range. - Schedule: paragraph about hybrid schedule, onsite Tue-Fri, relocation assistance, remote eligibility. We need to ensure we don't include filler like "Benefits listed herein may vary depending on the nature of your employment and the location where you work." That's substantive? It's a note about benefits varying; we could include it as part of Benefits section maybe as a sentence. We must not include application instructions, EEO, legal, etc. Now produce HTML. Structure:About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Benefits may vary depending on employment nature and location.
Pay
The starting base annual pay for this role is between $112,800.00 - $196,535.00, excluding annual bonuses and equity, depending on geographic market. Actual base salary varies based on level, function, training, transferable skills, work experience, business needs, and location.
Schedule
This position offers a hybrid schedule requiring onsite work Tuesday through Friday at one of Axon’s regional hubs in New York City, Boston, or Scottsdale, Arizona. Relocation assistance is available for qualified U.S.-based candidates authorized to work for a U.S. employer and open to relocating nearer to a hub. Full‑time remote eligibility is evaluated case‑by‑case to accommodate specific needs.
We need to ensure we didn't repeat any boilerplate. Also ensure we didn't include "About Axon 911" etc. That could be part of About the role? Actually "About Axon 911" is about the product, not the role. Might be considered extraneous. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The "About Axon 911" is substantive about the team/product. Should we include it? It could be part of About the role or maybe a separate section like "About the team". But we only have prescribed headings. Could include it in About the role paragraph as context. Let's incorporate a sentence: "Axon 911 brings together Prepared and Carbyne under Axon, creating a platform that combines modern 911 infrastructure with an AI intelligence layer to help public safety agencies move faster, make better decisions, and deliver better outcomes." That's substantive. Thus About the role paragraph: combine role description and Axon 911 context. Now check for any duplicated lines: we must avoid repeating same content. Ensure we don't duplicate bullet points. Let's extract bullet points precisely. From "What You’ll Do": - Electrical & Board Design: Develop mixed-signal schematics and drive PCB layout across application processors, RF transceivers, power management, battery charging, memory, and high-speed digital interfaces. - RF Integration & Coexistence: Design and validate RF and radio systems across multiple wireless technologies, addressing RF performance, coexistence, interference, isolation, and electromagnetic compatibility. - Mechanical Integration: Partner closely with Mechanical and Industrial Design to optimize board layout, component placement, antenna integration, and form factor within tight physical constraints. - Bring-Up & Debugging: Bring up, characterize, and troubleshoot hardware using oscilloscopes, spectrum analyzers, logic analyzers, power supplies, and other electrical and RF test equipment. - Production Readiness: Drive component selection, Bills of Materials (BOMs), design documentation, verification, and electrical readiness from concept through certification and mass production. - Technical Leadership: Provide technical direction to electrical engineering team members and external design partners, reviewing designs and driving hardware objectives to completion. From "What You Bring": - 7+ years of embedded electronics design experience and a bachelor's degree in electrical engineering or a related discipline, with experience in high-speed, high-density, battery-powered, or low-power systems. - Demonstrated experience with PCB design and layout, RF integration and coexistence, mechanical integration, and hardware bring-up/debugging for highly integrated devices. - Experience across embedded subsystems, including application processors, microcontrollers, high-speed memory, power delivery, battery/charging circuitry, wireless/RF integration, and high-speed or wired interfaces. - Proven experience taking electronics from concept through schematic and PCB design, verification, certification, manufacturing ramp, and mass production. - Strong understanding of RF coexistence and interference across cellular and regulated frequency bands, along with signal integrity, power integrity, and electromagnetic compatibility considerations. - Hands-on experience with Cadence OrCAD and Allegro, as well as oscilloscopes, spectrum analyzers, logic analyzers, power supplies, and related electrical and RF test equipment. - Experience designing rigid, flex, or rigid-flex PCBs and working within tight mechanical and form-factor constraints. - Experience designing electronics to meet U.S. and international hardware, wireless, and safety standards and regulations. - Experience working with design partners, Original Design Manufacturers (ODMs), or Joint Design Manufacturers (JDMs) and collaborating effectively across cross-functional and geographically distributed teams. - Flexibility to travel domestically up to 50% of the time, as needed, to support the team. Now we need to split into Requirements and Skills. Requirements could be: education/experience, years, degree, demonstrated experience with PCB design, RF integration, mechanical integration, bring-up/debugging, experience across embedded subsystems, proven experience taking electronics from concept through mass production, strong understanding of RF coexistence, etc. Also maybe experience designing electronics to meet standards. Skills could be: hands-on experience with Cadence OrCAD and Allegro, oscilloscopes, spectrum analyzers, logic analyzers, power supplies, etc.; experience designing rigid/flex/rigid-flex PCBs; working with design partners/ODMs/JDMs; travel flexibility. But note that some items overlap; we need to avoid duplication. We'll allocate as best. Let's define Requirements list: - 7+ years of embedded electronics design experience - Bachelor's degree in electrical engineering or related discipline - Experience in high-speed, high-density, battery-powered, or low-power systems - Demonstrated experience with PCB design and layout, RF integration and coexistence, mechanical integration, and hardware bring-up/debugging