Hire me as your AI Enablement Engineer
Availability
| Role | AI Enablement Engineer |
| Start | Immediately |
| Engagement | Permanent or part-time |
| Work mode | Onsite or hybrid in Vienna, remote EU, remote worldwide |
| Work authorisation | Austrian citizen — no work permit or visa sponsorship needed anywhere in the EU |
| Languages | Spanish (native), English (C2), German (C1) |
| Based in | Vienna, Austria |
| Currently | Agentic engineering & AI enablement (since July 2026) |
The role I do best is a mix: hands-on in one product team, with a mandate to spread the practice to the others.
What I take on
- Applied AI, from need to MVP. I scope the problem with the people who have it, then build prototypes, proofs of concept and MVPs on their real data and systems. I say plainly when a demo isn't a product yet.
- LLM features and internal tools. End-to-end applications and pipelines on hosted models: retrieval (RAG) over a team's own documents and code, orchestration and tool use over MCP, guardrails and evaluations that show whether it works.
- Innovation sprints. Short, time-boxed sprints with founders, domain experts or a product team: frame the problem, test the riskiest assumption first, and iterate on what users actually do.
- Mentoring and advice. I pair with engineers and advise leads on where AI fits in their product and delivery, and where it doesn't.
- Workshops, tutorials and playbooks. Hands-on sessions in the team's own repository, and written, team-specific guides that stay behind.
- Responsible AI in practice. Privacy, security, fairness and EU compliance built into the design, not bolted on; see Responsible AI and EU regulation.
- Written learnings. Decision logs and runbooks: what we tried, what we kept, what we dropped and why.
I don't train models or run ML infrastructure. I build on hosted models and wire them into software a team can own.
What you'd get
- Your team up at least one rung, measured against the baseline we take at the start.
- Guardrails in the repository: instruction files, code ownership, hooks, CI gates and human-only paths — written down, not held in someone's head.
- People who run it without me: at least two others who can run and debug the workflow.
- Hands-on delivery: I ship product work myself while I enable the team.
Contact
The quickest way to reach me is email.
Also: Book a call LinkedIn GitHub CV (PDF)