Seven Interview Questions That Expose Weak Job Descriptions

The Interview Question That Means You Failed

When a finalist asks 'So what would I actually be doing day-to-day?' in a final interview, you have already lost. That question is not curiosity. It is a red flag that your job description provided zero clarity about the actual role.

Elite recruiters track which questions candidates ask most frequently during interviews. These questions are not random. They reveal exactly what your job description failed to communicate. And when top candidates have to use precious interview time extracting basic information, 61% will accept competing offers instead.

Question 1: 'What Does Success Look Like in the First 90 Days?'

This question appears in 73% of interviews for senior roles, according to LinkedIn talent data. It should never need to be asked because your job description should already include a first-90-days roadmap.

When candidates ask this, they are telling you: your posting was all inputs (responsibilities, requirements) and zero outputs (outcomes, metrics, goals).

Before posting your next [Product Manager](/job-description/product-manager-general) or [Senior Project Manager](/job-description/senior-project-manager-general) role, add a section titled 'What Success Looks Like' with 3-4 specific, measurable outcomes for months 1, 2, and 3.

Question 2: 'Who Would I Be Working With?'

When candidates ask about team composition, they are really asking: Why did your job description omit the most important context about collaboration, reporting structure, and team dynamics?

Top performers want to know if they will be the first data hire or joining a team of twelve. If they will work with engineers in Austin or designers in Manila. If the team skews junior or senior.

Add one paragraph to every job description: 'You will work directly with [specific roles], report to [title], and collaborate across [departments]. Our team is [size] people, including [breakdown].' This eliminates the question entirely.

Question 3: 'Why Is This Role Open?'

This is the politest way candidates ask: Did someone quit? Get fired? Is this a toxic situation I should avoid?

When 68% of candidates ask this question (Glassdoor research), your job description lacked transparency. High-performing recruiters now include a brief 'Why We Are Hiring' section that states: new headcount due to growth, backfill for promotion, backfill for departure, or newly created role.

Being vague creates suspicion. Being direct builds trust.

Question 4: 'What Are the Biggest Challenges in This Role?'

Translation: Your job description was all sunshine and buzzwords. What are you hiding?

Weak job descriptions list responsibilities like 'manage stakeholder relationships' without acknowledging that those stakeholders are in six time zones and frequently misaligned. Or they mention 'lead product strategy' without noting the product is in turnaround mode after a failed launch.

A-players want hard problems. They do not want surprises. Add a 'Key Challenges' section with 2-3 honest obstacles. For a [Data Scientist](/job-description/data-scientist-general) role, that might be: 'Our data infrastructure is fragmented across four systems' or 'You will need to build stakeholder buy-in for ML adoption.'

Question 5: 'What Is the Timeline for This Hire?'

When candidates ask about hiring urgency and start dates, they are really saying: your job description gave me no idea if this is urgent, planned, or just a fishing expedition.

Recruiters who add one sentence about timeline increase application quality by 34%. Simply state: 'We are looking to make an offer within three weeks, with a start date in early June' or 'This is a planned Q3 hire with flexibility on start date.'

Passive candidates especially need this. They are not job-searching. They need to know if you are serious.

Question 6: 'How Does This Role Grow?'

If every [Software Engineer](/job-description/software-engineer-general) candidate asks about career progression, your job description treated the role like a static box instead of a growth opportunity.

Add 15 words: 'This role typically progresses to [next level] within [timeframe] based on [criteria].' Or be honest: 'This is an individual contributor track with deep technical growth but not a management pipeline.'

Clarity beats aspiration every time.

Question 7: 'What Happened to the Last Person in This Role?'

This is the nuclear version of Question 3. Candidates ask this when something feels off. When Glassdoor reviews mention high turnover. When the job has been reposted four times.

You cannot always control the narrative, but you can reduce suspicion by adding retention context to job descriptions: 'Our last three hires in this role were promoted within 18 months' or 'This role was held by Jane for four years before she moved to our London office.'

What to Do Before Your Next Post

Open your draft job description. Read it as if you are a skeptical candidate. Then ask: would I still need to ask any of these seven questions in an interview?

If yes, rewrite. Because every question a candidate asks in an interview is a gap you should have filled in the posting. And every gap costs you the candidates who never applied because they could not get answers upfront.

The best job descriptions make interviews about fit and vision, not basic information gathering. Stop writing job descriptions that create work for your interviews. Write them so thoroughly that candidates show up already excited, already informed, and already selling you on why they are the right fit.

Ready to write better JDs?

Generate professional job descriptions for any role in 30 seconds. Bias-checked and ATS-ready.