Before your interview: know your own resume
Anything on your resume can become an interview question. Be ready to explain every internship, certificate, project, instrument, software skill, clinical-trial phase or production/QC activity you mention: what it means, what you personally did, why you did it, the result and what you learned. Clearly distinguish observation, simulation, supervised practice and independent work. A certificate demonstrates training, not automatic practical competence. Adapt the examples to your own experience; never invent achievements.
Guide scope: Entry-level analytical consulting and healthcare-process improvement.
Practise each answer aloud, then explain it in your own words. These are original preparation questions and example approaches, not a verified employer question paper or a promise of selection. Confirm current role-specific requirements with authorised sources.
Jump to a section
Resume, internships, certificates and HR
Question 1 / 101
1. Tell me about yourself.
Give a 60–90 second introduction: your qualification, one relevant experience, a skill you can demonstrate and why this role fits. A useful structure is: 'I studied …, worked on …, personally handled …, and learned …'. Replace each example with truthful details; avoid reciting your entire resume.
Question 2 / 101
2. Walk me through the parts of your resume most relevant to this job.
Select two or three relevant experiences and explain the link to the job description. For each, state the setting, your responsibility and a concrete output. Clearly identify classroom, simulated and workplace experience. Expect follow-up questions about every technical term you mention.
Question 3 / 101
3. What exactly did you do during your internship?
Explain the department, duration, supervisor and tasks you actually performed. Separate observations from hands-on work. Describe one activity from input to output, including checks and escalation. If you only observed a process, say so and explain what you understood rather than claiming independent responsibility.
Question 4 / 101
4. Which internship activity could you explain from beginning to end?
Choose one real activity. Explain its purpose, required input, sequence, safety or quality checks, documentation and the person who approved the result. Be ready to explain why each step existed and what would happen if it was missed. Do not disclose confidential patient or company details.
Question 5 / 101
5. What did your certificate teach you, and what did you practise?
Name the course, provider, completion date and main modules. Then distinguish lectures, assessed exercises and practical tasks. For example: 'I completed the theory module and practised with a training dataset; I have not used the production system.' Explain one concept well instead of listing certificates without understanding them.
Question 6 / 101
6. Explain the objective of a project on your resume.
State the problem, why it mattered, the objective and your own contribution. Explain the setting and limitations before describing results. If the work was simulated or academic, say so. Do not imply that a classroom exercise produced real patient, manufacturing or commercial outcomes.
Question 7 / 101
7. How did you choose your project's method?
Explain why the method addressed the objective, what alternatives you considered and which constraints mattered. Identify the protocol, reference or supervisor input used. Discuss one limitation honestly. A strong answer shows reasoning; naming a technique without explaining its purpose does not demonstrate competence.
Question 8 / 101
8. How did you check the accuracy of your project results?
Describe the real checks you performed: source comparison, calculations, controls, peer review or supervisor verification as applicable. Explain how you handled missing information and discrepancies. Avoid saying that the result was 100% accurate unless you can define and substantiate that claim.
Question 9 / 101
9. Your resume mentions an improvement percentage. How was it calculated?
State the baseline, final value, denominator and time period. Explain whether the result is an absolute difference or a relative change, and identify your contribution. If you cannot reconstruct a number from authorised evidence, correct the claim rather than invent a calculation during the interview.
Question 10 / 101
10. Which instrument or software function have you personally used?
Name the specific task and your level of access or supervision. Walk through the input, action, output and checks. Separate familiarity with terminology from hands-on competence. Be prepared for a practical demonstration using nonconfidential training material and do not claim certification or administrator access you do not have.
Question 11 / 101
11. Which academic subject is most relevant to this role?
Choose a subject you understand and connect one concept to a real role activity. Explain the concept in simple language, then give an example and limitation. Revise any subjects or clinical-trial phases you highlight on your resume; mentioning a topic invites deeper questions about it.
Question 12 / 101
12. Why do you want to work in this department?
Connect your interest to actual responsibilities in the job description. Support it with a truthful course, project or work example. Explain what you want to learn and contribute. Avoid claims that the department is easy, guarantees high pay or provides a shortcut around the technical learning required.
Question 13 / 101
13. Why are you interested in this employer?
Use two current facts from the employer's own website or job description and explain their relevance to the role. Then connect your demonstrated skills to the team's work. Do not invent company rankings, employee counts, client relationships or promises about training that you have not verified.
Question 14 / 101
14. What is a strength you can demonstrate?
Choose one relevant strength and prove it with a brief example. 'I use a source-check checklist; in my project it helped me catch a date mismatch before review' is stronger than 'I never make mistakes'. State what you personally did and what evidence supports the result.
Question 15 / 101
15. What is a weakness you are working on?
Describe a genuine, manageable development area and the steps you are taking. For example: 'I used to give overly long explanations, so I practise a one-minute summary before the detail.' Explain progress without disguising a boast as a weakness or suggesting that essential safety requirements are optional.
Question 16 / 101
16. How do you explain a career gap or change of field?
Give a brief factual explanation at a level you are comfortable sharing, then discuss relevant learning and readiness for the role. You do not need to invent employment, training or personal circumstances. Connect transferable skills to the job while acknowledging the department-specific training still needed.
Question 17 / 101
17. Give an example of teamwork.
Use Situation, Task, Action and Result. Describe the shared objective, your own contribution and how you handled communication or a handoff. An academic project is a valid example when labelled accurately. Do not take credit for the whole team's work or reveal confidential information.
Question 18 / 101
18. How do you work under pressure?
Explain how you identify the highest-impact tasks, confirm priorities, work through a checklist and communicate delays early. Support the answer with a real example. Speed should not mean skipping required checks, hiding errors or working outside your training and authority.
Question 19 / 101
19. Can you work shifts, relocate or meet the joining date?
Answer honestly about your availability and constraints, then ask for the actual schedule and role expectations. Do not automatically say yes to conditions you cannot meet. You can be professional and interested while clarifying notice periods, transport arrangements or practical limitations.
Question 20 / 101
20. What would you do if you realised your resume overstated a skill?
Correct the claim promptly and explain your actual level. Offer an accurate example of what you can demonstrate and a realistic learning plan. Honesty protects both you and the employer; rehearsing an invented answer is especially risky in work involving safety, regulated records or confidential information.
Technical interview questions
Question 21 / 101
21. Can you explain A problem statement?
A problem statement defines the gap or decision to address. It should identify the context and desired outcome without assuming the solution prematurely.
Question 22 / 101
22. Can you explain A proposed solution?
A solution is an option intended to address the defined problem. It needs evaluation against evidence, feasibility and stakeholder requirements.
Question 23 / 101
23. Can you explain A hypothesis?
A hypothesis is a testable proposed explanation. Use evidence to challenge it rather than collect only information that supports the initial idea.
Question 24 / 101
24. Can you explain an assumption?
An assumption is a condition temporarily accepted for planning or analysis. Make it explicit and test material assumptions where possible.
Question 25 / 101
25. Can you explain A primary research source?
Primary research gathers evidence directly for the question, such as interviews or measurements. Its quality depends on method and participants.
Question 26 / 101
26. Can you explain A secondary research source?
Secondary research uses existing material. Check provenance, definitions and applicability before treating it as a direct answer to a new question.
Question 27 / 101
27. Can you explain A qualitative finding?
Qualitative evidence explains experiences, themes or reasoning. Its depth differs from an estimate of population frequency.
Question 28 / 101
28. Can you explain A quantitative finding?
Quantitative evidence reports numerical measurements or estimates. Sample design, definitions and uncertainty determine what the numbers support.
Question 29 / 101
29. Can you explain A current-state process?
A current-state map records how work actually occurs. Verify it with evidence rather than copy the official procedure and assume practice matches.
Question 30 / 101
30. Can you explain A future-state process?
A future-state design proposes a better way of working. Feasibility, controls and implementation need assessment before presenting benefits as achieved.
Question 31 / 101
31. Can you explain A deliverable?
A deliverable is a defined output to be produced. It may support an outcome but is not automatically the outcome itself.
Question 32 / 101
32. Can you explain A business outcome?
An outcome is the effect the engagement seeks, such as reduced delays. Attribute improvements cautiously and distinguish estimates from measured results.
Question 33 / 101
33. Can you explain A stakeholder?
A stakeholder can affect or be affected by the work. Needs and authority differ, so communication should match the actual role.
Question 34 / 101
34. Can you explain A project sponsor?
A sponsor supports and authorises the engagement within defined responsibilities. Their priorities matter, but they do not erase safety or legal constraints.
Question 35 / 101
35. Can you explain A risk?
A risk is an uncertain event or condition that may affect objectives. Track responses before it becomes an issue.
Question 36 / 101
36. Can you explain an issue?
An issue is a current problem requiring action. It needs an owner and resolution plan rather than only a probability score.
Question 37 / 101
37. Can you explain A metric?
A metric quantifies a defined feature or performance. State its source, calculation and limitations before comparing teams.
Question 38 / 101
38. Can you explain A target?
A target is a desired value or state. It should not be mistaken for evidence of actual performance.
Question 39 / 101
39. Can you explain A recommendation?
A recommendation proposes a course of action supported by analysis. Explain trade-offs and uncertainty instead of presenting preference as proven fact.
Question 40 / 101
40. Can you explain an implementation decision?
A decision authorises action within governance. Consultants advise, but the responsible client or authority must approve relevant changes.
Question 41 / 101
41. Can you explain scope definition?
Scope clarifies included and excluded work, outputs and responsibilities. It reduces misunderstandings about what the engagement will achieve.
Question 42 / 101
42. Can you explain A work plan?
A plan connects activities, owners, milestones and dependencies. Revise it transparently when evidence or constraints change.
Question 43 / 101
43. Can you explain an interview guide?
A guide structures consistent research while allowing relevant follow-up. Avoid leading participants toward the answer the project team wants.
Question 44 / 101
44. Can you explain root-cause analysis?
Investigate causes using evidence and appropriate methods. A correlation or repeated complaint may identify a symptom rather than the underlying cause.
Question 45 / 101
45. Can you explain benchmarking?
Benchmarking compares relevant practices or performance with appropriate peers. Adjust for differences in scope, definitions and operating conditions.
Question 46 / 101
46. Can you explain A business case?
A business case weighs costs, benefits, risks and alternatives for a decision. Assumptions should be visible and benefits should not be guaranteed without evidence.
Question 47 / 101
47. Can you explain sensitivity testing?
Sensitivity tests show how conclusions depend on assumptions. They help identify what information is most important before committing resources.
Question 48 / 101
48. Can you explain A RACI matrix?
RACI clarifies responsibility and accountability for activities. It is useful only when people understand and accept the actual assignments.
Question 49 / 101
49. Can you explain change management?
Change management prepares people and processes to adopt a change. Sending an announcement alone does not establish readiness or sustained adoption.
Question 50 / 101
50. Can you explain A pilot?
A pilot tests a proposed approach on a limited scope. Its conditions and success criteria must support decisions about broader implementation.
Question 51 / 101
51. Can you explain evidence triangulation?
Triangulation compares independent sources or methods. Agreement is more persuasive when sources are genuinely independent rather than copied from one another.
Question 52 / 101
52. Can you explain confidentiality?
Use client information only within authorised purposes and access. Remove sensitive details from interview examples and do not reuse another client's confidential work.
Question 53 / 101
53. Can you explain an executive presentation?
Present the decision, evidence, options and implications clearly for the audience. Visual simplicity should not conceal material uncertainty.
Question 54 / 101
54. Can you explain professional disagreement?
Compare assumptions and evidence respectfully, then document the decision route. Do not alter analysis to satisfy a senior person's preferred outcome.
Question 55 / 101
55. Can you explain benefits tracking?
Track whether intended improvements occur after implementation using defined measures. A completed slide deck is not evidence of operational benefit.
Question 56 / 101
56. How does A problem statement differ from A proposed solution?
A problem statement: A problem statement defines the gap or decision to address. It should identify the context and desired outcome without assuming the solution prematurely. A proposed solution: A solution is an option intended to address the defined problem. It needs evaluation against evidence, feasibility and stakeholder requirements.
Question 57 / 101
57. How does A hypothesis differ from an assumption?
A hypothesis: A hypothesis is a testable proposed explanation. Use evidence to challenge it rather than collect only information that supports the initial idea. An assumption: An assumption is a condition temporarily accepted for planning or analysis. Make it explicit and test material assumptions where possible.
Question 58 / 101
58. How does A primary research source differ from A secondary research source?
A primary research source: Primary research gathers evidence directly for the question, such as interviews or measurements. Its quality depends on method and participants. A secondary research source: Secondary research uses existing material. Check provenance, definitions and applicability before treating it as a direct answer to a new question.
Question 59 / 101
59. How does A qualitative finding differ from A quantitative finding?
A qualitative finding: Qualitative evidence explains experiences, themes or reasoning. Its depth differs from an estimate of population frequency. A quantitative finding: Quantitative evidence reports numerical measurements or estimates. Sample design, definitions and uncertainty determine what the numbers support.
Question 60 / 101
60. How does A current-state process differ from A future-state process?
A current-state process: A current-state map records how work actually occurs. Verify it with evidence rather than copy the official procedure and assume practice matches. A future-state process: A future-state design proposes a better way of working. Feasibility, controls and implementation need assessment before presenting benefits as achieved.
Question 61 / 101
61. How does A deliverable differ from A business outcome?
A deliverable: A deliverable is a defined output to be produced. It may support an outcome but is not automatically the outcome itself. A business outcome: An outcome is the effect the engagement seeks, such as reduced delays. Attribute improvements cautiously and distinguish estimates from measured results.
Question 62 / 101
62. How does A stakeholder differ from A project sponsor?
A stakeholder: A stakeholder can affect or be affected by the work. Needs and authority differ, so communication should match the actual role. A project sponsor: A sponsor supports and authorises the engagement within defined responsibilities. Their priorities matter, but they do not erase safety or legal constraints.
Question 63 / 101
63. How does A risk differ from an issue?
A risk: A risk is an uncertain event or condition that may affect objectives. Track responses before it becomes an issue. An issue: An issue is a current problem requiring action. It needs an owner and resolution plan rather than only a probability score.
Question 64 / 101
64. How does A metric differ from A target?
A metric: A metric quantifies a defined feature or performance. State its source, calculation and limitations before comparing teams. A target: A target is a desired value or state. It should not be mistaken for evidence of actual performance.
Question 65 / 101
65. How does A recommendation differ from an implementation decision?
A recommendation: A recommendation proposes a course of action supported by analysis. Explain trade-offs and uncertainty instead of presenting preference as proven fact. An implementation decision: A decision authorises action within governance. Consultants advise, but the responsible client or authority must approve relevant changes.
Question 66 / 101
66. Describe an end-to-end Life Sciences Consulting workflow.
A useful answer is: Define the problem and scope; identify stakeholders; gather authorised evidence; test hypotheses; compare options and uncertainty; recommend a practical course; support approved implementation and benefits review. Explain who owns each decision and distinguish your own performed tasks from those you have only studied. The actual employer's procedures and role scope take priority over this preparation example.
Question 67 / 101
67. What would you verify before starting an assigned technical task?
I would confirm the purpose, my training and authority, and the current approved requirements. In this role, relevant inputs include client question, authorised evidence, scope and assumptions. I would verify identity, version, status and completeness, then clarify any material gap before relying on the information.
Question 68 / 101
68. What outputs would you check before considering the work complete?
Relevant outputs include a justified recommendation, implementation plan and documented limitations. I would compare the result with its requirements and source evidence, resolve discrepancies through the approved process and confirm required review. I would not mark a task complete just because a file exists or a tracker demands closure.
Question 69 / 101
69. Which performance measures matter in Life Sciences Consulting?
Examples include evidence quality, deliverable acceptance and measured benefit where attributable. I would define the numerator, denominator, time window and data source before interpreting a metric. Volume and speed need to be assessed alongside complexity, quality and risk; I would not improve a score by hiding errors or excluding difficult work.
Question 70 / 101
70. Which tools should you be prepared to discuss?
Relevant examples include approved analysis tools, interview guides and presentation systems. I would explain the specific functions I have actually used and my supervision or training level. For unfamiliar systems, I would describe transferable understanding and how I would learn through approved training, rather than pretend to have production experience.
Situational and workplace questions
Question 71 / 101
71. You find different metric definitions between sites. What would you do?
I would verify the discrepancy against the authorised source, preserve the original information and assess its immediate impact. I would pause affected work where necessary and involve the engagement lead and client decision owner. I would document the clarification or correction and check whether other records or decisions are affected.
Question 72 / 101
72. Required information is missing from an analysis and its documented assumptions. What next?
I would identify exactly what is missing and whether it prevents a safe or valid next step. I would seek the information from the authorised owner and document follow-up. I would not invent a value, and I would escalate any deadline or risk implication through the engagement lead and client decision owner.
Question 73 / 101
73. You notice a recommendation presented as proven despite material evidence gaps. What is your priority?
I would follow the relevant immediate safety, quality or incident process and promptly involve the engagement lead and client decision owner. I would preserve facts, restrict affected activity where required and avoid acting beyond my competence. Routine productivity targets would not justify delaying an urgent concern or bypassing a protective control.
Question 74 / 101
74. A deadline is close, but work on an analysis and its documented assumptions remains incomplete. What would you do?
I would separate critical issues from lower-impact work, identify dependencies and communicate the realistic status early. With the engagement lead and client decision owner, I would agree priorities and an authorised plan. I would not conceal incomplete checks or certify an unsupported result merely to meet the original deadline.
Question 75 / 101
75. A colleague asks you to skip a required check because the team is busy. How would you respond?
I would explain the purpose of the check and look for an authorised way to manage the workload. If a genuine alternative exists, I would seek appropriate approval; otherwise I would complete the requirement or escalate. The relevant escalation route here includes the engagement lead and client decision owner.
Question 76 / 101
76. You discover the wrong version was used for an analysis and its documented assumptions. What next?
I would identify the affected work, compare it with the correct baseline and inform the owner. I would assess whether any output was already shared or used, then follow the controlled correction process with the engagement lead and client decision owner. I would preserve version history rather than overwrite evidence silently.
Question 77 / 101
77. You made an error in a record that has already been reviewed. How do you handle it?
I would acknowledge the error, establish its impact and notify the responsible reviewer promptly. I would correct through the approved process, keeping the original history and rationale. I would consider downstream outputs and inform the engagement lead and client decision owner if the error affects safety, quality or an external decision.
Question 78 / 101
78. You accidentally send confidential information to the wrong recipient. What would you do?
I would stop further sharing and immediately follow the organisation's privacy or security incident process. I would notify the authorised incident team, preserve facts and follow their instructions on containment and communication. Deleting my sent message or privately asking for deletion would not replace incident reporting.
Question 79 / 101
79. The same problem, different metric definitions between sites, keeps recurring. How would you address it?
I would review examples to identify the common failure point, assess the impact and involve the process owner. I would consider instructions, training, system design and handoffs rather than assume individual carelessness. Corrective actions should have owners and an effectiveness check, not only a promise to be more careful.
Question 80 / 101
80. The approved system becomes unavailable during urgent work. What would you do?
I would preserve available work and follow the approved outage or continuity process. I would contact the support route and assess the deadline or safety impact with the engagement lead and client decision owner. I would not move confidential information into a personal account or create an uncontrolled workaround to appear productive.
Question 81 / 101
81. Someone asks to use your login or grants you access beyond your role. How do you respond?
I would not share credentials or use unnecessary privileges. I would explain the accountability and confidentiality risks and request properly authorised access for the right person and task. Unexpected excessive access should be reported through the access-control process, with the facts recorded.
Question 82 / 101
82. Your manager gives you two assignments with overlapping deadlines. How would you prioritise?
I would compare risk, external commitments and dependencies, then explain the conflict with realistic time estimates. For this role I would consider evidence quality, deliverable acceptance and measured benefit where attributable alongside the immediate consequences. I would agree priorities and ownership rather than silently choose which commitment to miss.
Question 83 / 101
83. A reviewer disagrees with your technical conclusion. What would you do?
I would clarify the exact point, compare the evidence and applicable requirements, and explain my reasoning respectfully. If the issue remains unresolved, I would use the engagement lead and client decision owner and document the decision appropriately. I would not change source facts to make the disagreement disappear.
Question 84 / 101
84. A source record contradicts a summary or dashboard. Which do you trust?
I would investigate the origin, version, definitions and transformations rather than blindly choose either. I would trace the summary back to authorised evidence and determine whether the mismatch affects other outputs. I would raise the issue through the engagement lead and client decision owner and preserve the correction trail.
Question 85 / 101
85. How would you hand over unfinished work to another colleague?
I would record the current status, completed checks, source locations, unresolved issues and time-sensitive risks. I would identify the next owner and confirm understanding, using approved systems. In Life Sciences Consulting, the handover should make the status of an analysis and its documented assumptions unambiguous.
Question 86 / 101
86. A productivity metric improves while significant errors increase. What would you say?
I would check the metric definitions and investigate the quality trend before calling the change a success. Relevant measures include evidence quality, deliverable acceptance and measured benefit where attributable. I would present both speed and quality evidence, propose proportionate improvements and avoid treating hidden rework or safety risk as acceptable throughput.
Question 87 / 101
87. You are asked to perform an unfamiliar technical task without adequate training. What would you do?
I would explain my current competence and ask for the required training, supervision and authorisation. I could assist within an agreed safe scope while learning, but would not claim independent capability. I would involve the engagement lead and client decision owner if the request could create a material risk.
Question 88 / 101
88. A stakeholder wants a more favourable answer than the evidence supports. How do you respond?
I would explain what the evidence does and does not show, identify uncertainty and offer an accurate alternative statement or further work. I would not alter results, remove inconvenient facts or invent justification. If pressure persists, I would use the appropriate quality, ethical or compliance escalation route.
Question 89 / 101
89. How would you explain a problem with an analysis and its documented assumptions to a nontechnical colleague?
I would describe what is wrong, why it matters, what activity is affected and the decision needed in plain language. I would separate known facts from uncertainty and provide a clear owner and next step. I would avoid excessive jargon and unsupported accusations about who caused it.
Question 90 / 101
90. How would you respond to repeated critical feedback during training?
I would ask for concrete examples, compare them with the required standard and identify the main gap. I would agree a practice and review plan, use a focused checklist where appropriate and ask for reassessment. I would show progress with evidence rather than become defensive or hide difficult tasks.
How to handle an answer you do not know
Question 91 / 101
91. What should you say when you do not know an answer?
Say calmly: 'I do not know that detail confidently, and I do not want to guess. I understand …; I would verify the remaining point in the approved reference or ask the appropriate expert.' Explain any sound knowledge you do have. Do not turn uncertainty into a fabricated rule.
Question 92 / 101
92. What if you understand the concept but forget the exact term or number?
Explain the concept accurately and separate it from the detail you cannot recall. For example: 'I understand the sequence, but I would check the current specification before quoting a limit.' If invited to reason aloud, state your assumptions clearly rather than presenting an estimate as an approved value.
Question 93 / 101
93. How should you respond to an unclear or unfamiliar question?
Ask a focused clarification: 'Do you mean the clinical-trial process or the postmarketing process?' or 'Which product and market should I assume?' Then answer within that scope. Clarification is useful professional judgement, not an excuse to avoid a question you understand.
Question 94 / 101
94. What if the interviewer points out that your answer is wrong?
Listen, acknowledge the correction and restate the corrected understanding briefly. If your earlier answer depended on a different setting, explain that respectfully without arguing. A useful response is: 'Thank you; I mixed those concepts. In this setting the distinction is …'. Show that you can learn and correct errors.
Question 95 / 101
95. Would you guess when asked an unfamiliar safety-critical question?
No. Explain what action you would pause, which authorised person or reference you would consult and how you would preserve the record. In an interview, describe a safe decision process. Do not imply that you would independently change a patient treatment, release a batch or override a control to avoid admitting uncertainty.
Questions to ask the interviewer
Question 96 / 101
96. What should you say when asked Do you have any questions for us?
Prepare two or three relevant questions rather than asking all of them mechanically. A useful opening is: 'Yes, thank you. What would you most like the person in this role to achieve during the first three months?' Listen to the answer and ask one focused follow-up.
Question 97 / 101
97. How can you ask about training and supervision?
Ask: 'How is initial training organised, and how do you assess readiness for independent work?' This shows that you want to build competence responsibly. Avoid implying that you expect to work without required training or that a course certificate should exempt you from the employer's qualification process.
Question 98 / 101
98. How can you ask about the team's actual work?
Ask which responsibilities, systems, products or projects this position would support and how work is divided across the team. Use the department guide to make the question specific. Do not ask for confidential client names, patient information or unpublished company plans.
Question 99 / 101
99. What is a good question about performance expectations?
Ask: 'How do you balance quality, timeliness and workload when assessing this role?' Follow up on the review and feedback process. This gives a more useful picture than asking only how many items you must finish each day without considering their complexity or quality.
Question 100 / 101
100. When can you ask about shifts, compensation or practical conditions?
Ask the appropriate recruiter or interviewer at a suitable point, especially if a condition affects your availability. Be polite and specific about what you need to understand. You do not need to promise acceptance before receiving the terms, and there is no universal rule that candidates must never discuss pay.
Question 101 / 101
101. How should you close the interview?
Thank the interviewers, briefly reaffirm your interest and ask about the next stage and expected communication process. For example: 'Thank you for explaining the role. I am interested in the opportunity; could you share the next steps?' Avoid demanding an immediate decision or claiming qualifications you did not demonstrate.
Final preparation checklist
- Explain every technical claim on your resume with a truthful example.
- Revise the job description, required tools, terminology and role boundaries.
- Prepare two real examples of a challenge, learning or teamwork using Situation, Task, Action and Result.
- Practise admitting uncertainty clearly and describing how you would verify information.
- Prepare two or three thoughtful questions for the interviewer.