Technical Content Writer jobs in Delhi at CryptoMize are open on a rolling, always-hiring basis — full-time, permanent, with immediate joining. This is the documentation seat for a real platform stack: user guides, online help, developer references and UI text for the intelligence platforms operators work in daily, plus methodology documentation for OSINT and forensics teams. The pipeline is docs-as-code — documentation lives in version control, moves through review like code, and ships on the engineering cadence. If you are a technical writer who wants material that matters and a bar to match, below is the complete job description — responsibilities, requirements, the seniority path, and the selection process.
LOCATION New Delhi (HQ)
EMPLOYMENT Full-time · Permanent
AVAILABILITY Immediate · Rolling intake
COMPENSATION Discussed at screening
TRACKS ON THIS DESK22
CRAFT SKILLS NAMED12
TOOLS & SYSTEMS5
PATH STAGES4
01
01The actual work
What will you actually do as a Technical Content Writer at CryptoMize?
01
Own the documentation estate for the intelligence platform stack — guides, references, and troubleshooting paths that engineers and operators actually use
02
Run the needs analysis properly: engineer and operator interviews, task mapping, and structures built from how users fail rather than how products are organized
03
Own the interface language: labels, empty states, and error messages — the words a system speaks, written as craft
04
Govern single-sourcing across the estate: one change propagating everywhere it must, the same truth maintained once
05
Keep the information architecture honest — restructure when the evidence says users cannot find, and defend the structure when the evidence says they can
06
Commission and create the visuals prose cannot replace: diagrams, graphs, and screenshots chosen for the idea they transfer
07
Edit other writers’ and engineers’ material to house standard, and mentor the documentation interns attached to the desk
ROLE RESPONSIBILITIES
As a Technical Content Writer at CryptoMize you will research, write and maintain the documentation real operators work from: user guides and references for the intelligence platform stack, methodology documentation, and UI text. You analyze existing and potential content for reuse and single-sourcing opportunities, and you keep the documentation set coherent as the platforms beneath it change.
The seat works upstream of the page: meeting with engineers, analysts and product staff to understand the documentation requirements, determining the clearest and most logical way to present information, and revising instructions and FAQs as the systems evolve. A writer who waits for specs will stall here — the craft includes extracting the knowledge.
Quality is measured by task completion: whether a user can set up, operate and troubleshoot from your pages without asking a human. Reviews are code-style — pull requests, line comments, merge gates — and the bar is engineering-adjacent because the readers are operators under pressure.
Security-aware documentation is part of the seat: what may be documented publicly, what stays internal, and how capability is described without exposing method — an agency's documentation carries the same confidentiality discipline as its client work.
02
02Capability profile
What skills and tools does a Technical Content Writer need?
astro-island,astro-slot,astro-static-slot{display:contents}
Craft skills12 Tools & systems5 Offer standards4
Simplifying complex concepts without dumbing them downInformation architecture for documentation setsAudience analysis — first-time user vs. operator vs. developerTechnical interviewing — extracting knowledge from specialistsSingle-sourcing and content reuse disciplineUI microcopy craftEditing other writers' material with restraintVisual explanation — diagrams, annotations, screenshotsVersion-control workflow for docs (Git-class)Consistency and standardization across platforms and mediumsPrecision — in technical material, ambiguity is a defectMentorship of docs interns
Markdown docs-as-code pipelines (Git-based)Static-site documentation generators (MkDocs-class)Mermaid / draw.io-class diagrammingGitHub review workflow for docs pull requestsGoogle / Microsoft developer-documentation style guides
Depth of demonstrated skill in the specific role disciplineClassification and scope of the client engagement the role supportsUrgency and time-sensitivity of active project requirementsTrack record built across CryptoMize engagements
Also known as: technical writer jobs · documentation writer vacancy · docs writer openings · information developer jobs
03
03Seniority ladder
Technical Content Writer — seniority path at CryptoMize
Writers advance by whether users complete tasks with their docs, not tenure. The ladder below is how the documentation function is actually organized.
Technical Content Writer
Owns documentation areas inside the platform stack — guides, references and release notes through the docs-as-code pipeline.
1/4
Senior Technical Writer
Owns the documentation architecture: structure, standards, single-sourcing strategy, and the review bar other writers meet.
2/4
Documentation Lead
Runs the documentation function — pipeline, tooling, platform relationships, and the task-completion evidence the stack is judged by.
3/4
Head of Technical Content track
The leadership route: full docs-and-technical-content ownership across platforms, products and methodology teams.
4/4
04
04The engagement surface
CryptoMize work a Technical Content Writer touches
Every role plugs into live engagements across the five Penta-P domains — these are the services your work feeds.
Technical Content Writer · Job Opening
This seat plugs into 6 live CryptoMize services across the five Penta-P domains — the work below is where yours lands.
6 SERVICESPENTA-P
Content Creation
Content Marketing
OSINT
Big Data Mining
Media Consultancy
Search Management
WHAT DOES TECHNICAL CONTENT WRITER COMPENSATION DEPEND ON?
Compensation is discussed during screening — never a fixed public figure, because it varies per person and per engagement. It depends on:
# OFFER CONSTRUCTION FACTOR
01 Depth of demonstrated skill in the specific role discipline
02 Classification and scope of the client engagement the role supports
03 Urgency and time-sensitivity of active project requirements
04 Track record built across CryptoMize engagements
