Skip to main content

Software Engineer II - Production Automation

Posted today

rocket labLong Beach (CA)

SENIORITY

Senior

Apply (opens in a new tab)

About the role

Overview: As Software Engineer II in Production Automation, you’ll build and sustain software that enables automated testing and production integration for spacecraft components. You’ll collaborate with avionics and manufacturing engineers to test, validate, and deploy production-ready software in a fast-paced, cross-functional environment. You’ll contribute to test rigs, documentation, and agile practices while solving complex production challenges. This role offers impact across rocket programs and opportunities to grow with a mission-driven team. Compensation / Benefits Stock purchase program medical plans (HMO, PPO, HDHP with HSA) dental and vision coverage paid vacation and sick time 401(k) with company match EV charging subsidy
Responsibilities: Develop, improve, and support production automation software for acceptance testing and system verification Integrate production systems and supporting software within the manufacturing environment Develop software and unit tests for bug-fixes and new features Create and maintain operational documentation for software products Participate in code reviews and architecture discussions Document architecture designs and refine product backlog items Facilitate agile ceremonies and keep tickets up-to-date Collaborate with stakeholders to investigate issues and drive solutions Deploy software in production and ensure alignment with business processes Take ownership of tasks and deliver solutions Support cross-functional teams and learn to assist other groups Domestic and international travel may be required Perform additional duties as reasonably required
Key requirements: Bachelor’s degree in Computer Science or Software/Electrical/Mechatronics Engineering (4+ years experience may substitute for a degree) 2+ years of experience in a software engineering-related role Experience with source control and issue trackers (git, jira, redmine) collaboration across cross-functional teams stakeholder engagement ownership and accountability Python or C++ or similar languages Linux development environment experience with interfaces/protocols (TCP/UDP, serial, CAN)

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this