I got referred to a research engineer job in a team called special projects (robotics). The job description and the requirements are very vague with no mention of specific programming languages, robotic simulators, or specific proficiency.

I am confused how to prepare for the technical loop interview. I keep getting advice not to wait to be approached by the recruiter as the process can go quite fast, but I just do not know what to prepare. Anyone can help with what I would expect to be interviewed for technically (python? ROS?, …)

Note: I am a postdoc for a top uni worldwide and my expertise is mainly in experimental work, prototyping and building new robots from scratch. My software skills are limited to what get my robots to work, reading sensors, data visualization, and modeling through reduced order models and some NN.

I had my Google onsite Round 2 today. The problem was design-heavy with multiple methods and ended up being 80+ lines of code using object-oriented design. I’d consider it a fairly difficult question.
I managed to complete the implementation, although I got interrupted a couple of times by the interviewer while coding (he later apologized for it) but later ran out of time during drying run and couldn't able to find a bug.

I’m trying to set realistic expectations and assume this round will be a Lean Hire.

My interview feedback (based on my own assessment) would roughly be:
Phone Screen (DSA): Lean Hire
Googliness: Strong Hire
Onsite 1: Hire
Onsite 2: Lean Hire
Given this mix, what are the chances of still moving to team matching and eventually getting an HC (Hiring Committee) approval? I know nobody can predict the outcome, but I’m curious if anyone has been in a similar situation with a mix of Hire and Lean Hire ratings and still made it through.
I’ve intentionally kept my expectations very low to avoid overthinking, but I’d love to hear real experiences from people who’ve gone through Google’s interview process.