A written test for an ITSM Technical Writer role typically assesses your ability to create clear, structured, and technically accurate documentation. It may include questions and tasks related to ITSM processes, ITSM tools (like ServiceNow, BMC Helix, or Jira Service Management), structured authoring (DITA/XML), and best practices for technical writing.
Sample ITSM Technical Writer Written Test
—————————————————————————————————————————
Section 1: Writing and Documentation Skills
1. Write a step-by-step user guide for creating an incident ticket in ServiceNow.
(Include screenshots if applicable, but focus on structure, clarity, and completeness.).
Creating an Incident Ticket in Jira Service Management
Introduction:
Jira Service Management (JSM) allows users to report incidents quickly, ensuring that IT teams can resolve them efficiently. This guide walks you through the process of creating an incident ticket in JSM.
Prerequisites
- You must have access to the Jira Service Management portal.
- You need the correct permissions to submit an incident request.
Steps to Create an Incident Ticket
Step 1: Access the Jira Service Management Portal
- Open your web browser and navigate to the Jira Service Management portal.
- Log in using your credentials if prompted.
Step 2: Navigate to the Incident Request Form
- On the portal homepage, locate the “Help Center” or “Service Desk” section.
- Click on the “Report an Incident” option.
Step 3: Fill in the Incident Details
- Summary – Enter a brief but descriptive summary of the issue. (e.g., “Unable to access company email”)
- Description – Provide detailed information about the issue, including steps taken, error messages, and affected users.
- Priority – Select the appropriate priority level based on the impact and urgency:
- High – Critical business impact (e.g., system outage).
- Medium – Moderate business disruption.
- Low – Minor impact or inconvenience.
- Attachments (Optional) – Upload screenshots, logs, or relevant files to support the issue report.
- Affected Services (Optional) – Choose the impacted application or service from the dropdown list.
Step 4: Submit the Incident Ticket
- Review all the entered details for accuracy.
- Click the “Submit” button.
Step 5: Track the Incident Status
- After submission, you will receive a ticket ID (e.g., INC-12345).
To check the status:
- Go to the “Requests” section in the portal.
- Use filters to find your incident under “My Requests”.
- You can add comments or attach additional files if needed.
Step 6: Communicate with the Support Team
- If an agent updates the ticket, you will receive a notification.
- You can reply to comments or provide additional details as requested.
- Once the issue is resolved, confirm the resolution and close the ticket if required.
Conclusion
By following these steps, you can efficiently create and track an incident ticket in Jira Service Management, ensuring that IT teams can resolve the issue promptly.
—————————————————————————————————————————
2. Rewrite the following technical paragraph for clarity and conciseness:
“The configuration management database (CMDB) is a repository that stores information about hardware, software, network devices, and other IT assets used in an organization’s IT environment. The CMDB helps organizations track asset relationships, dependencies, and changes, thus making it easier to manage IT services, resolve incidents, and perform impact analysis before implementing changes.”
The Configuration Management Database (CMDB) is a centralized repository that stores information about an organization’s IT assets, including hardware, software, and network devices. It tracks asset relationships, dependencies, and changes, enabling efficient IT service management, incident resolution, and impact analysis before implementing changes.
———————————————————————————————————————————
3. Create a short knowledge base article (200-300 words) explaining the difference between Incident Management and Problem Management in ITSM.
Difference Between Incident Management and Problem Management in ITSM
Introduction
Incident Management and Problem Management are key processes in IT Service Management (ITSM) that help organizations maintain service quality. While they are closely related, they serve distinct purposes in managing IT issues.
What is Incident Management?
Incident Management focuses on restoring normal service operations as quickly as possible when an issue occurs. An incident is any unplanned interruption or degradation of an IT service, such as a server outage or application crash. The goal of Incident Management is to minimize downtime and impact on users by providing a quick resolution, often through temporary workarounds.
Key Aspects of Incident Management:
- Objective: Restore services quickly.
- Example: A user reports that they cannot access their email. The service desk resets the password to resolve the issue.
- Approach: Reactive—addresses issues as they arise.
What is Problem Management?
Problem Management focuses on identifying and eliminating the root cause of recurring incidents to prevent future disruptions. Unlike Incident Management, which provides immediate fixes, Problem Management conducts root cause analysis (RCA) and implements long-term solutions to reduce the frequency and impact of incidents.
Key Aspects of Problem Management:
- Objective: Identify and resolve underlying causes of incidents.
- Example: After multiple email access issues, an investigation reveals a faulty authentication server. A permanent fix is applied.
- Approach: Proactive—prevents future incidents by addressing their root cause.
Conclusion
While Incident Management handles immediate service disruptions, Problem Management prevents recurring issues by addressing their root causes. Both processes work together to enhance IT service stability and efficiency.
===============================================================================
Section 2: ITSM Process & Best Practices
4. Define the following ITSM terms in simple language:
- Change Management
- Service Level Agreement (SLA)
- Knowledge-Centered Service (KCS)
- Request Fulfillment
- IT Asset Management (ITAM)
ITSM Terms and Definitions
1. Change Management
Change Management ensures that IT changes (such as software updates, infrastructure upgrades, or new system implementations) are planned, reviewed, and approved before implementation. The goal is to minimize risks, avoid service disruptions, and maintain system stability.
Example: Before rolling out a new email server, the IT team follows a structured approval process to assess risks and schedule the change during off-peak hours.
2. Service Level Agreement (SLA)
A Service Level Agreement (SLA) is a contract between an IT service provider and its customers that defines the expected service quality, response times, and responsibilities. It sets clear performance benchmarks to ensure accountability.
Example: An SLA may state that IT support must respond to high-priority incidents within 15 minutes and resolve them within 4 hours.
3. Knowledge-Centered Service (KCS)
KCS is a knowledge management methodology that encourages IT teams to create, update, and share knowledge articles based on real-time issue resolution. This approach helps reduce repetitive incidents and empowers users with self-service solutions.
Example: A support agent documents a solution for fixing VPN issues, making it available in a self-service portal for future users.
4. Request Fulfillment
Request Fulfillment is the process of handling service requests, such as password resets, software installations, or new hardware provisioning. Unlike incidents, these are standard user requests that follow a predefined workflow.
Example: An employee submits a request for VPN access, and IT fulfills it within 24 hours as per company policy.
5. IT Asset Management (ITAM)
ITAM tracks and manages an organization’s IT assets, including hardware, software, and network devices, throughout their lifecycle. This ensures cost control, compliance, and optimal resource utilization.
Example: ITAM helps track laptop inventory, ensuring that outdated devices are replaced on time and software licenses remain compliant.
———————————————————————————————————————————-
5. You need to document a new Change Management process. What key details should you gather from Subject Matter Experts (SMEs)? List at least five.
When documenting a Change Management process, gathering accurate and detailed information from Subject Matter Experts (SMEs) is crucial. Here are five key details you should collect:
1. Change Types and Categories
- What are the different types of changes (e.g., Standard, Normal, Emergency)?
- How are changes categorized based on risk and impact?
2. Change Request and Approval Workflow
- What are the steps for submitting a Change Request (CR)?
- Who reviews and approves changes (e.g., Change Advisory Board (CAB), IT managers)?
- What are the escalation procedures for urgent changes?
3. Risk Assessment and Impact Analysis
- What criteria are used to assess the risk and impact of a change?
- What dependencies or systems might be affected?
- Are there rollback or contingency plans in case of failure?
4. Change Implementation and Communication
- What are the implementation steps, including pre-change testing and validation?
- How are stakeholders and affected users informed before and after the change?
- What communication channels (email, ITSM tool, meetings) are used?
5. Post-Implementation Review and Documentation
- How is the success of a change evaluated?
- What documentation needs to be updated after the change?
- Are there lessons learned or best practices to improve future changes?
By gathering these details, you can create a well-structured Change Management document that ensures clarity, compliance, and minimal service disruption. 🚀 Let me know if you need a DITA XML version!
================================================================================
Section 3: Structured Authoring & DITA/XML
6. Convert the following unstructured content into a structured DITA XML format: Title: ITSM Ticket Prioritization Introduction: Tickets are categorized into Priority 1, 2, 3, and 4 based on impact and urgency. Steps: Assess impact. Determine urgency. Assign priority level. Notes: Priority 1 tickets require immediate attention.
(Use appropriate DITA tags such as <concept>, <task>, <step>, etc.)
<?xml version=”1.0″ encoding=”UTF-8″?>
<!DOCTYPE concept PUBLIC “-//OASIS//DTD DITA 1.2//EN” “dita.dtd”>
<concept id=”itsm-ticket-prioritization” xml:lang=”en-US”>
<title>ITSM Ticket Prioritization</title>
<shortdesc>Tickets are categorized into Priority 1, 2, 3, and 4 based on impact and urgency.</shortdesc>
<task id=”prioritize-tickets”>
<title>Steps to Prioritize ITSM Tickets</title>
<stepsection>
<step>
<cmd>Assess impact.</cmd>
</step>
<step>
<cmd>Determine urgency.</cmd>
</step>
<step>
<cmd>Assign priority level.</cmd>
</step>
</stepsection>
</task>
<note type=”attention”>Priority 1 tickets require immediate attention.</note>
</concept>
—————————————————————————————————————
Scenario-Based Question
7. Your company is migrating ITSM documentation from Word documents to a DITA-based structured authoring system. How would you plan and execute this migration?
Migrating ITSM documentation from Word documents to a DITA-based structured authoring system requires careful planning and execution. Here’s how I would approach it:
1. Planning the Migration
a. Assess Existing Documentation
- Identify all Word documents and categorize them (e.g., Incident Management, Change Management, Knowledge Base).
- Analyze document structure, formatting inconsistencies, and metadata usage.
b. Define DITA Content Model
- Establish a DITA specialization or reuse strategy based on ITSM needs.
- Define topic types:
- Concepts (e.g., What is Change Management?)
- Tasks (e.g., How to create an incident ticket?)
- References (e.g., SLA priority levels)
- Identify common elements for DITA maps and conditional content (e.g., different versions for internal vs. external audiences).
2. Execution Phase
a. Convert Word Content to DITA
- Use automation tools like DITA-OT converters, scripts, or CCMS importers to transform Word content into DITA XML.
- Manually clean and structure content where automation is insufficient.
- Apply DITA best practices such as chunking content into modular topics.
b. Review and Validate Content
- Perform a content audit to ensure accuracy and consistency.
- Validate XML structure using DITA-OT and check for missing links or metadata.
c. Set Up the Publishing Pipeline
- Configure DITA-OT for multi-channel publishing (PDF, HTML, Knowledge Base).
- Integrate with a Component Content Management System (CCMS) like IXIASOFT, Heretto, or Vasont for version control and collaboration.
3. Post-Migration Optimization
a. Training and Adoption
- Train technical writers on DITA authoring tools (oXygen XML Editor, FrameMaker, or Arbortext).
- Document new workflows and governance guidelines.
b. Continuous Improvement
- Collect feedback from stakeholders.
- Optimize metadata, tagging, and linking for better searchability.
Conclusion
By following a structured migration approach—assessing content, defining a content model, converting data, validating outputs, and training users—the transition to DITA can enhance documentation consistency, reuse, and multi-channel publishing for ITSM teams. 🚀
GENERIC LEVEL TECHNICAL WRITER TEST
If you’re preparing for a written test as a technical writer, here are some common types of questions that might be included, along with suggestions on how to approach them:
1. Writing Skills Assessment
Example Question:
Write a brief user guide on how to configure a printer in a Windows environment.
Approach:
Focus on clarity, conciseness, and logical flow. Use headings, bullet points, and step-by-step instructions. Provide troubleshooting tips and any relevant screenshots if applicable.
2. Grammar and Style
Example Question:
Edit the following passage for clarity, grammar, and style.
“The printer wasn’t connected and it didn’t work, thus it was necessary to fix it quickly.”
Approach:
Ensure grammatical correctness and smooth sentence structure. For example, reword to: “The printer was not connected, so it needed to be fixed promptly.”
3. Technical Accuracy and Content Understanding
Example Question:
Explain how to reset a router to its factory settings in 3 simple steps.
Approach:
Provide clear, accurate steps for performing the task. Make sure the instructions are technically correct, and avoid unnecessary jargon or overly complex language.
4. Formatting and Structure
Example Question:
Create a short section of a user manual about installing software, using a table of contents, and bullet points for steps.
Approach:
Pay attention to the organization of the content. Start with a clear heading, and then provide the instructions in a structured format. If the steps are sequential, number them.
5. Understanding the Audience
Example Question:
Write a paragraph explaining how to log into a company’s VPN for an internal user versus an external user.
Approach:
Tailor the tone and level of detail based on the audience. For internal users, you can assume familiarity with basic IT processes, but for external users, provide more context and clear explanations.
6. Visuals and Illustrations
Example Question:
Describe how to annotate a screenshot for a troubleshooting guide.
Approach:
Make sure to explain the purpose of the annotations (to highlight areas of concern, steps, etc.), and suggest using arrows, text boxes, or labels to make the image clear.
7. Document Review and Revision
Example Question:
Review the following document excerpt and suggest improvements in terms of readability and user-friendliness.
Approach:
Focus on simplifying the language, eliminating redundancies, and improving overall flow. Break up long paragraphs into smaller sections with clear headings.
Technical writer written test questions
Here are some sample technical writer written test questions that assess a range of skills, from writing and editing to technical understanding and clarity. These questions can be used to evaluate candidates in the ITSM and general technical writing domains:
1. Writing & Editing
Question:
Edit the following paragraph for clarity, grammar, and tone. Explain your changes.
“The printer had problems during operation it could not print because there was no paper in it, and it wasn’t functioning properly so it was broken.”
Expected Response:
Candidates should improve sentence structure, correct grammar, and simplify the message for clarity. For example, they might revise it to:
“The printer was not functioning because it ran out of paper. Please load paper into the tray and try again.”
Explanation: The revision simplifies the message and removes redundant phrasing, while maintaining clarity.
2. Step-by-Step Instructions
Question:
- Write a step-by-step guide for configuring a VPN connection on a Windows 10 machine.
- Ensure your steps are clear, concise, and user-friendly.
Expected Response:
Steps should include the following structure:
- Open the Start menu and select Settings.
- Click on Network & Internet.
- Select VPN from the left-hand menu and click Add a VPN connection.
- Enter the VPN provider details, such as server name, your username, and password.
- Click Save and then select the VPN connection from the list to connect.
- Click Connect and enter credentials if prompted.
- Candidates should focus on clarity, consistency in terminology, and logical sequencing of the steps.
3. Audience Analysis
Question:
- Write a paragraph explaining how to reset a password for an internal IT administrator versus a non-technical user.
- For internal IT administrators, assume familiarity with the platform.
- For non-technical users, explain the process step by step in simple terms.
Expected Response:
- For the IT administrator, the response might be:
- “To reset the password, use the admin portal. Navigate to the user’s profile, select ‘Reset Password’, and follow the prompts.”
For non-technical users:
- “To reset your password, go to the login page and click on ‘Forgot your password?’ Enter your email address, and you’ll receive a link to create a new password. Follow the instructions in the email.”
- Candidates should demonstrate the ability to adjust their tone and level of detail based on the audience.
4. Document Formatting and Structure
Question:
You are asked to write a brief troubleshooting guide for a web application that is not loading. Organize your response using clear headings, bullet points, and concise instructions.
Expected Response:
Troubleshooting Guide: Web Application Not Loading
- Check Internet Connection.
- Ensure your device is connected to the internet.
- Try opening other websites to confirm the issue is with the application.
- Clear Cache and Cookies.
Try a Different Browser
Open the application in another browser to see if the issue persists.
Disable Browser Extensions
Temporarily disable any extensions that may interfere with the application.
Restart Your Device
Sometimes, restarting your device can resolve loading issues.
Contact Support
- If the problem persists, contact technical support for further assistance.
- Candidates should focus on concise steps with easy-to-follow formatting.
5. Technical Understanding
Question:
Explain the difference between a full backup and an incremental backup, and when each would be most appropriate in a business setting.
Expected Response:
A full backup captures all data, while an incremental backup only captures changes made since the last backup.
Full backup: Best for initial setups or when restoring data from scratch. It ensures all files are backed up, but can be time-consuming and take up more storage space.
Incremental backup: More efficient in terms of storage and speed. It only backs up changes made since the last backup, but it requires the previous backups for a complete restoration. It’s ideal for daily backups in an ongoing environment.
6. Visuals and Graphics
Question:
You are tasked with creating a screenshot with annotations for a user guide showing how to download an app on a smartphone. What key elements would you annotate, and how would you describe these elements in the user guide?
Expected Response:
The candidate should focus on these aspects:
- Annotation of the download button: “Tap the ‘Download’ button to begin the installation.”
- Arrow pointing to the app icon: “Once downloaded, tap the app icon to open it.”
- Highlighting the installation progress bar: “Wait for the installation to complete.”
The candidate should emphasize the importance of clarity and highlighting the most critical elements of the screenshot.
7. Troubleshooting Documentation
Question:
Write a troubleshooting section for a user guide addressing an issue where an application crashes upon launch.
Expected Response:
Troubleshooting: Application Crashes on Launch
- Check for Software Updates
- Make sure you are using the latest version of the application. Go to the app’s settings and check for updates.
- Restart the Application
- Close the app completely and reopen it to see if the issue persists.
Check System Requirements
- Ensure your device meets the minimum system requirements for the application.
- Clear App Cache: Go to your device’s settings, find the app, and clear its cache.
Reinstall the Application
If the problem continues, uninstall the app and reinstall it from the app store.
Contact Support
If none of the above solutions work, contact technical support with details about the issue.
The response should demonstrate clear instructions with an emphasis on logical troubleshooting steps.
To tailor the written test questions for a technical writer in the ITSM (IT Service Management) domain, I’ll focus on topics relevant to ITSM tools like ServiceNow, BMC Helix, and Jira Service Management, as well as DITA-based documentation. These questions will assess a candidate’s ability to handle both the technical writing and domain-specific aspects of ITSM.
1. Writing & Editing for ITSM
Question:
Edit the following ITSM-related passage for clarity, grammar, and tone. Explain your changes.
“The incident was resolved by the engineer after they done troubleshooting with the user, and they ask the customer to reset the system and everything was fine after that.”
Expected Response:
The candidate should focus on improving sentence structure, verb tense, and clarity. Example revision:
“The engineer resolved the incident after troubleshooting with the user. The engineer advised the customer to reset the system, which resolved the issue.”
Explanation: The revision removes unnecessary complexity, corrects verb tenses, and simplifies the message for clarity.
2. Step-by-Step Instructions for ITSM Tool Configuration
Question:
- Write a clear, concise step-by-step guide for configuring a new service request in ServiceNow.
- Ensure that the instructions are user-friendly for someone with basic technical knowledge.
Expected Response:
- Log in to your ServiceNow account.
- From the ServiceNow Dashboard, navigate to Service Catalog under the Request Management module.
Click on Create New Request.
- Select the appropriate request type from the list.
- Fill in the necessary fields (e.g., description, priority, etc.).
- Click Submit to create the request.
- You will receive a confirmation message and a reference number for tracking.
- The candidate should organize the steps clearly and avoid unnecessary jargon.
3. Audience Analysis for ITSM Documentation
Question:
Write a brief explanation for resetting a password in Jira Service Management, one intended for:
- A non-technical user
- A system administrator
Expected Response:
For a non-technical user:
“To reset your password in Jira Service Management, click on ‘Forgot Password’ on the login page. Enter your registered email address, and you will receive a password reset link. Follow the instructions in the email to create a new password.”
For a system administrator:
“To reset a user’s password in Jira Service Management, go to the User Management section under Jira Admin. Search for the user, click on their profile, and select Reset Password. Follow the prompts to set a new password for the user.”
The candidate should demonstrate the ability to adjust tone and detail according to the audience’s level of expertise.
4. Troubleshooting Guide for ITSM
Question:
Create a troubleshooting guide for an incident management system in BMC Helix where the user is unable to update the status of an incident.
Expected Response:
Troubleshooting Guide: Unable to Update Incident Status in BMC Helix
Check User Permissions:
Ensure your account has the appropriate permissions to update incident statuses. If not, contact your system administrator.
Refresh the Page:
Sometimes the system may fail to update in real-time. Refresh the page to see if the status options become available.
Verify Internet Connection:
Ensure your internet connection is stable. A slow or interrupted connection may prevent status updates.
Clear Cache:
If the issue persists, clear your browser cache and cookies, then try again.
Check for System Errors:
Verify if the issue is related to a system error or outage. Check the BMC Helix Status Page or contact technical support.
Contact Support
- If none of the above steps resolve the issue, contact BMC Helix support with detailed error information.
- The candidate should provide a logical troubleshooting flow and address common ITSM-related issues.
5. Visuals and Screenshots in ITSM Documentation
Question:
Describe how you would annotate a screenshot in a user guide for creating a new incident in ServiceNow. What key elements would you highlight, and how would you explain them in the documentation?
Expected Response:
Screenshot Annotations:
- Highlight the “Create New Incident” button: “Click this button to create a new incident record.”
- Point to the Incident Form: “Fill in the required fields such as Incident Description and Category.”
- Arrow to the Priority Field: “Select the appropriate priority for the incident based on its urgency.”
- Indicate the Submit Button: “Click Submit to create the incident and save the changes.”
The candidate should use clear language and ensure that the annotations are informative and easy to understand.
6. Technical Accuracy in ITSM Tools
Question:
Explain the process of creating and assigning a Service Request in BMC Helix ITSM. Ensure you include the key steps involved and any important considerations for accurate documentation.
Expected Response:
- Log in to BMC Helix ITSM: Ensure you have the appropriate access permissions to create service requests.
- Navigate to the Service Request Module: Under Service Management, select Service Requests.
- Click “Create New”: Fill in the necessary fields, such as Request Type, Priority, and Description.
- Assign the Request: Use the Assignment Group field to assign the request to the correct team or individual.
- Submit the Request: Once all details are filled in, click Submit. A reference number will be generated for tracking.
- Follow Up: Monitor the request and ensure timely resolution as per service-level agreements (SLAs).
The candidate should focus on providing accurate steps while including all key fields necessary for proper request management.
These tailored questions assess both the technical and writing skills required in ITSM-related documentation.