Week One at a Big Company: Finding Who Answers What

Your first week at a big company is not really about the work. It is about a quieter problem: you have questions, and you have no idea who holds the answers.

You start on a Monday. Your laptop works, your accounts mostly work, and you have a list of things to figure out by Friday. None of them are hard. The hard part is that you do not yet know a single name attached to any of them.

The org chart lies a little

Someone sends you the org chart on day one. It tells you who reports to whom. It does not tell you who actually knows how the billing system works, or who quietly owns the deploy process even though it is not in their title. At a big company those are almost never the same people. The chart shows the shape of the org. The answers live somewhere else.

The first real question

By Wednesday you hit a wall. You need to know why a setting is configured a certain way, and the doc that should explain it just says "see owner." There is no owner listed. You ask your manager, who is in back-to-back meetings. You post in the channel, and it scrolls past. You wait.

This is the thing nobody warns you about. The blocker is not the task. The blocker is finding the human who can unblock it, and then catching them at a moment they can respond.

How people actually find the answer person

Watch anyone who has been at a big company for a year, and you will see the same moves.

• They open the doc's history and see who wrote it.
• They look at who last changed the code or the config.
• They read a channel's pinned messages before asking.
• They ask one well-connected person "who owns this?" instead of asking the crowd "how does this work?"

None of this is taught. You learn it by getting stuck enough times that you build your own private map of who answers what.

Building your map on purpose

You can speed this up. Keep a simple running note during your first weeks. Every time you learn that a person owns a thing, write it down: the topic, the name, and how you know. It feels unnecessary on day three. By week three it is the most useful file you own, because the questions come back and the names fade.

Also notice the pattern of who gets pointed to. If three different people say "ask Alex about that," you have found a real owner, not a chart owner. Those are the names worth keeping.

Why it stays hard even after week one

Here is the uncomfortable part. The map you build is mostly in your head, and everyone else is building their own from scratch. When the one person who knows is off, or busy, or just moved teams, the knowledge does not wait for you. It sits inside a human who is not available, and you are back to asking the channel and hoping.

So the new-hire problem never fully ends. It just gets quieter. There is always a next thing you do not know, and always a person, somewhere, who does.

What would actually help

The fix is not a better org chart. It is making the answers reachable without needing the person to be free at the exact moment you are stuck. When someone writes down what they own and what they decided, at the end of a normal day, that knowledge stops living only in their head.

That is the idea behind StandIn. The people who know things write one short brief about their own work, and while they are away, it answers questions from what they actually wrote, with a source under each answer. For a new hire, that is the difference between waiting two days for a name and getting the answer, in that person's words, on your first try. When the answer is not in the record, it says so, so you know to keep looking instead of trusting a guess.