Starting at Google next week, tips for me

Dec 29, 2019 23 Comments

Joining Google as an L3 next week. Any helpful tips for me to succeed.
I have 5 yoe and got downleveled. I am joining a team where all tech stack including the programming language will be new to me. This is not too important though as I am pretty sure I can pick things up quick.
I got downleveled by HC, my goal is to succeed in this role and get to L4 ASAP.
Any tips for me to succeed in this role. I will be in Android org, productivity engineering.
Thanks in advance.
TC 205

comments

Want to comment? LOG IN or SIGN UP
TOP 23 Comments
  • Sorry I don’t have tips but can you help me with my interview prep?

    I have onsite in a month and can use help with the following qs
    1. How many leetcode had you solved n breakdown?
    2. Can you share your interview experience?
    3. Why do you think you got downleveled?
    4. Can you dm me? Im out of credits :(

    Thanks!
    Dec 29, 2019 4
  • Google
    no_you

    Go to company page Google

    no_you
    First tip: don't say you got downleveled. You got an offer you performed for and accepted. Make your peace with that and you will feel less unhappy.
    Dec 30, 2019 1
    • Google / Eng
      UwUwUwU

      Go to company page Google Eng

      PRE
      Amazon
      UwUwUwU
      If he's coming from another company with comparable levels, it's totally possible he was objectively down-leveled.

      That said, I've never heard of OP's company.
      Dec 30, 2019
  • Google / Eng
    FhAJ18

    Go to company page Google Eng

    FhAJ18
    The main difference between a L3 and L4 at Google is autonomy.

    Give yourself some time to ramp up - Google is a Tech Island meaning that it uses very little tooling, libraries, or frameworks that are generally available to the rest of the industry. You will need time to learn and your manager knows this - so focus intensely initially on learning and small initial tasks. Even basic things like how to commit code will be new.

    After that focus on being autonomous. You should be able to take larger, less well defined pieces of work, flesh it out, and complete it without overly relying on others. Senior devs are expected to be able to carry fairly abstract tasks to the finish line, resolving ambiguities and holes as needed. You should also be in the habit of proactively seeking work within the mission of your team - if you see something that should be a project but isn't yet, pitch it. Creating one's own work is also part of the expectation for senior engineers.
    Dec 30, 2019 1
  • This comment was deleted by original commenter.

    • OP
      I actually wanted to get into something new as I felt I was stagnating at my current role/skills. The hiring manager was open to the idea as well. I don't think they look for too much relevant exp for L3s anyway. And I also didn't wanted to gamble and wait forever to get that "ideal" match after hearing stories from some who couldn't get matched.
      Dec 30, 2019
  • Google
    bighead2

    Go to company page Google

    bighead2
    Stop talking about being "downlevelled" because Google sees you as an L3. Embrace it, and use the time with fewer expectations to explore everything.
    Dec 30, 2019 0