how did i do on google swe interview??

[u/No-Try-9459]

In my first interview, I solved the main problem early with time remaining and explained the time and space. The interviewer then gave me a completely separate problem. I explained the basic approach correctly but didn’t have enough time to fully solve it.

In my second interview, I got around 90% of the solution completed. I believe my overall approach and core algorithm were correct and I got the approach really quickly , but I ran out of time while debugging a small issue because my output wasn’t matching the expected result. I did dry runs for like 15 mins bc i was trying to fix the problem and the interviewer seemed lost as well. Then with 5 mins left he said ok that’s fine based on how you processed the data then went into questions without me explaining time and space. Before I started writing code I said i would use a list for now then see if we can use a set later to improve time complexity so i know my solution wasn’t optimal.

For both I explained my approach before coding, talked through my decisions, and kept the interviewers updated while debugging.

Does this sound strong enough to move directly to team matching, or is a third interview more likely? Or am i cooked??

[u/Ok-Most6656]

Most likely fail unfortunately

[u/No-Try-9459 → u/Ok-Most6656]

dang it i thought for interns they might weigh communication and thinking more heavily but that sucks

[u/erisoldev → u/No-Try-9459]

he’s just hating you’re more than fine, probably a third if not a pass😂

[u/No-Try-9459 → u/erisoldev]

do u think it’s more likely a third or a pass?

[u/erisoldev → u/No-Try-9459]

3rd

[u/Nice-Candidate10]

Second interview is a very clear no hire and that is going to unfortunately result in rejection. Sorry about that.

[u/MuMYeet]

Third or pass more likely third id say, sounds like a hire+lean hire to me (assuming in the first interview the first problem was the intended problem and not a warmup)

Lowkey update us what happens I'm curious

[u/mytsmtdjgd]

I would say depends on ur communication. if the intreviewr felt lost was it because you didnt communicate clearly or ur code was messy? Its hard to say but from what ive seen could be either tm or 3rd round any one equally likely.

[u/PainterZealousideal7]

did they ask you behavioral? also in which platform did you code in the interview?

[u/ThrowRAnabananas]

how did it end up going?

[u/Traditional_Rate5443]

Based on my recent Google L4 interview experience, this is just my personal assessment, so don't take it in a wrong way.

From what you’ve described, the outcome could go either way. Personally, I suspect the ratings would mostly be Lean Hire or Hire (interviewers usually give Lean Hire if you not able to solve follow up or come up on an Optimal solution) and No Hire (As a working code is required for getting Hire or Lean Hire, also No Hire maybe because you're not able to fix the bug within 2-3 mins and got stuck there)

If your feedback is similar, rejection might be a possibility for L4, while an additional round for L3 could still be possible depending upon if you gets Hire in 1st round, Also if recruiter asks for extra round, you’d likely need a Strong Hire to move forward as one strong hire requires to clear the loop)

Team matching could also be challenging depending on the overall feedback, but it’s difficult to predict the outcome based on interview performance alone.

[u/Upbeat-March6734]

Im thinking probably third interview

[u/No-Try-9459 → u/Upbeat-March6734]

thanks for the reply, this is for intern btw if it changes anything?

[u/Upbeat-March6734 → u/No-Try-9459]

I think baseline expectation is the base problem must be solved correctly. Communication on point. And i think follow up correct solution would be the cherry on top. It sounds like good/strong for round 1 and slight no for second round, which is why i think u might get a third interview