10 Questions to Ask About Company Culture in an Interview

Ten questions that pull an interviewer off the script and into how the team actually runs, plus the ones that land badly before you have an offer.

By Olu Adeyemi · Published · Updated · 9 min read

Featured image for "10 Questions to Ask About Company Culture in an Interview"

By the end of this guide you will have ten culture questions ready to go, know which to ask to a hiring manager versus a recruiter or a future teammate, and be able to read the answers for what they tell you about how the place really works.

Culture is not the words on a careers page. It shows up in how decisions get made, how feedback travels, how people are promoted and what happens on a bad week. These questions are built to surface that, and the last section covers the questions that cost you ground if you ask them too early.

How to use these questions

Bring more questions than you will use. Eight to ten written down means you still have three good ones left after the interviewer answers half of them unprompted. Plan to actually ask three to five — past that, you are interviewing them rather than having a conversation.

Match the question to the person. A recruiter can tell you about process, timelines and how the company talks about itself. A hiring manager can tell you about priorities, decisions and feedback. A future peer will tell you the truth about a bad week. Asking a peer about promotion criteria usually gets a shrug.

Take notes. Write the answer down in a few words, not verbatim. It signals you are weighing the job, it stops you asking the same thing twice across a panel, and it gives you something concrete to compare if two offers land in the same week.

About the role

Start here. Role questions feel natural to an interviewer, and the answers tell you more about culture than any question with the word "culture" in it.

1. What does a normal week in this role look like, and what does a bad week look like? The normal week tells you how the job is really spent, which is often different from the posting. The bad week is the useful half: you learn what goes wrong here, how often, and whether the interviewer can describe a hard period without getting defensive. Vague answers to the second half usually mean the role is still being figured out.

2. How will you know in six months that hiring for this role worked? This forces a specific answer about priorities and who is judging them. A manager who can name two or three concrete outcomes has thought about the role. One who says "we'll see how you settle in" may be hiring for a gap they have not defined, which tends to mean shifting expectations once you start.

About the team and manager

These three get at the daily experience of working here, which is mostly the experience of working with one manager and five or six colleagues.

3. How does the team handle it when two people disagree about the right approach? You find out whether decisions are made by discussion, by seniority, by data, or by whoever pushes hardest. Listen for a real example. A manager who describes a specific disagreement and how it ended is telling you something; one who says "we're all very collaborative here" is not.

4. How often do you meet one to one with the people reporting to you, and what usually happens in those meetings? The frequency tells you how much access you will have. The content tells you more — status updates only, or career conversations, blockers and feedback. If one to ones are frequently cancelled, a candid manager will say so, and that itself is worth knowing before you accept.

5. How does feedback usually reach people here — in the moment, in one to ones, or at review time? This separates places where problems are raised early from places where they are stored up for an annual review. Ask it of a peer as well as a manager; the two answers do not always match, and the gap between them is the real answer.

About growth and training

Development varies enormously by employer size and sector. A large company may have formal frameworks; a small one may have none and still promote people quickly. Both can be fine — you just need to know which you are joining.

6. What does someone in this role need to show to be considered for the next step, and who makes that call? You learn whether progression is defined or discretionary, and how many people have to agree. If the answer is a named framework or a short list of criteria, you can plan against it. If it is "we recognise good work when we see it," progression here depends heavily on your relationship with your manager.

7. What support do new people get in the first couple of months, and who runs it? Onboarding quality is a reliable signal of how organised a team is. Listen for whether someone owns it by name, whether there is anything written down, and whether recent hires were paired with a colleague. "You'll pick it up as you go" means you will be learning in public from week one.

About the company

Two questions here is plenty. You are testing whether the interviewer's picture of the company is current and honest, not quizzing them on strategy.

8. What has changed about how the company works in the past year? Reorganisations, leadership turnover, a shift in funding or ownership, a return-to-office change — these shape day-to-day life more than stated values do. Someone who answers with specifics is giving you a genuine picture. Someone who says nothing has changed either has not been there long or is choosing not to say.

9. What is expected around working hours and availability, and what counts as exceptional? Every workplace has an unwritten rule about evenings, weekends and messages after hours, and it varies by employer, team and state. Asking what counts as exceptional, rather than asking about hours directly, invites an honest answer about busy periods, on-call rotations and deadline crunches instead of a policy recital.

About next steps

Close with one question that does two jobs: it gets you the timeline and gives you a last chance to fix a doubt before they decide.

10. What are the next steps and the rough timeline, and is there anything in my background you would like me to clarify before you decide? The timeline helps you manage other conversations and tells you how fast this organisation moves. The second half is the valuable part — it invites the interviewer to name a concern while you are still in the room, and it is often the only chance you get to address a misunderstanding about your experience or a gap in your record.

Questions to avoid

