# Technical Content Writer Job Opening at CryptoMize 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. ## Facts - Location: New Delhi (HQ), CDR Building, Chhatarpur - Type: full-time permanent - Availability: immediate, rolling intake (always hiring) - Compensation: discussed at screening ## What you will actually do - Own the documentation estate for the intelligence platform stack — guides, references, and troubleshooting paths that engineers and operators actually use - Run the needs analysis properly: engineer and operator interviews, task mapping, and structures built from how users fail rather than how products are organized - Own the interface language: labels, empty states, and error messages — the words a system speaks, written as craft - Govern single-sourcing across the estate: one change propagating everywhere it must, the same truth maintained once - Keep the information architecture honest — restructure when the evidence says users cannot find, and defend the structure when the evidence says they can - Commission and create the visuals prose cannot replace: diagrams, graphs, and screenshots chosen for the idea they transfer - Edit other writers’ and engineers’ material to house standard, and mentor the documentation interns attached to the desk ## Skills - Simplifying complex concepts without dumbing them down - Information architecture for documentation sets - Audience analysis — first-time user vs. operator vs. developer - Technical interviewing — extracting knowledge from specialists - Single-sourcing and content reuse discipline - UI microcopy craft - Editing other writers\' material with restraint - Visual explanation — diagrams, annotations, screenshots - Version-control workflow for docs (Git-class) - Consistency and standardization across platforms and mediums - Precision — in technical material, ambiguity is a defect - Mentorship of docs interns ## Tools - Markdown docs-as-code pipelines (Git-based) - Static-site documentation generators (MkDocs-class) - Mermaid / draw.io-class diagramming - GitHub review workflow for docs pull requests - Google / Microsoft developer-documentation style guides ## Questions and answers ### What are the requirements for Technical Content Writer jobs at CryptoMize? Demonstrated technical documentation — shipped docs users completed tasks from, experience extracting knowledge from engineers, and comfort in a Git-class review pipeline. An engineering or CS background helps; the shipped documentation decides. ### Are the Technical Content Writer openings in Delhi? Yes — the position is based full-time at our New Delhi HQ in Vasant Vihar, embedded with the platform and methodology teams you document. ### Is this Technical Content Writer vacancy immediate joining? Yes. Openings are rolling and always active — documentation capacity is staffed ahead of platform releases, so strong candidates are onboarded as soon as notice periods allow. ### What does a Technical Content Writer do at CryptoMize? They document the intelligence platform stack — user guides, references, UI text and release notes — in a docs-as-code pipeline, structure the documentation set around real user tasks, and edit technical material from engineers into shippable form. ### What is the salary for a Technical Content Writer at CryptoMize? Compensation is discussed at screening and depends on demonstrated skill, engagement classification, urgency, and track record. We do not publish figures — each offer is built individually. ### How does the selection process work? Application with documentation samples, one explanation task — document a small process from a source brief we provide — and a final interview with the documentation lead where you defend structure and wording live. Typical cycle: two to three weeks. ### What is the seniority path from this seat? Writer → Senior Technical Writer (documentation architecture) → Documentation Lead (runs the function) → Head of Technical Content track. Writers whose docs measurably complete user tasks move fastest. Apply: https://cryptomize.com/careers/job-openings/apply/