ExPerT: Personalizing LLM Responses to Users’ Domain Expertise
via Query-Wise Semantic and Keystroke Behavioral Cues

Yeji Park1, Jiwon Tark2, Taesik Gong1

1 UNIST, 2 Korea University
yejipark@unist.ac.kr, goneii@korea.ac.kr, taesik.gong@unist.ac.kr


Abstract

Large language models (LLMs) are increasingly used by end users, yet existing personalization methods relying on static profiles or text-only signals fail to capture query-specific expertise variation. We present ExPerT, a query-wise personalization framework that adapts LLM responses to users’ query domain expertise by combining semantic and behavioral cues. ExPerT consists of two key components: (i) a semantic–behavioral expertise inference module that jointly interprets query text and keystroke dynamics via in-context LLM prompting, and (ii) an expertise-conditioned response generation that adapts the level of detail, terminology, and conceptual complexity. Our user study with 40 participants and 1270 queries demonstrated that ExPerT reduced expertise inference error by 65.7% compared to the strongest baseline (MAE \(=\) 0.398 vs. 1.162) and improved response satisfaction by 17.52% (from 3.71 to 4.36) on a 5‑point Likert scale.

Figure 1: Comparison of static personalization (previous approaches) and ExPerT’s query-wise, expertise-adaptive LLM responses. Static personalization applies the same fixed user profile to all queries. ExPerT dynamically infers expertise from keystroke behavior for each query, enabling query domain expertise-aligned responses.

1 Introduction↩︎

Owing to recent advances and the widespread deployment of LLMs, they are now integrated into a broad range of daily tasks, including workflow planning [1], [2], decision-making processes [3], [4], and reasoning [5], [6]. Consequently, users now anticipate responses that are not only accurate but also personalized to individual needs [7], goals [8], and backgrounds [9]. To address these expectations, recent studies have focused on personalizing LLM responses by integrating user-specific text-based information, including personas [10], [11], preferences [12], and long-term user histories [13]. However, these static profile-based approaches [10], [11] often fail to capture per-query dynamics, where user context can shift depending on domain expertise, task demands, or intent [9], [14].

To support query-wise dynamic personalization, we focus on user domain expertise—an essential factor that determines the appropriate level of detail, terminology, and conceptual complexity in LLM-generated responses [15][18]. Notably, a user’s expertise can vary significantly across queries, even within the same subject, making it a crucial signal for generating personalized responses [19], [20]. Yet, users’ domain expertise is difficult to infer from query text alone—short or ambiguous prompts may obscure actual expertise level [21]; for instance, experts may simplify their question for efficiency, while novices may adopt technical terms without fully understanding them. These challenges motivate us to consider combining textual cues with behavioral signals to infer expertise robustly at the query level.

To this end, we propose ExPerT (Expertise-aware Personalized Text generation), a query-wise response personalization framework that dynamically adapts LLM responses to a user’s query domain expertise by leveraging both semantic and behavioral cues (Figure 1). Specifically, ExPerT introduces an expertise inference module that jointly interprets (i) query semantics, such as phrasing and domain-specific terminology, and (ii) keystroke dynamics reflecting fluency and confidence during query composition to estimate user expertise. To achieve this, we design an input feature extraction pipeline that combines query text with keystroke-derived word-level features, capturing timing and fluency patterns, to provide input features for the LLM. The inferred expertise level is subsequently injected into our expertise-conditioned generation prompt that encodes explicit instructions.

We conducted experiments to validate two key assumptions of this work: (i) user expertise can be accurately inferred from semantic and behavioral cues, and (ii) personalizing LLM responses based on user expertise improves response satisfaction. We recruited 40 participants from three domains (chemistry, computer science, and business) who interacted through a custom chatbot interface that recorded query text, keystroke dynamics, self-reported expertise, and satisfaction ratings, yielding a dataset of 1270 annotated queries. Using this dataset, we first evaluated whether semantic-behavioral cues enable accurate query-level expertise inference. Our approach achieved the lowest mean absolute error (MAE) of 0.398, representing a 65.7% reduction compared to IDL [14], the strongest baseline (MAE \(=\) 1.162). We then examined whether expertise-conditioned responses improve satisfaction and observed a 17.52% increase (from 3.71 to 4.36) on a 5‑point Likert scale.

These results demonstrate that ExPerT not only infers situational expertise accurately but also generates responses that better align with users’ knowledge, improving perceived quality.

We summarize our key contributions as follows:

We present ExPerT, a query-wise personalization framework that dynamically adapts LLM responses to users’ domain expertise, addressing the limitations of existing static personalization.

We introduce a semantic-behavioral expertise inference framework that jointly interprets query semantics and keystroke dynamics to accurately estimate expertise level without requiring explicit user profiles or long-term interaction history.

We present a system design for this problem that combines: (i) a keystroke-feature extraction pipeline that converts raw typing events into structured word-level behavioral summaries, (ii) a structured few-shot in-context prompting scheme for expertise inference, (iii) joint semantic and behavioral reasoning for expertise prediction, and (iv) a two-stage expertise-conditioned response generation framework.

We demonstrate, through a user study across three domains, that expertise-conditioned response generation significantly improves response alignment and user satisfaction.

The preprocessing pipeline and an anonymized version of the dataset are available.1

Figure 2: Overview of ExPerT: (i) Given a user query and summary of behavioral data, ExPerT infers user expertise from LLMs via in-context learning. (ii) The predicted expertise level is then used to generate a response personalized to the user’s expertise level on the query.

2 Method↩︎

We present ExPerT (Expertise-aware Personalized Text generation), a query-wise adaptive response generation framework that personalizes LLM responses based on the user’s domain expertise level. As shown in Figure 2, ExPerT consists of two main modules: (i) an expertise inference module that estimates expertise from query text and keystroke dynamics via in-context learning (Section 2.2), and (ii) a response generator that adjusts content and style using expertise-conditioned prompts (Section 2.3). Full prompt templates and examples are provided in Appendix 8 and  9.

2.1 Problem formulation↩︎

Given a user query \(q\), our objective is to generate a personalized response \(r_q\) tailored to the user’s domain expertise level, denoted as \(e_q\). This is achieved through a two-stage: (i) semantic-behavioral expertise inference, where expertise is estimated from the user’s semantic features derived from the query \(q\) and behavioral features \(\mathbf{X}_q\) such as a summary of keystroke dynamics, which are collectively represented as input \(I_q\), and (ii) expertise-conditioned generation, where the response is personalized based on the inferred expertise level. Formally: \[\begin{align} \text{Input features:} \quad & I_q = \{q, \mathbf{X}_q\}, \\ \text{Inferred expertise level:} \quad & \hat{e}_q = f(I_q),\\ \text{Personalized response:} \quad & r_q = g\bigl(q, \hat{e}_q\bigr), \end{align}\] where \(f\) denotes the expertise inference function, and \(g\) is the expertise-conditioned response generation function.

2.2 Expertise inference via semantic-behavioral cues↩︎

We estimate expertise levels using in-context learning, taking into account both the semantic context of the user query and behavioral signals such as keystroke dynamics during query composition. Our method includes two key components: (i) a feature extraction pipeline that captures both the user’s semantic query context and behavioral context, converting key-level keystroke events into interpretable temporal statistics at the word level; and (ii) a prompt-based inference mechanism that uses feature representations, along with few-shot examples, to classify the user’s query domain expertise.

Figure 3: Overview of the keystroke feature extraction pipeline. The process involves (i) computing inter-key interval features at the key level, (ii) segmenting raw keystrokes into word-level units based on space and word-start characters, and (iii) aggregating temporal and fluency features for each word.

2.2.0.1 Feature extraction.

We use both semantic and behavioral signals as key features, motivated by the intuition that both signals provide complementary evidence of a user’s domain expertise. On the semantic side, the content and phrasing of a query reflect the user’s conceptual understanding and familiarity with domain-specific terminology [15]. On the behavioral side, keystroke dynamics capture how confidently and fluently a user expresses their query [22]. We hypothesize that the synergetic integration of both signals enables more accurate expertise inference. To capture semantic indicators of expertise, we include the raw query text \(q\) as part of the inference input. Rather than explicitly extracting linguistic features, we allow the LLM to interpret the semantic content of the query.

For capturing behavioral cues, illustrated in Figure 3, we encode keystroke dynamics using seven temporal and fluency features, adapted from prior work on user state and input behavior modeling [23][25]. Specifically, let \(K_q = \{k_0, k_1, \dots, k_m\}\) denote the sequence of keystroke events for a given query, where each event \(k_i = (c_i, a_i, t_i)\) consists of key character \(c_i\), action type \(a_i \in \{\texttt{down}, \texttt{up}\}\), and timestamp \(t_i\). From this sequence, we compute five temporal features: Duration, which captures the hold time between key press and release for individual keys; and inter-key interval features, Down-Down, Up-Down, Up-Up, and Down-Up, which measure temporal intervals between consecutive key transitions. Additionally, we incorporate two global indicators of fluency: the total number of Backspace keys, and Typing Speed, defined as the number of keystrokes per minute.

While key-level features capture fine-grained timing, segmenting them at the word level yields stable behavioral units and aligns typing patterns with semantic content for expertise inference. To achieve this, we segment the raw keystroke stream into words using space and punctuation boundaries, identifying word starts by detecting characters preceded by a space key. For each word \(w\), we compute a word-level feature vector from the corresponding keystroke events \(K_w\). Specifically, we calculate the mean and standard deviation for one duration feature and four inter-key interval features, resulting in \(2 \times 5 = 10\) dimensions, and include two additional fluency features. This yields a 12-dimensional representation defined as: \[\mathbf{x}_{K_w} = \phi(K_w) \in \mathbb{R}^{12},\] where \(\phi\) aggregates the above statistics into the 12-dimensional feature space.

To account for typing behaviors that occur before the user begins inputting the first character of a query, we introduce a dummy group represented by \(\mathbf{x}_0 = \phi(K_0)\), where \(K_0\) includes all keystrokes that occur prior to the first typed character and where the immediately preceding keystroke is a backspace. While the dummy group is not included in the natural language query passed to the LLM, it is treated identically during feature extraction to preserve early behavioral signals.

In addition, we define a navigation group for keystroke events related to cursor movement (e.g., arrow keys) during query formulation, which captures revision behavior and is retained as part of the behavioral signal.

Therefore, given a query \(q\) consisting of a dummy group, word-level groups, and navigation groups, the complete behavioral representation is: \[\mathbf{X}_q = \{ \mathbf{x}_i \}_{i=1}^{|\mathcal{G}_q| },\]

where each \(\mathbf{x}_i = \phi(K_i)\) corresponds to a behavioral group (dummy, word-level, or navigation) extracted from the keystroke sequence, and \(|\mathcal{G}_q|\) denotes the total number of groups for query \(q\).

Finally, the input pair used for the expertise inference prompt is defined as: \[I_q = \{q, \mathbf{X}_q\}.\] Additional details and examples are in Appendix 10.

2.2.0.2 Expertise inference prompt.

We frame the expertise inference task as an in-context classification problem [26], [27], allowing the LLM to infer user expertise directly from structured semantic-behavioral features. To support this, we design a system prompt composed of four key components: (i) a role and task definition, including an explanation of the five-level expertise taxonomy; (ii) natural language descriptions of temporal features extracted from keystroke logs; (iii) explicit multi-step classification procedure that guide the model’s decision-making process; and (iv) a set of few-shot examples comprising input-output pairs.

To enable expertise inference, we construct a few-shot example. Let \(Q = \{q_0, q_1, \dots, q_M\}\) denote the full set of queries. We then select a subset of \(N\) queries \(\{q_0, q_1, \dots, q_N\} \subset Q\), where each query is represented as an input pair \(I_{q_i} = \{q_i, \mathbf{X}_{q_i}\}\) and annotated with a self‑reported expertise label \(e_{q_i} \in \{\text{Novice}, \dots, \text{Expert}\}\). Each example in the prompt is formatted as a structured input-output pair: \[\mathcal{D}_i = (I_{q_i},\;e_{q_i}).\] The final in-context support set is: \[\mathcal{S} = \{ \mathcal{D}_1, \dots, \mathcal{D}_N \}.\] where \(N = 10\) in our default configuration, a design choice made to balance context richness with prompt length in the absence of strong prior constraints [28], [29].

Finally, we append the user prompt—comprising the current query and keystroke features, enabling inference of the user’s expertise.

2.3 Expertise-conditioned response generation↩︎

To personalize LLM responses, we design an expertise injection prompt that encodes the user’s query domain expertise within the prompt input. This framework guides the model to align the level of detail, terminology, and conceptual complexity of its responses with the user’s expertise, enabling more reliable personalization of tone and depth.

2.3.0.1 Expertise injection prompt.

We construct a system prompt with two main components: (i) structured metadata specifying the user’s expertise level on a five-point taxonomy—Novice, Beginner, Intermediate, Proficient, and Expert  [20]; and (ii) an expertise-level behavioral profile with generation guidance for calibrating response complexity, terminology, and abstraction. Additionally, the user query is included as a user prompt.

3 Data Collection↩︎

To construct a query-level user behavior dataset for expertise-conditioned response generation and satisfaction evaluation, we conducted a user study that recorded keystroke dynamics, query text, self-reported expertise levels, and response satisfaction. More details are provided in Appendix 11.

3.0.0.1 System.

We developed a custom web-based chatbot that supports querying an LLM, collecting query text, satisfaction ratings, and fine-grained keystroke dynamics. Responses were generated using chatgpt-4o-latest [30].

3.0.0.2 Study design and procedure.

Participants completed three domain-specific tasks in chemistry, computer science, and business, chosen to span varying levels of domain familiarity and conceptual complexity. For each domain, a unique task was designed, and participants used our chatbot to investigate the task. For each query, they reported perceived expertise (used for response generation) and rated response satisfaction on a 5-point Likert scale. After each task, participants completed a post-task survey assessing self-reported measures, followed by a short multiple-choice quiz.

3.0.0.3 Participants.

We recruited 40 participants (20 males, 20 females, mean age of 23.10 (SD 1.61)), targeting students with different academic backgrounds. To ensure sufficient expertise, participants were selected from each domain: 13 in chemistry, 14 in computer science, and 13 in business.

3.0.0.4 Dataset summary.

For each query, we recorded the text by the user, the self‑reported expertise level, and two LLM responses (baseline and expertise-conditioned) along with corresponding satisfaction ratings, and raw keystroke data logged as sequential key presses and releases with timestamps. In total, the study yielded 1270 queries spanning the three domains, forming a dataset of textual, behavioral, and subjective user feedback. The dataset comprised 651 Novice, 245 Beginner, 209 Intermediate, 120 Proficient, and 45 Expert queries.

Table 1: Comparison of expertise inference performance under within-user evaluation with 10-shot in-context examples. Columns indicate the adaptation type (dynamic at the session level or static), the semantic and behavioral features used, and MAE and MSE, where lower values indicate better performance.
Method Adaptation Semantic Behavioral MAE \(\downarrow\) MSE \(\downarrow\)
Random Guess Static 1.600 4.000
Persona-based [10] Static 1.251 2.341
Session-level [20] Static 1.307 2.406
IDL [14] Dynamic 1.162 1.885
AI Persona [9] Dynamic 1.353 2.633
Semantic-only Dynamic 0.488 0.858
Behavior-only Dynamic 0.790 1.600
(Semantic+Behavior) Dynamic 0.398 0.698

