Base Power
System Design and Architecture Engineer
About this role
Base is looking for a System Design and Architecture Engineer to manage system-level hardware architecture for multi-subsystem products. This role will involve defining system boundaries, writing requirements, and overseeing integration and root cause analysis as the product develops.
What you'll do
- Define hardware architecture and system boundaries across subsystems
- Write and own system-level requirements during the design phase
- Transition into system integration as the project matures
- Make cross-domain architectural decisions and resolve trade-offs
- Lead investigations on subsystem failures using first-principles reasoning
What they're looking for
- 4+ years of experience with multi-subsystem systems
- Strong electrical and firmware engineering fundamentals
- Proficient in root cause analysis
- Knowledge of classical dynamic controls
- Experience with MATLAB/Simulink and Python scripting
- Ability to drive cross-domain decisions
- Understanding of communication architectures
- Knowledge of functional safety concepts [optional]
Benefits
- Fast-paced startup environment
- Opportunity to work on innovative projects
- Collaborative team culture
- Focus on personal and professional growth
- Potential for evolving responsibilities
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Base Power
Base Power develops high-power-density battery energy storage systems and related hardware for residential and commercial energy applications. The company is hiring System Design, Thermal, and Mechanical Engineers for product development, plus Supply Chain and Data Engineers to build internal platforms and infrastructure supporting distributed battery operations at scale.
View all jobs at Base PowerLikely interview questions
- Walk us through a multi-subsystem product you've architected end-to-end—how did you decide where system boundaries fell, and what was your toughest cross-domain trade-off?
- Describe a time you owned system-level requirements and had to push back on or override a domain team's implementation approach. How did you handle it?