Questions to Ask in Your First Week
The first week of a new job is loud with information and quiet on the things that actually matter: how decisions really get made, what good looks like here, and who you need in your corner. Most people spend that week nodding along and hoping it clicks later. This guide gives you the specific questions to ask in your first week of a new job so you leave day five with a real map instead of a vague feeling.
What’s inside
Why the questions you ask now compound later
Questions to ask your new manager
Questions that reveal what “good” looks like
Questions to ask your teammates
Questions about how decisions actually get made
Questions about tools, process, and the boring stuff
Questions you should ask yourself
How to ask without looking clueless
How Blomma helps you start strong
Why the questions you ask now compound later
There is a short window at the start of a new job where curiosity is expected, even celebrated. Nobody blinks when the new person asks how something works. That window closes faster than you think — usually within a few weeks, once people assume you have your footing. So the goal of week one is not to look competent. It is to get oriented fast, while the cost of asking is near zero. Every good question now saves you a month of guessing later. The people who onboard well are not the ones who already knew things; they are the ones who asked better first-week questions and wrote the answers down. Treat this like starting anything: the hardest part is momentum, and questions are how you build it. You are not being needy. You are doing the actual work of the first week, which is building an accurate model of how this place operates before you commit to how you will operate in it.
Questions to ask your new manager
Your manager sets the terms of your success more than anyone else, so their answers are the highest-value ones you will collect. Book time early and come with real questions, not filler. Ask: What does a great first 90 days look like to you? What would make you say this hire was clearly a good decision? How do you like to receive updates — async, in our 1:1, or only when something’s on fire? What’s the thing you’re hoping I take off your plate first? Is there any context about the team or the last person in this role I should know? That last one matters more than it seems. You are often stepping into a history you can’t see. Understanding what your manager values, and how they judge progress, is the same signal executives use when they make promotion decisions later — clarity on expectations now is what makes advocacy possible down the line. Write down their answers verbatim where you can. You will reread them in month two.
Questions that reveal what “good” looks like
Every team has an unwritten standard for quality, speed, and polish — and it rarely matches what the job description implied. New people get tripped up not because they are incapable, but because they are optimizing for the wrong bar. So ask directly: Can you show me an example of work from this team that everyone considered excellent? What made it good? What’s something that looked fine but missed the mark, and why? How fast is fast enough around here — is a same-day rough draft better than a polished one next week? These first week questions surface the real rubric. A team that prizes speed and iteration will be frustrated by someone perfecting quietly; a team that prizes precision will be alarmed by someone shipping fast and loose. Neither is written down anywhere. Ask to see two or three concrete artifacts — a doc, a deck, a pull request, a campaign — that the team is proud of. Examples teach the standard faster than any adjective someone can give you. Then you can calibrate your own output against something real instead of guessing.
Questions to ask your teammates
Your peers know things your manager either doesn’t see or won’t say. Grab short, informal chats in your first week — coffee, a walk, a 20-minute intro call — and ask questions that invite honesty. Try: What do you wish someone had told you when you started? What’s something that’s harder here than it looks from the outside? Who do people go to when they’re stuck — and it’s not always the person on the org chart? What’s a mistake new people tend to make? How do you like to be worked with? These onboarding questions do two jobs at once. They give you the informal map — the real influencers, the landmines, the shortcuts — and they start relationships on a note of genuine interest rather than transaction. People remember the new hire who asked what they wished they’d known and then actually listened. Keep a running list of names and what each person owns or knows. In a few weeks, when you need something, you’ll know exactly whose door to knock on instead of broadcasting into a channel and hoping.
Questions about how decisions actually get made
Every organization has an official decision process and a real one. The official one is in the wiki. The real one lives in hallway conversations, a particular Slack channel, or one person’s inbox. Confusing the two is how good ideas quietly die. Ask: How do decisions usually get made here — who needs to be in the room? When something needs sign-off, what’s the actual path? Where do important conversations happen — in meetings, in docs, or in DMs? How much autonomy do I have on things in my lane versus what needs a check-in first? That autonomy question is one of the most useful first-week questions you can ask, because it tells you where you can move without permission and where you can’t. Getting it wrong in either direction — asking permission for everything, or charging ahead on something that needed buy-in — is one of the fastest ways to erode trust early. Understanding the informal wiring is also how you learn to read the culture of a place, which shapes almost everything else about how you’ll operate here.
Questions about tools, process, and the boring stuff
The unglamorous questions save you the most time. Nobody feels smart asking where the shared drive is, but a week of not knowing is a week of quiet friction. Ask on day one or two: What tools does the team live in day to day? Where does documentation actually live — and is it trusted or out of date? What meetings am I expected to be in, and which are optional? What’s the rhythm of the week — standups, planning, demos? How do people handle time off, focus time, and after-hours messages? Batch these so you are not pinging people constantly. A single message like, “I’m getting set up — mind if I ask five quick logistics questions?” is far better received than five separate interruptions across the day. Also ask about the norms nobody documents: Is it normal to block focus time? Do people actually take lunch? Is a fast reply expected or is async fine? Getting the rhythm right early means you spend your energy on the work, not on decoding basic mechanics for a month.
Questions you should ask yourself
Not every first-week question is for other people. Some of the most important ones are quiet and internal, and they are easy to skip in the rush to prove yourself. Ask yourself at the end of each day: What surprised me today, and what does that tell me about this place? Where did I feel energy, and where did I feel drag? What am I assuming that I haven’t actually checked? Who did I connect with, and who do I still need to? A few minutes of reflection turns a blur of a week into actual learning. The point of a new job is not just to fit in — it is to grow, and there is genuinely nothing cooler than learning in a stretch of your career where everything is new and you’re allowed to be a beginner. Keep a simple first-week doc: what you learned, who you met, what still confuses you. Revisit it at 30 and 90 days. You’ll be surprised how much you understood early and how much you’d have forgotten without writing it down.
How to ask without looking clueless
The fear underneath most unasked questions is looking like you don’t belong. But how you ask matters more than whether you ask, and a few habits make questions land as sharp rather than lost. Show your thinking first: “My read is that X — is that right, or am I missing something?” beats a blank “How does this work?” It signals you’re engaged, not passive. Batch related questions so you’re respectful of people’s time. Write down answers the first time so you never ask the same thing twice — asking twice is what actually erodes confidence, not asking once. And match the question to the person. Strategy and expectations go to your manager; the real, informal map goes to peers; logistics go to whoever’s fastest to answer. Spreading questions across the right people keeps any one person from feeling like your help desk. Done this way, questions don’t make you look junior. They make you look like someone who moves deliberately and learns fast — exactly the reputation you want in week one.
How Blomma helps you start strong
The hard part of a new job isn’t the questions — it’s asking them in the moment, out loud, when you’re worried about how you’ll come across. That’s where having a coach in your corner changes things. Blomma is an always-on AI career coach you can talk to before your first 1:1, after a confusing meeting, or at 10pm when you’re second-guessing whether a question is dumb (it isn’t). You can use Blomma to draft the exact questions to bring to your manager, pressure-test your read on the team’s culture, and turn a blurry first week into a clear 30-60-90 plan. It remembers your context, so the advice compounds instead of resetting every time. See how Blomma works for individuals if you want a sense of the day-to-day. Starting a new role is one of the rare moments where a little structure pays off for years. You don’t have to figure out the questions alone. Start your new role with Blomma free →
Related reading
Your career isn’t stuck
There is nothing cooler than learning
How to start anything