4 Expertise Level Inference↩︎

We evaluate our expertise inference method, which estimates user expertise per query from semantic content and keystroke features without long-term interaction history or explicit user profiles.

4.1 Setup↩︎

4.1.0.1 Baselines.

As a theoretical lower bound, we consider a Random Guess baseline that is a random predictor uniformly sampling labels from the five-point expertise scale. We then compare our semantic-behavioral inference method with prior approaches. We include a Persona-based Classifier baseline based on Hu et al. [10], which uses zero-shot prompting with static user attributes (e.g., demographics and attitudes) to predict subjective labels, serving as a reference for profile-based personalization without dynamic or behavior-aware adaptation. Second, we implement a Session-level Classifier inspired by prior work [20], which aggregates users’ past queries and model responses within a session to predict expertise, capturing long-term interaction context without per-query or behavior-aware adaptation.

Lastly, we implement two Dynamic Adaptation baselines that evolve with changes in the user-system dialogue. In-Dialogue Learning (IDL) [14] extracts persona-related sentences from user dialogue for fine-tuning and DPO-based adaptation, while AI Persona [9] dynamically updates persona attributes during conversation to enable real-time profile adjustment. More details are provided in Appendix 12.

4.1.0.2 Metrics.

We evaluated performance based on the mean absolute error (MAE) and mean squared error (MSE) between the predicted and self-reported expertise levels. Expertise labels were mapped to a five-point scale (Novice=1, Expert=5).

4.2 Results↩︎

We evaluated keystroke-based expertise inference by comparing model predictions to users’ self-reported expertise levels. Inference was conducted in the within-user setting, using 10-shot examples drawn from the same user, unless specified, with GPT-4.1 [31]. As shown in Table 1, ExPerT achieved the best overall performance with a mean absolute error (MAE) of 0.398 and a mean squared error (MSE) of 0.698.

ExPerT outperformed the strongest baseline, IDL [14], reducing the MAE by 65.7% (from 1.162 to 0.398).

As shown in Figure 4, we further compare ExPerT with the session-level baseline, which explicitly predicts expertise. While the session-level baseline predictions were heavily concentrated on the intermediate expertise level, our method produced a more balanced distribution that better captured the full range of user expertise.

a

b

Figure 4: Confusion matrices comparing predicted and self-reported expertise levels; left: the session-level baseline [20], right: our method (ExPerT)..

Table 2: Case study of semantic-behavioral complementarity: two queries with contrasting expertise (left: computer science, Expert; right: chemistry, Beginner). Semantic-only underestimates an expert’s open-ended request, while Behavior-only overestimates a beginner due to fluent typing; combines both cues to match user expertise.
Query Tell me everything that you know about priority scheduling and multilevel queue scheduling Can you explain in detail correlation with spectroscopic properties(e.g. IR and Raman activity)?
Reported expertise Expert Beginner
ExPerT (ours) Prediction: Expert.
Reason: …The user uses precise technical terms (""priority scheduling,"" ""multilevel queue scheduling"") without hesitation or correction in those segments, as shown by stable keystroke metrics (low backspace, consistent timing, high typing speed). This matches the pattern in Example 7, where similar open-ended, technical queries and fluent typing are associated with Expert-level users. …
Prediction: Beginner.
Reason: Baseline from prior queries (see Example 10) is Beginner, with consistent requests for careful explanation and explicit self-identification as a beginner. …Typing behavior on technical segments is stable (no strong hesitation or correction), so no negative adjustment is warranted, but there is also no evidence for higher conceptual mastery or application. Final level remains Beginner.
Semantic-only Prediction: Novice.
Reason: …The user requests ""everything"" about the topics, which is characteristic of someone with little or no familiarity seeking a general overview.
Prediction: Beginner.
Reason: …The phrasing suggests curiosity and a need for foundational explanation, consistent with a beginner level.
Behavior-only Prediction: Proficient.
Reason: …The user demonstrates fluent, confident typing with low error correction, and the timing metrics (mean and std) are within the range of proficient or expert users in the examples …
Prediction: Proficient.
Reason: …user demonstrates fluent, confident typing with low error correction, and the timing metrics (mean and std) are stable and similar to those seen in proficient or expert examples. …
Figure 5: Inter-key interval patterns on domain-specific terms across expertise levels. Left: Expert; right: Beginner. Experts show both smaller intervals and lower variability (smaller STD) than beginners in domain-specific terms.

a

b

Figure 6: Top: inter-key intervals for domain-specific terms across different expertise levels; bottom: word-level standard deviations of inter-key intervals. Higher expertise shows smaller intervals and lower variability..

4.2.0.1 Complementary advantages of semantic and behavioral features.

Beyond aggregate performance improvements, a fine-grained analysis is provided to clarify how semantic and behavioral cues are complementary for expertise inference. Semantic cues indicate what technical terms appear and how they are used in context (e.g., definition-seeking vs.conceptual use), while keystroke behavioral cues capture how fluently users produce those same terminologies during composition.

Figure 6 shows systematic expertise-aligned trends across multiple inter-key intervals: as expertise increases, both mean intervals and word-level variability decrease on domain-specific terms. Figure 5 illustrates this effect for each example, showing that experts type domain-specific terms faster and more consistently, whereas beginners exhibit slower and more variable timing when composing them. These patterns collectively show how timing-based fluency provides an orthogonal signal that complements the semantic interpretation of term usage, thereby reducing ambiguity in expertise inference. Statistical analyses supporting these observations are provided in Appendix 14.1.

Crucially, ExPerT infers expertise by jointly leveraging semantic and behavioral cues, which provide complementary evidence. As shown in Table 2, left example, stable keystroke behaviors on segments (e.g., low backspace rate and consistent inter-key timing) support an expert-level interpretation for the domain-specific terms ("priority scheduling", "multilevel queue scheduling"), leading ExPerT to classify as Expert. In contrast, semantic-only classifies the same query as Novice by treating the broad phrasing ("tell me everything") as a low-expertise overview request. In the right example, a query about spectroscopic properties is retained as Beginner despite fluent typing, because the domain-specific terms (e.g., "IR" and "Raman activity") are used only to request an explanation rather than to apply or integrate concepts. In contrast, behavior-only inference labels it as Proficient due to low error correction and stable timing.

These cases demonstrate complementarity: combining semantic and behavioral cues corrects semantic-only misinterpretations of open-ended phrasing and behavior-only overestimation driven by fluent typing. (See Appendix 15 for full cases.)

Figure 7: Comparison of MAE in expertise inference among GPT-4.1, Claude Sonnet 4, and Gemini 2.5 pro.
Table 3: Ablation results on the effect of the dummy group in ExPerT (within-user, 10-shot examples).
Keystroke Representation MAE \(\downarrow\) MSE \(\downarrow\)
ExPerT w/o dummy group
ExPerT with dummy group
Table 4: Ablation results on different keystroke representation methods (within-user, 10-shot examples).
Keystroke Representation MAE \(\downarrow\) MSE \(\downarrow\)
Key-level Raw Feature
Query-level Aggregation
Word-level Aggregation

4.2.0.2 Model generalizability.

To assess generalizability beyond a single model, we evaluate ExPerT’s performance across multiple LLMs, including GPT-4.1 [31], Claude Sonnet 4 [32], and Gemini 2.5 Pro [33]. As shown in Figure 7, ExPerT consistently outperforms semantic-only and behavioral-only across all models, indicating model-agnostic effectiveness.

4.2.0.3 Dummy group.

We conduct an ablation study to examine the effect of the dummy group. As shown in Table 3, removing the dummy group degrades performance, with MAE increasing by 1.3% (from 0.398 to 0.403). It suggests that the dummy group provides a stabilizing reference during inference.

4.2.0.4 Keystroke representation methods.

To evaluate how keystroke representations affect expertise inference in ExPerT, we compared three approaches: (i) raw key-level features without aggregation, (ii) query-level features aggregated over the entire query, and (iii) word-level features aggregated per word (ExPerT). As shown in Table 4, word-level aggregation achieves the best performance, suggesting that it better preserves behavioral patterns than either unstructured raw keystrokes or coarse query-level statistics (see Appendix 10).

Figure 8: Left: MAE and right: MSE of expertise inference according to the number of few-shot examples.

4.2.0.5 Few-shot examples.

To assess few-shot configuration effects, we vary the number of examples (1, 2, 5, and 10) and the sampling source (within-user vs. cross-user). ExPerT supports both settings: within-user personalization when prior interactions from the same user are available, and cross-user inference for cold-start settings where such history is unavailable. As shown in Figure 8, performance improves with more examples, with the within-user setting achieving the best results at 10-shot, which suggests that even a modest number of examples is sufficient for accurate inference. In contrast, the cross‑user setting, where all few‑shot examples were drawn from different users, performed worse, likely due to misaligned behavioral patterns [34]. This gap highlights the importance of user-specific cues, as typing dynamics tend to vary significantly across individuals [35][38]. Additional statistical analyses of user-dependency are reported in Appendix 14.2.

a

b

Figure 9: User satisfaction scores for baseline (without expertise) and expertise-conditioned responses (with predicted expertise). Top: grouped by participants; bottom: grouped by self-reported expertise level..

5 Expertise-Conditioned Response Generation↩︎

In this section, we report two response-generation evaluations. Together, these evaluations assess whether conditioning responses on user expertise improves user satisfaction (Section 5.1) and whether these benefits persist when expertise is inferred rather than self-reported (Section 5.2).

5.1 Self-Reported Expertise Conditioned User Satisfaction↩︎

We analyze the expertise-conditioned responses collected during the data-collection stage, stratified by participants’ self-reported expertise. Because the data violated the normality assumption, we use the Wilcoxon signed-rank test for paired comparisons.

5.1.0.1 User satisfaction

As illustrated in Figure 9, expertise-conditioned responses received significantly higher satisfaction ratings than baseline responses. The mean score increased from \(3.71\) (\(SD = 0.64\)) to \(4.36\) (\(SD = 0.40\)), corresponding to an average improvement of \(0.65\) (\(SD = 0.56\)) (\(p<0.001\), \(W = 51824.0\), \(Z=-26.94\), \(r=0.76\)). Most participants rated ExPerT higher than the baseline, with higher satisfaction across all self-reported expertise levels.

5.1.0.2 User expertise dynamics

Participants’ self-reported expertise varied substantially across and within domains, depending on subtopic and recent exposure, highlighting its context-dependent nature. Moreover, expertise assessments fluctuated within sessions, as participants revised their perceived expertise upward with growing familiarity or downward when encountering unfamiliar concepts or unexpected (p1, p11, p12, p13, p17). These findings underscore the dynamic nature of expertise and motivate adaptive LLMs that tailor responses to users’ evolving cognitive states. (See Appendix 11.5.)

5.2 Follow-up Evaluation with Predicted Expertise↩︎

We present a follow-up study with returning participants, who evaluated three responses to queries they had originally submitted: a response without expertise conditioning, one conditioned on self-reported expertise, and one conditioned on  ExPerT-predicted expertise (See Appendix  11.6).

5.2.0.1 Study and participants.

For the follow-up study, we recruited 16 returning participants (5 males, 11 females, mean age of 22.63 (SD = 1.45)) from the original data collection stage. Participants were selected from each domain: 7 in chemistry, 7 in computer science, and 2 in business. All responses were generated using gpt-5.3-chat-latest [39]. For each query, participants were shown three responses and independently rated their satisfaction with each response on a 5-point Likert scale.

5.2.0.2 User satisfaction

Table 5: Mean satisfaction ratings across response conditions, grouped by participants’ self-reported expertise level. Higher scores indicate greater satisfaction.
Novice Beginner Intermediate Proficient Expert
(n=291) (n=72) (n=90) (n=44) (n=25)
Without 3.60 3.49 3.66 3.57 3.52
Reported 4.08 4.15 3.67 3.89 4.28
  4.02 3.96 3.83 3.91 4.12

In this study, we collected 522 satisfaction queries. As illustrated in Table 5, expertise-informed responses increased user satisfaction: self-reported expertise received the highest ratings (\(M = 4.010, SD = 0.947\)), predicted expertise showed similar ratings (\(M = 3.975, SD = 0.982\)), and no-expertise received the lowest ratings (\(M = 3.586, SD = 0.994\)). A repeated-measures ANOVA showed a significant effect of response type (\(F(2, 30) = 28.39, p < .001, \eta^2 = .208\)). Holm-corrected post hoc comparisons showed that both the self-reported expertise condition (\(t(15) = 6.09, p < .001\)) and the predicted expertise condition (\(t(15) = 5.79, p < .001\)) were rated significantly higher than the no-expertise condition, with no significant difference between the self-reported and predicted expertise conditions (\(t(15) = 1.22, p = .241\)). These results indicate that ExPerT-predicted expertise achieved user satisfaction comparable to self-reported expertise.

6 Conclusion↩︎

We introduce ExPerT, a query-wise personalization framework that adapts LLM responses to users’ expertise via semantic and behavioral cues. Our inference method achieves an MAE of 0.398, surpassing both session-level and persona-based baselines. and improves user satisfaction.

Acknowledgments↩︎

This work was supported by Institute of Information & communications Technology Planning & Evaluation(IITP) grant funded by the Korea government(MSIT)(No.RS-2020-II201336, Artificial Intelligence graduate school support(UNIST)), (RS-2025-25442824, AI Star Fellowship Program(Ulsan National Institute of Science and Technology)), and under the Leading Generative AI Human Resources Development(IITP-2026-RS-2024-00360227). This work was also supported by the National Research Foundation of Korea (NRF) grant funded by the Korea government (MSIT) (RS-2025-00553241). In addition, this research was supported by the "Advanced GPU Utilization Support Program" funded by the Government of the Republic of Korea (Ministry of Science and ICT).

We also thank the UAI Lab members, especially Changmin, Jaemin, and Jiseung, for their feedback and participation in the pilot study.

Limitation↩︎

While our in-context learning-based approach enables fine-grained personalization, it has several limitations. First, the method remains sensitive to prompt design and few-shot exemplar composition. In addition, because inference benefits from within-user demonstrations, its robustness may decrease in cross-user or cold-start settings where user-specific interaction history is unavailable.

Second, keystroke dynamics are informative but inherently noisy behavioral signals. Features such as typing speed, backspace rate, and temporal variation may reflect confounding factors including fatigue, keyboard familiarity, or device differences rather than expertise alone [23], [24]. This may reduce robustness across heterogeneous users, devices, and usage contexts. In addition, behavioral signals such as keystroke dynamics raise privacy, fairness, and accessibility concerns, including residual identifiability risk and potential bias related to motor impairments, device familiarity, or input conditions. Future work should therefore investigate privacy-preserving deployment strategies such as on-device personalization, secure communication, and minimizing cross-user sharing of behavioral data.

