ispace
Software & Simulation Test Design Engineer
About this role
ispace U.S. seeks a Software & Simulation Test Design Engineer to develop a unified test framework and simulation environment for lunar lander systems. You'll architect standardized testing practices and automation infrastructure that support mission-critical validation across global teams in this rapidly growing space exploration company.
What you'll do
- Design and lead development of unified test software framework spanning simulation, hardware-in-the-loop, integration, and system testing
- Establish standardized testing practices and automation infrastructure across the organization
- Create simulation environments that enable high-confidence validation of mission-critical systems
- Enable distributed engineering teams to operate efficiently within shared testing frameworks
- Ensure consistency, scalability, and reliability of testing approaches globally
- Support validation of high-capacity payload lunar landers for future missions
What they're looking for
- Test software architecture and design
- Simulation environment development
- Hardware-in-the-loop (HIL) testing
- Test automation and framework development
- System-level testing and validation
- Software engineering best practices
- Distributed systems coordination
- Mission-critical systems experience
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.
ispace
ispace builds lunar landers and spacecraft systems for space exploration missions. The company is hiring manufacturing engineers to oversee spacecraft fabrication and assembly, as well as software engineers to develop testing frameworks and simulation environments for mission-critical validation.
- Website
- ispace.co.jp
Likely interview questions
- Can you describe your experience designing and architecting test frameworks or simulation environments? What challenges did you face in making them scalable across distributed teams?
- Tell us about a time you standardized testing practices or processes across an organization or multiple teams. How did you handle resistance to change?