We've sat on the other side of the table at big tech companies. We've written the feedback, waited on the meetings, and watched candidates go quiet with worry while the process crawled along. The wait almost never feels as long from the inside as it does from your side. This guide explains what's actually going on after your interview and what you can do about it.

How long does it usually take to hear back?

It depends on the stage. After a phone screen, most big tech companies get back to you within a week. Sometimes it's a day or two. If the interviewer submits their notes quickly and the recruiter isn't swamped, you can hear back the same week.

After an onsite (or a virtual final loop), the wait is longer. One to three weeks is common. Some companies move faster than others:

• Amazon usually holds its debrief within a few days of the loop, so many candidates hear back in about a week. See our Amazon interview process guide.
• Microsoft decisions often come within five to ten business days. See our Microsoft interview process guide.
• Google and Meta can take much longer, because passing the interviews isn't the last step. A committee review and team matching both add time. See our Google and Meta guides.
• Nvidia and Apple are known for long silences after the final round. A few weeks with no news is normal there. See our Nvidia and Apple guides.

These are typical ranges, not promises. A holiday, a recruiter on vacation, or a busy hiring season can easily add a week.

Why haven't I heard anything after my onsite?

Silence feels like a bad sign, but it usually just means the process is slow. Here's what tends to be happening behind the scenes.

Your interviewers are still writing feedback. Each interviewer writes up what you did and gives a score. Engineers do this between their normal work, and some of them are slow. The recruiter often can't move until every write-up is in.

The decision meeting hasn't happened yet. Some companies review candidates in a weekly meeting. If you just missed this week's slot, you wait for next week's. At Google, a hiring committee reads your packet, and those committees run on their own schedule.

You're in team matching. At companies like Google and Meta, you can pass the interviews and still need a team to pick you before an offer exists. That can take weeks. We cover this in what is team matching.

The job itself is up in the air. Sometimes the team is waiting for budget approval, or the opening got frozen. That has nothing to do with how you did.

They're comparing candidates. If the team has one opening and is interviewing a few people, they may wait until everyone finishes before deciding. That's frustrating, but it's common.

What does "we're still gathering feedback" mean?

It usually means exactly what it says. At least one interviewer hasn't submitted notes yet, or the review meeting hasn't happened. It's a neutral phrase. Recruiters say it to people who get offers and to people who don't.

Here are a few other phrases and what they tend to mean:

• "Your packet is going to committee." Your interviews are done and written up. A group of people will now review them together. This is a normal step, not a warning.
• "We need a little more signal." The feedback was mixed, and they might ask you to do one more round. That's actually a decent sign. They wouldn't bother if they'd already decided no.
• "We'd like to schedule a call to go over feedback." This could go either way. Some recruiters deliver offers on a call, and some deliver rejections on a call. Don't try to read it.
• "We've decided to move forward with other candidates." That's a rejection. Ask if you can reapply later and when.

If your recruiter just stops replying, that's the hardest one. It often means they're waiting on someone else and have nothing new to tell you. It doesn't always mean you're out.

When should I follow up?

If the recruiter gave you a date, wait until that date passes, then give it one or two more business days. If they didn't give you a date, a good rule is to follow up about a week after your onsite. After that, checking in once a week is fine. More often than that won't speed anything up.

Keep it short and friendly. Your recruiter is probably handling dozens of candidates, so make it easy for them to reply. Here's an example:

Hi Priya, thanks again for setting up my interviews last Tuesday. I really enjoyed meeting the team. I wanted to check in and see if there's any update on next steps, or a rough timeline I should expect. Happy to send anything else that would help.

That's it. Don't ask how you did in each round, and don't apologize for following up. If it's been two weeks since your onsite and your recruiter hasn't replied at all, try a second recruiter or coordinator you talked to. If you got the interview through a referral, your referrer can sometimes check the status internally. Our guide on how to connect to recruiters covers finding the right people.

Can a competing offer speed things up?

Yes, and it's the most effective thing you can do. Companies move much faster when they know they might lose you. If you get an offer from another company, tell your recruiter right away. Include the deadline you're working with.

You could write something like this: "I wanted to let you know I received an offer from another company, and they've asked for an answer by Friday the 10th. I'm still very interested in this role. Is there any way to speed up the decision on your end?"

Only say this if it's true. Recruiters sometimes ask for details, and a made-up offer can blow up on you. Even a late-stage interview at another company is worth mentioning, since it tells them you're in demand.

What should I do while I wait?

Keep your other interviews going. It's tempting to pause everything once you finish an onsite you liked, but that leaves you with nothing if the answer is no. And if the answer is yes, another offer in hand gives you room to negotiate.

It also helps to write down what you remember about each round while it's fresh. If you get rejected, you'll have notes on what to practice. If you pass, you'll have questions ready for team match calls. And if you're still unsure how interviewers score your rounds, read what interviewers look for in coding interviews.