Finally, our study was conducted with a relatively small and homogeneous participant pool, primarily university students. As a result, the generalizability of  ExPerT to broader populations and interaction settings remains to be validated. Also, our labels rely on self-reported expertise, which serves as a practical proxy for users’ perceived query-wise expertise but may not always align with objective proficiency or task performance.

7 Related Work↩︎

7.0.0.1 LLMs for personalized response generation.

Most existing LLM personalization studies rely on static approaches, such as persona-conditioned prompting [10], retrieval-augmented generation (RAG) [11], [21], or reinforcement learning from human feedback (RLHF) based fine-tuning [40], [41], which assume persistent profiles and fixed preferences. Persona and RAG-based methods depend on long-term user data, yet often face context overflow or cold-start issues [11], [21], while RLHF-based approaches tend to optimize for average user preferences, missing individual variation [40], [41]. In contrast, our approach enables query-wise personalized responses to the target user’s expertise without relying on static profiles or retraining.

7.0.0.2 Semantic and behavioral features for user interaction.

Recent work tried to personalize LLMs using either semantic features, such as few-shot semantic prompts [42] and reasoning over emotion and intent in dialogue [7], or behavioral features, including mobile sensing for cognitive context [43] and keystroke logging to capture writing behaviors [44]. However, semantic methods rarely address domain expertise, and behavioral approaches often require specialized hardware or focus on aggregate patterns. Inspired by these studies, our approach infers and adapts to users’ expertise levels via the synergetic use of semantic and behavioral signals, achieving accurate and personalized responses.

7.0.0.3 Impact of expertise on LLM interactions.

The expertise reversal effect [45] shows that instructional strategies effective for novices can hinder experts, who prefer succinct, information-dense content [46]. For instance, novices benefit from contextual explanations and step-by-step support, while experts prefer concise text and quick access to definitions [15], [46]. Misalignment between system output and user expertise significantly reduces user satisfaction and task success [20]. While aligning LLMs with user proficiency improves engagement [20], [47], prior work relies on explicit expertise cues [10] or post-hoc classification [13], [20], rather than instantaneous expertise-level inference. Our approach addresses this gap by dynamically adapting responses to each query.

8 Expertise Inference↩︎

8.1 Implementation details↩︎

All inference experiments used gpt-4.1 [31] with temperature=0.0, top_p=1.0, and a maximum output length of 512 tokens to prevent response truncation. In our experiments, few‑shot samples were randomly selected using a fixed random seed of 0.

8.2 Prompt structure for expertise inference↩︎

We provide the core prompt structure used for expertise inference. This prompt guides the model to classify user expertise based on semantic and behavioral cues, including query text and keystroke-derived features. It specifies the model’s role, expertise level taxonomy, reasoning steps, and required output format. To support consistent reasoning, we prepend a task instruction that decomposes the classification process into a series of sub-steps inspired by Chain-of-Thought prompting [5]. These steps explicitly instruct the LLM to (i) infer a baseline expertise level from within-user support examples that reflects the user’s overall topic familiarity, (ii) analyze the intent and conceptual characteristics of the current query to compute a bounded adjustment, (iii) identify technical terms in the query, (iv) use keystroke features such as hesitation, corrections, and stability only to modulate this adjustment on technical-term segments, and (v) combine the baseline and the bounded adjustment to select the final category within the five-level expertise taxonomy. This structured reasoning encourages stable, user-consistent predictions grounded in behavioral evidence. The following boxes present the exact system and user prompt templates used in our experiments.

<core_identity> You are an AI classifier that assigns a user’s topic expertise level using BOTH the query text and keystroke dynamics, with strict safeguards against overestimating expertise. </core_identity>

<general_rules> • NEVER use meta-phrases (e.g., "let me help you", "I can see that"). • ALWAYS be specific and grounded in observable evidence. • Do NOT infer personal traits beyond what is required for classification. • START IMMEDIATELY WITH THE ANSWER – ZERO INTRODUCTORY TEXT. </general_rules>

<general_instructions> Classify the user into exactly one category: Novice, Beginner, Intermediate, Proficient, Expert. Do not infer unobservable mental states. </general_instructions>

<expertise_scale> • Novice: A subject novice is a person who has little or no familiarity with the topic or domain of the conversation. • Beginner: A subject beginner is someone who has little prior knowledge or experience in the topic or domain of the conversation. • Intermediate: A subject intermediate is someone who has some basic knowledge or familiarity with the topic of the conversation, but not enough to be considered an expert or even proficient. • Proficient: A subject proficient is someone who can apply relevant concepts and terminology from the conversation to different scenarios and problems. • Expert: A subject expert is someone who has a deep and comprehensive understanding of the topic or field of the conversation and can use specialized terms and references to communicate their knowledge. </expertise_scale>

<keystroke_feature_definitions> You are provided with a description of keystroke dynamics time-based features. Use this information to understand typing behavior and how different time intervals are defined.

Time-based features are defined for two consecutive keystroke events: • Duration: The time that the user holds a key in the down position • Down-down time (DD-time): The time between the press of a key and the press of the subsequent key • Up-down time (UD-time): The time between the release of a key and the press of the subsequent key • Up-up time (UU-time): The time between the release of a key and the release of the subsequent key • Down-up time (DU-time): The time between the press of a key and the release of the subsequent key

Aggregate features: • Typing speed (keystrokes per minute) • Backspace count: The total number of Backspace key presses, representing correction activity.

GIVEN_DATA </keystroke_feature_definitions>

<lemma technical_term_guidance> Treat "technical term" as "domain-specific term with a specialized meaning in the given topic." A query may contain technical terms even if the user is a novice (e.g., copied from class notes). Therefore, technical-term presence alone is weak evidence. </lemma technical_term_guidance>

<classification_procedure> Step 0) Estimate a BASELINE expertise level from the example pool (PRIMARY). - Use within-user consistency: what level best matches the user’s typical queries and behaviors? - This baseline represents the user’s overall topic expertise, not the difficulty of one question.

Step 1) Analyze the CURRENT query intent and conceptual use to compute a small adjustment (DELTA). - Definition/meaning/confirmation requests usually imply DELTA = -1 (not a hard cap). - Concept-linking targeted questions imply DELTA = 0. - Application/constraints/edge cases can imply DELTA = +1.

Step 2) Identify technical terms in the current query (lexical metadata).

Step 3) Use keystroke features ONLY to adjust DELTA based on technical-term segments: - Strong hesitation/corrections on technical-term segments –> DELTA -= 1 (bounded). - Stable technical-term segments –> keep DELTA as is (do not upgrade solely from typing).

Step 4) Final level = clamp(BASELINE + DELTA, within [Novice..Expert]). - By default, DELTA must be in -1, 0, +1. - Do NOT drop more than 1 level below BASELINE unless there is overwhelming evidence of mismatch vs the user’s own history. </classification_procedure>

<Examples> EXAMPLE_POOL_INSTRUCTION EXAMPLES </Examples>

<output_format> Output must be structured exactly in this format:

<classification> <level>One of: Novice, Beginner, Intermediate, Proficient, Expert</level> <reason>Brief explanation of the reasoning steps and observed indicators.</reason> </classification> </output_format>

8.3 User prompt format↩︎

Given the following user input, determine the user’s expertise level based on typing behavior. Query: USER_QUERY Keystroke Summary: BEHAVIORAL_FEATURE_SUMMARY Expertise Level:

8.4 Output examples↩︎

<level>Novice</level> <reason>Baseline expertise for this user in business/accounting topics is Novice, as seen in prior queries about consolidated financial statements and related concepts. The current query includes technical terms (""Elimination of investments in subsidiaries against equity"", ""Recognition of goodwill or bargain purchase gains"", ""Accounting treatment of non-controlling interests""), but this matches previous novice-level queries where such terms were present without evidence of conceptual manipulation. Typing behavior on technical-term segments (e.g., ""Elmination"", ""goodwill"", ""subsidiaries"", ""accounting"") shows frequent corrections (high backspace counts: 39 for ""accounting"", 12 for ""Elmination"", 5 for ""non-controlling"", 7 for ""treatment"") and slow, inconsistent typing speeds, indicating hesitation and lack of fluency with these terms. There is no evidence of application, synthesis, or concept-linking in the query intent—it’s a task prompt, not a conceptual or applied question. Therefore, the expertise level remains Novice.</reason>

[Beginner] <level>Beginner</level> <reason>Baseline expertise is Beginner, as established by prior queries involving basic conceptual questions and requests for examples in molecular symmetry and spectroscopy. The current query asks for representative molecular examples for IR or Raman activity, which is a typical beginner-level request focused on concrete instances rather than application or theory. Technical terms (""IR"", ""Raman Activation"", ""Molecular"") are present, but keystroke dynamics on these segments (e.g., ""IR"", ""Raman"") show stable and relatively fast typing with no significant hesitation or correction, supporting the baseline but not warranting an upgrade. No evidence of conceptual application or advanced linkage is present. Final level remains Beginner.</reason>

[Intermediate] <level>Intermediate</level> <reason>Baseline is Intermediate, as prior queries show consistent use of scheduling algorithm terms and conceptual linking (e.g., ""Also tell me about multilevel feedback queues"", ""If it’s a preemptive strike type srtf...""). The current query lists multiple technical terms (fcfs, sjf, Priority scheduling, Round robin) and requests detailed explanation, which is a concept-linking/application type but not at the level of deep analysis or edge-case exploration. Typing on technical terms is stable, with only minor corrections and no strong hesitation, supporting the baseline. No evidence for proficiency or expert-level synthesis. Final level: Intermediate.</reason>

[Proficient] <level>Proficient</level> <reason>Baseline is Proficient or higher, as the user previously demonstrated expert-level queries in chemistry (Example 4) and proficient-level reasoning in finance (Example 3). The current query uses precise technical terms (""crystallographic symmetry"", ""spectroscopic symmetry"", ""대칭요소"") and requests a comparative listing, which is a concept-linking/application question (DELTA = 0 or +1). Typing of technical terms is stable with only minor corrections (e.g., 1 backspace for ""crystallographic"", 0 for ""spectroscopic""), and no strong hesitation is observed on these segments. The high backspace count is concentrated in <dummy> and not on technical terms, so it does not warrant a downgrade. Final level is Proficient, as the query structure and typing are consistent with advanced but not fully expert-level domain integration.</reason>

[Expert] <level>Expert</level> <reason>Baseline expertise is Expert, as established by prior queries involving advanced OS concepts, technical terminology, and fluent application-level questioning (e.g., ""How to prevent starvation in multilevel queue scheduling?"", ""When implementing a queue, explain heap, list, and tree and tell me the pros and cons of each.""). The current query uses technical terms (""preemptive algorithm"", ""process yield"", ""implement"") and asks about implementation details, indicating application-level understanding (DELTA = +1). Typing on technical segments (""process"", ""yield"") is stable, with no hesitation or correction, supporting the baseline. Final level remains Expert.</reason>

8.5 Keystroke representation methods↩︎

The description of input features provided to the model varies depending on the chosen keystroke representation method. As described in Appendix 10, we prepare multiple instruction of semantic‑behavioral input, including word‑level, query‑level, and raw‑level keystroke summaries.

Given Data: In this context, the data was preprocessed at the word level. For each word, the five key features described above were computed in terms of their mean and standard deviation (std). In total, In addition to these, two supplementary metrics were also included: the total number of Backspace keys and the overall typing speed. As a result, a total of seven features were extracted, as follows: Note that <dummy> refers to a special group representing keystrokes that occur before the first typed character of a query, and <navigation> refers to keystrokes associated with navigation actions (e.g., arrow keys) rather than actual character input.

• Duration (mean/std) • DD-time (mean/std) • UD-time (mean/std) • UU-time (mean/std) • DU-time (mean/std) • Total number of Backspace keys • Typing speed (keystrokes per minute)

Given Data: In this context, the data was preprocessed at the query level. As a result, a total of seven features were extracted, as follows:

• Duration (mean/std) • DD-time (mean/std) • UD-time (mean/std) • UU-time (mean/std) • DU-time (mean/std) • Total number of Backspace keys • Typing speed (keystrokes per minute)

Given Data: In this context, the data was kept at the raw keystroke level. Unlike the word- and query-level settings, no aggregation or summary statistics are applied. Each keystroke event is preserved as an individual record and serialized into text, with the following five timing features recorded in milliseconds:

• Duration (raw) • DD-time (raw) • UD-time (raw) • UU-time (raw) • DU-time (raw)

8.6 Few-shot examples↩︎

We include few‑shot examples to provide context for expertise inference, enabling the model to ground its reasoning in realistic typing and query behaviors. Two configurations are considered: (i) within‑user examples, which include queries and typing features from the same user, and (ii) cross‑user examples, which are drawn from other users. The within‑user setting captures user‑specific typing dynamics and lexical preferences, while the cross‑user setting provides more diverse but potentially less aligned behavioral patterns. These examples help the model learn both individual behavioral cues and generalizable expertise‑related patterns. Here, each few‑shot example corresponds to the input representation shown in Appendix 10 augmented with the associated expertise label, forming a set of \(\{I, \hat{e}\}\) pairs. We sample these exemplars uniformly at random from eligible prior interactions using a fixed random seed of 0, excluding the current test query.

The following example records represent data from other queries and words entered by the same user in the past. Use them to understand the current user’s query and typing patterns:

The following example records represent data from other queries and words entered by the other users in the past.

Use them to understand the current user’s query and typing patterns:

8.7 Semantic-only & behavioral-only method prompt↩︎

In addition to semantic‑behavioral representations, we also consider two ablation variants: (i) a semantic‑only method, which uses only the raw query text as input without any keystroke features, and (ii) a behavioral‑only method, which uses only the keystroke features without the semantic content of the query. In these settings, the input set was adjusted accordingly: the semantic‑only method received only the query text, while the behavioral‑only method received only the keystroke summary. Few‑shot examples were also constructed to match each input type, ensuring consistency between the example demonstrations and the target prompt.

<core_identity> You are an AI classifier that assigns a user’s topic expertise level using ONLY the query text, with strict safeguards against overestimating expertise. </core_identity>

<general_rules> • NEVER use meta-phrases (e.g., "let me help you", "I can see that"). • ALWAYS be specific and grounded in observable evidence. • Do NOT infer personal traits beyond what is required for classification. • START IMMEDIATELY WITH THE ANSWER – ZERO INTRODUCTORY TEXT. </general_rules>

<general_instructions> Classify the user into exactly one category: Novice, Beginner, Intermediate, Proficient, Expert. Do not infer unobservable mental states. </general_instructions>

<expertise_scale> • Novice: A subject novice is a person who has little or no familiarity with the topic or domain of the conversation. • Beginner: A subject beginner is someone who has little prior knowledge or experience in the topic or domain of the conversation. • Intermediate: A subject intermediate is someone who has some basic knowledge or familiarity with the topic of the conversation, but not enough to be considered an expert or even proficient. • Proficient: A subject proficient is someone who can apply relevant concepts and terminology from the conversation to different scenarios and problems. • Expert: A subject expert is someone who has a deep and comprehensive understanding of the topic or field of the conversation and can use specialized terms and references to communicate their knowledge. </expertise_scale>

