Senior Technical Writer

We are looking for a technical writer with a strong engineering background who can write complex, detailed, "engineering" articles—with clear logic, verifiable steps, diagrams, tables, constraints, and measurement methodology.

The role focuses on low latency/HFT/trading infrastructure.

Publications will be published on the following platforms: support.metaquotes.net , mql5.com .

The key difference of the role: we need a specialist who doesn't "rehash" or write marketing text, but translates complex engineering expertise into clear, production-level materials—with fact-checking, structure, examples, and validation of the results.

Tasks

• Write in-depth technical articles and guides for support.metaquotes.net and mql5.com:
• Reworking other people's articles and source materials (internal notes, drafts, English-language materials, public sources):
• refactoring of structure and narrative,
• increasing clarity and "engineering",
• updating, adding diagrams, tables, examples, and "how to make sure it works" checks.
• Create cycles/series (example formats)
• Create regular how-to materials:
• short step-by-step instructions without fluff,
• checklists, troubleshooting, FAQ.
• Prepare visual elements:
• diagrams, charts, sequences, "data flows",
• illustrations of measurements and benchmarks (what was measured, what was measured with, how to repeat).
• Work with SMEs (managers, developers, etc.):
• interview, extraction of expert opinion,
• fact-checking, agreement on terms, final proofreading.
• Repurpose pipeline with the content team:
• each large article → plan/script for 1 screencast,
• 3-5 shorts,
• 5 posts/extracts for social networks/announcements.

Requirements

• Technical background is required.
• Understanding the topics (not at the level of terms, but at the level of causes and effects):
• latency budgets, jitter, throughput,
• lock contention, profiling, bottlenecks,
• kernel/network tuning, TCP/UDP, multicast (plus),
• time sync: NTP/PTP,
• measurement techniques and reproducibility of results.
• Ability to write "like an engineer":
• specifications and step-by-step guides,
• tables, diagrams, benchmarks,
• restrictions, trade-offs,
• sections "how to check/validate", "typical mistakes", "when not to do this".
• Confident editing and revision of materials:
• You know how to "extract the meaning," restructure, and make the text shorter/clearer without losing precision.
• Tools:
• Git (basic workflow),
• Markdown,
• diagrams: Mermaid / draw.io (or equivalents),
• Basic work with code: reading, commenting, carefully inserting fragments.
• Communication:
• ability to interview engineers and bring material to publication through approval.
• Russian — fluent (literate). English — sufficient for reading documentation/sources and working with terminology.

Important: You write texts that can withstand the scrutiny of engineers—without making "eyeball" assumptions, with careful wording and verifiable steps.

It will be a plus

• Experience in fintech/trading/exchange infrastructure.
• Practical experience in performance tuning, latency measurements, profiling (prod or close to prod).
• Experience with docs-as-code, content pipelines, editorial templates, and unified style guidelines.
• The skill of turning an article into a script: structure, timing, bullet points, CTA (for linking with a screencaster).
• Practical experience using AI tools as an accelerator (drafts, translation, subtitling/voiceover for derivative materials) while maintaining responsibility for accuracy.

Test task

After the initial interview:

• Rewrite 1 existing article (yours or someone else's) into the following structure: 
  problem → context → solution → steps → validation → pitfalls → FAQ → CTA
• Write a mini-article: "Latency measurement methodology for matching engines" (1200–1800 words) + 2 diagrams.

Expected result (KPI)

• 2–4 long technical articles per month + 4–8 short how-tos per month
• Mandatory repurpose: each long article → 1 screencast + 3–5 shorts + 5 posts/announcements

What we offer

• Work in Cyprus, registration in accordance with local legislation.
• Competitive salary (negotiated based on experience and level of writing/portfolio).
• Medical insurance (conditions depend on the type of employment and are discussed at the final stages).
• Direct access to experts and live case studies: you'll write about real-world production challenges and engineering solutions.

How to respond

In your response, please include:

• resume,
• links to 2-5 relevant materials (articles, documentation, posts, guides - it is important that the "engineering letter" is visible),
• briefly (5-10 lines):
• your technical background,
• 1-2 topics in which you are strongest,
• an example of how you reworked someone else's material (what was "before" and what was "after").