When the title is the same but the job underneath isn't
Say you've found a specific opening, a product team naming a design system and heavy component reuse, or a smaller company where the same person runs interviews, synthesizes findings, and ships the final screens. Paste that posting in and the questions come from those specifics directly rather than a generic template.
A candidate targeting a design-system-heavy role gets asked differently than one targeting a generalist UX role covering the full process solo, even though both postings share the same job title, because the actual day-to-day work underneath each one is barely comparable.
What gets covered
Expect questions built around the exact responsibilities and tools named in the posting you supplied, plus follow-ups shaped by what you actually say, since the voice agent reacts to your answers instead of running a fixed script. A posting emphasizing solo end-to-end ownership pulls different questions than one describing a specialized role inside a larger design team.
This is separate from resume-based practice, which works from your own past projects instead of a posting, and from general practice, which needs no document at all.
Scoring
What scoring weighs here
Scoring reflects how directly your answers connect to that specific posting's actual mix of responsibilities, not just general UX competence. Calibration floors and caps apply the same way as on every other type, so a generic research-process answer scores lower than one that clearly ties back to what the posting itself described.
Technical and Communication both get weighed against that same posting-specific language, so a strong answer for a design-system role won't automatically read as strong for a research-first one.
Frequently asked questions
Can I use a posting found outside the Intervieux job board?
Yes. Any posting text can be pasted in, whether it's on the Intervieux job board or a company's own careers page, as long as the description itself is available to work from.
Will the questions reflect whether a role is research-heavy or more visual?
Yes. Questions are built from what the posting actually emphasizes, whether that's independent research ownership, visual and interaction design, or some mix of both.
How is this different from a general practice session?
General practice runs standard opening questions with no document required. This type reads a specific posting you supply and questions from its actual responsibilities and tools.
Does it help to run this even before I've applied?
Yes. Pasting in a posting works whether or not an application has already gone in, which makes it useful for deciding whether a role is a fit as much as for preparing after applying.
What if a posting is vague about whether the role owns research end to end?
The session works from whatever detail is actually there. A posting that stays vague on ownership will lean its questions on the parts it does specify rather than assuming a structure the listing never described.
Related pages
Practice against the posting you're actually targeting
Paste in a real UX designer job description and get questioned on its specific research and design mix before the real interview.