ai-llm

Generates interview questions for AI/LLM application engineering roles covering RAG, agents, and evaluation.

23|1|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/yuecao365/OfferCome --skill ai-llm-yuecao365
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-llm
Source: https://github.com/yuecao365/OfferCome/tree/main/src/lib/mock-interviews/skills/ai-llm
Command: npx skills add https://github.com/yuecao365/OfferCome --skill ai-llm-yuecao365

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interviewers hiring for LLM application engineering roles often struggle to design questions that distinguish real production experience from tutorial-level projects, especially in fast-moving areas like RAG, agents, and fine-tuning. ## Core Features & Use Cases - Topic Coverage: Provides structured question ladders across RAG pipelines, embedding retrieval, agent architecture, MCP tool governance, prompt engineering, context management, fine-tuning, inference optimization, evaluation systems, safety, and cost control. - Signal Detection: Each topic lists danger signals and expected signals so interviewers can score answers consistently and probe resume claims like "accuracy improved X%" or "built a RAG system". - Use Case: When a candidate's resume mentions an Agent project, use this Skill to generate follow-up questions about tool counts, termination conditions, token budgets, and past incidents to verify depth of experience. ## Quick Start Generate interview questions for a candidate whose resume mentions a RAG project and LangChain experience.

Frequently Asked Questions about ai-llm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I interview candidates for LLM application engineering roles?▼

Focus on engineering judgment rather than terminology: ask how candidates verify improvements with evaluation sets, how they debug RAG failures across retrieval and generation layers, and how they control agent loops. Probe resume claims for concrete failure cases and metrics.

What are good RAG interview questions?▼

Ask candidates to walk through debugging a report of "answer doesn't match the document", specifying the order of checks and metrics at each step. Strong answers separate retrieval recall failure from generation failure and cite layered metrics like recall, context precision, and faithfulness.

How to evaluate whether a candidate's agent project experience is real?▼

Ask about tool counts, termination conditions, maximum steps run, highest token cost, and past incidents. Candidates with only demo experience typically cannot describe failure attribution, budget limits, or which parts they hardcoded instead of delegating to the model.

When should interviewers ask about fine-tuning versus RAG?▼

Ask when a resume mentions fine-tuning or style customization. Strong candidates explain that fine-tuning teaches format, style, and behavior while knowledge belongs in retrieval, and can discuss data sourcing, catastrophic forgetting, and evaluation before and after training.

What are red flags in LLM engineer interviews?▼

Red flags include treating framework names like LangChain as capability, having no evaluation set, claiming improvements without baselines, adding reranking as a cure-all without diagnosis, and lacking any step limits or budget controls on agents.