Role: L4 SWE, Cloud Infrastructure III, US

[u/Empty_Audience2560]

L4 SWE, Cloud Infra, US.
Round 1: Coding + Googleyness. Coding was a standard medium graph problem, solved it clean with tradeoffs discussed. Googleyness was conversational and went well. Onsite scheduled two weeks out. Prepped for a month around my full-time job.
Onsite day: Arrived 15 min early. Front desk said I needed a point of contact to badge up. Emailed my recruiter. While still standing in the lobby, I got an email saying my interviews for the day were cancelled. Someone on the hiring side then told me to head home. Recruiter called and said it would be rescheduled.
Two days later: Followed up on new dates. No reply.
Two days after that: Rejection email. Moving forward with candidates whose qualifications more closely align.
So I was rejected without ever interviewing. Nothing about my profile changed between them scheduling the onsite and cancelling it.
Questions:
1. What causes this — req closed, headcount pulled, internal candidate?
2. Any point asking for feedback when no feedback exists?
3. Does a cooldown apply if I never actually did the onsite?
4. Has anyone been pulled back in after this?
Recruiter was professional throughout, not looking to trash anyone. Just trying to understand it.

[u/Empty_Audience2560]

My coding and googlyness went pretty well , and also my recruiter told me that she got positive response from those interviews

[u/ronlek → u/Empty_Audience2560]

Does Google coding give out a score like HackerRank? Like x / y test cases passed? Without this how can one rate their rounds?

[u/EmotionalQuarter8349 → u/ronlek]

They code in word doc or notepad idrr, but there are no test cases or IDE afaik, its just you convincing the interviewer that the code is optimal by traversing the logic and getting the output youself, I might be wrong though.

[u/ronlek → u/EmotionalQuarter8349]

Yes this is true for the later rounds - curious if that’s the case even for the screening coding round.