New opportunity

PocketPills - AI Engineer - LLM & Agentic AI

PocketPills · Gurgaon/Gurugram, India

About this role

PocketPills seeks an AI Engineer in Gurgaon/Gurugram to build production-grade LLM applications and AI agents. The full-time role spans prototyping through production deployment, with a focus on scalable agentic workflows and intelligent systems.

Responsibilities

  • Design agents and multi-step workflows using LangChain, LangGraph or similar frameworks. Implement tool calling, structured outputs, state management, memory systems and dynamic loops.
  • Develop RAG systems using embeddings, vector search, retrieval optimization and reranking.
  • Build evaluation frameworks for accuracy, reliability, latency and cost efficiency. Establish production observability, guardrails, logging and error handling.
  • Own AI solutions from initial prototype through full-scale production deployment.

Required qualifications

  • 3–6+ years of software engineering experience with hands-on LLM and Generative AI development. The posting’s structured data also lists a bachelor’s degree.
  • Python proficiency; strong object-oriented programming, asynchronous programming, REST API, backend architecture and error-handling skills.
  • Hands-on LLM and AI agent development, including prompt engineering, loop design, agentic graph architecture, tool and function calling, structured outputs, and context and memory management.
  • Deep knowledge of RAG, embeddings, vector search and retrieval techniques; production experience with LangChain, LangGraph, LlamaIndex or equivalent frameworks.
  • Experience with vector databases such as pgvector, Pinecone, Weaviate or Qdrant, plus hands-on Docker and cloud infrastructure expertise.

Preferred qualifications

  • LangSmith or equivalent observability platforms; Model Context Protocol (MCP); agent evaluation, benchmarking and automated testing; and event-driven or asynchronous architectural patterns.

For full details about this role, click “Apply on company site” to view the employer’s original posting.

Skills for this role

PythonLLMsGenerative AIAI agentsLangChainLangGraphLlamaIndexRAGPrompt engineeringTool callingFunction callingStructured outputsState managementMemory systemsEmbeddingsVector searchRetrieval optimizationRerankingAgent evaluationBenchmarkingAutomated testingObservabilityGuardrailsLangSmithModel Context Protocol (MCP)Object-oriented programmingAsynchronous programmingREST APIsBackend service architectureVector databases

Your skill match

Checking your profile…

YOUR NEXT STEP

Get interview-ready for this role

A focused preparation guide, built around this job’s responsibilities and requirements.

✦ AI-generated guide
Preparation suggestions, not the employer’s actual interview questions. Always check the original posting for current requirements.
01

Understand the role

What matters most

  • Production-ready agent workflows

    The role calls for multi-step agents with tool calling, structured outputs, state management, memory and dynamic loops. Prepare to explain design decisions and failure handling in an agent workflow.

  • Reliable RAG retrieval

    The posting emphasizes embeddings, vector search, retrieval optimization and reranking. Prepare to explain how retrieval choices affect answer quality and how you would test them.

  • Evaluation across competing metrics

    The role includes building evaluation frameworks for accuracy, reliability, latency and cost efficiency. Prepare to describe how you would measure these dimensions and decide when a change is worth deploying.

  • Production observability and safeguards

    The posting calls for guardrails, logging, error handling and observability. Prepare to explain how a deployed system would expose failures and respond safely to malformed outputs or failed tool calls.

  • End-to-end backend delivery

    The engineer is expected to take solutions from prototype to full-scale deployment, drawing on Python, REST APIs, asynchronous programming, Docker and cloud infrastructure. Prepare to explain the engineering work needed beyond a working demo.

