A candidate looks promising on paper. What supports that impression, and what should you ask in the interview?
This walkthrough shows how to use TrueRole to examine a candidate's fit for a role, inspect the evidence behind the assessment, and prepare questions about what remains unclear. We follow a Sr. Principal Product Designer candidate from résumé review through supporting work and interview preparation, then follow the interviewer's notes through review and feedback analysis for the hiring team.
The workspace was set up directly in TrueRole. No ATS connection was required.
About this example: We used TrueRole founder Damien Dalli's career materials, with the candidate listed as Damien D. The scores and requirement assessments are actual outputs from a demonstration workspace. The summary includes a source-checked editorial correction to project attribution. The twelve other candidate profiles are fictional. Interview responses and interviewer notes are simulated and labeled. This is a product demonstration, not a customer result or a real hiring decision.
Start with what the role needs
The example role focuses on cart and checkout experiences. Its fifteen requirements cover areas such as complex business purchasing flows, design ownership, research, prototyping, collaboration, and delivery. Four nice-to-haves sit separately from those requirements.
Reviewing these criteria gives the hiring team a shared basis for evaluating candidates. For this role, the reviewer needs to understand both the complexity of the work and the candidate's responsibility for it. A familiar employer or senior title alone cannot answer those questions.
All thirteen candidates were evaluated against the same saved criteria. The role description came from Ingram Micro; its use here does not imply that the company uses or endorses TrueRole.
Use the candidate list to choose where to look closer
The candidate list keeps the wider group in view while the selected candidate's details open alongside it. It shows role fit, evaluation stage, level alignment, and relevant experience, helping the reviewer decide which profiles need a closer look.
Damien's initial résumé review scored 80, below the two highest initial scores in the fictional comparison group. It gave the reviewer a starting point for examining his commerce and procurement experience more closely. We then used deeper analysis to examine the supporting work available in his profile.
Review the materials behind the assessment
The Materials section in Overview keeps the résumé and supporting sources together. Each item shows whether it was used in the evaluation, and its actions let the reviewer open the source or update the material. Add materials provides a way to bring in additional evidence when the existing profile leaves a question open.
The initial review used the original PDF résumé. For deeper analysis, we preferred four supporting sources: the Hyundai website redesign, Hyundai Drive, Vocre, and The UX Lenses. TrueRole also selected the portfolio overview and Anything After case study, bringing the supporting-source count to six. A material being present in the workspace and being used in an evaluation are different things, so the usage labels matter.
The reviewer can use this view to check that the right materials are attached, open a case study, or identify what to request from the candidate. In Damien's case, the written case studies provide project context, while the actual design artifacts remain useful for a closer craft review.
Use deeper analysis to examine supporting work
Deeper analysis builds on the initial résumé review by examining the supporting material against the role criteria. In this example, it used six supporting sources from the profile. The Hyundai website case study describes Damien's guidance across research, design, implementation, and post-launch review. Hyundai Drive adds UX and prototyping work, including collaboration with an external research partner. Vocre describes interaction changes prompted by usability problems and operating-system constraints. The UX Lenses explains a design approach. The portfolio overview and Anything After case study add career context and another example of hands-on product work.
Together, these materials give the reviewer more detail about how Damien worked, the constraints involved, and the questions to explore. In the Overview, What deeper analysis added groups new evidence, confirmed findings, and remaining questions so the reviewer can see where to look closer.
In this run, the initial résumé assessment scored 80, labeled Good fit, and deeper analysis scored 87, labeled Great fit. This is one observed evaluation sequence, with different inputs and processing at each stage; adding materials does not guarantee a higher score.
Screenshot context: The following candidate views show Damien's completed deeper assessment. The twelve fictional peers retain their initial-review scores, so their displayed order is not a comparison at the same evaluation stage or a benchmark.
Get oriented in the Overview
The Overview brings together the candidate summary, strengths, additional signals, risks, requirement assessments, career context, and supporting materials. A reviewer can start with the overall picture, then examine the parts that matter most for this role.
Damien's summary identifies senior experience, large product initiatives, and research collaboration as strengths. The requirement assessment leaves a specific question open: the materials suggest senior stakeholder involvement, but do not explicitly document ownership of executive reviews.
That distinction helps the reviewer prepare. There is evidence worth discussing, along with a clear reason to ask for another example.
Generated summaries are interpretations of the supplied materials. The reviewer should check the wording against the sources, particularly where it describes individual ownership. For Hyundai Drive, the case study identifies UX engineering and prototyping alongside work with an external research partner. Keeping that contribution specific helps the interviewer ask about the decisions Damien personally made.
Open a requirement to understand its assessment
The requirement breakdown shows where the available evidence supports the role and where it leaves gaps. In Damien's assessment, prototyping is a stronger area, while executive communication and technical collaboration need a closer look. Visual Craft and Design Judgment remains Unscored in this run.
That breakdown helps the reviewer focus the next conversation. They can explore a particular responsibility or missing example rather than relying on the overall fit label.
Opening Executive Communication & Stakeholder Management reveals the assessment, its weight, a Partially Evidenced label, and two excerpts from the résumé. The panel links to the original and labels both excerpts as supporting evidence.
The excerpts describe providing UX direction on the Hyundai website redesign and leading an Experience Design team. They provide context for senior communication, but do not establish what Damien presented in an executive review, what objections came up, or how a difficult decision was reached. That is a useful boundary for the interviewer to investigate.
Put a varied career in context
Damien's background includes agency work, enterprise product design, and founding products. The Career path section provides another way to examine that history in relation to the role. It shows level alignment and distinguishes experience classified as directly relevant from adjacent experience.
Here, TrueRole marks the recent scope At level, while identifying the career path as a partial fit. These are generated classifications that the reviewer can investigate by opening the role history. A useful follow-up is to ask how responsibilities in an agency, a large company, and a founder role relate to the work this position needs.
Inspect Application Checks and their coverage
Application Checks highlights unusual content and inconsistencies that may need a closer look. From Overview, View all checks opens the individual results. These checks give the reviewer another way to examine the application materials, alongside the assessment of fit for the role.
With the original PDF résumé and six supporting sources, all nine check categories show Clear. The overall status is No concerns detected. Hidden text, overlapping text, and instructions in metadata have document-level results from inspecting the PDF itself. The shared-contact check uses the identity information available in the material.
The detail view still distinguishes what applies to each source. A captured web page has no PDF or Word rendering layer, so its hidden-text and overlapping-text checks can correctly show Not applicable. The active PDF's corresponding checks are Clear.
Clear means the supported checks found no matching concern in the inspected content. It does not verify every career claim or establish authenticity. Incomplete, Not applicable, and Clear describe different situations; the reviewer should inspect the source and coverage before drawing a conclusion. Findings do not establish fraud or AI authorship.
Prepare an interview around the remaining questions
The saved question set addresses questions that remain open in the assessment. From the candidate's Interview tab, we chose a hiring manager interview with behavioral and technical/functional questions. We added guidance to focus on personal ownership and design tradeoffs in Hyundai Drive, the Hyundai website, and Vocre.
TrueRole generated five questions. One carries the open stakeholder-management question from the Overview into the interview:
Walk me through the closest Hyundai website redesign example where you personally resolved a disagreement over a design tradeoff?
The Why ask this explanation connects it to the need to understand stakeholder management beyond positive project reception. Listening guidance & follow-ups asks the interviewer to listen for a concrete disagreement, the people involved, Damien's responsibility, the reasoning used, and the decision reached. Suggested follow-ups include what Damien recommended, who disagreed and why, and what Damien personally led.
This gives the interviewer a purpose for the question and a way to explore an incomplete answer.
Another generated question examines a documented design sequence:
Walk me through one Vocre interaction you personally drove from early concept to a shipped iteration?
The interviewer can use this second question to understand Damien's contribution to work already described in the materials, alongside the stakeholder question that investigates an unresolved gap.
Capture what the candidate said and what you still need to know
The following notes are simulated for this demonstration. No interview occurred.
In the Interview tab, notes stay attached to their question. Recording the candidate's account separately from the interviewer's assessment helps the team understand what was said and what still needs clarification. For the Vocre question, the demo notes read:
Damien walked through Vocre's move from a tilt-based interaction to a tabletop experience and then a messaging-style interface. They described some users struggling with the tilt interaction and an iOS keyboard-orientation constraint making it harder to correct speech-recognition errors. They identified their role as co-founder and CPO, responsible for product direction and interaction design, working with Andrew Lauder.
My assessment: A concrete example of usability and a technical constraint shaping successive designs. I still want to see the screens, clarify which decisions Damien personally led, and ask how the team assessed each iteration. The response does not establish a measured improvement for each change.
The stakeholder-disagreement question remains open pending a real example. A separate note about validation priorities is labeled as hypothetical, distinguishing an approach to a future situation from past experience.
Notes are saved privately until the interviewer reviews and submits them as feedback. This gives them room to clarify attribution and correct wording before sharing with the team.
Bring the evidence back to the hiring team
We selected Update feedback to review the five saved notes together. TrueRole generated an editable summary while preserving the originals. Before approving it, we clarified the opening to state explicitly that these were simulated notes and that no interview occurred. No hiring recommendation was selected.
After Approve & add to analysis, the feedback finished processing. When the material assessment was later refreshed, the existing feedback was carried forward. In the captured Feedback tab, it shows Applied to score, with a baseline of 87 and interview evidence fit of 87, a change of zero. This is the observed result for simulated notes, not validation of a real interview.
From here, the reviewer can open Source notes to read the original question-by-question record or expand Feedback analysis to inspect how individual statements were handled. In this run, the analysis identified three positive signals: research collaboration and Vocre iteration were marked Used as evidence, while the broader technical-collaboration observation was treated as Opinion. The evidence entries include the linked role requirement, reasoning, and a source excerpt. The view also exposes controls to treat a signal as opinion or restore it as evidence, giving the reviewer a way to correct its treatment.
The analysis retains warnings that no interview occurred and the material is simulated. Because two statements were still marked as evidence, the simulation label should not be read as a guarantee that such notes are excluded from analysis. The reviewer needs to inspect the result and its limits.
The value of this final step is traceability: the team can move from the feedback summary back to the source notes and see which statements informed the analysis, rather than treating every interview impression as equally supported.
By this point, the reviewer has an assessment tied to the role, supporting evidence they can inspect, focused interview questions, and reviewed feedback that separates the candidate's account from their own judgment. They can explain both why a candidate looks promising and what they still need to learn.
For Damien, the next steps are specific: examine the design work, ask for a stakeholder-disagreement example, and clarify one engineering tradeoff and one research finding that changed a decision. The hiring team can carry those questions into its next conversation.
This is how TrueRole serves as an intelligence layer across candidate review and interview preparation. It connects the criteria, materials, assessments, and notes the team uses to make its judgment. The workflow is useful with or without an ATS; the hiring decision remains with people.
To explore the workflow with your own role, request a demo. You can also read how to evaluate candidates without an ATS.