
Robotics Forward Deployed Engineer
Posted Oct 21, 2026
The role in short
Write and maintain production software for customer-deployed robotics systems while providing on-site engineering support during go-lives and incidents.
About Destro AI
Destro AI is building the intelligence layer for robotics — the system that coordinates robots, humans, and workflows across complex real-world operations. Founded by former leaders from HAI Robotics, Dexterity, and Matic, Destro is built on a simple thesis: robotics has solved movement, but not decision-making. Destro is backed by investors who have previously invested in and built companies like Brex, Figma, Notion, and Instacart.
Destro's MothershipOS is a shared brain across all robots, unlocking complex factory and warehouse workflows. Unlike traditional systems that rely on local intelligence on each robot, Destro brings global intelligence across the entire operation. Destro recently closed its Seed round at one of the highest valuations for a robotics company at this stage, and is already deploying in production with large enterprise operators.
About The Role
We're hiring a Robotics Forward Deployed Engineer, to own the software that runs MothershipOS in live customer warehouses. This role is responsible for writing and maintaining production code, not solely for troubleshooting it, and will serve as the engineering presence on-site when systems need to be brought up, stabilized, or restored to full function.
Schedule Expectations
This is a field deployment role, not a standard office-hours position. Warehouse operations run multiple shifts, and go-lives, incidents, and integrations are not confined to business hours.
- Regular work outside standard business hours should be expected, including nights and weekends. Go-lives are frequently scheduled during off-hours or weekend downtime windows to avoid disrupting customer operations.
- This role may be paged for production issues, including robot faults, network outages, and server failures, outside normal hours, and is expected to respond promptly, either remotely or on-site.
- Extensive travel to customer sites is required, at times on short notice.
- Candidates seeking a fixed 9-to-5, Monday-through-Friday schedule are unlikely to find this role a fit.
What You'll Do
Software
- Write, test, and maintain the software services that run MothershipOS at customer sites, including deployment tooling and diagnostic utilities.
- Design and build internal tools that make field deployments faster and more repeatable.
- Translate field learnings into production-hardening fixes and improvements in the core codebase.
- Maintain clear technical documentation and runbooks so issues can be diagnosed consistently across sites.
Field Deployment
- Deploy and validate Destro's software stack in live warehouses, working directly with customer operations, IT, and engineering teams.
- Own production issues end-to-end during launch and stabilization, including off-hours incidents.
- Improve uptime, throughput, and reliability of deployed systems through both code and infrastructure changes.
Systems and Infrastructure
- Build and maintain containerized services (Docker Compose) running on Destro-managed servers and edge devices.
- Work with cloud infrastructure (GCP) for image management, versioning, and deployment tooling.
- Configure and troubleshoot networking, including VLANs, DHCP, internal DNS, and certificate-based service security.
- Debug across the full stack: robot state faults, sensor issues, API failures, container networking, database queries, and monitoring dashboards.
Who You Are
- 2 to 6 years of experience in systems engineering, robotics software, backend engineering, infrastructure, or field engineering, with genuine software development experience rather than field support alone.
- Comfortable being paged off-hours and traveling on short notice.
- Able to operate independently in ambiguous, high-pressure environments without a fully specified solution.
- Calm under pressure, direct with customers, and demonstrates strong ownership.
Technical Skills
Required
- Strong Python or C++, with the ability to write maintainable, production-grade code.
- Hands-on Docker/Docker Compose experience, including building, deploying, debugging, and versioning images.
- Linux/server administration: command line, logs, processes, systemd, firewalls.
- Networking fundamentals: DHCP, DNS, VLANs, static IP reservations, TLS/certificates.
- Experience with APIs and communication protocols (REST, WebSockets, MQTT).
- Proficiency with Git and standard software development workflows.
Strongly Preferred
- Experience with AMRs, warehouse automation, or fleet management.
- Cloud deployment experience, ideally GCP.
- Familiarity with observability tooling such as Grafana, Prometheus, or time-series databases.
- WMS/WES/ERP integration experience.
Nice to Have
- Experience with robot task allocation, scheduling, or routing.
- Experience with wearables, scanners, or other warehouse hardware.
Prep for this interview
5 questions likely to come up at Destro AI, each matched to a line in this posting.
- 1Travel
They wrote: “Extensive travel to customer sites is required, at times on short notice.”
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.
- 2Integrations and APIs
They wrote: “This is a field deployment role, not a standard office-hours position. Warehouse operations run multiple shifts, and go-lives, incidents, and integrations are not confined to business hours.”
Walk me through connecting our product to a customer's internal system that has no documentation.
How to answer
Why they ask: This happens weekly in the job. They want a calm, step-by-step method.
- Find who owns the system and get read access to a test environment
- Watch real traffic or logs to learn the data shapes
- Build a thin adapter with logging around every call
- Agree on how failures get reported, and who fixes what
Tip: Talk about finding the owner of the system first. The code is the easy part.
- 3LLMs, RAG and agents
They wrote: “This role may be paged for production issues, including robot faults, network outages, and server failures, outside normal hours, and is expected to respond promptly, either remotely or on-site.”
A customer wants a chatbot over their internal documents. How do you build it?
How to answer
Why they ask: RAG is the most common first project. They want the whole path, from messy files to answers people trust.
- Collect and clean the documents; handle permissions per user
- Split them into chunks, embed, and store with source links
- Retrieve, then answer with citations; say “I don't know” when retrieval is weak
- Build a test set of real questions with expected answers before launch
Tip: Spend more time on the data and on testing than on the model.
- 4Cloud, deployment and security
They wrote: “Build and maintain containerized services (Docker Compose) running on Destro-managed servers and edge devices.”
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.
- 5Coding
They wrote: “Regular work outside standard business hours should be expected, including nights and weekends. Go-lives are frequently scheduled during off-hours or weekend downtime windows to avoid disrupting customer operations.”
Build a small in-memory cache. Then add expiry. Then a size limit.
How to answer
Why they ask: Staged exercises show how your code holds up when requirements change mid-interview, like at a customer.
- Start with get and set on a dictionary, plus tests
- Store an expiry time with each value and check it on read
- Track use order and evict the least recently used entry when full
- Say what you'd change for many threads or many machines
Tip: Keep the first version simple and well tested so the next stage is a small change.
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.
