
Forward Deployed Software Engineer
Posted 11 days ago
The role in short
Deploy, debug, and support UFORCE's autonomous systems in the field, writing scripts and managing software configurations during customer trials and operations.
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
We’re looking for a Forward Deployed Engineer to make UFORCE systems work reliably in the field. You’ll work alongside engineers, operators and customers during trials, demonstrations, training and deployments, resolving issues and turning field experience into practical improvements.
Software is your primary discipline, but this is not a desk-based software role. It’s a hands-on, deployed position where you’ll work across the wider system, from networking and communications to equipment setup and operator workflows.
You don’t need deep mechanical, marine or electronics expertise. We’re looking for strong software skills, practical operational experience and the ability to learn quickly.
The role is a remote based role, with regular travel to field sites and customer locations locally and internationally.
What You Will Do
- Own technical execution in the field: deploying, configuring, and supporting our systems during trials, demonstrations, training, and customer activity, often with limited backup.
- Manage the software side of deployments, including baselines, versions, configuration control, release notes, validation checks, and rollback and recovery procedures.
- Diagnose faults across the whole deployed system using structured fault isolation, separating software, hardware, network, comms, power, sensor, configuration, operator, and environmental causes.
- Read logs, reproduce issues, test hypotheses, and capture clear evidence, then hand issues back to Engineering with enough context to act on them quickly.
- Write scripts and small tools that automate checks, validate configuration, parse logs, and reduce manual work in the field.
- Prepare for field activity by checking equipment, cabling, compute setup, spares, tools, checklists, and documentation. Support practical tasks beyond software, such as system setup and compute swaps, and improve preparation so deployments become faster and more repeatable.
- Turn field observations into clear feedback for Software, Product, Operations, and Engineering, closing the gap between what is built, what is deployed, and what the customer expects.
- Support operators and customers during demonstrations and training, explain technical issues clearly to both specialist and non-specialist audiences, and help customers become more self-sufficient after handover.
- Improve software readiness over time, including observability, release discipline, documentation, and knowledge transfer, so the field depends less on engineering reach-back.
What We're Looking For
- Strong software engineering ability as your primary discipline, with skills in Python and/or C++ for debugging, log analysis, and system maintenance.
- You can read, write, and debug code and scripts and are comfortable with version control, APIs, services, and logs.
- Systems-minded judgment. You can explain interfaces, dependencies, and trade-offs across software, compute, networking, comms, sensors, hardware, and field operations, and you avoid assuming that every problem is a software problem.
- Experience deploying and configuring Linux-based software systems, including package management, services, containers, updates, rollbacks, and repeatable deployment methods.
- Practical field troubleshooting experience in deployed or operational settings, such as military or global operations, motorsport, field engineering, remote production, customer sites, maritime, robotics, aerospace, or automotive environments.
- Working knowledge of networking and integration, including TCP/IP, VLANs, routing, VPNs, DNS, DHCP, firewalls, and how to tell a software failure from a connectivity, sensor, or data-link problem.
- Operational discipline: you prepare thoroughly, use checklists, manage risk, escalate sensibly, and stay calm under pressure.
- Clear technical communication, including structured, unambiguous reporting that Engineering can act on and operators can understand.
- A team-first, high-ownership approach. You work well with a small, multidisciplinary team, including during extended deployments, and are willing to travel regularly and support field activity.
Nice to Have
- Experience with robotics, uncrewed systems, autonomy or mission software, sensors, telemetry, operator interfaces, or defence trials.
- Experience deploying software to edge compute or in disconnected environments, including containers and orchestration, CI/CD, infrastructure automation, observability, and controlled updates.
- Familiarity with tools such as Docker, Kubernetes, Helm, Ansible, or Terraform.
- Experience representing a technical team in customer demonstrations, trials, training, or deployments.
- Experience working in security-sensitive or controlled environments.
The nature of combat has changed.
Tomorrow’s battlefield success depends on autonomy, speed, and adaptability.
And UFORCE is ready.
Are You?
Prep for this interview
5 questions likely to come up at UForce, each matched to a line in this posting.
- 1Cloud, deployment and security
They wrote: “Familiarity with tools such as Docker, Kubernetes, Helm, Ansible, or Terraform.”
How would you debug a deployment that works in staging but fails at the customer's site?
How to answer
Why they ask: Customer environments differ in ways you can't see. This tests method under pressure.
- Compare versions, config and environment variables
- Check network rules, proxies and certificates (common in enterprise)
- Look at resource limits and permissions
- Add the missing check to your install steps afterwards
Tip: List the usual suspects and how you'd check each without full access.
- 2Coding
They wrote: “Strong software engineering ability as your primary discipline, with skills in Python and/or C++ for debugging, log analysis, and system maintenance.”
Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.
How to answer
Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.
- Read with a proper CSV parser; check the header first
- Validate each row and collect errors, not crash on the first one
- Send in batches with retries and a clear report at the end
- Write one or two quick tests for the parsing
Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.
- 3Integrations and APIs
They wrote: “You can read, write, and debug code and scripts and are comfortable with version control, APIs, services, and logs.”
A customer's API starts returning errors in production at 2am. What do you do?
How to answer
Why they ask: FDEs often own production for their customers. This tests incident handling and communication.
- Check your side first: logs, recent deploys, retries piling up
- Stop the damage (pause jobs, queue requests, turn off the feature)
- Tell the customer what you see and what you've done, in plain words
- Afterwards: add a check that would have caught it, and write a short report
Tip: Split the answer into the first hour and the week after.
- 4Ownership and working with customers
They wrote: “A team-first, high-ownership approach. You work well with a small, multidisciplinary team, including during extended deployments, and are willing to travel regularly and support field activity.”
Tell me about something you shipped that broke in production.
How to answer
Why they ask: Everyone has broken production. They want to hear you own it and change something afterwards.
- What broke and who it affected
- How you found out and what you did in the first hour
- The root cause, said plainly
- What you changed so it can't happen the same way again
Tip: Pick a real one with a cost. Spend most of the answer on what you changed.
- 5Travel
They wrote: “The role is a remote based role, with regular travel to field sites and customer locations locally and internationally.”
How do you handle being on the road with customers for weeks at a time?
How to answer
Why they ask: Many FDE roles involve regular travel. They check you know what you're signing up for.
- Your past travel or on-site experience
- How you stay productive away from the team
- What travel level works for you, said plainly
Tip: Be honest about what works for you. A mismatch here hurts both sides later.
Not the one? Get the next one by email
New roles land here every day. Pick what you want to hear about.
Want the job, not just the posting? Learn how FDEs work.
FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.
Free. One email a week. Unsubscribe in one click.
