Jobs · Engineering · Texas

Senior Electronics Design Engineer

Base Power Company · San Carlos, TX · 1 mo ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: About Base (company description) maybe not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections that have real specific content. The posting includes "About Base" (company overview) and "About The Role". There's no separate "About the role" heading but there is "About The Role". We can treat that as "About the role". Then responsibilities: "What You'll Do". Requirements/Qualifications: "What You'll Bring". Preferred Skills: "Preferred Skills". Also there is "Please note: Base is a startup..." maybe not a section. Values etc maybe not needed as heading; but could be considered part of description but not required headings. We should not create Pay/Benefits/Schedule sections because not present. So we will have sections: About the role, Responsibilities, Requirements, Qualifications (maybe combine?), Skills. But we need to avoid duplication. The instruction: Use headings as listed; we can choose which to include. We have content for About the role, Responsibilities, Requirements (maybe "What You'll Bring" includes requirements), Qualifications (maybe similar), Skills (Preferred Skills). Could combine Requirements and Qualifications into one? But better to follow typical: Requirements = mandatory, Qualifications = preferred? However we have both "What You'll Bring" (mandatory) and "Preferred Skills". So we can make Requirements = "What You'll Bring", Qualifications = maybe empty? But we should not create empty sections. So we could treat "What You'll Bring" as Requirements, and "Preferred Skills" as Skills. Qualifications maybe not needed. Or we could treat "What You'll Bring" as Qualifications and "Preferred Skills" as Skills. But we need to avoid filler. Let's decide: Use sections: About the role, Responsibilities, Requirements, Skills. That covers all. We'll not include Qualifications if no distinct content. We'll embed company overview maybe as a paragraph before sections? The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. The company overview "About Base" could be a short paragraph before sections, not a heading. That's fine. Thus output:

About Base Base is America’s next-generation power company...

Then

About the role

with paragraph(s) from "About The Role" section. Then

Responsibilities

