Google Interview for Embedded Software Engineer

I recently interviewed for an L5 Embedded Software Engineer role at G. Seeking guidance on my chances from Googlers based on my own assessment of my performance: Interview 1 (Googleyness) - 7.5/10. Answered most questions well as they were relatable, with interviewer showing positive body language and gestures. I think I could have answered one question related to diversity better. Interview 2 (Coding) - 8.5/10. Performed well with +ve feedback from interviewer. He said "hoping to see you around here" - guess that's a positive sign. Interview 3 (Coding) - 7/10. Got the solution but the interviewer provided many (unsolicited) hints which were just obvious mistakes that I could have fixed myself when I walked through the code after implementation. Read on blind that taking hints doesn't look good, so not really sure if those unsolicited hints count as a bad thing. Interview 4 (Embedded Domain) - 5/10. Interviewer asked 2 questions. The first one was completely outside my domain and I think I may have bombed it. Interviewer asked me to implement something based on what I think it would be like, when I mentioned to him that I have no experience in that area, and I just wrote some random API's with s#it load of assumptions. The second question was something that I knew and I performed well. Interviewer didn't provide any feedback/hint throughout both questions and appeared to be disinterested/distracted. Not sure what to make of it. Interview 5 (System Design) - 9 or 10/10. Honestly thought I was going to bomb this, but performed pretty well. Interviewer said the design was thorough and appreciated some parts of it as that was exactly what they expected. What are my chances of making it based on above (as objective as possible) assessment? #tech #Google #Embedded #Qualcomm #Apple #L5 EDIT: TC: 230K, 7 YOE EDIT 2: Recruiter mentioned the feedback has been positive, moved to team matching phase. For Systems Design, I just searched for 'Embedded Systems Design Interview' on YouTube and used the approaches in the first few videos that turned up. I also watched some Software system design videos and tried to apply relevant principles like scalability, fault tolerance, design tradeoffs and alternatives etc. to my approach.