0

How long does it take to ramp up?

Profile picture
Junior Software Engineer at Taro Communitya month ago

I just started a new SWE role at an AI startup and this is my third day at work. This is my first time changing jobs and I’m on my second ticket so far. I followed the tips that Rahul gave in his onboarding course to quickly get to action and try to make impact. The tickets that I have been given so far are mainly small tasks but I’m taking extremely long to just do some basic things like filtering etc because the codebase is massive and I m unfamiliar with it, and I often need to ask my buddy or someone else for some help. Is this ok or am I underperforming? How long should I take to be properly familiar? I am a full stack SWE so some changes do require me to look at both the front and backend.

hope to get some advice on what’s considered normal so I know where I am at! I have 2+ YOE.

54
6

Discussion

(6 comments)
  • 0
    Profile picture
    Tech Lead @ Robinhood, Meta, Course Hero
    a month ago

    Do your tasks have due dates? If not, ask your manager to put due dates on them.

    ...and I often need to ask my buddy or someone else for some help. Is this ok or am I underperforming?

    If your team isn't super mean, this is perfectly normal. It's literally just your 3rd day. Your goal though is to make sure that your need for help drastically drops over time due to following the advice here: https://www.jointaro.com/course/ask-great-questions-that-get-great-answers-quickly/learn-to-fish/

    Needing help isn't inherently a problem. Needing the same type of help in the same amount over and over again is.

    hope to get some advice on what’s considered normal so I know where I am at! I have 2+ YOE.

    It really depends on the startup. If it's a tiny 5-engineer company, the expectation will be much higher for you to move fast and become independent. If it's a massive unicorn with 500+ engineers, the expectation will be much lower as companies at that point are more like Big Tech than tiny startups.

    If I had to throw a number on it, I would say you should be operating at 90% productivity compared to a similar engineer of your level after 2-3 months. But again, I could be completely wrong based on what kind of startup you're working for.

    • 0
      Profile picture
      Junior Software Engineer
      Taro Community
      a month ago

      it’s about 10 ish lean team, of which about 6 are engineers. My tasks have vague story points, but also these tickets can be a little vague as the intended user outcome is usually clearly stated, but the implementation details are for me to figure out. The vagueness is fine for me, just that I am trying to gauge how fast I need to ramp up to leave a good impression and if I should be concerned that I m not pulling my weight.

      thanks for the course on asking good questions, I’ll defo have a look!

    • 0
      Profile picture
      Tech Lead @ Robinhood, Meta, Course Hero
      a month ago

      Your team is quite small - I'm sure expectations are high then (if they aren't, the company won't survive).

      Definitely talk to your manager to take expectations as clear as possible. When in doubt about your own performance, having an honest conversation with your manager is usually the right call.

    • 0
      Profile picture
      Junior Software Engineer
      Taro Community
      a month ago

      thanks for the advice Alex and yep I'll have a 1:1 soon. Yeah I think I can feel the pressure as we recently onboarded a few enterprise clients and there's urgency in getting certain features polished up

    • 0
      Profile picture
      AI/ML Eng @ Series C startup
      a month ago

      Engineering team was a similar size at my last job, seed stage. The general expectation was 3-4 months.

    • 0
      Profile picture
      Junior Software Engineer
      Taro Community
      a month ago

      Thanks Elliot!