When Technical Questions Go Beyond What You Prepared
Most viva question categories are predictable enough to prepare for — why this methodology, what do your findings mean, what would you do differently. But for Malaysian postgraduate students in quantitative disciplines, engineering, computer science, medicine, and the physical sciences, there is a category of viva question that can arrive with unexpected specificity: highly technical questions that probe the mathematical, statistical, computational, or procedural details of your research at a level of granularity you may not have anticipated. Knowing how to handle technical questions in your viva is a specific skill that requires preparation beyond the standard content-based review of your thesis.
These questions are not designed to trip you up. They are designed to verify that you understand the technical foundations of the methods you used — that you are not simply someone who ran a software package and reported the output, but someone who understands what the software was doing and why it was appropriate for your research problem.
The Most Common Technical Viva Question Categories
Understanding the most common categories of technical questions in Malaysian postgraduate vivas allows you to prepare specifically for each type. Statistical assumption questions are among the most frequent in quantitative theses: “What assumptions does this test require, and how did you verify that your data meets them?” For structural equation modelling, confirmatory factor analysis, regression, or analysis of variance, examiners expect you to know the specific assumptions — normality, homoscedasticity, independence of observations, multicollinearity — and to be able to describe the specific diagnostic tests you ran.
Software and analytical process questions probe whether you understand what your analysis actually did: “Can you explain what happens mathematically when your SEM converges to a solution?” or “How does NVivo determine similarity when you run a cluster analysis?” You do not need to be a software developer to answer these questions, but you do need to understand the conceptual basis of the analytical procedures your software implemented.
Validity and reliability questions in technical contexts ask about the specific evidence for measurement quality: “What fit indices did you use to evaluate your confirmatory factor analysis, and why are these specific indices appropriate for your sample size?” or “How did you establish inter-rater reliability for your coding process, and what threshold did you set for acceptable agreement?” These questions require specific, evidence-based answers — the actual values from your analysis — not general statements about the importance of validity.
Preparing Technical Answers Before the Viva
The most effective preparation for technical questions in your Malaysian viva is to build a technical summary document in the weeks before the examination. This document contains the key technical details of every major analytical decision in your study — the specific tests run and their outputs, the assumptions checked and the diagnostic results, the software settings used for any non-default configurations, the specific values for any goodness-of-fit indices or reliability coefficients, and the explicit reasoning for each technical choice.
Creating this document forces you to review the technical details of your analysis at a level of depth that re-reading the thesis chapter does not provide. Many students write their methodology and findings chapters at a level of abstraction that is appropriate for the thesis but does not require them to consciously hold all the underlying technical details in mind. The technical summary document makes those details conscious and accessible, which is exactly the state you need to be in when answering detailed viva questions.
What to Do When a Technical Question Exceeds Your Knowledge
There will occasionally be technical questions in the viva that probe an area of methodology beyond what you studied in depth. An examiner with deep expertise in a specific statistical procedure may ask about nuances of that procedure that you implemented correctly — following established guidance in your field — without fully understanding the mathematical mechanics behind it. This is not a failure of preparation; it reflects the genuine boundaries of expertise that exist in every researcher.
When handling technical questions in your viva that go beyond your knowledge, the same principles that apply to non-technical surprise questions apply here. Be honest about the limit of your current knowledge. Demonstrate what you do know about the procedure and why you chose it. Acknowledge what you would want to investigate further if extending this research. “I applied the Hu and Bentler (1999) cut-off criteria for fit indices because these are the most widely cited guidelines in this literature, and my values met those thresholds. The deeper statistical justification for why those specific cut-offs are appropriate is something I haven’t examined in full mathematical detail, but I can explain the practical reasoning behind the choice.”
Connecting Technical Decisions to Research Purpose
The most confident responses to technical questions in a Malaysian viva are those that connect technical decisions back to research purpose. Rather than describing a technical procedure in isolation, explain why that procedure was the right one for your research question, your data characteristics, and your analytical goals. This connection demonstrates that your technical choices were purposeful rather than arbitrary — that you selected a procedure because it was the right tool for the specific job, not because it was the most familiar or the most commonly used in your department.
“I used partial invariance testing before proceeding to the comparison of latent mean scores because my preliminary analysis suggested that one item may not have performed equivalently across groups. Without establishing at least partial metric invariance, the comparison of latent means would have been meaningless — the scales would not have been measuring the same construct in both groups.” This response is technically specific, clearly reasoned, and explicitly connected to the research purpose. It is the kind of answer that turns a technical challenge into a demonstration of genuine methodological understanding.
