Junior engineers get to work with a broad range of technology.
They use some great technology, which gives ample opportunities for platform learning.
Management are genuinely clueless about software development, failing upwards into leadership roles, then operating without any formal training.
Outcomes are more important than their people at all times, but they also don't have a clear understanding what outcomes they're looking for, which means expectations aren't realistic. You can work 60+ hour weeks, release more code than entire teams, yet still get told your performance is lacking.
Senior engineers most likely have more understanding of the SDLC than Directors, but aren't allowed to question or improve processes, and will be managed by a mid-level intermediate who fits into the ego-driven boys-club.
After 10 years, the codebases still look like a university group project, held together by toothpicks and red-bull. Tests? Standards? Governance? You won't find any of that here. They like to believe they move fast and are agile, yet are ignorant to how slow they move compared to other software companies. It's almost comical at times.
"Rocket Lab can be a toxic and hostile place, and it's not for everyone" - said to me by my manager when I raised the ample sexism and racism in the workplace.
I felt my time there was genuinely damaging to my career, not because of their (poor) industry reputation, but because they operate with such terrible practices that I started to forget what good software looked like.
It's highly unlikely management would take advice from a Glassdoor review, given they don't take feedback from their employees.
First interview, recruiter, 2nd with the respective team, 3rd step test assessment (fairly easy), last step on-site interview. Interviews tend to be laid back and fairly chill some technicalities discussed in 2nd and 3rd interview but nothing trying
The interview process was structured and professional, consisting of technical discussions and problem-solving questions relevant to software engineering. The interviewer was polite and knowledgeable. However, the feedback after rejection was limited
Fair interview process, few years ago though. Still a small company so a bit unstructured but overall was pretty straightforward in their questions. Believe it was for a junior embedded role.
First interview, recruiter, 2nd with the respective team, 3rd step test assessment (fairly easy), last step on-site interview. Interviews tend to be laid back and fairly chill some technicalities discussed in 2nd and 3rd interview but nothing trying
The interview process was structured and professional, consisting of technical discussions and problem-solving questions relevant to software engineering. The interviewer was polite and knowledgeable. However, the feedback after rejection was limited
Fair interview process, few years ago though. Still a small company so a bit unstructured but overall was pretty straightforward in their questions. Believe it was for a junior embedded role.