Forward Deployed Engineering

How I became a forward deployed engineer without a software engineer title

The title is new; the work is old. Twelve years of enterprise deployments plus public, measured AI work. The honest path, artifacts included.

By Simon Gonzalez de Cruz (follow the build in public on X @KyaniteLabs_). 2026-08-24. The honest version, no resume inflation.

You do not need a software engineer title to do forward deployed work, and my path is the proof. I hold no FDE badge from an AI lab. What I have is twelve years of deploying enterprise systems for real organizations, then a period of building and measuring AI on my own hardware with everything published. That combination is the job. This post is the path exactly as it happened, with the artifacts, and without inventing anything.

Let me be precise about what I am not claiming, because this industry runs on inflated claims. I was never employed as a software engineer. I never worked at Palantir or an AI lab. If you want those lines on a resume, this is not your post. If you want to do the work and be findable by it, it is.

Phase one: twelve years of deployments nobody called FDE

Enterprise learning systems: Workday, SuccessFactors, Cornerstone, for organizations of more than 8,000 people. That work was forward deployment in everything but name. Configuration for a real customer's strange requirements. Integrations with whatever systems already existed. Data migrations where an error means a person's training record disappears. Rollout, training, and then ownership in production, for years.

The transferable skills from that world: reading a messy real workflow and finding where it actually breaks, writing for non-engineers, and treating go-live as the beginning, not the end. If you have done this kind of work in ERP, CRM, medical systems, or industrial software, you already have phase one. You just have not labeled it.

Phase two: own the whole stack, then measure it

The modern version of the job needs AI-specific skills. I built them in public, on my own hardware, because that removes every excuse. The rig is a $1,400 GMKtec EVO-X2 mini-PC running a 27B model locally. Everything below is linked and reproducible.

  • Serving in production. The model runs always-on with watchdogs, restart recovery, and queue discipline. The complete measured serving story, with the upstream llama.cpp bug we caught, bisected, and validated the fix for, is on this blog.
  • Benchmarking with intervals. 93% HumanEval (28/30, frozen subset) and 67% LiveCodeBench-30 (20/30, Wilson 95% interval 49 to 81). Published with conditions, seeds, and raw logs.
  • An eval with my name on it. delegation-bench: 495 trials, 29 cells, certified floors, a sabotage cell, walk-away certification. This artifact does more work than any title. Details in evals are the FDE skill nobody lists.
  • Shipped open source people actually use. A video-editing MCP server, Kinocut, with merged upstream contributions. Integration glue is the daily texture of forward deployed work.

The exact recipe, if you want to copy it

Step one: take a domain where you already know what "working" means. Step two: buy or rent hardware you control, or use cloud if you must, and run a real model workload on it. Step three: measure something honestly and publish the number with its interval and its conditions. Step four: build an eval for a decision someone actually makes. Step five: keep the system running unattended and write down what breaks.

Do those five things and you will have what interviewers for these roles are actually probing for: evidence you can find the leverage point, build with evals, and own it in production. None of the five steps requires a title. All of them produce artifacts with your name on them.

The honest gaps

What this path does not give you: the internal referral networks of a big lab, experience with frontier-scale training runs, and the specific brand names that recruiters filter on. Those are real costs and I will not pretend otherwise. The compensation is that everything you claim is checkable, and the buyers who care about checkable are the buyers worth having.

Start with the series: what a forward deployed engineer actually does, the title decoder, and the eval skill.

Want this work done in your environment instead of reading about it? Implementacion intake. Every artifact cited: delegation-bench (evals), qwen38-27b-strix-halo (serving), simongonzalezdc (Kinocut and other repos). Conditions for all numbers: $1,400 GMKtec EVO-X2, Qwen3.8-27B Q4_K_XL, llama.cpp.

Trabajar con Kyanite

¿Quieres que esto funcione en tu entorno?

Si esta nota describe una herramienta o resultado de Kyanite que necesitas, la ayuda de implementación cubre setup, asesoría, docs, ejemplos, checks y un handoff usable.

Límite de fit

Kyanite offers help grounded in its tools, products, and build practice. La consultoria mas amplia se enruta por PuenteWorks.

Sigue el sistema.

The One-Line Bug That Crashed Our Fast Lane: finding, fixing, and measuring a speculative-decoding crash on a $1,400 mini-PC

Spec decoding crashed our fastest lane on day one. The bug was one missing line in our fork; the fix bought +17.7% and a surprise about draft quantization.

Dos modelos, una mini-PC de $1,400: los números emparejados, fracasos incluidos

Un modelo de razonamiento de 35B ya corre junto a nuestro 27B diario en una caja de $1,400, al mismo tiempo. Cada número emparejado, mismos problemas, misma máquina. Los fracasos también están aquí.

Evals are the FDE skill nobody lists: my 495-trial public benchmark

The market says it cannot find people who can build AI evals. The skill is learnable and I published mine: 495 trials, certified floors, sabotage cell, open source.