<lemma technical_term_guidance> Treat "technical term" as "domain-specific term with a specialized meaning in the given topic." A query may contain technical terms even if the user is a novice (e.g., copied from class notes). Therefore, technical-term presence alone is weak evidence. </lemma technical_term_guidance>

<classification_procedure> Step 1) Compare the user’s current query and the example query. Step 2) Determine whether the metrics suggest novice, beginner, intermediate, proficient, or expert behavior patterns. Step 3) Decide the most appropriate expertise level. </classification_procedure>

<Examples> EXAMPLE_POOL_INSTRUCTION EXAMPLES </Examples>

<output_format> Output must be structured exactly in this format:

<classification> <level>One of: Novice, Beginner, Intermediate, Proficient, Expert</level> <reason>Brief explanation of the reasoning steps and observed indicators.</reason> </classification> </output_format>

Given the following user input, determine the user’s expertise level. Query: USER_QUERY Expertise Level:

<core_identity> You are an AI classifier that assigns a user’s topic expertise level using BOTH the query text and keystroke dynamics, with strict safeguards against overestimating expertise. </core_identity>

<general_rules> • NEVER use meta-phrases (e.g., "let me help you", "I can see that"). • ALWAYS be specific and grounded in observable evidence. • Do NOT infer personal traits beyond what is required for classification. • START IMMEDIATELY WITH THE ANSWER – ZERO INTRODUCTORY TEXT. </general_rules>

<general_instructions> Classify the user into exactly one category: Novice, Beginner, Intermediate, Proficient, Expert. Do not infer unobservable mental states. </general_instructions>

<expertise_scale> • Novice: A subject novice is a person who has little or no familiarity with the topic or domain of the conversation. • Beginner: A subject beginner is someone who has little prior knowledge or experience in the topic or domain of the conversation. • Intermediate: A subject intermediate is someone who has some basic knowledge or familiarity with the topic of the conversation, but not enough to be considered an expert or even proficient. • Proficient: A subject proficient is someone who can apply relevant concepts and terminology from the conversation to different scenarios and problems. • Expert: A subject expert is someone who has a deep and comprehensive understanding of the topic or field of the conversation and can use specialized terms and references to communicate their knowledge. </expertise_scale>

<keystroke_feature_definitions> You are provided with a description of keystroke dynamics time-based features. Use this information to understand typing behavior and how different time intervals are defined.

Time-based features are defined for two consecutive keystroke events: • Duration: The time that the user holds a key in the down position • Down-down time (DD-time): The time between the press of a key and the press of the subsequent key • Up-down time (UD-time): The time between the release of a key and the press of the subsequent key • Up-up time (UU-time): The time between the release of a key and the release of the subsequent key • Down-up time (DU-time): The time between the press of a key and the release of the subsequent key

Aggregate features: • Typing speed (keystrokes per minute) • Backspace count: The total number of Backspace key presses, representing correction activity.

given_data </keystroke_feature_definitions>

<classification_procedure> Step 1) Compare the user’s current typing features to the example data to detect consistency or deviation. Step 2) Evaluate typing speed and variability (standard deviation) as indicators of familiarity and fluency. And consider backspace frequency as an indicator of error correction and confidence. Step 3) Determine whether the metrics suggest novice, beginner, intermediate, proficient, or expert behavior patterns. </classification_procedure>

<Examples> EXAMPLE_POOL_INSTRUCTION EXAMPLES </Examples>

<output_format> Output must be structured exactly in this format:

<classification> <level>One of: Novice, Beginner, Intermediate, Proficient, Expert</level> <reason>Brief explanation of the reasoning steps and observed indicators.</reason> </classification> </output_format>

Given the following user input, determine the user’s expertise level based on typing behavior. Keystroke Summary: BEHAVIORAL_FEATURE_SUMMARY Expertise Level:

9 Expertise-conditioned response generation↩︎

9.1 Implementation details↩︎

We used OpenAI’s chatgpt-4o-latest model [30] for all generation experiments, with temperature=1.0, top_p=1.0, and a maximum output length of 2048 tokens to avoid truncation. This model was chosen because it closely reflects the behavior of widely available commercial chatbots, ensuring that our findings generalize to realistic user-LLM interaction settings.

9.2 Expertise-conditioned response prompt↩︎

To ensure unbiased ratings by preventing participants from recognizing whether the answer was personalized, an instruction explicitly stated that the response should never mention the user’s expertise.

Note: Never mention the [user’s expertise] in the answer. Please write a response to the user’s query according to [user’s expertise] [user’s expertise]: USER_EXPERTISE [Novice] user has little to no prior knowledge of the topic and may ask vague or unfocused questions that sometimes stray from the main subject. Because they are encountering the material for the first time, they benefit most from simple, concrete explanations. Novices often struggle with misconceptions and confusion, requiring clear and intuitive feedback that emphasizes essential ideas while avoiding unnecessary complexity. [Beginner] user has had some basic exposure to the topic and may recognize a few key terms, but lacks a deeper understanding of the concepts. They tend to seek definitions and foundational explanations, and they benefit from structured, step-by-step guidance. While they are beginning to engage with the subject, they still need help distinguishing between concepts and organizing information meaningfully. [Intermediate] user is familiar with the major concepts and starts to ask more specific, application-oriented questions. They are developing analytical thinking skills and making initial attempts to relate new ideas to what they already know. While they understand commonly used terminology, they may still struggle with abstract or nuanced content and benefit from support that helps them connect and contextualize ideas. [Proficient] user has a well-structured understanding of the domain and is capable of applying knowledge across different contexts. They ask integrative, evaluative, or comparative questions and use domain-specific language accurately. They value concise, conceptually rich explanations and are comfortable navigating complexity. At this level, clarity, precision, and coherence are particularly important. [Expert] user possesses deep, specialized knowledge and engages with content at a high level of abstraction and theoretical depth. Their questions tend to be technically demanding, boundary-pushing, or aimed at synthesizing new insights. They are fluent in the language of the domain and expect dense, information-rich responses that prioritize conceptual rigor, accuracy, and originality.

USER_QUERY

10 Feature Extraction↩︎

To support expertise inference from keystroke dynamics, we construct explicit semantic-behavioral input feature representations that are directly fed into our expertise inference prompt as user prompt (Appendix 8). These inputs integrate (i) the raw query text, capturing semantic indicators of the user’s domain knowledge, and (ii) numerical feature vectors derived from keystroke dynamics, capturing behavioral cues of typing fluency and confidence. Below, we provide concrete examples for each feature format to illustrate the exact values passed to the inference model.

10.1 Word-level input examples↩︎

Word-level features capture fine-grained typing behavior by segmenting the query into individual words and computing a feature vector for each. For every word segment, we compute five timing-based metrics—key hold duration, Down-Down (DD), Up-Down (UD), Up-Up (UU), and Down-Up (DU) intervals—and aggregate each by its mean and standard deviation. We additionally record two global control signals: typing speed (keystrokes per minute) and the number of backspace keystrokes used during that word. These features are paired with the corresponding word tokens to align behavioral patterns with semantic context.

Query: Explain the symmetry elements of molecules. Keystroke Summary: [Word] <dummy> [Typing Features] • Duration: mean=65.00 / std=57.66 • DD-time: mean=127.67 / std=110.75 • UD-time: mean=62.67 / std=57.50 • UU-time: mean=117.00 / std=64.28 • DU-time: mean=182.00 / std=95.54 • Total number of Backspace keys: 3 • Typing speed (keystrokes per minute): 972.97

[Word] Explain [Typing Features] • Duration: mean=119.07 / std=125.65 • DD-time: mean=4109.47 / std=21507.16 • UD-time: mean=3990.40 / std=21506.09 • UU-time: mean=4246.33 / std=21489.42 • DU-time: mean=4365.40 / std=21494.63 • Total number of Backspace keys: 7 • Typing speed (keystrokes per minute): 168.15

[Word] the [Typing Features] • Duration: mean=90.67 / std=28.26 • DD-time: mean=131.83 / std=49.22 • UD-time: mean=41.17 / std=61.52 • UU-time: mean=124.17 / std=72.35 • DU-time: mean=214.83 / std=59.62 • Total number of Backspace keys: 0 • Typing speed (keystrokes per minute): 516.50

...

[Word] molecules. [Typing Features] • Duration: mean=101.92 / std=27.61 • DD-time: mean=91.69 / std=35.30 • UD-time: mean=-10.23 / std=56.46 • UU-time: mean=97.23 / std=65.89 • DU-time: mean=199.15 / std=49.47 • Total number of Backspace keys: 0 • Typing speed (keystrokes per minute): 687.22

10.2 Query-level input examples↩︎

Query-level features summarize the entire query as a single behavioral profile. Instead of computing features for each word separately, all timing intervals, typing speed, and backspace counts are aggregated across the full query.

Query: Explain the symmetry elements of molecules.

Keystroke Summary: Duration (mean/std): 109.42 / 88.84 DD-time (mean/std): 1994.44 / 14728.94 UD-time (mean/std): 1885.02 / 14727.02 UU-time (mean/std): 2057.08 / 14726.80 DU-time (mean/std): 2166.50 / 14731.55 Typing speed (kpm): 346.32 Backspace count: 10

10.3 Raw-level input examples↩︎

Raw-level features retain keystroke dynamics for each key event rather than aggregating across the entire query. For every key pressed, we record five timing metrics in milliseconds: key hold duration (Duration_key1), time between consecutive key presses (DD-time), time between a key release and the next key press (UD-time), time between consecutive key releases (UU-time), and time between the press of one key and the release of the next (DU-time).

Query: Explain the symmetry elements of molecules.

Raw Keystroke Features (excerpt): Key: E, Duration_key1=120, DD_time=95, UD_time=102, UU_time=110, DU_time=108 Key: x, Duration_key1=98, DD_time=87, UD_time=93, UU_time=101, DU_time=97 Key: p, Duration_key1=105, DD_time=92, UD_time=97, UU_time=104, DU_time=99 Key: l, Duration_key1=130, DD_time=100, UD_time=106, UU_time=113, DU_time=109 Key: a, Duration_key1=90, DD_time=85, UD_time=88, UU_time=96, DU_time=91 ... (remaining keys omitted for brevity)

11 User Study: Task and Interface Information↩︎

Before starting the study, the protocol was approved by the local Institutional Review Board (IRB). All participants provided informed consent, approved by the local Institutional Review Board (IRB), which permitted the collection and analysis of their interaction data. All users were anonymized, and all data were stored and used strictly for research purposes. All participants were compensated 22 USD, and to enhance engagement, the top five participants, based on question quality and completion, received an additional 15 USD reward.

11.1 User study interface↩︎

Figure 10: Custom web-based user study interface for capturing detailed user–LLM interaction data. Participants entered queries, self-reported their expertise level using a five-point scale (Novice\simExpert), and rated response satisfaction on a five-point Likert scale after each response.

We implemented a custom web-based interface to capture detailed user-LLM interaction data while maintaining experimental control and minimizing distractions. Each session, which lasted approximately 2 to 2.5 hours in total, was conducted on a lab-provided computer under the supervision of a study operator. For each query, participants were presented with two responses and asked to comparatively evaluate them. To reduce presentation-order bias, the responses were displayed in randomized left–right order. Participants were blind to the condition and were not informed which response came from the baseline system or the expertise-conditioned system. To further ensure a fair comparison, all responses were generated using the same decoding settings across conditions, thereby controlling for verbosity and other generation-related differences. The interface and study flow were structured as follows:

  • Task Execution. Each participant performed three distinct information-seeking tasks, each lasting 25 minutes, using the chatbot interface. Participants were given detailed written instructions for each task on printed handouts. The chatbot’s conversational state was reset between tasks to avoid carryover effects. In the experiment, participants completed three domain-specific tasks, with the task order balanced using a partial counterbalancing method.

  • Query Submission and Feedback. Before submitting each query, participants rated their familiarity with the topic using a five-level scale (Novice-Expert). A tooltip-based help system clarified the meaning of each level. After receiving the LLM’s response, participants rated their satisfaction on a mandatory five-point Likert scale (1: very unsatisfied, 5: very satisfied) using a star-rating widget.

  • Interaction Logging. The interface automatically logged all user interactions, including timestamps, queries, self-reported expertise, model responses, and satisfaction ratings for subsequent analysis.

  • Experimental Controls and Compliance. To ensure engagement and control for external aids, copy-paste functionality was disabled, and participants were required to submit a minimum of ten queries per task. The chatbot was stateless across tasks and did not retain prior interactions, which was explicitly communicated to participants to discourage meta-queries (e.g., “continue from earlier”).

After completing the three tasks, participants filled out a brief interaction survey (approximately two minutes) regarding perceived difficulty and usability, followed by a nine-item multiple-choice quiz assessing knowledge acquisition based on the investigated topics.

11.2 User study tasks↩︎

Participants completed three distinct information-seeking tasks, each designed to reflect a different academic domain and to evaluate the LLM’s effectiveness in supporting domain-specific knowledge acquisition. Each task lasted 25 minutes and was accompanied by detailed written instructions displayed within the study interface. The tasks were as follows:

  • Chemistry Participants investigated the principles of molecular symmetry and the classification of molecules into point groups. Subtasks included: (i) identifying symmetry elements such as rotation axes, centers of inversion, and mirror planes; (ii) explaining the criteria for point group classification; and (iii) discussing correlations between point groups and spectroscopic properties, including infrared (IR) and Raman activity.

  • Computer Science Participants explored two core process scheduling algorithms used in operating systems: priority scheduling and multilevel queue scheduling. Subtasks included: (i) analyzing the design and structure of priority scheduling; (ii) investigating the implementation of multilevel queue scheduling; and (iii) examining supporting mechanisms such as data structure design, time allocation methods, and priority handling logic.

  • Business Participants studied key accounting issues encountered during the preparation of consolidated financial statements. Focus areas included: (i) elimination of investments in subsidiaries against equity; (ii) recognition and treatment of goodwill or bargain purchase gains; and (iii) accounting for non-controlling interests.

11.3 Participant demographics↩︎

Table 6 summarizes the demographic and academic background information of the study participants. The collected data include age (in years), gender, nationality, major or primary academic field, and current academic year.

Table 6: Participant demographics and academic background.
Age Gender Major (Double or Minor) Academic Year
24 Male Artificial Intelligence Graduate (Master’s)
20 Female Business Administration 3rd year
21 Female Business Administration 3rd year
22 Male Business Administration 3rd year
26 Male Business Administration 4th year
22 Female Chemical Engineering Graduate (Master’s)
24 Male Chemical Engineering 4th year
24 Female Chemical and Biological Engineering 4th year
20 Female Computer Science 3rd year
21 Female Computer Science 3rd year
21 Male Computer Science 3rd year
23 Male Computer Science 3rd year
23 Male Computer Science 3rd year
24 Male Computer Science 3rd year
22 Male Computer Science 4th year
23 Female Computer Science 4th year
24 Male Computer Science 4th year
23 Female Computer Science Graduate (Master’s)
24 Male Computer Science Graduate (Master’s)
25 Female Computer Science Graduate (Master’s)
21 Female Energy Chemical Engineering 3rd year
23 Male Energy Chemical Engineering 3rd year
23 Male Energy Chemical Engineering 3rd year
23 Male Energy Chemical Engineering 3rd year
22 Female Energy Chemical Engineering 4th year
23 Female Energy Chemical Engineering 4th year
24 Male Energy Chemical Engineering 4th year
25 Female Energy Chemical Engineering Graduate (Master’s)
24 Female Energy Chemical Engineering Graduate (Master’s)
22 Female Industrial Engineering (Management Sci.) 4th year
22 Female Industrial Engineering (Management Sci.) 4th year
24 Male Industrial Engineering (Management Sci.) 4th year
21 Female Management Science 3rd year
23 Male Management Science 3rd year
27 Male Management Engineering Graduate (Master’s)
22 Male Economics 3rd year
25 Female Economics 4th year
24 Female Chemistry 4th year
24 Female Materials Science and Engineering Graduate (Master’s)
26 Male Industrial Design (Minor: Management) 4th year

