Skip to content
Preptima

GenAI / LLM Application Engineer Interview Prep & Rubrics

The loop for building LLM features in a product: prompting and structured output, retrieval, agents and tool use, evaluation, and the cost and safety questions that follow.

The loop, in order

  1. Generative AI & Large Language Models26 questions · 7 topicsPrompting and structured output, context and tokens, adaptation, evaluation, inference economics, injection defence, and running LLM features in production.
  2. RAG, Retrieval & Agents24 questions · 7 topicsRetrieval-augmented generation end to end: ingestion, embeddings and vector indexes, hybrid search and reranking, retrieval evaluation, permissions, and agentic tool use.
  3. Backend Engineering30 questions · 7 topicsLanguage-agnostic service engineering: the protocols, boundaries, and failure handling that sit between a coding round and a full system design round.
  4. System Design70 questions · 12 topicsOpen-ended design rounds broken into the building blocks they draw on, plus full case studies worked end to end with explicit trade-off reasoning.
  5. Python22 questions · 7 topicsPython for backend, automation, and data roles, including the runtime behaviour that surprises candidates who only know the syntax.
  6. DevOps & Cloud37 questions · 8 topicsPlatform and infrastructure questions for DevOps, SRE, and any backend role expected to own its service in production.
  7. Behavioural & Culture Fit25 questions · 8 topicsThe round candidates most often under-prepare, treated as a skill with structure rather than small talk, including the rubric interviewers score against.
  8. HR, Screening & Offer19 questions · 6 topicsThe recruiter and HR rounds that gate the technical loop and decide your compensation, where most candidates improvise and lose money.

Latest for this track

mediumScenarioCoding

You are dropped into an unfamiliar repository with one failing business rule and an AI assistant that only gives hints. What do you do in the first ten minutes?

Debugging an unfamiliar codebase starts by running the failing test, then reading it as the rule and tracing its call path to the code that computes the wrong value. Let the size of the error narrow the cause, ask the assistant to locate and explain rather than patch, and prove the fix with a test that failed before.

Backend Scenarios5 minmid, senior