In my previous post, I explained why technical written tests are useful. In this one, I want to explain what kind of questions candidates can expect on those tests.
The scope of technical written tests is pretty broad. They’re used in a variety of roles that require some level of technical knowledge:
• Technical writing
• QA/manual testing
• IT contracting
• Mechanical engineering
And so on.
But the focus of this article is not on how to prepare for these tests — it’s on what kinds of questions you might actually be asked. I’ll talk about what kind of questions are asked in each role, and how to handle them.
Technical writing questions
Let’s start with technical writing. The most commonly asked question in technical writing interviews is probably “Can you tell me about your experience writing documentation?” This is an example of a behavioral interview question, which asks about specific situations from your past work. But there are also plenty of other types of questions that come up in technical writing interviews, including more general questions about the field. Some examples include:
• How do you approach documenting a new product?
• What tools do you use to create technical documentation?
• How do you ensure that your documentation is accurate and up-to-date?
• What steps do you take to make sure that your documentation is easy to understand?
• What challenges have you faced when creating technical documentation, and how did you overcome them?
These questions help employers assess your knowledge of the field, your communication skills, and your ability to write clear and concise documentation.
When preparing for a technical writing interview, it’s important to practice answering questions like these. You should be able to provide representative questions with appropriate answers. A strong answer will show that you understand the importance of clear communication in technical writing and that you know how to apply that understanding in your work.
QA and manual testing questions
Manual testing and QA written tests tend to focus on a few core areas of knowledge. Here are 25+ manual testing interview questions to help you get ready:
-
Explain SDLC and STLC.
-
What is test design?
-
What is defect life cycle?
-
What is severity vs priority?
-
What is difference between verification and validation?
-
What is test case?
-
What is test plan?
-
What is test scenario?
-
What is test strategy?
-
What is test objective?
-
What is test environment?
-
What is test data?
-
What is test automation?
-
What is performance testing?
-
What is load testing?
-
What is stress testing?
-
What is usability testing?
-
What is regression testing?
-
What is compatibility testing?
-
What is smoke testing?
-
What is sanity testing?
-
What is acceptance testing?
-
What is integration testing?
-
What is system testing?
-
What is unit testing?
A strong answer to any of these questions will cover both domain knowledge and communication ability. For example, when asked to define a test case, a candidate who just says “It’s a document that describes what we’re going to test” won’t impress the interviewer. Instead, they need to explain the purpose of a test case, how it relates to other elements of the software development lifecycle, and why it’s important to write good test cases.
Scenario-based vs. situational questions
Scenario-based and situational questions are two different types of questions that appear on written tests. Scenario-based questions ask candidates to describe how they would respond to a specific situation. Situational questions ask candidates to describe how they would respond to a hypothetical situation.
Scenario-based questions are usually based on real-life situations that candidates might encounter on the job. These questions often ask candidates to describe their thought process and behavior in response to a particular situation. Situational questions are typically hypothetical, and they ask candidates to describe how they would respond if a certain circumstance arose.
The ideal answer to a scenario-based question includes three parts: a description of the situation, a description of the strategy the candidate would use to correct the error, and a description of the benefits that the candidate would extract from the situation (e.g., reframe the situation as a learning opportunity). A strong answer to a situational question should be similarly structured.
Engineering and project-based roles
Written tests for engineering roles require candidates to demonstrate their knowledge of the field. However, unlike oral interviews or academic exams, these tests don’t necessarily require candidates to answer every question correctly. Instead, they require candidates to demonstrate their knowledge by providing well-written, thoughtful answers to a selection of questions.
For example, a mechanical engineering written test might ask candidates to elaborate on their experience with technical projects, their personal contributions to those projects, and the results they achieved. Candidates might also be asked to describe where they thrived and what they liked working on. These types of questions help employers assess a candidate’s knowledge of the field, their ability to communicate effectively, and their ability to think critically.
In addition to demonstrating their knowledge of the field, candidates should also demonstrate their ability to communicate effectively. This means being able to write clearly and concisely, using proper grammar and punctuation, and organizing their thoughts in a logical way.
Finally, candidates should demonstrate their ability to think critically. This means being able to analyze information, draw conclusions, and make decisions. It also means being able to identify problems and develop solutions.
Candidates should prepare for a written technical test by practicing answering questions like these. They should also make sure that their answers are clean and well-organized.
If a question is unclear
If you’re unsure about what a question is asking, it’s permitted and even advised to ask for clarification. There’s no reason to guess at an answer to a question you don’t understand. If you’re unsure about what a question is asking, ask for clarification. You can say something like, “I don’t quite follow, could you explain?” Or you can ask, “How important is that to the project?”