Turning LLM work into a product instead of a demo: agent architecture, context management, retrieval, evaluation, and the trade-offs between quality, cost, latency and scalability. The post says plainly that connecting an LLM API is not the job. Fully remote.
What they ask for
Listed as written in the original post.
PythonSystem architectureRAGAgent architectureContext managementVector databasesDeploying AI systemsModel evaluationQuality, cost, latency and scalability trade-offsFine-tuning (bonus)Hugging Face (bonus)vLLM (bonus)MCP (bonus)Multi-agent systems (bonus)GPU optimisation (bonus)LLM security (bonus)
This role was posted publicly by another company. I am not the employer, I am not a recruiter, and I have no involvement in their hiring — apply through the original post. Details are transcribed as written and may have changed since. Where the post left something out, it says "Not specified" rather than a guess.
More in AI & Data
- AI EngineerRestar
- Senior AI EngineerTelegraphi
- AI Enablement EngineerAzki
- Senior Generative AI EngineerLinkup
New roles go out on Telegram as I find them —@pjmentoring.
Join on Telegram ↗