1. Professional profile
1.1 Chapter introduction
I am an AI-first technical writer and subject matter expert who turns complex technology into practical guidance. My background in enterprise support and network systems informs how I research product behaviour, write structured documentation, and build tools for research, review, migration, and publishing. My formal role is Technical Writer II at SOTI.
1.2 Who I am
I am Aiman Nabeel Peerji, an AI-first technical writer and subject matter expert with a foundation in network systems and enterprise technical support. I investigate how technology works, turn that understanding into usable guidance, and improve the tools and workflows that help teams produce reliable documentation. My current role is Technical Writer II at SOTI. The experience behind this portfolio spans troubleshooting, structured authoring, product research, documentation quality, and AI-assisted automation.
My journey began with network-systems education and service desk work at RWDI. Working with directory services, email, computers, and access problems taught me to connect technical details with the person trying to get something done. Enterprise support expanded that experience into device management, identity integration, logs, databases, and customer environments.
Writing grew naturally out of that work. Through knowledge-base articles and Project Sherpa, I helped turn individual investigations into reusable knowledge and supported other agents in explaining their findings. Moving into technical writing brought that practice into DITA/XML, source control, peer review, and product releases. Over time, my scope expanded again: from improving individual topics to improving how content is researched, reviewed, migrated, and published.
That progression is the central story of this portfolio. SOTI products provide substantial examples of the work. The capabilities I have developed—technical investigation, clear explanation, editorial judgement, collaboration, and practical automation—define my professional direction.
1.3 How I use subject matter expertise
My subject matter expertise is grounded in enterprise mobility, device enrollment, identity and directory integration, server behaviour, application deployment, and troubleshooting. As a writer, I use that operational background to ask better questions, investigate prerequisites and exceptions, and check procedures against product evidence. My documented research includes Signal properties and events, device audit logging, Apple enrollment, and declarative application policies.
I also consider the reader's route through the information. Task structure, navigation, screenshots, related guidance, and rendered output all affect whether someone can find and follow an explanation. The verified Git examples show changes to those concrete parts of the help. “Subject matter expert” describes this domain experience and practice; it is not presented as an additional formal job title or a claim of expertise in every technology listed here.
1.4 What AI-first means in my work
I use AI as a regular part of research, drafting, review, and tool development. My work includes reusable documentation skills, workflows that connect product evidence to structured content, and experiments that make authoring and review more accessible. The July 2026 workflow account connects Jira research, implementation details, design evidence, screenshots, DITA source, validation, Git, and peer review.
Technical understanding and human judgement remain central to that process. I check generated material, refine review guidance from actual decisions, and distinguish a proposal, a working utility, and a published result. My AI-first approach builds on earlier writing and support experience.
The career journey explains how that approach developed. The Projects page follows the tools and workflows, Writing shows inspectable source changes, and Skills pairs the products and tools with the roles where I used them.