We build electric motorcycles. The ride feels simple and alive. The rest should be too.We are not there yet. You will help us get there.The Product Experience (P.Ex) organization is responsible for how the motorcycle feels to use. We design and build the firmware that runs on the bike, the dash the rider sees, the mobile app they carry, the diagnostic tools used in the field, and the cloud systems that connect them.The Firmware Products team, within the P.Ex org, is responsible for delivering the behavior of the motorcycle itself. The team spans firmware development, battery performance engineering, and test engineering, owning the full value chain from firmware requirements to field validation. Every safety decision, performance characteristic, and response the bike makes to the rider runs through this system. Riders love and trust it.We are moving from something that works well to something riders and technicians can trust without thinking, where we are deliberate about what deserves to exist, make it excellent, and get out of the way. We are looking for a leader who can learn alongside the team and mentor them to learn continuously without disrupting the care they have for each other.<h3>What you will help build</h3>We are building a system where we can quickly and reliably understand how what we ship behaves in the real world, and use that to make better product decisions. This goes beyond processes or frameworks. In practice, it looks like:<ul><li>A change is made and within hours we can see how it affected real riders, not just whether tests passed.</li><li>When something goes wrong, we can reconstruct what the rider experienced, how the system responded, and which interactions or changes led to it.</li><li>We reduce the time between making a change and understanding its impact, without increasing risk.</li><li>What we learn from real-world behavior directly changes what we build next.</li><li>We use that learning to decide what not to build, what to simplify, and where to focus next.</li></ul>If answering these depends on meetings, reports, or interpretation, the system is not giving us the feedback we need.<h3>What You'll Do</h3>You will lead the Firmware Products team end to end, leading 8-12 engineers across firmware development, battery performance, and test, spread across Scotts Valley, Netherlands, and India. You decide what problems need to be solved next, and you work with the Firmware, BMS, and Vehicle Architects to ensure they are framed and addressed well. You will care deeply about the people on the team and invest in their growth as engineers, system thinkers, and craftspeople.You walk in every Monday with more ideas to make your team shoot for greatness than you have the time to implement.Team Leadership and Growth<ul><li>Understand what each person on the team is working toward and what is getting in their way, and act on it continuously.</li><li>Give direct, specific feedback and create the conditions for a team that improves how it works and becomes self-organizing over time.</li></ul>Firmware as a Product <ul><li>Think about what riders need from firmware before thinking about what the team should build. That order is not negotiable. Translate user and business needs into small, testable work.</li><li>Keep the backlog honest by saying no to what does not move the product forward, and do not let closing tickets masquerade as solving problems.</li></ul>Stay Technically Hands-On <ul><li>Get in the trenches with Firmware, BMS, and Vehicle Architects to create the conditions for strong work, clear priorities, protected focus, and problems framed well enough to be worth solving.</li><li>Write, review, debug, and critique with enough technical depth that architects trust you with their hardest problems and decisions.</li></ul>Delivery System and Flow<ul><li>Own and improve the system from idea to field so the team learns faster without increasing fragility.</li><li>Keep batches small, integration continuous, and validation part of building, and surface risk early enough for the team to act on it.</li></ul>Instrumentation and Field Learning<ul><li>Be accountable for firmware behavior across real riders, environments, and failure modes, and ensure the system captures what is needed to understand it.</li><li>Build feedback loops from field behavior into planning so the team learns from usage and not just incidents.</li></ul>Cross-functional Collaboration<ul><li>Review hardware, vendor firmware, and system decisions, and ensure firmware behavior stays coherent from component to customer experience.</li><li>Work with CX, PMO, and leadership to ensure releases reach customers smoothly, field feedback shapes priorities, and commitments reflect technical reality and surface risk early.</li><li>Represent the team's work to the exec team and marketing in terms that shape decisions, not just inform them.</li></ul>AI Adoption<ul><li>Use AI tools fluently and daily, with tools like Claude Code as a starting point, and push well into using AI as a genuine thought partner in architecture, debugging, prioritization, and technical decision-making.</li><li>Drive AI adoption across the team and upward, using it to unlock higher performance and advocating for tools and capabilities the team needs.</li></ul><h3>What You Bring</h3>You bring 10-15 years of embedded development experience and at least 3-5 years leading a multi-discipline team. You will be stretched, but you will not be doing it alone. You do not need to check every box on this list. If you bring the hunger to close gaps and the self-awareness to know where they are, the team and the manager will meet you there. People Leadership<ul><li>You have grown engineers who were not ready for the next level and got them there. You have given feedback that was hard to hear, in a way that strengthened the relationship.</li><li>You have managed across locations and found ways to make distance irrelevant to the quality of someone's experience on the team.</li></ul>Product Thinking<ul><li>You have made prioritization calls that are right in the long term, even when unpopular, and explain them clearly.</li><li>You have worked in environments where the temptation to build more was constant, and you developed the discipline to build less, better.</li></ul>Embedded Systems and Firmware Depth<ul><li>You have deep experience shipping multithreaded, real-time embedded firmware in C / C++ and can smell problems before they surface.</li><li>You are proficient debugging embedded systems at the bench. You read schematics and datasheets, and you are comfortable with UARTs, JTAG, and oscilloscopes.</li></ul>Delivery and Flow<ul><li>You have moved teams toward smaller batches in constrained environments and made a measurable difference.</li><li>You have shipped in safety-critical systems and improved CI/CD to move faster without compromising integrity.</li></ul>Collaboration and Influence<ul><li>You have worked effectively with technical experts to move decisions forward without needing to win every argument.</li><li>You have navigated competing priorities across teams without creating turf wars or waiting for someone above you to resolve the tension.</li></ul>AI Fluency<ul><li>You use AI tools daily to think through hard problems, well beyond basic usage.</li><li>You have driven adoption and apply sound judgment on where AI can and cannot be trusted in safety-critical systems.</li></ul><h3>What You Can Expect</h3><ul><li>Real cross-functional work with Firmware, BMS, Vehicle Architecture, PMO, CX, and Hardware in problem spaces that require you to understand the whole system.</li><li>A team and management that will tell you the truth about your work, fight for your growth, and have your back when things get hard.</li><li>Problems that are not fully defined, where your judgment about what matters next is what the role actually requires.</li><li>A system that is in use, under pressure, and not finished, which means the work you do here has consequences that show up in the field.</li></ul><h3>How We Hire</h3>We're an AI-fluent team. But our hiring decisions belong to humans; every step is owned by someone on our team.<ul><li>Step 0: We read your resume and respond within 5 business days.</li><li>Step 1: A short exercise. A 2-question (&lt; 20 minute) written questionnaire or a 15-minute problem-solving conversation, depending on the role. No prep needed for either. We respond within 3 business days.</li><li>Step 2: Initial conversations. 45 minutes with the hiring manager and a 45-minute technical screen, back to back in a single sitting. We respond within 5 business days.</li><li>Step 3: Panel discussion with the team.</li><li>Step 4: Offer.</li></ul><h3>Location</h3>Scotts Valley, CA<h3>Physical Requirements</h3><ul><li>Ability to communicate in real-time with internal and external partners.</li><li>Ability to safely and effectively navigate a lab environment.</li><li>Ability to occasionally lift 30 pounds.</li><li>Ability to work for extended periods in face-to-face meetings, on computers, or in a lab environment.</li></ul>We believe diversity is our strength, and inclusion is our foundation. As an Equal Opportunity Employer, we are committed to building a workplace where everyone - regardless of race, ethnicity, gender identity, sexual orientation, disability, age, or background - can thrive. We celebrate individuality, amplify diverse voices, and strive to foster an environment where everyone feels seen, heard, and empowered to do their best work. Together, we’re shaping a future that works for all. The estimated salary range for a new hire in this position is $180,000 to $200,000. Actual salary may vary depending on job-related factors, which may include candidate's knowledge, skills, and experience. In addition to regular salary, Zero offers a comprehensive benefits package including health, life, and disability insurance, paid time off, and a 401(k)-matching plan.