with
  • items from "What You'll Do". Then

    Requirements

    with
    • items from "What You'll Bring". Then

      Skills

      with
      • items from "Preferred Skills". We must preserve all substantive information, not invent or summarize away detail. So we need to copy the bullet points exactly as they appear, maybe rephrase slightly but keep meaning. Use
        • . Ensure no extra headings. Let's extract text. About Base paragraph: "Base is America’s next-generation power company. We’re rebuilding the foundation of modern civilization–electricity–by deploying a vast network of distributed batteries that is transforming today’s fragile, centralized grid into a resilient and abundant system. We are engineers, operators, and creatives solving some of the most complex, interdisciplinary challenges of our time." About The Role paragraph: "We are looking for a senior level electronics design engineer to own and drive the electrical architecture of Base's energy storage systems —inverters, batteries, and interconnect devices— from concept through high-volume manufacturing and field deployment. This is a foundational leadership role and you will define how Base builds the most reliable, cost-efficient, high-performance batteries and inverters in the world. This role is for someone who has spent years deep in power electronics and multi-function distributed ECU system design—someone who has personally taken products from napkin sketches to millions of units in the field—and is now ready to lead a team doing the same. You should have a strong point of view on how to design robust, manufacturable energy systems at scale, and the hands-on credibility to back it up. We want a builder who is equally comfortable debugging a gate driver at the bench and setting the technical direction for the entire electrical platform." What You'll Do bullet points (list): - Set the electrical architecture and technical direction for Base's full product line, including inverters, battery management systems, and microgrid interconnect devices. - Own specifications, topology selection, schematic capture, PCB layout strategy, board bring-up, validation, and reliability testing. - Build, mentor, and lead a team of electrical engineers. - Set high standards for design rigor, validation methodology, and documentation. - Create an environment where engineers do the best work of their careers. - Drive LV embedded systems and power converter design and validation across the product portfolio, including inverter power stages, battery pack architectures, and BMS. - Collaborate firmware, mechanical, test, reliability, and manufacturing teams to move products from prototype to high-volume production. - Own production end of line testers. - Debug and resolve complex system-level electrical issues across power, control, and communication domains. - Be the person the team turns to when something doesn't make sense. - Champion continuous product improvement—drive design iterations informed by field data, manufacturing feedback, and evolving performance targets. What You'll Bring bullet points: - 10+ years of experience in electrical system design, with significant time spent on systems like energy storage, inverters, EV charging, motor drives, or similar high-power applications. - Demonstrated experience taking complex electrical products from initial architecture through production ramp and field deployment—ideally at scale. - Strong command of PCB design (Altium preferred) and hands-on bring-up skills: you can solder, probe, wire, and debug with the best of them. You can write and run a transient thermal simulation in MATLAB or Python - Familiarity with embedded systems, microcontrollers and their peripherals, and scripting (Python or similar) for test automation and data analysis. - Working knowledge of control theory as applied to power conversion—loop compensation, sensor bandwidth, filtering, and stability. - Experience with automotive or industrial communication protocols (CAN, LIN, Ethernet). - Proficiency with lab equipment including oscilloscopes, power analyzers, function generators, and programmable power supplies. - A track record of leading or mentoring engineers, with a desire to build and grow a high-performing team. Preferred Skills bullet points: - BSEE or higher, particularly with a focus on power electronics. - Experience designing products for UL/CSA/IEC certification and regulatory compliance. - Familiarity with electric motor design, thermal simulation, or mechanical integration. - Experience in high-volume manufacturing environments and DFM/DFT optimization. Also there is a note: "Please note: Base is a startup, which means priorities shift and evolve quickly. Your role may expand or change based on the needs of the business at any given time, so the responsibilities listed may not be exhaustive." This is minor metadata; we can fold into a short

          after sections or drop. Probably include as a paragraph after sections. Also values etc maybe not needed; we can drop as boilerplate? It's not cookie/navigation/legal/EEO etc but could be considered culture; but instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Values are not those; but they might be considered boilerplate? Not sure. Safer to include maybe as a paragraph? But they are not required headings; we could include as a paragraph after the note. However they are somewhat generic; but they are part of posting. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep them. But they are not under a heading; we can just put them as a

          after the note. Thus final HTML:

          About Base Base is America’s next-generation power company. We’re rebuilding the foundation of modern civilization–electricity–by deploying a vast network of distributed batteries that is transforming today’s fragile, centralized grid into a resilient and abundant system. We are engineers, operators, and creatives solving some of the most complex, interdisciplinary challenges of our time.

          About the role

          We are looking for a senior level electronics design engineer to own and drive the electrical architecture of Base's energy storage systems —inverters, batteries, and interconnect devices— from concept through high-volume manufacturing and field deployment. This is a foundational leadership role and you will define how Base builds the most reliable, cost-efficient, high-performance batteries and inverters in the world. This role is for someone who has spent years deep in power electronics and multi-function distributed ECU system design—someone who has personally taken products from napkin sketches to millions of units in the field—and is now ready to lead a team doing the same. You should have a strong point of view on how to design robust, manufacturable energy systems at scale, and the hands-on credibility to back it up. We want a builder who is equally comfortable debugging a gate driver at the bench and setting the technical direction for the entire electrical platform.

          Responsibilities

          • Set the electrical architecture and technical direction for Base's full product line, including inverters, battery management systems, and microgrid interconnect devices.
          • Own specifications, topology selection, schematic capture, PCB layout strategy, board bring-up, validation, and reliability testing.
          • Build, mentor, and lead a team of electrical engineers.
          • Set high standards for design rigor, validation methodology, and documentation.
          • Create an environment where engineers do the best work of their careers.
          • Drive LV embedded systems and power converter design and validation across the product portfolio, including inverter power stages, battery pack architectures, and BMS.
          • Collaborate firmware, mechanical, test, reliability, and manufacturing teams to move products from prototype to high-volume production.
          • Own production end of line testers.
          • Debug and resolve complex system-level electrical issues across power, control, and communication domains.
          • Be the person the team turns to when something doesn't make sense.
          • Champion continuous product improvement—drive design iterations informed by field data, manufacturing feedback, and evolving performance targets.

          Requirements

          • 10+ years of experience in electrical system design, with significant time spent on systems like energy storage, inverters, EV charging, motor drives, or similar high-power applications.
          • Demonstrated experience taking complex electrical products from initial architecture through production ramp and field deployment—ideally at scale.
          • Strong command of PCB design (Altium preferred) and hands-on bring-up skills: you can solder, probe, wire, and debug with the best of them. You can write and run a transient thermal simulation in MATLAB or Python
          • Familiarity with embedded systems, microcontrollers and their peripherals, and scripting (Python or similar) for test automation and data analysis.
          • Working knowledge of control theory as applied to power conversion—loop compensation, sensor bandwidth, filtering, and stability.
          • Experience with automotive or industrial communication protocols (CAN, LIN, Ethernet).
          • Proficiency with lab equipment including oscilloscopes, power analyzers, function generators, and programmable power supplies.
          • A track record of leading or mentoring engineers, with a desire to build and grow a high-performing team.

          Skills

          • BSEE or higher, particularly with a focus on power electronics.
          • Experience designing products for UL/CSA/IEC certification and regulatory compliance.
          • Familiarity with electric motor design, thermal simulation, or mechanical integration.
          • Experience in

Similar jobs