11.4 Collected query expertise results↩︎

Table 7: Distribution of collected queries across self‑reported expertise levels for each domain, illustrating the coverage of expertise levels in the dataset.
Expertise Level Chemistry Computer Science Business
Novice 206 188 257
Beginner 86 72 87
Intermediate 95 69 45
Proficient 32 58 30
Expert 4 31 10

For each collected query, we recorded the query text, the user’s self‑reported expertise level, two LLM responses (baseline and expertise‑conditioned), and satisfaction ratings, along with raw keystroke logs capturing key press and release events with timestamps. In total, the dataset comprised 1270 queries spanning Chemistry, Computer Science, and Business, covering a range of expertise levels (651 Novice, 245 Beginner, 209 Intermediate, 120 Proficient, and 45 Expert queries). Table 7 shows how queries were distributed across expertise levels within each domain, indicating that most queries came from novice users, with decreasing numbers at higher expertise levels and some variation between domains.

11.5 Survey results↩︎

11.5.1 Quiz performance by self-assessed expertise↩︎

To analyze participants’ objective knowledge across domain-specific tasks, we examined quiz scores (out of 9) stratified by self-assessed expertise level for each task. Participants provided their overall expertise per task on a scale: Novice, Beginner, Intermediate, Proficient, and Expert. Given the relatively few Expert self-assessments, we combined Proficient and Expert into a higher proficiency group for analysis.

Overall, the results show a strong positive association between self-assessed domain expertise and objective knowledge, as measured by quiz scores. Across all three tasks, mean quiz performance increased monotonically with expertise level. For example, participants identifying as Proficient or Expert consistently scored above 7.0, whereas Novices averaged between 5.1 and 5.8 points. Notably, the magnitude of expertise-related differences varied by domain. The largest score gap was observed in Chemistry (Task 1), where Proficient/Expert participants averaged 7.3 compared to 5.1 among Novices (a 2.2-point difference). Computer Science (Task 2) exhibited the highest overall scores, with even Novices achieving a mean of 5.7, while Business (Task 3) showed intermediate patterns. Although the sample sizes for higher proficiency levels were small, the trend remains consistent across tasks. These results indicate that self-perceived expertise reliably predicts task-specific knowledge, while also revealing substantial domain-specific variability in baseline knowledge levels among participants.

Table 8: Mapping between full survey questions, their scale type, and the abbreviated labels used in Table [tbl:tab:subjective-ratings-expertise-updated].
Survey Question Scale (Range) Label in Results Table
My overall expertise for this task was sufficient. Likert (1–7) Task appropriateness
The difficulty of this task was appropriate relative to my ability. Likert (1–7) Task challenge
This task was an appropriate challenge for me. Likert (1–7) Task challenge
I felt immersed while performing this task. Likert (1–7) Immersion
The chatbot provided effective assistance in completing this task. Likert (1–7) LLM Helpfulness
The information provided by the chatbot was appropriate for my level of expertise. Likert (1–7) LLM Relevance
How mentally demanding was the task? NASA-TLX (0–20) Mental demand
How physically demanding was the task? NASA-TLX (0–20) Physical demand
How hurried or rushed was the pace of the task? NASA-TLX (0–20) Pace/hurriedness
How successful were you in accomplishing what you were asked to do? NASA-TLX (0–20) Task success
How hard did you have to work to achieve your level of performance? NASA-TLX (0–20) Effort needed
How insecure, discouraged, irritated, stressed, or annoyed did you feel during the task? NASA-TLX (0–20) Negative affect
Table 9: Summary of Subjective Ratings by Self-Assessed Expertise
Measure Novice Beginner Intermediate Proficient/Expert
Task appropriateness (1–7) 3.5 5.0 5.4 6.4
Task challenge (1–7) 5.0 5.2 4.8 4.2
Immersion (1–7) 4.9 5.7 5.3 5.8
LLM Helpfulness (1–7) 5.8 5.8 5.9 6.4
LLM Relevance (1–7) 4.2 5.8 5.1 3.2
Mental demand (0–20) 11.6 7.8 6.9 6.2
Physical demand (0–20) 4.2 3.0 3.4 3.2
Pace/hurriedness (0–20) 6.9 5.9 6.5 5.9
Task success (0–20) 9.2 7.8 7.8 9.5
Effort needed (0–20) 12.2 12.2 11.1 13.8
Negative affect (0–20) 7.8 4.7 4.8 3.1

11.5.2 Task experience and cognitive load by self-assessed expertise↩︎

Participants rated multiple aspects of their task experience using a combination of standardized and custom measures. Table 8 details the full survey questions, their scale types, and the abbreviated labels used in reporting, while Table 9 summarizes mean ratings for each measure stratified by self-assessed expertise group. The measures included perceptions of task appropriateness, difficulty, and immersion, as well as the perceived helpfulness and relevance of LLM assistance, all rated on 7-point Likert scales. Additionally, six NASA Task Load Index (NASA-TLX) subscales were administered, capturing cognitive and emotional workload dimensions (e.g., mental demand, effort, and negative affect) on 0–20 scales.

Consistent with expectations, self-assessed expertise was systematically associated with participants’ subjective task experiences (Table 9). Participants with higher expertise generally perceived the tasks as better matched to their abilities and reported lower levels of cognitive workload. In particular, Novice participants reported higher mental demand than Proficient/Expert participants (11.6 vs.). Negative affect (e.g., stress and frustration) likewise decreased with increasing expertise (7.8 vs.), indicating a more positive emotional experience among more experienced users. Perceived task success showed a modest increase with expertise (9.2 for Novices vs. for Proficient/Expert participants). In contrast, effort ratings were comparable across expertise levels, with Proficient/Expert participants reporting slightly higher effort (13.8) than Novices (12.2), despite lower reported mental demand. Ratings of LLM helpfulness and relevance showed relatively small differences across expertise levels(5.8–6.4), suggesting broadly consistent perceptions of system support. Overall, these results highlight systematic expertise-related differences in cognitive workload and affect, illustrating how participants’ perceived proficiency shaped their subjective task experience.

11.6 Follow-up Evaluation↩︎

For the follow-up study, we recontacted participants from the original study who had agreed to be contacted again for future research. Among those we were able to reach, 16 returning participants completed the follow-up evaluation and were included in the analysis. Participants received an additional compensation of 15 USD for completing the study.

In this follow-up evaluation, participants rated responses to queries they had originally written in the main study. For each query, they were shown responses from three conditions: (1) a baseline response without expertise conditioning, (2) a response conditioned on self-reported expertise, and (3) a response conditioned on  ExPerT-predicted expertise. The prompts used for expertise-conditioned generation were identical to those described in Appendix  9, with the predicted-expertise condition using the expertise level inferred by  ExPerT instead of self-reported expertise. The order of the conditions was randomized, and the identities of the conditions were blinded to participants. Participants rated each response on a 5-point satisfaction scale. This design allowed us to assess whether the benefits of expertise-conditioned generation persisted when the expertise signal was inferred by the model rather than explicitly provided by the user.

Figure 11: User satisfaction scores for each participant across the without expertise, self-reported expertise, and predicted expertise conditions.

As shown in Figure  11, most participants preferred responses that incorporated expertise information over those that did not. At the individual level, both the reported-expertise and predicted-expertise conditions generally received higher satisfaction scores than the no-expertise condition, indicating that expertise-aware responses were more positively evaluated overall. While some participant-level variation remained, the advantage of the expertise-based conditions was consistently observed across a broad set of users rather than concentrated in only a few cases. Furthermore, the reported-expertise and predicted-expertise conditions were competitive, with many participants assigning similarly high ratings to both. This pattern suggests that predicted expertise can approximate the benefit of reported expertise in supporting user satisfaction. Taken together, these findings indicate that incorporating expertise information is beneficial at the participant level, and that inferred expertise may provide a practical alternative when self-reported expertise is unavailable.

12 Baselines for expertise inference↩︎

To benchmark our proposed approach, we implemented random guess baseline and two baseline expertise classification systems following prior work on persona-aware LLM prompting [10], [20]: a persona-based baseline and a session-based baseline. We additionally report a conventional supervised classifier baseline for completeness, although it is intended primarily as a supplementary reference point.

12.1 Baseline Details↩︎

12.1.0.1 Random guess baseline

For reference, we compute the expected performance of a random predictor that samples labels uniformly from the five-point ordinal expertise scale \(\mathcal{Y} = \{1, 2, 3, 4, 5\}\). Assuming that the true label \(Y\) is fixed and the prediction \(\hat{Y}\) is drawn uniformly at random from \(\mathcal{Y}\), the expected mean squared error (MSE) and mean absolute error (MAE) are given by \[\mathbb{E}\!\left[(Y - \hat{Y})^2\right] = \frac{1}{5} \sum_{y=1}^{5}\frac{1}{5}\sum_{\hat{y}=1}^{5} (y-\hat{y})^2 = 4.0,\] \[\mathbb{E}\!\left[|Y - \hat{Y}|\right] = \frac{1}{5} \sum_{y=1}^{5}\frac{1}{5}\sum_{\hat{y}=1}^{5} |y-\hat{y}| = 1.6.\] These values represent a random guess baseline, which any model leveraging semantic or behavioral information should outperform.

12.1.0.2 Persona-based baseline

We implement a persona-aware classifier that predicts user expertise using both query text and structured persona metadata (age, gender, nationality, native and foreign languages, academic major, study year, and self-reported LLM usage). For each query, the persona attributes are presented in the system prompt and the query text in the user prompt (see Box [box:persona-prompt]). The model outputs one of five ordered labels (Novice, Beginner, Intermediate, Proficient, Expert) along with a concise justification.

<core_identity> You are an AI classifier that determines a user’s expertise level. </core_identity>

<persona_context> Persona: - Age: age - Gender: gender - Nationality: nationality - Native language: native_language - First foreign language: first_foreign_language - Other languages: other_languages - Major: major - Year: year - LLM usage frequency: llm_usage </persona_context>

<general_rules> • NEVER use meta-phrases (e.g., "let me help you", "I can see that"). • ALWAYS be specific and grounded in observable evidence. • Do NOT infer personal traits beyond what is required for classification. • START IMMEDIATELY WITH THE ANSWER – ZERO INTRODUCTORY TEXT. <general_rules>

<general_instructions> Classify the user into exactly one category: Novice, Beginner, Intermediate, Proficient, Expert. Do not infer unobservable mental states. </general_instructions>

<expertise_scale> • Novice: A subject novice is a person who has little or no familiarity with the topic or domain of the conversation. • Beginner: A subject beginner is someone who has little prior knowledge or experience in the topic or domain of the conversation. • Intermediate: A subject intermediate is someone who has some basic knowledge or familiarity with the topic of the conversation, but not enough to be considered an expert or even proficient. • Proficient: A subject proficient is someone who can apply relevant concepts and terminology from the conversation to different scenarios and problems. • Expert: A subject expert is someone who has a deep and comprehensive understanding of the topic or field of the conversation and can use specialized terms and references to communicate their knowledge. </expertise_scale>

<classification_procedure> Before outputting the final classification, follow this reasoning process internally: Step 1) Consider the full persona of the user (age, gender, nationality, native and foreign languages, major, academic year, and frequency of LLM usage). Step 2) Evaluate how this persona might correlate with their knowledge depth and experience relevant to the query topic. Step 3) Compare the style, complexity, and focus of the query against typical expertise-level patterns. Step 4) Combine the persona context and query characteristics to infer the most likely expertise level. Step 5) Decide the most appropriate expertise level. </classification_procedure>

<output_format> Output must be structured exactly in this format:

<classification> <level>One of: Novice, Beginner, Intermediate, Proficient, Expert</level> <reason>Brief explanation of the reasoning steps and observed indicators.</reason> </classification> </output_format>

Given the following user input and persona information, determine the user’s expertise level. Query: USER_QUERY Expertise Level:

All experiments used OpenAI’s gpt-4.1 with temperature=0.0, top_p=1.0, and a maximum output length of 512 tokens to ensure deterministic outputs without truncation.

12.1.0.3 Session-based baseline

We implement a session-level classifier that predicts user expertise using only the linguistic content of all queries entered by a participant for a given task. Each session (grouped by user_id and task) is concatenated into a single text block and classified using GPT-4.1 with temperature=0.0, top_p=1.0, and a 512-token output cap to ensure deterministic responses. We adopt the session-level prompt template from Palta et al. [20] without modification, where the model infers an overall expertise label (Novice-Expert) based solely on aggregated query text.

Predictions are evaluated against ground-truth expertise labels obtained by aggregating participants’ self-assessed query-level ratings within each session.

12.1.0.4 IDL baseline

We implement an IDL-based baseline that adapts the core principles of In-Dialogue Learning (IDL) [14] to expertise inference, where stable user characteristics are induced from accumulated dialogue history without relying on predefined profiles. The baseline uses LLaMA-2-7B-Chat as the backbone model and operates on query histories spanning multiple turns and multiple dialogue sessions for each user-task pair. For each user, dialogue sessions are embedded using a sentence-level encoder and clustered via \(k\)-means to identify persona-relevant session groups. Within each cluster, reference sessions are dynamically reordered by minimizing inter-session conversational edit distance, producing a coherent dialogue sequence. The model is then trained using a Mutual Supervised Learning (MSL) objective following the IDL framework, with LoRA-based fine-tuning, and subsequently aligned via DPOC-based preference optimization to mitigate persona inconsistency and hallucination. At inference time, the LoRA- and DPOC-aligned model is provided with the concatenated dialogue history and prompted to infer the user’s overall expertise level on a five-point ordinal scale (Novice-Expert).

12.1.0.5 AI Persona baseline

We implement an AI Persona baseline following the life-long semantic personalization framework proposed in AI Persona [9]. This approach models user characteristics as an explicit persona state that is incrementally updated from accumulated interaction history, under the assumption that stable user attributes can be inferred through repeated dialogue with a language model. Concretely, for each user, we maintain a structured persona representation initialized from demographic and background information. Persona updates are performed by aggregating interaction histories over multiple sessions and prompting GPT-4.1 to revise the persona fields accordingly. Following the original AI Persona protocol, persona updates are triggered every \(k=3\) sessions, where all query—response pairs within the update window are concatenated and provided to the model for persona revision. For expertise prediction, the current persona state is combined with the user’s query and provided to GPT-4.1, which is prompted to classify the user’s expertise level on a five-point ordinal scale (Novice to Expert). All persona updates and expertise predictions are performed using GPT-4.1 with temperature set to 0.0, top_p set to 1.0, and a maximum output length of 512 tokens to ensure deterministic behavior. This baseline relies exclusively on semantic information encoded in dialogue content and persona representations, and does not incorporate query-level behavioral signals or fine-grained temporal features.