Zero Motorcycles is the next step in motorcycle evolution and represents the ultimate electric motorcycle technology. Unencumbered by conventional thinking about how they design, manufacture, and sell high-performance electric motorcycles, they're on a mission to turn heads and revolutionize their industry by combining the best aspects of a traditional motorcycle with today's most advanced technology. The result is an electric motorcycle line that's insanely fast, and environmentally friendly.

Since its inception, Zero Motorcycles, Inc. (formerly Electricross) has been dedicated to developing the very best in electric motorcycle technology. Built for both experienced and entry-level riders their premium motorcycle line offers blistering acceleration and speed with optional settings for the less aggressive. What separates them from their competition is the performance, quality, and reliability of each bike.

It was founded in 2006 and is headquartered in Scotts Valley, California.

Firmware Engineering Manager (Products & Systems)

We build electric motorcycles. The ride feels simple and alive. The rest should be too.We are not there yet. You will help us get there.The Product Experience (P.Ex) organization is responsible for how the motorcycle feels to use. We design and build the firmware that runs on the bike, the dash the rider sees, the mobile app they carry, the diagnostic tools used in the field, and the cloud systems that connect them.The Firmware Products team, within the P.Ex org, is responsible for delivering the behavior of the motorcycle itself. The team spans firmware development, battery performance engineering, and test engineering, owning the full value chain from firmware requirements to field validation. Every safety decision, performance characteristic, and response the bike makes to the rider runs through this system. Riders love and trust it.We are moving from something that works well to something riders and technicians can trust without thinking, where we are deliberate about what deserves to exist, make it excellent, and get out of the way. We are looking for a leader who can learn alongside the team and mentor them to learn continuously without disrupting the care they have for each other.<h3>What you will help build</h3>We are building a system where we can quickly and reliably understand how what we ship behaves in the real world, and use that to make better product decisions. This goes beyond processes or frameworks. In practice, it looks like:<ul><li>A change is made and within hours we can see how it affected real riders, not just whether tests passed.</li><li>When something goes wrong, we can reconstruct what the rider experienced, how the system responded, and which interactions or changes led to it.</li><li>We reduce the time between making a change and understanding its impact, without increasing risk.</li><li>What we learn from real-world behavior directly changes what we build next.</li><li>We use that learning to decide what not to build, what to simplify, and where to focus next.</li></ul>If answering these depends on meetings, reports, or interpretation, the system is not giving us the feedback we need.<h3>What You'll Do</h3>You will lead the Firmware Products team end to end, leading 8-12 engineers across firmware development, battery performance, and test, spread across Scotts Valley, Netherlands, and India. You decide what problems need to be solved next, and you work with the Firmware, BMS, and Vehicle Architects to ensure they are framed and addressed well. You will care deeply about the people on the team and invest in their growth as engineers, system thinkers, and craftspeople.You walk in every Monday with more ideas to make your team shoot for greatness than you have the time to implement.Team Leadership and Growth<ul><li>Understand what each person on the team is working toward and what is getting in their way, and act on it continuously.</li><li>Give direct, specific feedback and create the conditions for a team that improves how it works and becomes self-organizing over time.</li></ul>Firmware as a Product <ul><li>Think about what riders need from firmware before thinking about what the team should build. That order is not negotiable. Translate user and business needs into small, testable work.</li><li>Keep the backlog honest by saying no to what does not move the product forward, and do not let closing tickets masquerade as solving problems.</li></ul>Stay Technically Hands-On <ul><li>Get in the trenches with Firmware, BMS, and Vehicle Architects to create the conditions for strong work, clear priorities, protected focus, and problems framed well enough to be worth solving.</li><li>Write, review, debug, and critique with enough technical depth that architects trust you with their hardest problems and decisions.</li></ul>Delivery System and Flow<ul><li>Own and improve the system from idea to field so the team learns faster without increasing fragility.</li><li>Keep batches small, integration continuous, and validation part of building, and surface risk early enough for the team to act on it.</li></ul>Instrumentation and Field Learning<ul><li>Be accountable for firmware behavior across real riders, environments, and failure modes, and ensure the system captures what is needed to understand it.</li><li>Build feedback loops from field behavior into planning so the team learns from usage and not just incidents.</li></ul>Cross-functional Collaboration<ul><li>Review hardware, vendor firmware, and system decisions, and ensure firmware behavior stays coherent from component to customer experience.</li><li>Work with CX, PMO, and leadership to ensure releases reach customers smoothly, field feedback shapes priorities, and commitments reflect technical reality and surface risk early.</li><li>Represent the team's work to the exec team and marketing in terms that shape decisions, not just inform them.</li></ul>AI Adoption<ul><li>Use AI tools fluently and daily, with tools like Claude Code as a starting point, and push well into using AI as a genuine thought partner in architecture, debugging, prioritization, and technical decision-making.</li><li>Drive AI adoption across the team and upward, using it to unlock higher performance and advocating for tools and capabilities the team needs.</li></ul><h3>What You Bring</h3>You bring 10-15 years of embedded development experience and at least 3-5 years leading a multi-discipline team. You will be stretched, but you will not be doing it alone. You do not need to check every box on this list. If you bring the hunger to close gaps and the self-awareness to know where they are, the team and the manager will meet you there. People Leadership<ul><li>You have grown engineers who were not ready for the next level and got them there. You have given feedback that was hard to hear, in a way that strengthened the relationship.</li><li>You have managed across locations and found ways to make distance irrelevant to the quality of someone's experience on the team.</li></ul>Product Thinking<ul><li>You have made prioritization calls that are right in the long term, even when unpopular, and explain them clearly.</li><li>You have worked in environments where the temptation to build more was constant, and you developed the discipline to build less, better.</li></ul>Embedded Systems and Firmware Depth<ul><li>You have deep experience shipping multithreaded, real-time embedded firmware in C / C++ and can smell problems before they surface.</li><li>You are proficient debugging embedded systems at the bench. You read schematics and datasheets, and you are comfortable with UARTs, JTAG, and oscilloscopes.</li></ul>Delivery and Flow<ul><li>You have moved teams toward smaller batches in constrained environments and made a measurable difference.</li><li>You have shipped in safety-critical systems and improved CI/CD to move faster without compromising integrity.</li></ul>Collaboration and Influence<ul><li>You have worked effectively with technical experts to move decisions forward without needing to win every argument.</li><li>You have navigated competing priorities across teams without creating turf wars or waiting for someone above you to resolve the tension.</li></ul>AI Fluency<ul><li>You use AI tools daily to think through hard problems, well beyond basic usage.</li><li>You have driven adoption and apply sound judgment on where AI can and cannot be trusted in safety-critical systems.</li></ul><h3>What You Can Expect</h3><ul><li>Real cross-functional work with Firmware, BMS, Vehicle Architecture, PMO, CX, and Hardware in problem spaces that require you to understand the whole system.</li><li>A team and management that will tell you the truth about your work, fight for your growth, and have your back when things get hard.</li><li>Problems that are not fully defined, where your judgment about what matters next is what the role actually requires.</li><li>A system that is in use, under pressure, and not finished, which means the work you do here has consequences that show up in the field.</li></ul><h3>How We Hire</h3>We're an AI-fluent team. But our hiring decisions belong to humans; every step is owned by someone on our team.<ul><li>Step 0: We read your resume and respond within 5 business days.</li><li>Step 1: A short exercise. A 2-question (&lt; 20 minute) written questionnaire or a 15-minute problem-solving conversation, depending on the role. No prep needed for either. We respond within 3 business days.</li><li>Step 2: Initial conversations. 45 minutes with the hiring manager and a 45-minute technical screen, back to back in a single sitting. We respond within 5 business days.</li><li>Step 3: Panel discussion with the team.</li><li>Step 4: Offer.</li></ul><h3>Location</h3>Scotts Valley, CA<h3>Physical Requirements</h3><ul><li>Ability to communicate in real-time with internal and external partners.</li><li>Ability to safely and effectively navigate a lab environment.</li><li>Ability to occasionally lift 30 pounds.</li><li>Ability to work for extended periods in face-to-face meetings, on computers, or in a lab environment.</li></ul>We believe diversity is our strength, and inclusion is our foundation. As an Equal Opportunity Employer, we are committed to building a workplace where everyone - regardless of race, ethnicity, gender identity, sexual orientation, disability, age, or background - can thrive. We celebrate individuality, amplify diverse voices, and strive to foster an environment where everyone feels seen, heard, and empowered to do their best work. Together, we’re shaping a future that works for all. The estimated salary range for a new hire in this position is $180,000 to $200,000. Actual salary may vary depending on job-related factors, which may include candidate's knowledge, skills, and experience. In addition to regular salary, Zero offers a comprehensive benefits package including health, life, and disability insurance, paid time off, and a 401(k)-matching plan.

Firmware Engineering Manager (Products & Systems)

About the Job

About the Company

Zero Motorcycles

Similar Jobs

Principal Embedded Firmware Engineer

Principal Embedded Firmware Engineer

Embedded Software Product Manager

Embedded Software Product Manager

Staff Technical Program Manager, Software Engineering

Staff Technical Program Manager, Software Engineering

Software Engineering Manager - IT Enterprise Applications

Software Engineering Manager - IT Enterprise Applications

Staff Technical Program Manager, Engineering

Staff Technical Program Manager, Engineering

Director, R&D Engineering

Director, R&D Engineering

Senior Manager, Flight Software

Senior Manager, Flight Software

Manager, Firmware Engineering

Manager, Firmware Engineering

Senior Technical Program Manager, Embedded Software

Senior Technical Program Manager, Embedded Software

Sr. Software Engineering Manager

Sr. Software Engineering Manager