Machina Labs
Software Engineer in Test (SET)
About this role
Machina Labs seeks a Software Engineer in Test to establish quality standards and oversee software releases for an intelligent manufacturing platform. You'll build test automation frameworks, validate features, manage CI/CD pipelines, and ensure production readiness while collaborating with software and robotics teams.
What you'll do
- Define and implement quality strategy across the software platform
- Build and maintain automated testing infrastructure and CI/CD pipelines
- Validate release candidates and execute production deployments
- Triage and troubleshoot software issues across the system
- Act as gatekeeper for software releases to production
- Collaborate with robotics and automation engineers on production impact testing
What they're looking for
- Test automation and QA methodologies
- CI/CD pipeline design and implementation
- Software engineering fundamentals
- Production release management
- Problem diagnosis and troubleshooting
- Python or similar automation languages
- Robotics systems understanding
- Release validation processes
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.
Machina Labs
Machina Labs builds intelligent manufacturing software and robotic systems, particularly advanced metal forming technology called RoboForming that converts digital designs into physical production parts for aerospace, defense, and mobility industries. The company is hiring software engineers in test, robotics automation engineers, and robotic process engineers to establish quality standards, develop automation frameworks, and optimize manufacturing processes.
View all jobs at Machina LabsLikely interview questions
- Describe your experience building and maintaining CI/CD pipelines. What tools have you used, and how did you ensure they caught critical issues before production?
- Walk us through how you've designed a test automation strategy from scratch. What testing pyramid approach did you use, and how did you prioritize coverage?