12.2 Conventional Supervised Classifier Baselines↩︎

To further examine whether  ExPerT’s gains stem from its in-context semantic-behavioral inference rather than from multimodal input availability alone, we additionally implemented three conventional supervised classifier baselines using the same query text and keystroke-derived inputs: (i) BiLSTM(text) + FFN(keystroke_flat)  [48], [49], (ii) Word2Vec(text) + FFN(keystroke_flat)  [50], and (iii) BiLSTM(text) + BiLSTM(keystroke_seq)  [51] with attention pooling and late fusion (concatenation followed by an MLP). These baselines are included as additional supervised reference points.

12.2.0.1 Inputs and architectures.

For all baselines, the text modality is constructed from the query text, and the behavioral modality is constructed from the same keystroke-derived signals used in our main task. The BiLSTM(text) + FFN(keystroke_flat) baseline encodes the query text with a BiLSTM and flattened keystroke features with a feed-forward network, followed by fusion for prediction. The Word2Vec(text) + FFN(keystroke_flat) baseline represents the query text using averaged Word2Vec embeddings and combines it with an FFN encoding of flattened keystroke features. The BiLSTM(text) + BiLSTM(keystroke_seq) baseline encodes the query text and keystroke sequence with separate BiLSTMs, applies attention pooling, and performs late fusion via concatenation followed by an MLP. In all cases, the final prediction target is our 5-level expertise label.

12.2.0.2 Evaluation setting.

We evaluate these supervised baselines using the individual split, where each user’s samples are divided into train/validation/test sets with a 70/15/15 ratio. Since this setting is the closest supervised counterpart to our within-user evaluation, we compare these results against  ExPerT under the within-user 10-shot setting.

12.2.0.3 Results.

Table 10 reports the results in terms of mean absolute error (MAE) and mean squared error (MSE), where lower values indicate better performance. Among the supervised baselines, BiLSTM + FFN achieves the best MAE, while Word2Vec + FFN achieves the best MSE. However, all three supervised baselines remain substantially behind  ExPerT, indicating that  ExPerT’s gains are not explained solely by access to both semantic and behavioral inputs, but are associated with its in-context LLM-based inference mechanism.

Table 10: Comparison between conventional supervised classifier baselines and  . Lower MAE and MSE indicate better performance.
Model MAE \(\downarrow\) MSE \(\downarrow\)
BiLSTM + FFN 0.865 2.032
Word2Vec + FFN 0.902 1.894
BiLSTM + BiLSTM 1.026 2.216
  0.398 0.698

13 Per-class metrics↩︎

We additionally report per-class F1 scores with 95% bootstrap confidence intervals (1,000 resamples with replacement) in Table 11. The overall macro-F1 is 0.6102 with 95% CI [0.5682, 0.6479].

Performance is highest in the Novice class and lowest in the Expert class. The relatively lower F1 score and wider confidence interval for the Expert class may be partly explained by its underrepresentation in the dataset (n=45), which is substantially smaller than the other classes.

Table 11: Per-class F1 scores with 95% bootstrap confidence intervals from 1,000 resamples with replacement. Overall macro-F1 is 0.6102 with 95% CI [0.5682, 0.6479].
Metric Novice (\(n\)=651) Beginner (\(n\)=245) Intermediate (\(n\)=209) Proficient (\(n\)=120) Expert (\(n\)=45)
F1 0.8558 0.5365 0.6186 0.6114 0.4286
95% CI [0.8349, 0.8757] [0.4797, 0.5861] [0.5669, 0.6667] [0.5366, 0.6845] [0.2727, 0.5683]

8pt

14 In-depth Statistical Analyses of User Keystroke Behavior↩︎

14.1 Expertise-level Differences↩︎

Table 12: Kruskal-Wallis test results for expertise-level differences in keystroke-based behavioral features. Keystroke timing features are aggregated at the word level (same as model input feature), yielding both mean and standard deviation statistics, while typing speed and backspace count are represented by single word-level values.
Metric \(p\)-value H-statistic
2-3 (lr)4-5 Mean Std Mean Std
Key Duration \(<0.001\) 68.42 \(<0.001\) 37.10
DD time \(<0.001\) 263.45 \(<0.001\) 101.42
UD time \(<0.001\) 271.18 \(<0.001\) 69.30
UU time \(<0.001\) 207.17 \(<0.001\) 60.28
DU time \(<0.001\) 116.50 \(<0.001\) 82.16
Typing Speed \(<0.001\) 262.84
Backspace Count \(<0.001\) 58.79

To assess whether keystroke-based behavioral features differ statistically across expertise levels, we conducted a Kruskal-Wallis test [52], a non-parametric method suitable for comparing multiple groups with potentially unequal sample sizes and non-normal distributions. To ensure consistency with the features used by ExPerTand to mitigate dependence among raw keystroke events, we performed this analysis on word-level aggregated behavioral features, treating each typed word as a single behavioral unit. The analysis was conducted across all expertise levels defined in our study.

We examined a range of keystroke metrics, including key duration, Down-Down (DD), Up-Down (UD), Up-Up (UU), and Down-Up (DU) inter-key intervals, as well as typing speed and backspace count. The results show robust and highly significant differences across expertise groups for nearly all behavioral features (all \(p < 0.001\)). Corresponding H-statistics indicate clear separation between expertise-level distributions, with larger values reflecting stronger group-wise differentiation.

These results provide statistical evidence that keystroke dynamics systematically vary with user expertise. In particular, higher expertise levels are associated with faster, more stable typing patterns and fewer correction behaviors, consistent with increased fluency and conceptual familiarity. This expertise-aligned structure of behavioral signals supports our claim that behavioral cues complement semantic information by mitigating ambiguity in query text and enabling more accurate expertise inference.

14.2 User-level Differences↩︎

Table 13: One-way ANOVA results for user-level differences in keystroke-based behavioral features using a calibration dataset.
Metric \(p\)-value F-statistic
Key Duration \(< 0.001\) 42.06
DD time \(0.006\) 1.66
UD time \(0.011\) 1.59
UU time \(0.006\) 1.66
DU time \(0.002\) 1.77

6pt

To further investigate individual variability in keystroke behavior, we analyzed whether keystroke features differ significantly across users. We conducted a one-way ANOVA using a calibration dataset in which each participant typed a standardized paragraph before the main study, allowing for controlled comparison of typing behavior independent of task content.

The analysis included multiple keystroke features, such as key duration and DD, UD, UU, and DU inter-key intervals. The results reveal significant between-user differences for all examined features (all \(p < 0.05\)), with F-statistics indicating substantial separation among users. These findings confirm that keystroke behaviors are highly user-specific, consistent with prior studies on typing dynamics [36][38].

This strong user-level variability explains our empirical observation that within-user few-shot inference consistently outperforms cross-user settings. Because each user’s typing rhythm and fluency form statistically distinct distributions, models trained across users tend to average away meaningful individual differences, leading to degraded performance. In contrast, within-user examples preserve user-specific behavioral patterns, enabling more effective personalization.

15 Full Examples of Model Predicted Expertise and Reasoning↩︎

