Ground Systems Engineer II
Job description
Ground Systems Engineer at Rocket Lab Corporation.
About the role
The position collaborates across teams to handle real hardware, launch pads, and missions from design through operations.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
Location: Auckland
Engagement: Full-time
Team: Ground Systems Engineering
Years: 1+
Degree: Diploma or degree in Aerospace, Mechanical, Mechatronics, or CAD Engineering (or equivalent)
Visa / export / citizenship: Eligible to access equipment and data regulated by ITAR; must hold citizenship of Australia, Japan, New Zealand, Switzerland, the European Union, or a NATO country, or be a U.S. citizen, lawful permanent resident, or asylum/refugee eligible for required authorizations
Domestic and international travel may be required
Commitment to health, safety, and company policies is essential
What you'll do
Project requirements are defined through collaboration with cross-functional teams, ensuring alignment with mission objectives. Design trade studies are performed, and compliance with engineering standards is ensured while producing manuals, procedures, and work instructions. Component- and system-level test plans are developed and executed, and test equipment is designed and maintained.
Requirements
A diploma or degree in Aerospace, Mechanical, Mechatronics, or CAD Engineering (or equivalent) is required. Experience with structural design and industrial equipment is mandatory. The ability to read and interpret technical drawings and schematics is required. Strong communication skills and a collaborative mindset are required. Comfort working in a fast-paced, hands-on environment is required. One or more years of engineering design experience in aerospace or industrial sectors is required.
Nice to have
Experience with launch pad systems, or industries such as oil & gas, mining, or process engineering is beneficial. Exposure to fluid system design is beneficial. Experience with NX, Teamcenter, SolidWorks, or EPDM is beneficial. Familiarity with ASME, ASTM, AS/NZS, or NASA ground system standards is beneficial.
Practical notes
Security checks including nationality verification apply under ITAR regulations. Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
The role emphasizes ownership, curiosity, proactive collaboration, and continuous learning. It uses tools such as CAD software, design and test documentation, and standards like ASME and ASTM. The environment is fast-paced, safety-focused, and team-oriented under tight deadlines.
Questions to ask
Good questions to ask the employer in the interview: what does success look like in the first six months, how is the team structured, what is the current biggest challenge, and how are decisions made. Asking about growth paths and the review process is also well received. Employers expect questions, and good ones show preparation.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.