Likely challenges to think through

  • Controlling agent complexity

    A likely challenge is that added tools, memory and dynamic loops can improve capability while making behavior harder to predict and debug. Prepare a bounded workflow design with clear state transitions, stop conditions and failure paths; this is a preparation hypothesis, not a reported PocketPills problem.

  • Balancing retrieval quality against speed and cost

    A likely trade-off is that broader retrieval or reranking may improve answer quality while adding latency and expense. Prepare a comparison plan using representative queries and the posting’s accuracy, latency and cost measures; no specific performance targets are stated.

  • Moving from prototype to dependable service

    A prototype may work on selected examples but encounter malformed outputs, tool failures or concurrency issues in production. Prepare to explain testing, logging, guardrails and error handling for that transition; these are plausible engineering challenges, not confirmed issues at PocketPills.

03

Practice your answers

Technical practice

How would you design a multi-step agent workflow with conditional loops?

What to coverThe posting calls for agentic graph architecture, state management and dynamic loops. Suggested answer focus: explain how you would represent steps and transitions, preserve state, and prevent a loop from continuing indefinitely.

How would you make tool calls and structured outputs reliable?

What to coverTool and function calling, structured outputs and error handling are stated requirements. Suggested answer focus: discuss validating tool inputs and outputs, handling failures, and deciding when the agent should retry or stop.

How would you manage context and memory across an agent workflow?

What to coverThe role explicitly includes context management and memory systems. Suggested answer focus: distinguish information needed for the current step from information retained across steps, and explain the trade-offs in relevance, latency and cost.

How would you improve a prompt that works in a prototype but fails inconsistently in production?

What to coverPrompt engineering and the transition from prototype to production are part of the posting. Suggested answer focus: describe how you would isolate failure cases, revise instructions or output constraints, and check improvements against representative examples.

How would you design a RAG pipeline using embeddings and a vector database?

What to coverThe posting names RAG, embeddings, vector search and vector databases such as pgvector, Pinecone, Weaviate and Qdrant. Suggested answer focus: walk through indexing and retrieval choices, then explain how you would check whether the retrieved material supports the generated answer.

How would you diagnose poor retrieval and decide whether to add reranking?

What to coverRetrieval optimisation and intelligent reranking are stated responsibilities. Suggested answer focus: separate failures to find relevant material from failures to rank it well, and weigh relevance gains against added latency and cost.

How would you evaluate an agent before and after a change?

What to coverThe role calls for evaluation of accuracy, reliability, latency and cost efficiency; benchmarking and automated testing are preferred. Suggested answer focus: define representative tasks and failure cases, measure each dimension, and explain how you would judge trade-offs rather than relying on a single score.

What would you observe and guard against in a production LLM application?

What to coverProduction observability, guardrails, logging and error handling are explicit responsibilities. Suggested answer focus: identify useful workflow and tool-call signals, explain how failures would be surfaced, and describe how guardrails could be tested without assuming they eliminate risk.

How would you structure a Python REST service that runs agent workflows asynchronously?

What to coverThe posting requires Python, OOP, asynchronous programming, REST APIs and backend service architecture. Suggested answer focus: explain separation of responsibilities, handling of concurrent or slow operations, and how API errors would be reported reliably.

What would you change when moving an LLM prototype to a cloud deployment?

What to coverEnd-to-end production deployment, Docker and cloud infrastructure are stated parts of the role. Suggested answer focus: discuss packaging, configuration, scaling and operational failure handling, while distinguishing a working prototype from a service that can be monitored and maintained.

Behavioural practice

Tell me about a time you took an AI or software solution from prototype to production.

What to coverThe posting calls for end-to-end ownership of AI solutions. Suggested preparation: use a real situation, your specific actions and the result; explain what changed between the prototype and deployment without claiming work you did not do.

Describe a time you investigated an unreliable workflow or production failure.

What to coverReliability, observability, logging and error handling are central to the stated work. Suggested preparation: give the situation, the evidence you used to isolate the problem, your actions and the observed result.

Tell me about a time evaluation results changed your technical approach.

What to coverThe role calls for assessing accuracy, reliability, latency and cost efficiency. Suggested preparation: describe the situation, the measurements and trade-off you considered, the decision you made and its result.

Describe a time you chose between a simpler implementation and a more flexible workflow.