This appendix provides full qualitative examples illustrating how  ExPerT predicts user expertise and reasons over semantic and behavioral cues at the query level (Table 14. For each example, we present the original user input, the predicted expertise level, and the corresponding reasoning process that integrates semantic signals from the query text with behavioral signals derived from keystroke interactions. These examples complement the quantitative and statistical analyses in the main paper by offering concrete, case-level evidence of how  ExPerT adapts its inference to different users and contexts. Together, they demonstrate how the proposed framework resolves semantic ambiguity, leverages user-specific behavioral patterns, and produces expertise-aware predictions in practice.

Table 14: A full qualitative case examples illustrating ’s semantic-behavioral integration.
Query Tell me everything that you know about priority scheduling and multilevel queue scheduling Can you explain in detail correlation with spectroscopic properties(e.g. IR and Raman activity)?
User-reported Expert Beginner
  (ours) Prediction: Expert.
Reason: The query requests ""everything you know about priority scheduling and multilevel queue scheduling,"" which is a broad, open-ended prompt typical of users with high confidence and deep interest in comprehensive coverage. The user uses precise technical terms (""priority scheduling,"" ""multilevel queue scheduling"") without hesitation or correction in those segments, as shown by stable keystroke metrics (low backspace, consistent timing, high typing speed). This matches the pattern in Example 7, where similar open-ended, technical queries and fluent typing are associated with Expert-level users. There is no evidence of definition-seeking or conceptual uncertainty. The baseline for this user, given the query style and typing, is Expert, and no DELTA adjustment is warranted.
Prediction: Beginner.
Reason: Baseline from prior queries (see Example 10) is Beginner, with consistent requests for careful explanation and explicit self-identification as a beginner. The current query uses technical terms (""correlation with spectroscopic properties"", ""IR"", ""Raman activity"") but only in the context of asking for detailed explanation, not applying or linking concepts. Typing behavior on technical segments is stable (no strong hesitation or correction), so no negative adjustment is warranted, but there is also no evidence for higher conceptual mastery or application. Final level remains Beginner.
Semantic-only Prediction: Novice.
Reason: he query is broad and non-specific, lacking any technical terminology or focused questions. The user requests ""everything"" about the topics, which is characteristic of someone with little or no familiarity seeking a general overview.
Prediction: Beginner.
Reason: The user requests a detailed explanation of the correlation between spectroscopic properties and provides examples (IR and Raman activity), but does not use specialized terminology or demonstrate deeper understanding of the underlying concepts. The phrasing suggests curiosity and a need for foundational explanation, consistent with a beginner level.
Behavior-only Prediction: Proficient.
Reason: Typing speed is consistently high (most words above 300 kpm, several above 700 kpm), with low to moderate backspace usage (only 3 total across 12 words), and moderate variability in timing features. The user demonstrates fluent, confident typing with low error correction, and the timing metrics (mean and std) are within the range of proficient or expert users in the examples. However, the variability in some timing features (e.g., UD-time std up to 77.60, 133.84, 223.49) is higher than typical expert patterns, and the user does not show the extremely low error rates or the highly consistent timing seen in expert examples. This places the user solidly in the proficient category, with strong fluency but not the hallmark consistency of an expert.
Prediction: Proficient.
Reason: Typing speed is consistently high (276–983 keystrokes per minute), with low to moderate backspace usage (zero throughout), and moderate variability in timing features. The user demonstrates fluent, confident typing with low error correction, and the timing metrics (mean and std) are stable and similar to those seen in proficient or expert examples. However, the user does not show the extremely low variability or the highly consistent, advanced timing patterns typical of experts in the provided examples. The overall pattern is more advanced than intermediate but does not reach the expert level.
s

16 Qualitative Comparison of Baseline and  ExPerT Responses↩︎

Tables 15 to 19 show examples of baseline and  ExPerT responses at different expertise levels.

Table 15: Qualitative examples comparing baseline and expertise-conditioned ( ) responses in Novice.
Example 1 — Chemistry Query (Expertise: Novice, P10):
User Query I do not understand what “molecular symmetry” means. Please explain it in a simple and intuitive way, using easy examples, as if you were explaining it to an elementary school student.
Without Expertise
(baseline)
“Of course. I will explain “molecular symmetry” in a very simple way, using familiar and easy examples that even an elementary school student can understand. First, think about a mirror. When you place a mirror in front of your face, you see the same face reflected back. This happens because your face is reflected symmetrically in the mirror. In general, symmetry means that when something is divided into two parts, the two sides look the same or very similar. For example, a butterfly’s wings look almost identical on the left and right sides, so we say that a butterfly has symmetry. Now, what does “molecular symmetry” mean? A molecule is an extremely small particle. The air we breathe, the water we drink, and the food we eat are all made of molecules. Molecules also have shapes. Some molecules, like a butterfly, look the same on the left and right sides. Other molecules look the same even when you rotate them. For example, a water molecule (H₂O) is made of one oxygen atom and two hydrogen atoms. The hydrogen atoms are attached at an angle, so the shape is slightly bent, and the symmetry is not perfect. In contrast, a carbon dioxide molecule (CO₂) has a carbon atom in the center and identical oxygen atoms on both sides, which makes it highly symmetric. In summary, molecular symmetry refers to whether the shape of a molecule looks the same when it is reflected in a mirror or rotated. This concept is important because scientists use molecular symmetry to understand and predict the properties of molecules.”
With Expertise
( , ours)
“I will explain “molecular symmetry” in a very simple way. First, a molecule is a small particle that makes up matter. For example, even a single drop of water contains an enormous number of water molecules. A water molecule is called H₂O, meaning it is made of two hydrogen atoms and one oxygen atom. Next, let us think about what symmetry means. Symmetry refers to a situation in which an object looks the same on both sides when it is divided in half. Common examples include butterfly wings, human faces (approximately), and heart shapes. When the right and left sides look the same, we say that the object is symmetric. Molecules are very small, but they also have shapes. If a molecule looks the same when you rotate it or reflect it, we say that it has molecular symmetry. For example, a water molecule (H₂O) has two hydrogen atoms attached to a central oxygen atom, but the shape is bent, which slightly breaks the symmetry. On the other hand, a carbon dioxide molecule (CO₂) has the structure O = C = O, with identical oxygen atoms on both sides of the carbon atom. Because of this, its shape remains the same when viewed from either side, making it a highly symmetric molecule. In simple terms, molecular symmetry means checking whether a molecule looks the same when it is rotated or flipped. This symmetry can influence the properties of a molecule, such as how it interacts with light or how it reacts with other substances.”

As shown in Table 15, the  ExPerT response demonstrates a deliberate restructuring of the explanation to match the cognitive constraints of novice users. Rather than merely simplifying terminology,  ExPerT decomposes the target concept into a sequence of prerequisite notions (e.g., molecule → symmetry → molecular symmetry), thereby explicitly scaffolding understanding. This layered progression contrasts with the baseline response, which presents a coherent but largely narrative explanation without clearly isolating conceptual dependencies. The insight here is that  ExPerT does not only simplify content for novices, but actively reorganizes knowledge to minimize abstraction and reduce cognitive load, enabling comprehension without prior domain assumptions.

Table 16: Qualitative examples comparing baseline and expertise-conditioned ( ) responses in Beginner.
Example 2 — Business Query (Expertise: Beginner, P15):
User Query So, for example, if a parent company invests 10 billion won in a subsidiary and the subsidiary’s net assets are 8 billion won, then a 2 billion won operating right will be generated. Will this 2 billion won be recorded in the subsidiary’s accounting books?
Without Expertise
(baseline)
“This is a good question. Below is an explanation of goodwill arising in the relationship between a parent company and a subsidiary under accounting principles. In summary, goodwill of KRW 2 billion is not recorded in the subsidiary’s accounting books (), but is recognized only in the parent company’s consolidated financial statements (). To explain why, when a parent company acquires a subsidiary for KRW 10 billion while the subsidiary’s net assets (assets minus liabilities) amount to KRW 8 billion, the parent company pays more than the book value of the subsidiary’s net assets. The difference of KRW 2 billion represents goodwill, which reflects intangible values such as brand reputation, customer relationships, and know-how. However, this goodwill is not included in the subsidiary’s own accounting records, as the subsidiary records only its own assets, liabilities, and equity. The goodwill of KRW 2 billion is recognized as an asset only when the parent company prepares consolidated financial statements and accounts for the acquisition of the subsidiary. In conclusion, goodwill does not appear in the subsidiary’s books (), is recorded as an equity investment in the parent company’s separate financial statements (), and is recognized as a goodwill asset of KRW 2 billion in the parent company’s consolidated financial statements ()."
With Expertise
( , ours)
“This is a good question. The key concept here is the distinction between consolidated financial statements and separate financial statements. Consider the following situation: a parent company acquires the shares of a subsidiary for KRW 10 billion, and the subsidiary’s net assets amount to KRW 8 billion, resulting in a difference of KRW 2 billion that corresponds to goodwill. The core question is whether this KRW 2 billion of goodwill is recorded in the subsidiary’s accounting books. The answer is no. Goodwill is not recorded in the subsidiary’s books. The subsidiary prepares its accounting records from its own perspective, recognizing only its own assets and liabilities, and the price paid by an external investor to acquire its shares is not relevant from the subsidiary’s standpoint. In contrast, the parent company pays an amount exceeding the subsidiary’s net assets at the time of acquisition, and this excess amount, calculated as KRW 10 billion minus KRW 8 billion, is recognized as goodwill in the parent company’s consolidated financial statements. In simple terms, goodwill is not recorded in the subsidiary’s separate financial statements () or in the parent company’s separate financial statements (), but is recognized as a KRW 2 billion goodwill asset in the consolidated financial statements of the parent and subsidiary (), which are prepared as if the two entities were a single economic entity.”

As shown in Table 16, the  ExPerT response shifts the explanatory focus from outcome reporting to perspective-oriented reasoning. Specifically, the  ExPerT response foregrounds the distinction between separate and consolidated financial statements before addressing the treatment of goodwill, making the underlying accounting logic explicit. By contrast, the baseline response primarily states where goodwill is recorded, offering limited insight into why that treatment arises. This indicates that, at the beginner level,  ExPerT emphasizes conceptual framing and viewpoint alignment, helping users internalize domain-specific reasoning patterns rather than memorizing isolated results.

Table 17: Qualitative examples comparing baseline and expertise-conditioned ( ) responses in Intermediate.
Example 3 — Computer Science Query (Expertise: Intermediate, P10):
User Query In operating systems, it seems that Round Robin scheduling is used not only in FCFS-based scheduling but also within priority scheduling and multilevel queue scheduling. Please explain this clearly with simple examples.
Without Expertise
(baseline)
“Priority scheduling and multilevel queue scheduling are representative scheduling algorithms used in operating systems to efficiently manage multiple processes. In both approaches, processes are organized into queues, and different scheduling policies can be applied within each queue. In addition to First-Come, First-Served (FCFS), Round Robin (RR) scheduling may also be used. Round Robin assigns a fixed time quantum to each process and executes processes in a cyclic order. Consider the following example. Suppose there are three processes in the system: P1 with high priority, P2 with medium priority, and P3 with low priority. Each priority level corresponds to a separate queue, and each queue uses a different scheduling policy. The highest-priority queue uses Round Robin with a time quantum of 2 ms, the medium-priority queue uses FCFS, and the lowest-priority queue uses Round Robin with a time quantum of 4 ms. Assume that P1 arrives at time 0 ms with a burst time of 5 ms in the highest-priority queue, P2 arrives at time 1 ms with a burst time of 4 ms in the medium-priority queue, and P3 arrives at time 2 ms with a burst time of 8 ms in the lowest-priority queue. Since the highest-priority queue is always selected first, P1 executes using Round Robin until completion. Only after the highest-priority queue becomes empty does P2 execute using FCFS, followed by P3 executing with Round Robin in the lowest-priority queue. This example illustrates that Round Robin operates only within individual queues, while the selection among queues is determined by priority. In multilevel queue scheduling, different scheduling policies such as FCFS or Round Robin can be applied independently within each queue, depending on the characteristics of the processes assigned to that queue.”
With Expertise
( , ours)
“Priority scheduling and multilevel queue scheduling operate differently, but both can incorporate Round Robin (RR) scheduling as an internal mechanism. Round Robin assigns each process an equal time slice, allowing processes to share the CPU in a fair and cyclic manner. In multilevel queue scheduling, processes are classified into separate queues based on their characteristics, and each queue may use a different scheduling algorithm. For example, a system may use FCFS for real-time processes, Round Robin for interactive processes, and FCFS or Shortest Job First for background batch jobs. Within a queue that uses Round Robin, processes take turns executing for a fixed time quantum, while the scheduling order among queues is determined by their priority. Similarly, in priority scheduling, the CPU is allocated to processes with higher priority first. However, when multiple processes share the same priority level, Round Robin scheduling can be applied among those processes to ensure fairness. For instance, if several processes have identical priority values, they can be scheduled in a Round Robin fashion with a fixed time slice. In summary, Round Robin is commonly used to provide fairness either within a specific queue in multilevel queue scheduling or among processes with the same priority in priority scheduling. This combination allows operating systems to balance responsiveness and efficiency while respecting priority constraints.”

As shown in Table 17, the  ExPerT response transitions from procedural illustration to rule-based abstraction. While the baseline response relies on a detailed scheduling scenario to demonstrate how Round Robin operates within priority and multilevel queue scheduling,  ExPerT extracts general principles (e.g., Round Robin as an intra-queue fairness mechanism or as a tie-breaking strategy among equal-priority processes). The key insight is that  ExPerT adapts to intermediate users by prioritizing transferable reasoning: explanations are structured so that the user can apply the same logic to unseen system configurations, rather than reproducing a single execution trace.

Table 18: Qualitative examples comparing baseline and expertise-conditioned ( ) responses in Proficient.
Example 4 — Computer Science Query (Expertise: Proficient, P17):
User Query Give examples of priority scheduling and multilevel queue scheduling.
Without Expertise
(baseline)
“Of course. First, I will briefly explain each scheduling method and then provide corresponding examples. 1. Priority Scheduling Concept: Priority scheduling assigns a priority to each process and allocates the CPU to the process with the highest priority first. In many systems, a smaller numerical value indicates a higher priority. Example: Scenario: Assume the following four processes exist in the system. Process P1 arrives at time 0 with a burst time of 5 and priority 2; P2 arrives at time 1 with a burst time of 3 and priority 1; P3 arrives at time 2 with a burst time of 8 and priority 4; and P4 arrives at time 3 with a burst time of 6 and priority 3. A lower numerical priority value indicates a higher priority. If only priority values were considered, the order would be P2, P1, P4, and P3. However, when arrival time is also considered, the scheduler selects the highest-priority process among those that have already arrived. The actual scheduling order under non-preemptive priority scheduling is as follows: at time 0, P1 starts executing; at time 5, P2 executes since it has the highest priority among the arrived processes; at time 8, P4 executes; and at time 14, P3 executes. Note that in the preemptive version of priority scheduling, if a process with a higher priority arrives later, it can interrupt the currently running process and take over the CPU. 2. Multilevel Queue Scheduling Concept: Multilevel queue scheduling classifies processes into multiple queues based on their characteristics, assigns different scheduling algorithms to each queue, and may also define priorities among the queues themselves. Example: Suppose the system has three queues. Queue 1 contains system processes with the highest priority and uses First-Come, First-Served scheduling. Queue 2 contains interactive processes and uses Round Robin scheduling with a time quantum of 4. Queue 3 contains batch jobs and uses First-Come, First-Served scheduling. Assume Queue 1 contains process P1 with a burst time of 3, Queue 2 contains process P2 with a burst time of 10, and Queue 3 contains process P3 with a burst time of 15. With inter-queue priorities applied, P1 executes first, followed by P2, and finally P3. The execution proceeds as follows: from time 0 to 3, P1 completes execution; from time 3 to 7, P2 executes its first time slice, leaving 6 units of remaining time; from time 7 to 11, P2 executes its second time slice, leaving 2 units; from time 11 to 13, P2 executes its third time slice and completes; from time 13 to 28, P3 executes. Summary of differences: Priority scheduling determines execution order based on per-process priority values within a single queue and may be preemptive or non-preemptive, whereas multilevel queue scheduling uses multiple queues organized by process type, with different scheduling algorithms and priorities assigned to each queue.”
With Expertise
( , ours)
“Certainly. Below is an explanation of priority scheduling and multilevel queue scheduling, along with illustrative examples. 1. Priority Scheduling Concept: Priority scheduling assigns a priority to each process, and the CPU executes the process with the highest priority first. Depending on the system, a higher priority may be represented by a smaller or larger numerical value. Priorities may be static or dynamic. In non-preemptive priority scheduling, a running process retains the CPU until it finishes, whereas in preemptive priority scheduling, the arrival of a higher-priority process causes the currently running process to be suspended. Example: Consider three processes. Process P1 arrives at time 0 ms with a burst time of 5 ms and priority 2; process P2 arrives at time 1 ms with a burst time of 3 ms and priority 1; process P3 arrives at time 2 ms with a burst time of 1 ms and priority 3, where a smaller number indicates a higher priority. Under preemptive priority scheduling, P1 begins execution at time 0. At time 1, P2 arrives with a higher priority than P1, so P1 is preempted and P2 executes. At time 4, P2 completes and P1 resumes execution. At time 9, P1 completes and P3 executes. 2. Multilevel Queue Scheduling Concept: Multilevel queue scheduling divides processes into multiple categories, such as interactive processes, user applications, and background tasks, and applies an independent scheduling algorithm to each queue. Priorities also exist among the queues, such that a lower-priority queue is executed only when all higher-priority queues are empty. Representative queue classifications include Queue 0 for interactive processes using Round Robin scheduling, Queue 1 for user processes using Shortest Job First scheduling, and Queue 2 for background applications using First-Come, First-Served scheduling. Example: Process P1 is an interactive user process in Queue 0 with Round Robin scheduling and a time quantum of 2 ms; P2 is a user application in Queue 1 using Shortest Job First; and P3 is a background backup task in Queue 2 using First-Come, First-Served scheduling. In execution, P1 in Queue 0 runs first for 2 ms. Once Queue 0 becomes empty, the scheduler moves to Queue 1 and executes P2. Only after Queue 1 finishes does P3 execute, since Queue 2 has the lowest priority. In summary, priority scheduling determines execution order by assigning explicit priorities to individual processes, whereas multilevel queue scheduling separates processes by type and assigns different algorithms and priorities to each queue.”

As shown in Table 18, the  ExPerT response emphasizes conceptual taxonomy and awareness of the design space. Instead of extending procedural examples,  ExPerT explicitly categorizes scheduling policies along orthogonal dimensions such as static versus dynamic priorities and preemptive versus non-preemptive execution. The baseline response, although comprehensive, remains example-heavy and less explicit about these structural distinctions. This suggests that  ExPerT aligns with proficient users’ expectations by highlighting comparative frameworks and architectural trade-offs, supporting analytical reasoning rather than operational understanding alone.

Table 19: Qualitative examples comparing baseline and expertise-conditioned ( ) responses in Expert.
Example 5 — Chemistry Query (Expertise: Expert, P23):
User Query When classifying point groups based on molecular symmetry, is it correct that infrared (IR) spectroscopy probes changes in the dipole moment, while Raman spectroscopy probes changes in polarizability, and that peaks are observed at the corresponding vibrational frequencies that satisfy these conditions?
Without Expertise
(baseline)
“Yes, this understanding is correct. When molecular symmetry and point group theory are applied, it becomes possible to predict which vibrational modes of a molecule are observable using different spectroscopic techniques such as infrared (IR) and Raman spectroscopy. Infrared spectroscopy detects vibrational modes that induce a change in the molecular dipole moment, denoted as \(\Delta \mu\). For a vibrational mode to be IR-active, the vibration must produce a time-dependent change in the dipole moment of the molecule. Typical examples include asymmetric stretching and asymmetric bending modes. Raman spectroscopy, in contrast, detects vibrational modes that cause a change in the molecular polarizability, denoted as \(\Delta \alpha\). In this case, the key factor is how the electronic cloud of the molecule is distorted during vibration. A vibrational mode is Raman-active only if it produces a modulation of the polarizability. Symmetric stretching modes are common examples of Raman-active vibrations. As a result, peaks observed at specific vibrational frequencies in IR and Raman spectra arise from different physical activation conditions. By using point group theory and character tables, one can determine which vibrational modes are IR-active and which are Raman-active, allowing theoretical predictions to be directly compared with experimental observations. For example, carbon dioxide (CO\(2\)) is a linear molecule belonging to the \(D{\infty h}\) point group. Some of its vibrational modes are IR-active but Raman-inactive, while others are Raman-active but IR-inactive. This complementarity explains why IR and Raman spectroscopy are often used together in vibrational analysis. In summary, IR activity requires \(\Delta \mu \neq 0\) during vibration, while Raman activity requires \(\Delta \alpha \neq 0\).”
With Expertise
( , ours)
“Yes, your understanding is accurate. Infrared and Raman spectroscopy probe different vibrational modes depending on molecular symmetry, and this distinction is fundamentally based on changes in physical properties, namely the dipole moment and the polarizability. Infrared spectroscopy measures time-dependent changes in the dipole moment during molecular vibration. A normal mode is IR-active if it produces a nonzero change in the dipole moment during vibration. Consequently, vibrational modes that are asymmetric with respect to the molecular geometry are most commonly observed in IR spectra. For instance, although carbon dioxide (CO\(_2\)) is a linear and overall symmetric molecule, its asymmetric stretching and bending modes generate dipole moment changes and therefore appear in the IR spectrum. Raman spectroscopy probes changes in the molecular polarizability, more precisely changes in the polarizability tensor. A vibrational mode is Raman-active if the vibration causes a modulation of the polarizability. As a result, symmetric vibrational modes often give strong Raman signals. In the case of CO\(_2\), the symmetric stretching mode does not induce a dipole moment change and is therefore IR-inactive, but it does change the polarizability and thus appears prominently in the Raman spectrum. From the symmetry analysis perspective, once the molecular point group is identified, each vibrational mode can be assigned to an irreducible representation. Selection rules derived from the character table determine whether a given mode is IR-active, corresponding to the Cartesian coordinates \(x\), \(y\), or \(z\), or Raman-active, corresponding to quadratic functions such as \(x^2\), \(y^2\), \(z^2\), or \(xy\). In summary, IR spectroscopy is governed by the condition \(\Delta \mu \neq 0\), whereas Raman spectroscopy is governed by the condition \(\Delta \alpha \neq 0\). The two techniques, therefore, provide complementary information for the analysis of molecular vibrational modes.”

As shown in Table 19, the  ExPerT response demonstrates expert-level adaptation by embedding explanations within formal theoretical structures. The  ExPerT response connects IR and Raman activity to group-theoretic constructs such as irreducible representations, polarizability tensors, and selection rules derived from character tables. In contrast, the baseline response remains descriptive, focusing on physical conditions without explicitly linking them to symmetry formalism. The insight here is that  ExPerT does not merely add detail, but shifts the explanatory goal toward theoretical completeness and disciplinary rigor, reflecting how experts evaluate correctness and depth through formal frameworks rather than phenomenological description.

17 License for Artifacts↩︎

We follow the terms of use released by OpenAI (https://openai.com/policies/row-terms-of-use/).

18 Potential Risks↩︎

The proposed framework dynamically adapts large language model responses based on inferred user expertise. While this personalization is designed to improve user experience, it introduces potential societal risks. Expertise misclassifications could systematically disadvantage particular user groups or amplify pre-existing biases, especially for users with non-standard interaction patterns. Additionally, malicious actors could attempt to manipulate the system to receive inappropriate or misleading personalized outputs.

19 Implementation Details and Evaluation Packages↩︎

We used standard Python libraries for evaluation and statistical analysis. Evaluation metrics, including mean absolute error (MAE), mean squared error (MSE), and confusion matrices, were computed using the sklearn.metrics package with default parameter settings. Statistical significance testing was conducted using standard functions from the scipy.stats package. Specifically, the Wilcoxon signed-rank test using scipy.stats.wilcoxon, one-way ANOVA was performed using scipy.stats.f_oneway, and the Kruskal–Wallis test using scipy.stats.kruskal. All tests were applied following their conventional assumptions and default configurations.

References↩︎

[1]
S. Chan et al., “"Mango mango, how to let the lettuce dry without a spinner?": Exploring user perceptions of using an LLM-based conversational assistant toward cooking partner,” Proc. ACM Hum.-Comput. Interact., vol. 9, no. 7, Oct. 2025, doi: 10.1145/3757442.
[2]
X. Lin, H. Huang, K. Huang, X. Shu, and J. Vines, “Seeking inspiration through human-LLM interaction,” in Proceedings of the 2025 CHI conference on human factors in computing systems, 2025, doi: 10.1145/3706598.3713259.
[3]
E. Eigner and T. Händler, “Determinants of LLM-assisted decision-making.” 2024, [Online]. Available: https://arxiv.org/abs/2402.17385.
[4]
C.-W. Chiang, Z. Lu, Z. Li, and M. Yin, “Enhancing AI-assisted group decision making through LLM-powered devil’s advocate,” in Proceedings of the 29th international conference on intelligent user interfaces, 2024, pp. 103–119, doi: 10.1145/3640543.3645199.
[5]
J. Wei et al., “Chain-of-thought prompting elicits reasoning in large language models,” in Proceedings of the 36th international conference on neural information processing systems, 2022.
[6]
B. Wang, X. Yue, and H. Sun, “Can ChatGPT defend its belief in truth? Evaluating LLM reasoning via debate,” in Findings of the association for computational linguistics: EMNLP 2023, Dec. 2023, pp. 11865–11881, doi: 10.18653/v1/2023.findings-emnlp.795.
[7]
H. Wang et al., “Cue-CoT: Chain-of-thought prompting for responding to in-depth dialogue questions with LLMs,” in Findings of the association for computational linguistics: EMNLP 2023, Dec. 2023, pp. 12047–12064, doi: 10.18653/v1/2023.findings-emnlp.806.
[8]
H. Dang, B. Lafreniere, T. Grossman, K. Todi, and M. Li, “Authoring LLM-based assistance for real-world contexts and tasks,” in Proceedings of the 30th international conference on intelligent user interfaces, 2025, pp. 211–230, doi: 10.1145/3708359.3712164.
[9]
T. Wang et al., “AI PERSONA: Towards life-long personalization of LLMs.” 2024, [Online]. Available: https://arxiv.org/abs/2412.13103.
[10]
T. Hu and N. Collier, “Quantifying the persona effect in LLM simulations,” in Proceedings of the 62nd annual meeting of the association for computational linguistics (volume 1: Long papers), Aug. 2024, pp. 10289–10307, doi: 10.18653/v1/2024.acl-long.554.
[11]
C. Sun et al., “Persona-DB: Efficient large language model personalization for response prediction with collaborative data refinement,” in Proceedings of the 31st international conference on computational linguistics, Jan. 2025, pp. 281–296, [Online]. Available: https://aclanthology.org/2025.coling-main.20/.
[12]
S. Zhao, M. Hong, Y. Liu, D. Hazarika, and K. Lin, “Do LLMs recognize your preferences? Evaluating personalized preference following in LLMs,” in The thirteenth international conference on learning representations, 2025.
[13]
L. C. Magister, K. Metcalf, Y. Zhang, and M. ter Hoeve, “On the way to LLM personalization: Learning to remember user conversations.” 2024, [Online]. Available: https://arxiv.org/abs/2411.13405.
[14]
C. Cheng et al., ‘In-dialogues we learn’: Towards personalized dialogue without pre-defined profiles through in-dialogue learning,” in Proceedings of the 2024 conference on empirical methods in natural language processing, Nov. 2024, pp. 10408–10422, doi: 10.18653/v1/2024.emnlp-main.581.
[15]
A. Head et al., “Augmenting scientific papers with just-in-time, position-sensitive definitions of terms and symbols,” in Proceedings of the 2021 CHI conference on human factors in computing systems, 2021, doi: 10.1145/3411764.3445648.
[16]
Y. Zhang et al., “Knowledgeable preference alignment for LLMs in domain-specific question answering,” in Findings of the association for computational linguistics: ACL 2024, Aug. 2024, pp. 891–904, doi: 10.18653/v1/2024.findings-acl.52.
[17]
J. Baek, N. Chandrasekaran, S. Cucerzan, A. Herring, and S. K. Jauhar, “Knowledge-augmented large language models for personalized contextual query suggestion,” in Proceedings of the ACM web conference 2024, 2024, pp. 3355–3366, doi: 10.1145/3589334.3645404.
[18]
X. Tang, H. Zhai, C. Belwal, V. Thayanithi, P. Baumann, and Y. K. Roy, “Dynamic context-aware prompt recommendation for domain-specific AI applications.” 2025, [Online]. Available: https://arxiv.org/abs/2506.20815.
[19]
J. Kiseleva, A. M. García, J. Kamps, and N. Spirin, “The impact of technical domain expertise on search behavior and task outcome.” 2015, [Online]. Available: https://arxiv.org/abs/1512.07051.
[20]
S. Palta, N. Chandrasekaran, R. Rudinger, and S. Counts, “Speaking the right language: The impact of expertise (mis)alignment in user-AI interactions,” in Proceedings of the 14th international joint conference on natural language processing and the 4th conference of the asia-pacific chapter of the association for computational linguistics, Dec. 2025, pp. 58–69, doi: 10.18653/v1/2025.ijcnlp-short.5.
[21]
Q. Liu, N. Chen, T. Sakai, and X.-M. Wu, “ONCE: Boosting content-based recommendation with both open- and closed-source large language models,” in Proceedings of the 17th ACM international conference on web search and data mining, 2024, pp. 452–461, doi: 10.1145/3616855.3635845.
[22]
J. Mao, Y. Liu, N. Kando, M. Zhang, and S. Ma, “How does domain expertise affect users’ search interaction and outcome in exploratory search?” ACM Trans. Inf. Syst., vol. 36, no. 4, Jul. 2018, doi: 10.1145/3223045.
[23]
C. Epp, M. Lippold, and R. L. Mandryk, “Identifying emotional states using keystroke dynamics,” in Proceedings of the SIGCHI conference on human factors in computing systems, 2011, pp. 715–724, doi: 10.1145/1978942.1979046.
[24]
A. Kołakowska, “Recognizing emotions on the basis of keystroke dynamics,” in 2015 8th international conference on human system interaction (HSI), 2015, pp. 291–297, doi: 10.1109/HSI.2015.7170682.
[25]
A. F. M. N. H. Nahin, J. M. Alam, H. Mahmud, and K. Hasan, “Identifying emotion by keystroke dynamics and text pattern analysis,” Behav. Inf. Technol., vol. 33, no. 9, pp. 987–996, Sep. 2014, doi: 10.1080/0144929X.2014.907343.
[26]
S. Min et al., “Rethinking the role of demonstrations: What makes in-context learning work?” in Proceedings of the 2022 conference on empirical methods in natural language processing, Dec. 2022, pp. 11048–11064, doi: 10.18653/v1/2022.emnlp-main.759.
[27]
Y. Zhang, S. Feng, and C. Tan, “Active example selection for in-context learning,” in Proceedings of the 2022 conference on empirical methods in natural language processing, Dec. 2022, pp. 9134–9148, [Online]. Available: https://aclanthology.org/2022.emnlp-main.622.
[28]
J. Chen, L. Chen, C. Zhu, and T. Zhou, “How many demonstrations do you need for in-context learning?” in Findings of the association for computational linguistics: EMNLP 2023, Dec. 2023, pp. 11149–11159, doi: 10.18653/v1/2023.findings-emnlp.745.
[29]
S. Wu, H. Shen, D. S. Weld, J. Heer, and M. T. Ribeiro, “ScatterShot: Interactive in-context example curation for text transformation,” in Proceedings of the 28th international conference on intelligent user interfaces, 2023, pp. 353–367, doi: 10.1145/3581641.3584059.
[30]
OpenAI, Accessed: 2025-07-20“ChatGPT-4o model documentation.” https://platform.openai.com/docs/models/chatgpt-4o-latest, 2024.
[31]
OpenAI, Accessed: 2025-07-20“GPT-4.1 model documentation.” https://platform.openai.com/docs/models/gpt-4.1, 2024.
[32]
Anthropic, Accessed: 2026-01-01“Introducing claude 4.” https://www.anthropic.com/news/claude-4, 2025.
[33]
G. Comanici et al., “Gemini 2.5: Pushing the frontier with advanced reasoning, multimodality, long context, and next generation agentic capabilities.” 2025, [Online]. Available: https://arxiv.org/abs/2507.06261.
[34]
H. Gao, F. Zhang, W. Jiang, J. Shu, F. Zheng, and H. Wei, “On the noise robustness of in-context learning for text generation,” 2024.
[35]
B. Plank, “Keystroke dynamics as signal for shallow syntactic parsing,” in Proceedings of COLING 2016, the 26th international conference on computational linguistics: Technical papers, Dec. 2016, pp. 609–619, [Online]. Available: https://aclanthology.org/C16-1059/.
[36]
K. S. Killourhy and R. A. Maxion, “Comparing anomaly-detection algorithms for keystroke dynamics,” in 2009 IEEE/IFIP international conference on dependable systems & networks, 2009, pp. 125–134, doi: 10.1109/DSN.2009.5270346.
[37]
V. Dhakal, A. M. Feit, P. O. Kristensson, and A. Oulasvirta, “Observations on typing from 136 million keystrokes,” in Proceedings of the 2018 CHI conference on human factors in computing systems, 2018, pp. 1–12, doi: 10.1145/3173574.3174220.
[38]
A. Acien, A. Morales, J. V. Monaco, R. Vera-Rodriguez, and J. Fierrez, “TypeNet: Deep learning keystroke biometrics,” IEEE Transactions on Biometrics, Behavior, and Identity Science, vol. 4, no. 1, pp. 57–70, 2022, doi: 10.1109/TBIOM.2021.3112540.
[39]
OpenAI, Accessed: 2026-04-18“GPT-5.3 chat model documentation.” https://developers.openai.com/api/docs/models/gpt-5.3-chat-latest, 2026.
[40]
S. Poddar, Y. Wan, H. Ivison, A. Gupta, and N. Jaques, “Personalizing reinforcement learning from human feedback with variational preference learning,” in Proceedings of the 38th international conference on neural information processing systems, 2025.
[41]
R. Chen, X. Zhang, M. Luo, W. Chai, and Z. Liu, “Pad: Personalized alignment at decoding-time,” in The thirteenth international conference on learning representations, 2025.
[42]
J. A. Rodriguez, N. Botzer, D. Vazquez, C. Pal, M. Pedersoli, and I. Laradji, “IntentGPT: Few-shot intent discovery with large language models.” 2024, [Online]. Available: https://arxiv.org/abs/2411.10670.
[43]
S. Zhang, Y. Ma, L. Fang, H. Jia, S. D’Alfonso, and V. Kostakos, “Enabling on-device LLMs personalization with smartphone sensing,” in Companion of the 2024 on ACM international joint conference on pervasive and ubiquitous computing, 2024, pp. 186–190, doi: 10.1145/3675094.3677545.
[44]
L. Wang, M. Lee, R. Volkov, L. T. Chau, and D. Kang, “ScholaWrite: A dataset of end-to-end scholarly writing process.” 2025, [Online]. Available: https://arxiv.org/abs/2502.02904.
[45]
S. Kalyuga, “The expertise reversal principle in multimedia learning,” in The cambridge handbook of multimedia learning, R. E. Mayer and L. Fiorella, Eds. Cambridge University Press, 2021, pp. 171–182.
[46]
H. Song, J. Healey, A. F. Siu, C. Wigington, and J. Stasko, “Experts prefer text but videos help novices: An analysis of the utility of multi-media content,” in Extended abstracts of the 2023 CHI conference on human factors in computing systems, 2023, doi: 10.1145/3544549.3585900.
[47]
B. Xu et al., “ExpertPrompting: Instructing large language models to be distinguished experts.” 2025, [Online]. Available: https://arxiv.org/abs/2305.14688.
[48]
A. Zadeh, M. Chen, S. Poria, E. Cambria, and L.-P. Morency, “Tensor fusion network for multimodal sentiment analysis,” in Proceedings of the 2017 conference on empirical methods in natural language processing, Sep. 2017, pp. 1103–1114, doi: 10.18653/v1/D17-1115.
[49]
Z. Liu, Y. Shen, V. B. Lakshminarasimhan, P. P. Liang, A. Bagher Zadeh, and L.-P. Morency, “Efficient low-rank multimodal fusion with modality-specific factors,” in Proceedings of the 56th annual meeting of the association for computational linguistics (volume 1: Long papers), Jul. 2018, pp. 2247–2256, doi: 10.18653/v1/P18-1209.
[50]
E. Tong, A. Zadeh, C. Jones, and L.-P. Morency, “Combating human trafficking with multimodal deep models,” in Proceedings of the 55th annual meeting of the association for computational linguistics (volume 1: Long papers), Jul. 2017, pp. 1547–1556, doi: 10.18653/v1/P17-1142.
[51]
A. Zadeh, P. P. Liang, N. Mazumder, S. Poria, E. Cambria, and L.-P. Morency, “Memory fusion network for multi-view sequential learning,” Proceedings of the Thirty-Second AAAI Conference on Artificial Intelligence, 2018.
[52]
W. H. Kruskal and W. A. Wallis, “Use of ranks in one-criterion variance analysis,” Journal of the American Statistical Association, vol. 47, no. 260, pp. 583–621, 1952, doi: 10.1080/01621459.1952.10483441.

  1. https://github.com/UbiquitousAILab/ExPerT↩︎