Forward Deployed Engineer at Menlo

About Forward Deployed Engineering at Menlo

Menlo Research is an Applied R\&D lab building Asimov, an open\-source humanoid robot platform, and the full software stack that powers it. Our mission is to make humanoid labor economically viable, turning software into physical labor at scale. We build across the full stack: hardware architecture, locomotion, autonomy, simulation, and infrastructure. We move fast, ship to real robots, and open\-source everything we can. If you want your work to matter beyond a paper or a demo, this is the place. As a Forward Deployed Engineer on our Deployment team, you’ll embed with Menlo’s enterprise customers and own their Asimov deployments end to end, from a scoped use case to a robot doing real work in their environment. You’ll write the integration code, configure the platform, debug the robot on the floor, and bring back what you learn so the next deployment goes faster than the last. You’ll partner with our Enterprise Lead on the customer side, and with Brain, Platform, and Hardware on everything behind it.

Companies like Menlo typically structure FDE teams around a build-team model, where engineers join an existing customer engineering function and deploy the product across a portfolio of accounts. Based on FDE Pulse data across 1212 active postings, 1% of FDE roles are build-team positions and 0% are "first hire" situations where the engineer defines the function. Menlo's 1 active posting falls into the first hire category based on role count.

FDE roles across the market are 1% North America-focused based on 1212 active postings. 0% of FDE roles are classified as growth hires, meaning the company is expanding its customer base rather than backfilling an existing position. This context matters for FDE candidates evaluating Menlo: growth hire roles often come with more pressure to ramp quickly but also clearer performance metrics tied to customer success.

What FDEs Do at Menlo

Forward Deployed Engineers at Menlo own the technical success of customer deployments. This means designing integration architectures specific to each customer's infrastructure, writing and maintaining production code that runs in customer environments, and serving as the primary technical point of contact for enterprise accounts. The role sits at the intersection of product engineering and customer success without being either.

Day-to-day work for an FDE at Menlo varies by customer complexity and deployment stage. In the early phases of a new customer engagement, FDEs focus on environment setup, data mapping, and building the first integrations. As deployments mature, the work shifts toward performance tuning, expanding use cases, and training customer teams on new capabilities. Some FDE roles also feed product insights back to internal engineering, effectively acting as a bridge between customer needs and the roadmap.

Career Path for FDEs at Menlo

FDE careers typically progress along one of three paths: deepening technical specialization within the FDE function (moving from mid-level to senior to staff FDE), transitioning into engineering management (leading FDE teams or broader customer engineering organizations), or lateral moves into product management (where customer-facing FDE experience is highly valued). All three paths are available at companies with established FDE programs.

The FDE market median of $180,000 base salary across 134 active postings reflects a market that prices the role at a premium over equivalent-seniority software engineers at the same companies. Total compensation including equity, particularly at venture-backed companies, can be 20 to 50 percent higher than base salary. FDEs considering opportunities at Menlo should evaluate total compensation, rather than only base salary, when comparing offers.

Interview processes for FDE roles at most companies include a technical coding round, a system design round specific to customer deployment scenarios, and a customer scenario exercise where candidates are asked to scope a deployment, communicate trade-offs, and handle technical objections. Strong candidates combine engineering depth with the ability to explain complex systems to non-technical stakeholders clearly and without jargon.

Frequently Asked Questions