Taro Logo
1

How can I reduce the time spent waiting on answers from senior engineers during ramp-up?

Profile picture
Mid-Level Software Engineer [E4] at Meta2 days ago

Hi guys, I'm a new hire at Meta, and something that I've consistently struggled with across my previous roles is waiting hours, sometimes even days, for answers to questions I send to senior engineers. They’re usually busy or in back-to-back meetings, and while they are all nice and always encourage questions, responses tend to be delayed. This has been especially difficult during onboarding, when so much of the necessary context isn’t documented.

Even more frustrating is that, after waiting, the answers I get are often vague, partial, or not actionable. I try to be thoughtful with how I ask. I explore independently first, I check internal wikis and documentation, and I even use ChatGPT to help refine my questions. But I still frequently end up blocked—waiting on input, and then not getting the clarity I was hoping for.

One of the biggest challenges is that I often don’t even know what to search for. As someone new to the codebase and terminology, I’m unsure which direction to explore. Documentation exists, but I don’t always know how to utilize it effectively. I’m not sure what’s accurate, what’s outdated, or whether I’m even looking in the right place. At the same time, I’ve been told both “just read the docs” and “the docs are probably outdated,” which only adds to the confusion.

The frustrating part is that I don’t want to be blocked or slow things down, but sometimes I feel stuck waiting for clarification. Even when I do my best to explore on my own first, I eventually hit a wall where I need input from someone more experienced to move forward confidently.

I’m a mid-level backend engineer, and this is my first role at a FAANG company (Meta). I want to be more effective, but it’s been hard in an environment that seems heavily reliant on tribal knowledge and hallway context.

Has anyone else dealt with this kind of situation? Are there strategies that have helped you reduce turnaround time on questions, or work more effectively while waiting? I’d really appreciate any tips or insights.

18
1

Discussion

(1 comment)
  • 1
    Profile picture
    Senior Software Engineer at Walmart
    2 days ago

    I faced this problem quite a bit while ramping up. For one, I think all of tech needs to have better documentation and less dependency on other engineers. In a well-oiled machine, chances are that the documentation/training manuals need to be as well-equipped as an engineer. Having said that, if you really need someone to respond to you, there are a couple of ways

    1. Make sure there is something in it for them. It can be you taking time out to review their code or maybe helping them solve a critical bug. Make sure to be sincere in your request and be acknowledge that the other person took time out to help you.
    2. Make sure people around you are aware you are asking for 'specific' help for a 'specific' problem. This serves two purposes - it adds accountability when the other person responds, and, it lends to their reputation (aka, being a helpful engineer). Also, be super specific about your question. You can create a document just to make sure they understand your question and have seen your effort in solving it independently.