About Nutrient 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. Backed by Insight.
About the role
As a Forward Deployed Engineer (FDE) on our Sales team, your work starts with a customer: 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.
What they're looking for
- You can run a discovery conversation. You ask about the business process before the API, and you can tell the difference between a use case and a job to be done
- You get real leverage out of coding agents. Our customers expect the first working version in days, not sprints, and that only happens if you direct agents well
- You have shipped production software for years, and you still build. You are comfortable being the only engineer on a problem and being a part of a team that delivers the solution
- You are fluent in at least one of JavaScript or TypeScript, .NET/C#, Java, Python or Go, and you pick up the others without drama
- You can stand up and reason about infrastructure: containers, Kubernetes, at least one of AWS, Azure or GCP, reverse proxies and load balancing, Postgres, Redis
- You have worked with LLMs in production, not only in a notebook. Prompt and retrieval design, evaluating extraction quality, cost and latency tuning
More about this role
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.
- 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...
Browse similar: Startup jobs