Forward Deployed Engineer

At Nutrient, we're revolutionizing how the world works with documents. Our tools transform static files into intelligent, secure workflows, empowering businesses to innovate faster and smarter. Trusted by thousands of organizations across 80 countries, including Fortune 500 companies and public sector leaders, our platform supports nearly a billion end users globally in industries where documents aren't just files, they're mission-critical.

As a Forward Deployed Engineer (FDE) on our Sales team, your work starts with a customer:

• You will find the document problem that is actually costing them money, and build the working solution yourself, on their documents, that works with or within their environment, against a scorecard we agree on before we start.
• Then you will turn what you built into something the next customer can buy ready made. We commit to the specific outcome for the customer, and we then measure how much of each engagement converts into actual product.

Here’s how this role is different:

• If you are a solutions engineer today, the difference is that you ship.
• If you are a professional services engineer today, the difference is that the work is not billed by the hour against a spec someone else wrote, and success is not a signed-off SOW but a customer outcome and a reusable capability in the product.
• If you are a product engineer today, the difference is that your users are in the room, on the call, and occasionally disagreeing with you.

This is a role for someone who is genuinely comfortable in all three chairs: the discovery conversation where you work out what job the customer is actually trying to get done, the terminal where you build it by Friday, and the seat at the table when the product is being meaningfully developed.

• Discover the problem before anyone scopes it
  . Get into the customer's process deeply enough to state the job to be done in their words. Most engagements start because someone asked for a feature; the work is finding the outcome behind the request.
• Build the first implementation yourself
  . Working software on the customer's own documents and in their own environment if necessary, fast enough that the demo lands while the problem is still urgent. A prototype that shows beats a deck that tells, and a working solution closes the deal.
• Agree a scorecard upfront and hit it. Every engagement starts with a written definition of what success looks like and how it will be measured. We commit to that result.
• Stitch across the whole platform
  . Real solutions cut across Nutrient Workflow, Document Engine, our Document Web Services APIs, the Web and native SDKs, AI data extraction, and whatever the customer already runs. Recent engagements have meant SharePoint and Salesforce integrations, AWS Bedrock models, .NET services behind consistent-hash routing, bulk export pipelines, and database archiving.
• Productize what you build
  . Choose the implementation that makes the next customer easier, not the one that closes fastest. In a recent engagement we deliberately built a cover-sheet generator on AI Data Extraction rather than a SQL script, and that task is now stronger for every customer. Several deliverables from that engagement are now licensable product components and self-service features.
• Close the loop back into the company
  . Write up what you learned, file the defects you hit, articulate the pattern so the next engagement starts from it, and hand the template to the next team. Forward deployed work that stays inside one account is just consulting.
• Support the deal
  . You will work alongside account executives and solutions engineers before the contract as well as after it. What you build during the sales cycle is often what decides…