Learn behavioral question structure, job-related vs. illegal question distinctions, and technical difficulty calibration vocabulary.
0 / 10 completed
1 / 10
What does 'STAR-compatible question design' mean when creating behavioral interview questions?
STAR-compatible questions ask for a past experience ('Tell me about a time...', 'Describe a situation where...') so candidates answer with real evidence — Situation, Task, Action, Result. Hypothetical questions ('What would you do?') are easier to answer generically and harder to calibrate across candidates.
2 / 10
What is a 'job-related question' in interview design?
Job-relatedness is the legal and psychometric standard: each interview question must assess something necessary to perform the job. 'Tell me about a time you debugged a production incident under time pressure' is job-related for a senior engineer; 'Are you planning to have children?' is not job-related and is illegal.
3 / 10
Which of these is an example of an illegal interview question in most jurisdictions?
Questions about nationality, religion, age, disability, marital status, pregnancy, or family plans are illegal in most jurisdictions because they assess protected characteristics unrelated to job performance. Interviewers must be trained to recognise these and redirect if a candidate volunteers such information.
4 / 10
What is 'difficulty calibration' in technical interview question design?
Difficulty calibration ensures a question is neither too easy (no differentiation) nor too hard (everyone fails, no signal) for the target level. Calibration involves: having internal engineers at the level solve the problem, measuring time to solve, and tracking historical candidate success rates in the interview rubric.
5 / 10
What is a 'question rubric' in technical interview design?
A question rubric specifies what each performance level looks like: e.g., 'Strong Hire: identifies optimal algorithm, discusses edge cases proactively, clean code with clear variable names. No Hire: produces a working brute-force but cannot discuss time/space complexity or improve it when prompted.' Rubrics are essential for calibrated, defensible scorecards.
6 / 10
During a Slack conversation with the team lead, Sarah says, "Let's refactor this module to use dependency injection and improve testability.". Which of the following best describes the vocabulary she's employing?
Sarah is using the term 'Dependency Injection' – a crucial design pattern. Dependency injection promotes loose coupling, making code more modular and easier to test. She's also referencing 'testability,' which is the key benefit of applying this technique. Options A, C, and D represent broader concepts or actions, not the specific vocabulary used in her statement.
7 / 10
Reviewing a PR submitted by David, you notice he's added extensive logging throughout the codebase. He justifies this by saying, "I need to capture all error conditions and track performance metrics.". What is the primary vocabulary term associated with this approach?
David is utilizing 'Centralized Logging,' which involves collecting logs from all parts of the application into a central location for analysis and debugging. This allows for comprehensive monitoring of error conditions and performance metrics. The other options represent distinct design patterns or techniques with different purposes. It's important to differentiate between simply logging and implementing centralized logging practices.
8 / 10
During a standup meeting, Mark says, "I'm tackling the performance bottleneck by optimizing database queries and caching frequently accessed data.". What is the most relevant vocabulary term associated with Mark's actions?
Mark is focused on 'Performance Tuning,' which involves optimizing system resources to improve speed and efficiency. Specifically, he's addressing a bottleneck by optimizing database queries and implementing caching – techniques commonly used when dealing with large datasets or inefficient data access patterns. The other options represent different architectural approaches or deployment strategies.
9 / 10
You're crafting a PR description for a new feature that includes a detailed explanation of the API endpoint and its expected response format. Which term best describes this approach?
The description you provided focuses on 'API Documentation,' which is crucial for communicating the details of an API endpoint – its functionality, response format, and any relevant constraints. While Swagger and GraphQL are related technologies, they represent distinct approaches to API design and documentation. RESTful Design describes a broader architectural style.
10 / 10
During a code review session with Emily, she asks, "Can we apply the SOLID principles to this class to improve its maintainability and reduce coupling?"
Emily is referencing the 'SOLID Principles,' a collection of five design principles – Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion – that guide object-oriented design to create maintainable and robust software. These principles are fundamental to good code quality and reducing coupling between components. The other options describe different development methodologies or practices.
What does this Technical Interviewing exercise cover?
This exercise, "Designing 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.