None of these are forbidden. They are either too vague to produce a useful answer, or better timed for a later stage. Here is what to ask instead.

Don't ask this nowAsk this instead, or wait
"What's the culture like here?"Too broad — you will get the careers-page answer. Try: "What surprised you about working here in your first month?" A specific memory is harder to polish.
"How much vacation do I get?"Nothing wrong with the question, wrong moment. Hold entitlements for the offer stage. If you want the cultural version now, ask: "How does the team cover for each other when someone is off?"
"Can I work from home whenever I want?"Sounds like you are negotiating before you have an offer. Try: "What does the team's working pattern look like in a typical week?" Then negotiate specifics once they want you.
"Why did the last person leave?"Puts the interviewer in an awkward spot and may be confidential. Try: "Is this a new role or a replacement, and what has the team learned since it was last filled?"
"How did I do?" or "Do I have the job?"Asks for a decision the interviewer usually cannot make alone. Try: "Is there anything about my experience you'd like me to expand on?" Same goal, no pressure.
"What's going on with the leadership changes I read about?"Framed as gossip, it reads as a test. Try: "What's the hardest part of working here right now?" It gets you the honest version without asking anyone to comment on their bosses.

Frequently asked questions

How many questions should I actually ask?

Three to five in a standard hour-long interview, fewer if the conversation has already run long. Prepare eight to ten so you are never caught out, and treat the list as a menu rather than a script. If you are meeting several people in one day, spread them out — ask the manager about priorities and decisions, ask peers about the day to day, ask the recruiter about process and timing. Repeating the same question to everyone is a legitimate tactic for checking whether the answers line up, but only do it with one or two questions, and say that is what you are doing.

What if they answered all my questions during the interview?

Say so, and then go one level deeper on something they said. "You mentioned earlier that the team reorganised in the spring — how has that changed the way work gets assigned?" shows you were listening and keeps the conversation going. If you genuinely have nothing left, do not invent a question for the sake of it. Name the points that stuck with you, confirm the next steps and the timeline, and close by asking whether there is anything they would like you to clarify. That lands better than a filler question everyone recognises as filler.

When should I ask about pay?

Pay is a fair question, but the first screening call with a recruiter is usually the right place for it, not a culture conversation with the hiring manager. Ask what range the role is budgeted at and how pay is structured — base salary, hourly, commission, bonus, shift differentials or equity all behave differently. Several states and cities require ranges in job postings, so it may already be in the ad. Before you talk numbers, check current rates for the role in your area using public labor statistics, posted ranges for similar jobs and professional association surveys, so you are working from evidence rather than a guess.

Is it fine to read my questions off a notepad?

Yes, and in most interviews it helps you. Bringing written questions reads as preparation, not as weakness, and it stops you forgetting the one that mattered most. Keep them short enough to glance at — a few words each, not full sentences you read aloud. Jot down brief notes on the answers too. On a video interview, say what you are doing the first time you look away or start typing, so it does not look like you are distracted.

More in Interview Preparation

Featured image for "How to Answer "Where Do You See Yourself in Five Years?" (+ Example Answers)"
Interviews

How to Answer "Where Do You See Yourself in Five Years?" (+ Example Answers)

By the end of this guide you'll have a 60 to 90 second answer to "Where do you see yourself in five years?" that sounds honest, fits the job you're actually interviewing for, and doesn't box you into a title you may not want. The trick is to talk about scope, skills and contribution rather than a rung on a ladder.

Priya Nathwani · 13 min read

Featured image for "How to Answer "Why Do You Want to Work Here?" (+ Example Answers)"
Interviews

How to Answer "Why Do You Want to Work Here?" (+ Example Answers)

By the end of this guide you'll be able to build an answer to "Why do you want to work here?" that names a real detail about the employer, connects it to work you have actually done, and lands in under 90 seconds. The method is the same whether you're a new graduate, stepping up, switching industries or coming back after time out — only the evidence changes.

Desmond Okafor · 11 min read

Featured image for "In-Person Interview Checklist: What to Bring and Do Before You Go"
Interviews

In-Person Interview Checklist: What to Bring and Do Before You Go

An in-person interview is mostly won in the preparation you do before you leave the house: the route you have timed, the documents in your bag, and the three or four stories you can tell without hunting for them. This guide gives you a checklist for the week before, the morning of, the interview itself, and the hours afterwards.

Ananya Rao · 11 min read

Featured image for "The SOAR Method: How to Answer Behavioral Questions (+ Examples)"
Interviews

The SOAR Method: How to Answer Behavioral Questions (+ Examples)

By the end of this guide you will be able to spot a behavioral question from its first five words, build a short story that answers it, and tell that story in about ninety seconds without rambling. SOAR stands for Situation, Obstacle, Action, Result (University of Oregon, School of Design Career Advising, undated).

Junie Castellane · 18 min read