Nine client assignments, from a simple integration to an agent in production
A Forward Deployed Engineer works inside the client: gets an ambiguous business problem, does discovery, decides what to build, integrates it with what already exists and leaves it running with the team trained. Each assignment here is a fictional client with that full cycle, and each one ends in a public repo of yours.
Assignment content is in Spanish for now; the English version ships as an update.
Ingesta de pedidos desde Excel y email hacia su ERP
freePanel interno de stock unificando 3 fuentes
freePipeline diario de datos de producción y calidad
full courseCierre mensual de nóminas para la gestoría
full courseExtracción de datos de facturas PDF con LLM
full courseAsistente interno sobre pólizas y procedimientos
full courseAgente de soporte que consulta CRM y abre tickets
full courseDesplegar un agente apto para producción en la infraestructura del cliente
full courseAutomatizar de punta a punta la gestión de incidencias
full courseHow each assignment is worked
- Read the brief and the requirements. They are the client’s email and the initial document, ambiguous on purpose.
- Review concepts and tools. Each tool comes with setup, an example and resources; mark the ones you already master.
- Create the empty repo on GitHub with the name the assignment gives and ask your agent for the initial skeleton.
- Move step by step. Each one has a guide, checks, suggested branch and PR, and a mentor to ask.
- Handle the client’s twist when it shows up: it is the requirements change that always arrives.
- Deliver and take the quiz. Paste the repo link, tick the deliverables and check what you learned.
Repo conventions
Same skeleton in all nine repos, so whoever reviews them knows where to look.
fde-0N-cliente-tema/
├── README.md # inglés, enlaza a README.es.md
├── README.es.md # español
├── docs/
│ ├── es/ brief.md · requisitos.md · proceso.md · adr/ · handoff.md
│ └── en/ brief.md · requirements.md · process.md · adr/ · handoff.md
├── src/ tests/
├── .github/workflows/ci.yml
└── .env.example- Process docs in Spanish and English, in separate files. Written in Spanish and translated in the same PR when each step closes.
- Code, comments, commits and branches in English. Conventional Commits and one PR per step.
- Only fictional data generated by a script. Never secrets in the repo.