Questions to Ask Before Accepting a Job
Twenty questions to ask a hiring manager, a recruiter and your would-be colleagues once an offer is on the table, covering the first three months, how decisions get made, how the team is doing, and who left recently. For anyone deciding whether to say yes to the work itself rather than to the paperwork.
The questions
Open any question for the note
What would I be doing in my first two weeks?
Why ask it
A manager who has thought about you can describe the first fortnight in concrete terms: a system to learn, a person to shadow, a small piece of work to ship. A hazy answer usually means nobody has prepared for your arrival, and the first month will be spent looking for something to do.
Is this a new role, and if not, where did the last person go?
Why ask it
Backfills and new roles fail in different ways. If the previous holder was promoted, ask what they were good at. If they left the company, ask how long they lasted, because a role that has churned twice in two years is a problem with the job rather than the people.
Who would I report to, and how long have they been in that seat?
Why ask it
A manager appointed six weeks ago is still figuring out their own job, which changes how much support you can expect. Be alert if you have not met this person during the process, since interviewing without your future manager in the room is a sign of a disorganised or reorganising team.
How often would my manager and I meet, and what would those meetings cover?
Why ask it
The useful details are frequency, whether the meeting gets cancelled when things get busy, and whether it covers your work or your development. 'My door is always open' is the answer of someone who does not hold regular one-to-ones, which matters most in your first six months.
What would you want me to have finished by the end of three months?
Why ask it
Forces a specific deliverable rather than a description of the role. If the answer is something you could not achieve without four other teams cooperating, you have learned the real difficulty of the job, and you should ask who will unblock those teams.
Which decisions would be mine to make without checking first?
Why ask it
This is the practical measure of seniority, and it often contradicts the title. Listen for spending limits, hiring input, and whether you can change your own priorities. Roles with impressive titles and no unilateral decisions tend to be frustrating within a year.
Which other teams would I depend on to get my work done?
Why ask it
Most jobs are made hard by dependencies rather than by the work itself. Ask the names, then ask how those relationships currently stand, because inheriting a strained relationship with a team you cannot avoid is a specific and fixable thing to know about in advance.
What has this team tried before that didn't work?
Why ask it
Every team carries a history of abandoned attempts, and walking in without that history means proposing something they already tried in 2023. An honest answer here also shows whether the team can discuss failure without assigning blame.
What does a bad week here look like?
Why ask it
Better than asking about work-life balance, because it invites a story rather than a policy. Listen for the trigger: a release, a month end, a client escalation. Then ask how often that happens, since the answer converts an abstract worry into a number of weeks per year.
Who is actually online at nine at night, and how often?
Why ask it
Stated hours and real hours diverge in ways nobody volunteers. Naming a time makes the question hard to deflect. If the answer is that only a couple of people work late, ask whether they are the ones who get promoted, because that is what sets the real norm.
How is my performance reviewed, and when would my first review land?
Why ask it
Timing matters more than process. Starting two months before a review cycle can mean being assessed on almost no work, and in some companies it also means missing the first raise round entirely. Ask directly whether your start date affects your eligibility.
What's the promotion path out of this role, and who was promoted from it most recently?
Why ask it
The second half of the question is the one that matters. A path with no recent examples is a description of a hierarchy, not a route anyone has walked. If the last promotion was years ago, ask what changed.
Could I talk to two people who'd be my peers, without a manager in the room?
Why ask it
The request itself is a test. Companies confident in their teams arrange it within a day; hesitation or a carefully chosen chaperone tells you something the interviews will not. Ask those peers what surprised them in their first month.
When did someone last leave this team unhappy, and what happened?
Why ask it
Everyone has a departure like this, so a claim that nobody has ever left disgruntled is not credible. What you are listening for is whether the manager can describe the situation with any sympathy, or whether every departure gets filed under attitude problems.
How is the company funded, and how is the unit I'd be joining doing financially?
Why ask it
Company health and team health are different things, and people join profitable companies only to land in a division scheduled for cuts. At a private company ask about the last raise and rough runway; at a public one ask whether your unit's numbers are reported separately.
What has changed about this team's plan in the last six months?
Why ask it
Reorganisations are usually visible in the answer. A plan that has been rewritten twice means your role could look different by the time you finish onboarding, which is worth knowing before you resign from somewhere stable.
What's the part of this job people find hardest to get used to?
Why ask it
Asks for the friction rather than the challenge, and the answers tend to be procedural: the approval chain, the amount of documentation, the volume of meetings, the on-call rota. These are the things that make people quit, and none of them appear in a job description.
What's the one thing you would fix about this team if you could?
Why ask it
A manager who cannot name anything is either new, incurious, or managing you rather than answering you. The complaint they choose also tells you what they will and will not protect you from, which is the most useful thing you can learn about a future boss.
What would make you look back in a year and say this hire didn't work?
Why ask it
Turns the interview around and produces unusually candid answers, often about pace, independence, or willingness to work across teams. Whatever they name is the thing you will actually be judged on, regardless of what any written objectives say.
If I said yes, what would you want me to know that isn't in the offer letter?
Why ask it
An open door at the end of the conversation, and people frequently use it: an upcoming reorganisation, a difficult client, a colleague who is leaving. Silence is also an answer, and it is worth noticing which of your interviewers takes the opening and which does not.
Working out whether to say yes
Practical guidance for the conversation itself
Decide your dealbreakers before the offer arrives
Offers create urgency, and urgency makes people negotiate about salary because it is the easiest thing to talk about. Write down two or three things that would make you leave a job within a year, in specific terms: a commute over an hour, no ability to work from home on a fixed day, a manager who does not hold regular meetings, a team on call at weekends. Take that list into the conversation and ask about those items directly. Anything you decide after the offer lands, you will decide badly.
Split the questions by who can answer them
- Recruiter: process, timeline, bands, benefits, how flexible the package is, what happens if you need extra time.
- Hiring manager: the first three months, decision rights, dependencies, what went wrong before, why the last person left.
- Future peers: the real hours, how bad weeks actually feel, what onboarding was like, whether the manager keeps their commitments.
- Skip-level or director, if offered: where the team's funding sits and what is likely to change next year.
- Someone who left, if you can find them politely through your network. They answer the turnover question better than anyone still employed there.
Verify rather than trust
- Check the tenure of the team on public profiles. A team where nobody has been there more than eighteen months is telling you something.
- Ask for anything material in writing: start date, working pattern, title, reporting line, review timing.
- If a promise depends on a specific person, ask what happens to it if that person leaves.
- Treat online reviews as a source of questions rather than conclusions. Bring the recurring complaint into the conversation and see how they respond.
- Note how the process treated you. Cancelled interviews, silence for two weeks, and a rushed close are all previews of how the company handles its own people.
Pressure tactics and how to handle them
- A twenty-four hour deadline on a permanent job is a negotiating tactic. Asking for a few days is normal and rarely costs you the offer.
- If they refuse to give you until a stated date, ask what changes for them in that time. The answer is usually nothing.
- Never resign from your current job before you have the countersigned offer in hand.
- If a recruiter presses you to name a number before you have seen the full picture, it is fair to say you will discuss compensation once the role is clear.
- Beware of an offer that improves substantially the moment you hesitate. It means the first number was a test rather than a valuation.
When the answers are good but something feels off
Discomfort after a strong process usually points to something concrete you have not said out loud yet: the manager talked over you, nobody on the team seemed rested, the work is a lateral move dressed up as a step forward. Try to name it in one sentence, then ask one more question that would confirm or dismiss it. If you cannot get to a specific concern, the feeling may simply be the ordinary discomfort of change, which is not a reason to turn down work you otherwise want.