Start from the workflow, not the model
Sit with the people who own the process. Agree on the problem, the data, the constraints and what a good outcome looks like. Write the spec and the architecture decisions before the first line of code.
I'm Gustavo. I embed with a team to scope, build and ship LLM systems that reach real users: agents with guardrails, retrieval over your own data, evals, and the engineering to run them. Twenty years building product, ten of them as Product Manager.
Forward Deployed Engineer: I work inside the customer's team, understanding their needs from the first definition of the use case to the system running in production. AI agents write a lot of the code; I own the scoping, the architecture, the review and what ships.
Sit with the people who own the process. Agree on the problem, the data, the constraints and what a good outcome looks like. Write the spec and the architecture decisions before the first line of code.
Prototype fast, then harden: retrieval, guardrails, permissions, fallbacks and hand-off to a human. Every change is reviewed and checked against evals, tests, security and cost before it ships.
CI/CD with a preview per change, monitoring and usage metrics from the first release. Then playbooks and building blocks the team can keep running without me.