Google phone interview didn't get the optimal solution

Atlassian / Eng
madakastev

Atlassian Eng

PRE
Rakuten
madakastevmore
Jan 22 4 Comments

#google #interview #phone-interview
I had a phone interview with google yesterday but didn't arrive at the optimal solution.

I had two questions, the first was too easy and I don't remember what it was.
The second one was finding weighted intervals intersections while calculating the average weight in those intersections which is thweight of all overlapping intersections.
Got an n2 solution that could've been easily optimised to nlogn but couldn't get to the nlogn solution in time. The interviewer mentioned that I was definitely on the right track and that I would ge the solution if I had 30 more minutes, which I actually did.
is that a flop? what could I have done better.

Location is for Sydney BTW

YoE: 8

comments

Want to comment? LOG IN or SIGN UP
TOP 4 Comments
  • Google / Eng kool_aider
    It depends on a few things. (1) What level are you interviewing for? (2) How close were you to the optimal solution? (3) How is the overall quality of your code?

    In any case, it sounds to me that your interview rating would be either Leaning Hire or Hire. Which means you at least did ok.
    Jan 22 3
    • Atlassian / Eng
      madakastev

      Atlassian Eng

      PRE
      Rakuten
      madakastevmore
      OP
      2. I was quite close that I got the answer 10 minutes after the interview ended
      3. The code quality was quite good I believe, I mean I do pay good attention to my code quality
      Jan 22
    • Google / Eng kool_aider
      It sounds to me like most likely this is for L4 and you got a Hire. If you can get L5, that would be ideal.
      Jan 23

Salary
Comparison

    Real time salary information from verified employees