0

Tips for Onboarding

Profile picture
Mid-Level Software Engineer at private4 months ago

I'm about to join a FAANG level company soon, what are some of the best practices to follow and how to create a 30-60-90 day plan for onboarding?

66
3

Discussion

(3 comments)
  • 0
    Profile picture
    Tech Lead @ Robinhood, Meta, Course Hero
    4 months ago

    Congrats on getting a FAANG offer! I highly recommend this thread: "What would you do in the first 30 days after joining a FAANG like company?

    Are you joining as a mid-level engineer or senior engineer? Onboarding will vary heavily depending on that as a senior engineer will need to build up a lot of social capital while a mid-level engineer is primarily focused on solidifying raw technical proficiency (a senior engineer also needs to do this, but they can't spend 100% of time on it as they need the relationships).

    If you can share the FAANG company (FAANG companies are huge, so sharing this should be fine as there's tons of engineers getting in), that would be helpful as well.

    • 0
      Profile picture
      Mid-Level Software Engineer [OP]
      private
      4 months ago

      Hi Alex, thanks for responding, so I'll be joining as an L4, but was near to L5.

      Can you help me with how can an ambivert person like me can improve on their social capital (Might be an awkward question 😛)

    • 0
      Profile picture
      Tech Lead @ Robinhood, Meta, Course Hero
      4 months ago

      As an L4, the main avenue towards building trust is making sure that you ask really high-quality questions and get a ton out of those interactions end-to-end. Watch this course: Ask Great Questions That Get Great Answers Quickly

      On top of that, there's the very obvious foundational component of writing good code. For a new L4, I would expect their code quality to be fairly high, especially at a FAANG company: Level Up Your Code Quality As A Software Engineer

      If I were to lay it out quantitatively:

      • Decent trust (baseline): Write great code and have healthy interactions in code review discussions
      • Good trust: On top of the prior item, ask really good questions and make that experience joyful for folks who help you