System Design and Architecture Engineer

Base Power Company; San Carlos (TX); On-site; USD 90,000 - 120,000; Full time

Job summary

Base Power Company in San Carlos, Texas, seeks a System Design & Architecture Engineer to lead system-level hardware architecture for multi-subsystem products. You will define how subsystems work together, own requirements, and guide system integration.

Ideal candidates have 4+ years in system design, strong EE and firmware foundations, and experience in resolving cross-domain trade-offs decisively. Join Base and do the best work of your life.

Qualifications

• 4+ years designing or integrating multi‑subsystem electromechanical systems.
• Strong EE fundamentals and firmware understanding.
• Experience with root-cause analysis on multi-domain problems.

Responsibilities

• Define hardware architecture across subsystems.
• Write and own system-level requirements.
• Transition into system integration role during later phases.

Skills

System architecture design

Electromechanical systems integration

Embedded systems understanding

Root cause analysis

MATLAB/Simulink proficiency

Cross-domain decision-making

Education

4+ years in multi-subsystem design

Strong electrical engineering fundamentals

Working knowledge of dynamic controls

Tools

Python scripting

Modeling tools

Job description

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 transforms 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 seeking a System Design & Architecture Engineer to own the system‑level hardware architecture of multi‑subsystem products. This person decides how the subsystems work together as one coherent system, defines where system boundaries fall (which box owns the shared power supply?), and sets the communications, information, authority, and control flows across the system. They write and own requirements during the design phase and transition into a system integration role as the program matures, making the system‑level calls that keep cross‑domain design work from design‑by‑committee.

What You’ll Do

• System Architecture: Define the hardware architecture across subsystems—partitioning functions, resolving where system boundaries blur, and making the system‑level decisions (e.g., "how many data buses, and at what speed do they operate?") that the implementation teams design to.
• Requirements Ownership: Write and own system‑level requirements through the design phase, flowing them down to the domain teams and keeping them coherent as the design evolves.
• Integration: Transition into the system integration role in later development phases—bringing up the integrated system, owning multi‑subsystem behavior, and root‑causing issues that fall between domains.
• Cross‑Domain Decision‑Making: Hold system‑level authority over architecture decisions while influencing the implementation layer. Resolve cross‑domain trade‑offs decisively so multi‑part design work doesn’t stall.
• Root Cause Analysis: Lead root‑cause investigation on system‑level and inter‑subsystem failures, applying strong first‑principles reasoning.

What You’ll Bring

• 4+ years designing or integrating multi‑subsystem electromechanical, embedded, or power‑electronics systems, with system‑architecture ownership. Experience on a highly integrated system (e.g., automotive) is strongly relevant.
• Strong EE fundamentals and stronger firmware fundamentals—able to reason about embedded behavior, communications, and system timing, and to design across the HW/FW boundary.
• Very strong physics and first‑principles reasoning; strong root‑cause analysis on complex, multi‑domain problems.
• Working knowledge of classical dynamic controls (e.g., understands PID and feedback‑loop behavior).
• Proficiency with MATLAB/Simulink for modeling and analysis. Able to write Python scripts and quickly build tooling as needed; comfortable expressing designs as state charts and diagrams.
• Demonstrated ability to own cross‑domain system decisions and drive them to closure without defaulting to design‑by‑committee.

Preferred Qualifications

• Experience defining communications architectures (CAN, Ethernet, Modbus) and authority/control flows in a distributed embedded system.
• Working knowledge of functional safety concepts and their application to complex systems.
• Track record carrying a system from architecture definition through integration and bring‑up.
• Experience across multiple product domains or system types.
• Mechanical engineering depth is not required for this role.

Do the best work of your life at Base.