Forward deployed vs solutions engineer vs implementation vs customer engineer: el decodificador

Cuatro títulos, una familia de trabajo, barras de código distintas. Un decodificador para leer cualquier vacante y saber en qué te estás metiendo.

Qué hace realmente un forward deployed engineer

La respuesta directa y luego los recibos: todo el trabajo de un FDE sobre un mini-PC de $1.400, con evals públicas.

The Delegation Card: we asked a $1,400 mini-PC to take our jobs

Not is-it-smart but can-you-hand-it-work-and-walk-away. 495 certified trials, then re-validated at deeper n after the product changed: 965 total, floors to 92.8%.

Qwen 3.8 27B en Strix Halo: la historia completa, medida

Cada dial medido, cada numero publico: la configuracion optima congelada para un 27B en un mini-PC de $1.400.

Notas: the measured-knees method for reasoning effort

A methods note on reasoning-effort calibration. Thinking rescued 15/40 hards vs 4/40 off. On easy tasks it bought nothing. Publish the knee.

Notas de lab: 67% LiveCodeBench-30 en un rig de $1.400

20/30 = 67% LiveCodeBench-30 en un mini-PC de $1.400. IC Wilson 95% 49-81%. Easy 10/10, medium 8/10, hard 2/10. Subset n=30. No es la card.

Notas de lab: revertimos una regresión de llama.cpp

Encontramos una regresión de llama.cpp y la revertimos. Batería n=6 en un rig de $1.400: 0/6 slashes antes, 5/6 después. Mismo Q4_K_XL. No es una historia de quant.

Notas de lab: 93% HumanEval en un rig de $1.400

28/30 = 93% HumanEval en un mini-PC de $1.400. Qwen3.8-27B Q4_K_XL. Temp 0, thinking off. Fallos: 50 y 145. Log crudo linkeado.

Notas de lab: el modelo que no puede olvidar pero no puede recordar

El número primero: este modelo es 75% no transformer. 48 de 64 capas guardan un estado. En un rig de $1.400, carga 198k una vez (1818s) y consulta en 9-27s.

Notas de lab: la cuenca era un bug

Publicamos una cuenca. El hueco era el binario. Tras revertir c7d8722: 6/6 HIT a 198k. Mapa n=1 del build arreglado.

Notas de lab: el veredicto del KV

La pregunta q8-a-q4 del KV de la noche 1 ya tiene respuesta pareada: misma accuracy, cero tripwires, la mitad del cache. Y el label que tuvimos que corregir en público cuando el contador del server le ganó al estimado.

Notas de lab: la noche del veredicto

Un mini-PC de $1.400 sirviendo un 27B a 262k de contexto hace una pregunta: ¿capear cuánto piensa el modelo te cuesta accuracy? La respuesta pareada, el primer intento inválido, y la doctrina que quedó.

Un mini-PC, una noche y los numeros que discutian entre si: afinando Qwen3.8-27B en Strix Halo

Una noche y una tarde de medicion afinando un modelo denso de 27B en un mini-PC Strix Halo: las bandas honestas, la reversion, la doctrina de crashes y la historia detectivesca del EC.

GPT-5.6 Sol vs. Terra vs. Luna: politica de ruteo basada en evidencia

La division practica es Sol para descubrir, Terra para ejecutar trabajo acotado y Luna para procesar volumen verificable, cada uno con un contrato distinto.

Los agentes necesitan herramientas verificables, no mejor teatro de prompts

El patron util no es un prompt mas bonito. Es una superficie de herramienta que el agente puede llamar, inspeccionar, verificar y revisar.

El historial del repo es una señal de producto

Un repo no es solo almacenamiento. Es evidencia de decisiones, reparaciones, releases, cambios de nombre, huecos de pruebas y oficio real.

La ayuda de implementacion es parte de la superficie del producto

Una herramienta open source util todavia necesita una ruta desde repo publico hasta entorno funcionando. Esa ruta es producto.

Por que importa Kinocut

Kinocut da a los agentes de IA herramientas llamables sobre timelines, efectos, Hyperframes y medios terminados en kinocut.dev.

Monos infinitos, LLMs y el cuarto alrededor de la maquina

El argumento detras del video: la calidad no es solo probabilidad. Es arquitectura, filtros y gusto humano.

Lo que una herramienta de IA necesita antes de que alguien pueda usarla

Una guia practica para convertir una herramienta, flujo o app medio cruda en algo que otros puedan entender, instalar y usar.

Checklist de implementacion para servidores MCP

El checklist que Kyanite usa para distinguir un servidor MCP de juguete, una herramienta usable y algo que vale la pena implementar.

La arqueologia de repos convierte historia en evidencia

Por que el historial de commits es una de las fuentes de prueba mas fuertes para diagnosticos, implementacion y confianza tecnica.

El descubrimiento por IA necesita mas que un sitemap

Lo que Kyanite agrega para que buscadores y asistentes de IA entiendan herramientas, productos, prueba y rutas de soporte.