FORWARD DEPLOYED AI ENGINEERING · ENTERPRISE AI

Jorge Carbonell

Forward Deployed
Engineer.

AI agents, RAG and LLMs. From pilot to production.

I embed with your team and customers to take artificial intelligence from pilot to production. I build AI agents, RAG and LLM applications around real data and workflows; backend, integrations and cloud provide the foundation to operate them.

15+ years in engineering4+ apps in productionBACKEND / CLOUD / AI
01Customer problem
02Code & integration
03Production & adoption

01 / WHERE THE BUSINESS GETS STUCK

What's stopping your AI pilot from reaching production?

A model is not enough: enterprise AI needs accessible data, workflow integration, evaluations and operations. As an FDE, I work with your team to address these blockers.

01 /

The pilot works. Nobody wants to launch it.

Test data looks great. Real permissions, failures and users expose the gaps.

WHAT I IMPLEMENT

A scoped end-to-end path: real data, authentication, evaluations, observability and rollback.

WHAT WE TRACK

Testable acceptance criteria and a launch-readiness checklist.

02 /

Every enterprise customer becomes another project.

SSO, APIs, ERP and data requirements delay activation and consume engineering capacity.

WHAT I IMPLEMENT

Reusable connectors, API contracts and deployment patterns, alongside the customer's technical team.

WHAT WE TRACK

Time to the first operational workflow and open integration blockers.

03 /

The AI answers. But you can't rely on it.

Hallucinations, out-of-scope data and overprivileged agents hold back real usage.

WHAT I IMPLEMENT

Access-aware RAG, real-world evaluations, traces, tool boundaries and human review where it matters.

WHAT WE TRACK

Evaluation-set quality, failures and human escalations.

04 /

Everyone is involved. Nobody owns the next step.

Product, IT, security and business work separately. Launch falls between teams.

WHAT I IMPLEMENT

A technical point of contact who builds, documents decisions and makes dependencies and exit criteria visible.

WHAT WE TRACK

Open dependencies, owners and decisions needed to launch.

05 /

The customer wants exceptions. The roadmap pays.

Bespoke solutions accumulate. Every deployment adds maintenance that is hard to sustain.

WHAT I IMPLEMENT

Separate configuration from custom code, extract shared components and feed field signals back to product.

WHAT WE TRACK

Reused components, documented exceptions and maintenance burden.

06 /

It's deployed. Nobody uses it.

A new tool won't change a process if it forces people to work differently.

WHAT I IMPLEMENT

Embed in existing workflows, validate with users and prepare operations and team handover.

WHAT WE TRACK

Repeat workflow usage, completed tasks and operator feedback.

02 / THE MISSING ROLE BETWEEN TEAMS

Not another coordination layer. Someone who builds.

An FDE combines customer context with hands-on execution. I don't replace your product, security or sales teams: I work with them and bring the solution into the field.

01

Close to the customer

Discovery with real users, systems and constraints. Not a brief passed between teams.

02

Inside engineering

Code, APIs, data and deployments. Decisions visible in repositories, not just slide decks.

03

Back to product

Feedback, reusable patterns and documented boundaries so the next customer doesn't start from scratch.

Applied AI engineering: RAG, agents and LLMOps

01

Enterprise RAG and semantic search

Connect internal documents and data to LLMs using retrieval-augmented generation (RAG). Build context retrieval, citations and access permissions; evaluate relevance and answers against real queries.

02

AI agents and workflow automation

Build agents that use APIs and tools across support, operations and internal workflows. Define permissions, execution boundaries, retries and human approval for sensitive actions.

03

LLM applications and copilots

Integrate language models into existing products and tools. Build structured outputs, model selection and per-task quality, cost and latency evaluation.

04

LLMOps, evaluation and cloud deployment

Prepare regression tests, traces and output monitoring. Build GCP, AWS or Azure deployments with scalable backends, alerts and recovery procedures.

03 / WHERE THIS ROLE FITS

Pick the bottleneck. Let's make the work concrete.

Illustrative engagement scenarios, not client case studies or promised results.

Your next customer needs an integration that doesn't exist yet.

For product teams and CTOs who want to activate customers without turning every onboarding into a roadmap detour.

INTERVENTION

  • Map systems, identity and workflows with customer IT.
  • Build integrations, queues, retries and synchronization.
  • Prepare deployment and end-to-end workflow tests.

WHAT STAYS WITH YOUR TEAM

  • Connector and API contracts
  • Integration tests and traces
  • Runbook and reusable pattern

HOW WE TRACK PROGRESS

Time to the first operational workflow, synchronization failures and remaining manual work.

04 / DELIVERABLES, NOT BLACK BOXES

The engagement ends. The capability stays.

Code in your repositories

Reviewable changes, tests and documented architectural decisions.

Visible operations

Deployment, alerts, metrics and recovery procedures.

A team that can carry on

Context handover, known boundaries and prioritized next steps.

We define baselines and targets together. These are progress indicators, not guaranteed improvements or invented ROI percentages.

How I embed

First we scope a need. Then we build a useful end-to-end path and validate with its operators. Scope and pace depend on access, dependencies and complexity.

01 /

Understand on the ground

Work with the customer and team to map the problem, dependencies and success criteria.

02 /

Implement & validate

Build an initial solution using real data and workflows; iterate with the people who will use it.

03 /

Operate & hand over

Document decisions, deployment and operations; feed learning back to product and engineering.

Jorge Carbonell. Customer context, technical depth.

15+ years in engineering and 4+ apps in production. My focus: backend, microservices, integrations, GCP, AWS, Azure and applied AI. I work inside your systems and alongside the people using them.

APIsMicroservicesGCP / AWS / AzureRAG / LLMsObservability

Two ways to work together

Need to unblock an initiative or bring this role into your team? We can discuss either.

PROJECTS

A concrete challenge. Inside your team.

To implement an integration, deploy AI or take a customer solution to production. Scope, commitment and terms are agreed after reviewing the context.

Discuss a project

EMPLOYMENT

A role. End-to-end ownership.

For companies hiring an in-house Forward Deployed Engineer, close to customers and engineering. Let's discuss responsibilities, team, location and salary range.

Offer a role

Before I join your team.

How is an FDE different from a solutions architect?

Responsibilities may overlap between companies. In my offering, beyond architecture I write code and integrations and prepare deployment and operations alongside the customer. The responsibility doesn't end with a design or demo.

What does an AI-focused Forward Deployed Engineer do?

They work alongside customers to turn a use case into an integrated, operable AI application. My focus is RAG, agents and LLMs: connecting data and tools, evaluating outputs and preparing deployments with traceability and human oversight. This fits AI-first companies and enterprises adopting AI in existing workflows.

Do you work with our team or replace it?

I embed with product and engineering and collaborate with customer IT, security and users. We scope my technical responsibility without replacing business, security or legal-review owners.

What do you need to get started?

A concrete problem, a technical point of contact and agreed access to the necessary people and systems. Start by emailing customer context, the bottleneck and your stack; don't send credentials or sensitive data.

Do you accept both projects and employment?

Yes. For projects we agree scope, commitment and terms. For employment we discuss responsibilities, team, working arrangement, location and salary range. No predefined rate or availability.

How do we handle security and confidentiality?

We can agree an NDA before reviewing sensitive information. We use bounded access and document permissions and decisions. Security and legal reviews belong to your organization's owners; I don't issue certifications.

JORGE CARBONELL / FORWARD DEPLOYED ENGINEER

What's blocking your AI deployment?

Tell me the bottleneck, your stack and who's affected. I'll reply personally to assess the fit; no long form or generic proposal.

jorge@weddedgroup.com