Qureos

Find The RightJob.

Job Purpose

The Documentation Specialist (Technical) is responsible for owning internal technical documentation across engineering and cross-functional teams. The role focuses on converting technical work, meeting recordings, and internal inputs into clear, structured documentation that teams can rely on.

Operating in a fast-paced and high-chaos environment, this role helps reduce knowledge leakage, improve internal alignment, and ensure the internal wiki remains accurate, searchable, and consistently written.

Role and Responsibilities

Technical Documentation & Knowledge Capture

  • Create and maintain internal documentation in the company wiki, including:
  • Technical implementation notes
  • Requirements, user stories, and functional specifications provided by engineering or product owners
  • Internal processes, runbooks, SOPs, and checklists using standardised templates and structure
  • Release notes and change logs where relevant
  • Software manuals and user guides for internal tools and workflows
  • Convert post-meeting inputs into written artefacts by:
  • Listening to meeting recordings, calls, and voice notes
  • Capturing decisions, action items, outcomes, and ownership clearly
  • Writing structured summaries that engineers can use without re-watching recordings

Internal Wiki Ownership

  • Maintain the internal wiki as a reliable source of truth.
  • Apply consistent documentation structure, formatting, and naming conventions.
  • Organise content with clear hierarchy, cross-linking, and page ownership.
  • Review and update outdated documentation to ensure continued accuracy.

Cross-Functional Coordination

  • Coordinate with engineers and stakeholders to collect missing or incomplete inputs.
  • Request clarification on wording, timelines, or ownership when documentation is unclear.
  • Ensure updates are incorporated without turning documentation into scope or requirement debates.

Documentation Quality & Maintenance

  • Maintain clarity, accuracy, and conciseness across all documentation.
  • Track documentation that needs revision after releases or process changes.
  • Keep the wiki clean, organised, and usable for both technical and mixed audiences.

Who You Will Work With

  • Engineering teams and HQ stakeholders (primary audience)
  • QA, DevOps, and cross-functional leads (secondary audience)
  • Leadership teams when documentation is required for wider alignment

What Good Looks Like (Success Criteria)Within the first 30 to 90 days, the successful candidate should be able to:

  • Publish structured meeting summaries and technical documentation consistently
  • Create and follow repeatable documentation formats for requirements and user stories that engineers actually adopt
  • Reduce repeated “what did we decide?” discussions by making decisions and outcomes easy to locate
  • Keep the internal wiki organised, current, and clearly owned

Required Skills & CompetenciesTechnical & Documentation Skills

  • Proven experience writing precise and concise technical documentation, internal knowledge-base content, or software manuals, preferably in a software development or e-commerce environment
  • Experience documenting software systems, user requirements, internal tools, or engineering processes
  • Basic understanding of software development concepts, sufficient to document accurately without constant supervision
  • Strong listening skills and attention to detail, able to extract clear outcomes from unstructured discussion
  • Comfortable working with internal wiki tools, documentation templates, versioning, and cross-linking

Communication & Work Style

  • Strong written English with the ability to produce polished documentation quickly
  • Able to manage multiple documentation streams in a high-change environment Reliable, detail-oriented, and methodical

Nice-to-Have

  • Familiarity with Agile delivery environments (sprints, backlogs, release cycles)
  • Experience maintaining run books, incident notes, or operational documentation

Job Type: Full-time

Pay: Rs180,000.00 - Rs200,000.00 per month

Application Question(s):

  • Do you have 3+ years of experience in Technical Writing or Document Management for software/IT teams? (Yes/No)
  • Are you available to work on-site at Ferozpur Road, Lahore, from 11:00 AM to 8:00 PM? (Yes/No)
  • Rate your written English communication skills: (0–10)
  • Rate your familiarity with the Software Development Life Cycle (SDLC) and Agile workflows: (0–10)
  • Are you comfortable listening to long technical recordings (meetings) and extracting action items/decisions without supervision? (Yes/No)

Work Location: In person

© 2026 Qureos. All rights reserved.