Skip to content
Question Vault?
Free to readNo accountNo email wallNo invented statisticsNo ads on medical, legal or end-of-life pagesCopy or print any set and take it with you
03 · Professional & Academic

Questions to Ask Before Starting a New Job

Questions for the stretch between accepting an offer and your first day, while you can still ask almost anything without it counting against you. They cover first-week logistics, what your manager expects early on, how the team actually communicates, what happened to your predecessor, and benefits and payroll timing.

20 questions · each with a note on why · conversation guide

The questions

Open any question for the note

  1. What time should I arrive on the first day, where do I go, and who will meet me?

    Why ask it

    These are the details nobody remembers to send, and standing in a locked lobby with no named contact is a bad start to a day you have no control over. If nobody can say who is meeting you, that is worth noticing on its own.

  2. What paperwork or documents should I bring, and is any of it something I can complete beforehand?

    Why ask it

    Identity documents, direct deposit details and benefit forms often need originals that live in a drawer at home. Getting the list a week early saves a first morning spent at a photocopier instead of meeting people.

  3. What do people actually wear on a normal day, and on a day with client meetings?

    Why ask it

    Careers-page photos are unreliable, and 'casual' means something different in a warehouse, a studio and a bank. Asking about client days separately tells you whether you need one set of clothes or two.

  4. Will my laptop, accounts and building access be ready on day one, or should I expect a wait?

    Why ask it

    Provisioning delays are common and they change what your first week can be. If it honestly takes a week to get a laptop, you can line up reading and introductions instead of sitting at an empty desk.

  5. What is already on my calendar for the first week?

    Why ask it

    A structured first week suggests a team that has onboarded people before and thought about it. An empty calendar means you will be designing your own start, which is workable but better known in advance.

  6. Who are the five or six people I should meet first, and what does each of them do?

    Why ask it

    Names and roles up front let you arrive with questions instead of blank introductions. The list also exposes the informal map, including anyone who gets named repeatedly but appears nowhere on the org chart.

  7. What state is the work I am inheriting in, and is there a handover document?

    Why ask it

    Taking over a clean handover and taking over a mess are two different jobs at the same salary. A predecessor who left abruptly usually means undocumented systems, irritated stakeholders and a first month spent on archaeology.

  8. What would you like me to have done or learned by the end of my first month?

    Why ask it

    A concrete answer is the difference between real onboarding and being told you are doing fine right up until you are not. If your manager has no answer, draft your own version and get it agreed in writing.

  9. How will my performance be judged in the first six months, and by whom?

    Why ask it

    The 'by whom' matters as much as the criteria. If reviews draw on a skip-level manager or peer feedback, your work has to be visible to people you have not met yet, which changes how you spend the first quarter.

  10. Which meetings am I expected to be in, and which ones can I skip?

    Why ask it

    New hires get added to standing meetings by default and then feel they cannot leave. Explicit permission to skip things is far easier to get in week one than to claim back in month four.

  11. How does the team actually communicate, and what response time do people assume?

    Why ask it

    Most teams have one real channel and one decorative one. Knowing whether a message left for four hours reads as normal or as ignoring someone prevents a lot of early misreading.

  12. When do people usually start and finish, and is anyone expected to answer in the evening?

    Why ask it

    The gap between stated hours and observed hours is where burnout starts. Asking when the person you are talking to last worked a weekend gets a more honest answer than asking about balance in the abstract.

  13. Which days is the team actually in the office, and is that a policy or a habit?

    Why ask it

    A hybrid policy on paper often differs from the days people really overlap. If the useful days are Tuesday and Wednesday, you want that before arranging childcare or committing to a commute.

  14. What can I decide on my own, and what needs sign-off?

    Why ask it

    Scope is described more generously in an offer letter than it works in practice. A role where every spend and every hire needs approval two levels up is a different job from the one advertised, and this is how you find out which one you accepted.

  15. When something goes wrong, how do you prefer to hear about it?

    Why ask it

    Some managers want problems the moment they appear, others want them with an option attached, and guessing wrong is a standard early misstep. Asking turns it into a stated preference rather than a trap.

  16. What do people here figure out around month three that they wish they had known on day one?

    Why ask it

    At best you get a warning about a difficult stakeholder, a system that breaks weekly, or a reorganisation already under way. A long pause before the answer tells you something as well.

  17. What has caused someone in this role not to work out before?

    Why ask it

    This asks about the failure mode rather than the ideal candidate, which is far more useful. Answers about being slow to ask for help, or about mishandling one particular relationship, are worth more than any list of competencies.

  18. When does benefits enrollment open and close, and when does coverage actually begin?

    Why ask it

    Enrollment windows are short and often close within the first weeks, while coverage may not start for a month or more. If you are leaving existing coverage, the exact dates decide whether you have a gap.

  19. When is my first payday, and how does the pay cycle line up with my last check from my old job?

    Why ask it

    Pay cycles regularly leave three or four weeks between the last check at one employer and the first at the next. Knowing the date lets you plan for it instead of discovering it mid-month.

  20. Is there anything I could read, set up or learn before I start that would genuinely help?

    Why ask it

    A useful answer names a specific document, tool or account. A vague 'just relax' is fine too, and worth taking at face value rather than spending a fortnight preparing for a job you cannot see yet.

Using the weeks before your start date

Practical guidance for the conversation itself

Before day one

  1. 1Reread the offer letter, benefits summary and any bonus or equity terms now that you are no longer negotiating. Errors in start date, title or salary are much easier to correct before payroll runs once.
  2. 2If something specific matters to you, a medication, an existing therapist, fertility treatment, a dependent in another state, ask for the plan documents rather than the benefits brochure. The brochure will not answer it.
  3. 3Confirm your start date in writing, along with any time off you negotiated. A verbal 'of course you can take that week in August' disappears if the manager who said it moves on.
  4. 4Work out the calendar around notice, unused vacation payout and any bonus payment date at your current employer before you resign, not after.
  5. 5Resist preparing by studying. One conversation with your future manager about priorities is worth more than two weeks of reading industry press.

The first two weeks

Keep notes you can reread

Write down names, systems, acronyms and who owns what. You get to ask what something means once without comment, and that window closes sooner than anyone admits.

Get a thirty-day plan on paper

If your manager does not offer one, draft your own after the first week and ask them to correct it. Even a heavily edited draft forces a conversation about priorities that most new hires never have.

Meet people outside your own team

Fifteen minutes each with the people whose work feeds yours, and whose work you feed, shows where things really get stuck. Do it while being new is still reason enough to ask.

Warning signs in the first month

  • Nobody can describe what success looks like, including your manager.
  • The role as described in the interview keeps quietly widening.
  • Your predecessor's departure is discussed in careful language and nobody will say what happened.
  • Promised equipment, access or training keeps slipping and no one owns getting it done.
  • Two people give you contradictory instructions and each assumes you know which of them outranks the other.

If something in the offer looks wrong

Raise any discrepancy in the offer letter, start date or benefits in writing before the first payroll cycle, and raise it with whoever made the offer rather than your new manager. Corrections are routine at that stage and awkward afterward. If you signed an agreement containing non-compete, confidentiality or intellectual property terms that concern you, an employment lawyer can usually review it for a flat fee, and that review is more useful before you start than after.