What to coverThe posting spans scalable agentic workflows and production deployment. Suggested preparation: use a real situation, explain your decision criteria and actions, and state the result, including any limitation you accepted.

02

Sharpen your knowledge

Topics to prepare

  • Agent workflow design

    The posting requires multi-step agents with tool calling, structured outputs, state, memory and dynamic loops. Sketch an agent graph and explain its branching, stopping conditions and handling of a failed tool call.

  • Prompt and context management

    Prompt engineering and context/memory management are required. Compare two prompt-and-memory designs for a multi-turn task, explaining how each controls context growth and output consistency.

  • RAG and retrieval trade-offs

    The role calls for embeddings, vector search, retrieval optimisation and reranking. Diagram a retrieval pipeline and explain where irrelevant results could enter and how reranking might change the final context.

  • Evaluation criteria

    The posting calls for evaluation of accuracy, reliability, latency and cost efficiency. Draft a small evaluation plan with a test case and measurable signal for each dimension, including a tool-failure case.

  • Production backend architecture

    Python, OOP, asynchronous programming, REST APIs, error handling, Docker and cloud infrastructure are stated requirements. Draw a service architecture for an LLM endpoint and explain request timeouts, concurrent work and the path from prototype to deployment.

Skills to revise

  • Implement an agent graph

    As practice for the required hands-on agent work, build a small workflow with LangGraph, LangChain or an equivalent named in the posting. Include a tool call, validated structured output, persisted state and a bounded retry loop.

  • Build and tune a RAG pipeline

    As practice for the required RAG and vector-database experience, index a small document set with embeddings in pgvector, Pinecone, Weaviate, Qdrant or a similar database. Compare retrieval results before and after a reranking step.

  • Write an asynchronous Python API

    As practice for the required backend skills, implement a REST endpoint that invokes an LLM workflow. Separate responsibilities into classes and handle invalid input, tool errors and timeouts explicitly.

  • Test and instrument the workflow

    The posting calls for evaluation, observability, guardrails, logging and error handling. Create test cases for correct answers, malformed structured outputs and failed tool calls; record accuracy, reliability, latency and cost for each run.

  • Package for deployment

    Docker and cloud infrastructure are explicit requirements. Containerise the practice API, configure its runtime settings and rehearse a deployment walkthrough covering logs, failures and scaling decisions; the posting does not specify a cloud provider.

04

Your preparation checklist

  • Prepare an end-to-end project walkthrough

    The role covers LLM solutions from prototype through production. Prepare a diagram and concise account of a project you worked on, including your decisions, deployment, and measured results; if you lack an example, label a proposed design as hypothetical.

  • Sketch a multi-step agent

    For a hypothetical task, draw an agent graph showing tool calls, structured outputs, state and memory, loop termination, and failure handling. Be ready to explain how you would implement it with LangGraph, LangChain, or an equivalent framework.

  • Work through a RAG design

    Prepare a retrieval diagram covering embeddings, a vector database, search, retrieval optimisation, and reranking. Explain how you would test whether each stage improves answer quality.

  • Build an evaluation plan

    Draft a small test set and scorecard for accuracy, reliability, latency, and cost. Include proposed automated tests, guardrails, logging, and a way to investigate failures.

  • Review the backend and deployment path

    Prepare a Python REST API design that demonstrates OOP, asynchronous work, and error handling. Add a Docker and cloud deployment outline, distinguishing experience you can substantiate from design choices you would make.

  • Prepare questions about production priorities

    Ask which agent and RAG use cases matter most, how success is measured, and what observability and deployment constraints exist. These are questions to clarify, not established details about PocketPills.

AI-generated from the job information · Prepared Sep 30, 2026 (UTC)Useful preparation, not a guarantee of eligibility or an offer.

Availability last checked: 4 Nov 2026. Status can change after a check; confirm on the employer’s website. Report an issue · Our checking policy

KEEP EXPLORING

Similar AI jobs

Related skills and specializations in India. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…