What should employers tell candidates in a job interview?

Pay, day-to-day responsibilities, flexibility and how to close a recruitment process without leaving candidates waiting.

In a job interview, the employer asks about your salary expectations, your availability and why you want the role. When you ask about the pay or what a typical week would look like, the reply is: “We’ll come to that later.”

How are you supposed to explain why you want a job if you still don’t really know what it involves?

In my previous Perspectives article, I wrote about what happens when an honest answer changes how a candidate is assessed. This time I want to look at the other side of the table: what someone needs to know to decide whether they want the job, and what their treatment during the process says about the employer.

Talk about pay before both sides invest more time

If the employer already has a salary range, sharing it early helps both sides decide whether it makes sense to continue. If there is variable pay, it is worth explaining how much it accounts for, which targets it depends on and how much influence the person taking the role will have over those results.

It is reasonable to ask about salary expectations. Asking for a figure without explaining what the employer can offer, then leaving that discussion until after several interviews, is less useful. If the budget and expectations are far apart, finding out early saves everyone time.

A job title won’t tell you what the week looks like

In a commercial role, “business development” can mean managing an established portfolio or building a market from scratch. These jobs can share a title and call for different people. They also need different resources and timelines for results.

A useful question is: “What will take up most of my week, and what would you expect me to have achieved after three months?” The answer helps the candidate understand the job and explain, with examples, what they can bring to it.

What “flexibility” means in practice

Two job adverts can both describe the role as hybrid and mean very different things. In one, office days are agreed with the team. In another, they are fixed and there is frequent travel on top. Knowing how many days on site are expected, how often you need to travel and which hours are fixed can change your decision.

If the employer needs to understand someone’s actual availability, it helps to explain first what the role requires and where there is room to make arrangements. That gives both sides something concrete to discuss.

How the process ends shapes the employer’s reputation

After an interview, the employer promises an answer the following week. The week passes, the candidate follows up and nobody replies. That is ghosting. A standard email at least communicates the decision, but after several interviews or an assessment, “we’ve decided to proceed with other candidates” can feel inadequate.

A candidate can understand why someone else got the job and still come away with a poor impression of how they were told. Today’s candidate could be tomorrow’s customer, business partner or the person someone asks whether it is worth working there. How they were treated may stay with them longer than the outcome.

Not every application calls for detailed feedback. After an interview, thanking someone for their time and telling them the decision already shows consideration. If they have completed an assessment or gone through several rounds, briefly explaining which criterion mattered most, where possible, is more useful than a generic message. If the decision is delayed, an update with a realistic date means they don’t have to chase for an answer.

Here is what I would ask employers:

What impression of your company does someone take away when they don’t get the job?

Read part one: How much honesty is there room for in a job interview?

Back to Perspectives