The scenario: the posting decides which HR job this actually is
One posting names a sourcing quota, a specific applicant tracking system, and a time-to-fill target. Another names an employee-relations caseload, a client group of managers, and a performance-review cycle. Paste in the first and the questions lean toward pipeline strategy and channel selection.
Paste in the second and they lean toward handling a difficult manager conversation and coaching through a review cycle. Neither posting gets the other's questions, because a talent acquisition role and an HR business partner role are different jobs wearing the same department name, and the interview reads whichever text is actually supplied.
What gets covered
Questions draw from whatever the posting names directly: a specific ATS or HRIS tool, a client group or business unit the role supports, a sourcing channel or requisition volume, a compliance area like leave administration or benefits enrollment.
If the posting mentions a specific employee population, hourly retail staff versus salaried corporate staff, expect questions grounded in that population's actual realities rather than a generic employee-relations prompt.
A posting for a generalist role at a smaller company tends to spread its questions across sourcing, employee relations, and process design all at once, since that's genuinely what the job requires day to day.
Scoring
What actually gets scored here
Because job-description sessions in this field often surface a specific caseload or pipeline detail, the penalty for skipping situation-action-result structure matters here, an answer that names a difficult employee-relations case but never gets to what was actually decided or said still loses points, even if the situation itself was genuinely hard to navigate.
Frequently asked questions
Will a talent acquisition posting and an HR business partner posting generate different questions?
Yes. Questions build from what each posting actually names, so a sourcing-and-pipeline posting and an employee-relations-heavy posting lead to noticeably different questions even though both sit under an HR department.
Am I limited to postings that are actually listed on this job board?
No. Any HR or recruiting posting text can be pasted in, whether it's listed on the Intervieux job board or found elsewhere.
Can I use this to prepare before I've applied?
Yes. Pasting in a posting's description works whether or not an application has already been submitted.
Does it check whether my answer follows a clear structure?
Behavioral answers tied to a posting's specifics are checked for situation-action-result structure, and a story that names a hard case but never reaches the outcome still loses points.
Will a generalist posting at a small company generate a broader mix of questions?
Yes. A generalist posting tends to spread across sourcing, employee relations, and process design in the same session, closer to what a small-company HR role actually requires day to day.
Will the interview ask about a specific compliance area mentioned in the posting?
It can. A posting naming leave administration, benefits enrollment, or another compliance responsibility generates questions grounded in that specific area rather than a broad HR-knowledge question.
Related pages
Practice against the specific HR role you're applying for
Paste in a real HR or recruiting job description and get questioned on the specific sub-function, tools, and population it names.