UFORCE exists to make aggression unaffordable.
Founded in Ukraine and headquartered in London, UFORCE is a defence-technology company with operations across Europe, the United States and Asia.
UFORCE builds uncrewed vessels, ground robotics and aircraft, autonomy software, and the command-and-control layer that operates them together. Each platform is deployable on its own, and stronger as part of the system. Its product lines include the MAGURA family of uncrewed surface vessels, the NEMESIS family of strike platforms, the LIUT family of ground robotic platforms, and counter-UAS systems.
About the role
The Technical Writer, C2 Engineering will turn engineering knowledge into clear, accurate documentation that helps operators, Forward Deployed Engineers, customers, support teams, and engineers use UFORCE software with less direct engineering support.
This role sits in the C2 Engineering team and reports to the VP of Engineering. You will cover Nova Connect, Fleet Depot, Nova Console, UxV onboarding, observability, troubleshooting, deployments, upgrades, and rollback documentation.
What you’ll do
Create product guides that explain what each C2 product does, when to use it, and how to operate it safely.
Write deployment, monitoring, troubleshooting, onboarding, upgrade, rollback, and recovery procedures.
Document Nova Connect cloud deployment, including prerequisites, configuration, validation, handover, and common failure paths.
Build Grafana and observability guides that explain dashboards, metrics, normal/degraded states, and escalation paths.
Create symptom-based runbooks for Nova Connect, UxV behaviour, telemetry, connectivity, Kubernetes, infrastructure, and dependent services.
Document new UxV onboarding workflows from access setup through registration, configuration, pairing, health checks, and readiness confirmation.
Keep release notes, compatibility notes, known limitations, and upgrade guidance current.
Work with C2 Engineering, Platform, Product, FDEs, operators, support, and security teams to extract and validate technical truth.
Build a lightweight documentation process with owners, reviewers, statuses, review cadence, versioning, and clear internal/customer-ready labels.
What success looks like
Priority C2 products have clear, discoverable, validated documentation.
FDEs and customer technical teams can deploy, monitor, troubleshoot, onboard, and upgrade systems with less engineering support.
Grafana dashboards and operational metrics are understandable and actionable.
Common incidents have repeatable runbooks and triage paths.
A technically capable person who did not build Nova Connect can deploy a supported environment using the guide.
UxV onboarding and upgrade procedures include prerequisites, expected results, failure handling, validation, rollback, and escalation.
Documentation is part of release readiness and is reviewed after major product changes.
Recurring support questions and avoidable escalations reduce over time.
Required
5+ years in technical writing, developer documentation, SRE / operations documentation, solutions engineering, or a comparable technical role.
Experience documenting complex software, cloud, infrastructure, robotics, IoT, or mission-critical systems.
Ability to write clear user guides, deployment guides, troubleshooting runbooks, observability references, and upgrade procedures.
Working knowledge of cloud platforms, Linux, containers or Kubernetes, CI/CD, APIs, networking, logs, metrics, and Grafana or similar tools.
Ability to understand distributed systems well enough to document behaviour, dependencies, failure modes, and safe operating procedures.
Experience turning incomplete or conflicting engineering input into clear, reviewable documentation.
Experience validating documentation through execution, user testing, or technical review.
Strong information architecture, documentation lifecycle, and versioning discipline.
Clear communication, strong ownership, and comfort working with busy engineers and operational users.
Awareness of customer-specific, access-controlled, export-sensitive, or operationally sensitive information.
Nice to have
Defence, robotics, UxV, C2/C4ISR, air-gapped, regulated, or high-assurance environment experience.
Experience documenting Kubernetes, ArgoCD, K3s, cloud deployments, observability stacks, or incident response workflows.
Experience writing for FDEs, operators, support teams, customer engineers, or field teams.
Familiarity with telemetry, vehicle onboarding, mission systems, UxV operations, or constrained / low-connectivity environments.
Experience building documentation systems from scratch.
Ability to create useful diagrams, decision trees, tables, screenshots, templates, and examples.
Comfort using command-line tools and following technical procedures in test environments.
The nature of combat has changed.
Tomorrow’s battlefield success depends on autonomy, speed, and adaptability.
And UFORCE is ready.
Are You?
5+ years in technical writing or comparable role; experience documenting complex software, cloud, infrastructure, or mission-critical systems; knowledge of cloud platforms, Linux, containers, Kubernetes, CI/CD, APIs, networking, and Grafana.
Key Responsibilities
- creating product guides
- documenting deployment procedures
- building observability guides
Skills & Tools
Grafana, Kubernetes, ArgoCD, K3s, Linux, CI/CD, API
Job Details
- Category: Communications and Public Affairs
- Seniority: Senior Level
- Commitment: Full Time
- Workplace: Remote — Europe
- Languages: English
About UFORCE
A defence-technology company building uncrewed vessels, ground robotics, aircraft, and autonomy software. — Industry: Information Technology