Learn to write good technical interview questions: scenario-based, rubric-aligned, and inclusive.
0 / 10 completed
1 / 10
What is a 'scenario-based question' in technical interview design?
Scenario-based questions present a realistic work situation: 'Describe a time when you had to migrate a monolith to microservices under time pressure.' They elicit concrete, behavioural evidence rather than abstract knowledge claims.
2 / 10
What is a 'rubric' in technical interview vocabulary?
A rubric defines expected responses: what a strong answer looks like, what a passing answer looks like, and what a weak answer looks like — enabling calibrated, bias-resistant evaluation across different interviewers.
3 / 10
What makes a question 'inclusive' in technical interview design?
Inclusive questions avoid assumptions: don't use sporting metaphors unfamiliar globally, don't assume home internet or expensive tools, and don't use idioms that may not translate. Questions should evaluate the skill, not cultural familiarity.
4 / 10
What is a 'leading question' — and why should interviewers avoid it?
A leading question suggests the answer: 'Don't you think microservices are better here?' This allows candidates to signal agreement without demonstrating understanding. Open-ended questions ('What approach would you consider?') are better.
5 / 10
What is 'question calibration' in interview design?
Question calibration validates a new question: running it with current employees to see if strong engineers answer well and weaker ones struggle. Without calibration, questions may be too easy, too hard, or ambiguous.
6 / 10
Reviewer: 'This function isn't testable as written. It directly manipulates external state—we need a mock to isolate the logic.' What does 'mocking' typically refer to in the context of code reviews?
'Mocking' is about isolating units of code for testing. It involves creating a fake or simulated version of something that would normally be complex or unreliable (like a database connection or an external API). This allows developers to test their code without actually relying on the real dependency, simplifying debugging and ensuring more reliable results. Option A describes unit testing, not mocking.
7 / 10
Slack Message (from Alex to the team): 'Just deployed v2.1.0 – fixed that intermittent memory leak we spotted last week!'. What is Alex most likely referring to when discussing 'v2.1.0'?
In software development, 'version' refers to a specific build or release of software that includes changes and updates. The naming convention (e.g., v2.1.0) is a standard way of tracking these releases and their associated improvements. Option A describes a schema change, and options C & D are irrelevant to the term 'version'.
8 / 10
PR Description: 'Implemented the new user authentication flow using OAuth 2.0. The API endpoint returns a JWT token upon successful login.' What does 'JWT' stand for in this context?
'JWT' stands for 'JSON Web Token', which is a compact, self-contained way to securely transmit information about a user's identity and permissions. It's commonly used in modern web applications for authentication and authorization. Option A & C are incorrect; Option D is nonsensical.
9 / 10
Standup Update (from Ben to the team): 'I've been working on refactoring the payment processing module. I'm using a new library called 'FastPayments' to handle the transactions.' What is Ben likely trying to achieve by mentioning 'FastPayments'?
'FastPayments' is likely referring to a third-party library or service that specializes in payment processing. Using such a tool allows developers to leverage existing functionality and expertise, reducing development time and potentially improving the reliability and security of the payment system. This contrasts with options A (audit), C (timeline) and D (legal documentation).
10 / 10
Code Review Comment: 'Consider using a more descriptive name for this variable – it's currently just 'data'. It makes the code harder to understand and maintain.' What is the reviewer primarily addressing in this comment?
This comment focuses on code readability and maintainability – a core principle of good software development. Using descriptive variable names (e.g., 'customerOrderData' instead of just 'data') makes the code easier to understand for other developers (or yourself in the future). Options A & D relate to algorithm efficiency or initialization, while option B concerns data types.
What does this Technical Interviewing exercise cover?
This exercise, "Writing Technical Interview Questions — Vocabulary", tests your understanding of technical interviewing vocabulary and phrasing through 10 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this Technical Interviewing exercise for?
It's designed for IT professionals and learners who want to sound natural discussing technical interviewing topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more Technical Interviewing exercises?
Browse the full Technical Interviewing exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.