New opportunity

Artificial Intelligence Engineer

Kodiva.ai · Mumbai, India

About this role

Kodiva.ai seeks an Artificial Intelligence Engineer in Mumbai for an on-site, permanent role building AI agents and the full-stack applications that bring them into production. The posting lists compensation of ₹ 6–15 lacs per annum. Its experience badge says 2–4 years, while the detailed requirements specify 2–5 years of professional software engineering experience with hands-on AI/LLM-powered feature development.

Responsibilities

  • Design, build and deploy agentic workflows involving tool use, function calling, multi-step reasoning and orchestration.
  • Develop backend services, APIs and responsive front-end interfaces that integrate AI capabilities.
  • Use LLM frameworks to build retrieval-augmented generation (RAG), prompt pipelines and evaluation systems. Integrate third-party APIs, vector databases and model providers, including OpenAI, Anthropic and open-source models.
  • Improve the latency, cost, reliability and accuracy of AI features. Work with product and design teams, own features through production, write testable and documented code, and participate in code reviews.

Requirements

  • Experience building AI agents or agentic systems, including orchestration, tool integration or autonomous workflows.
  • Proficiency in a backend language such as Python, Node.js or Go and a modern front-end framework such as React, Next.js or Vue.
  • Understanding of LLM APIs, prompt engineering and AI-output evaluation and testing; experience with SQL or NoSQL databases and familiarity with vector stores such as Pinecone, Weaviate or pgvector.
  • Comfort with AWS, GCP or Azure and CI/CD practices, plus strong problem-solving and end-to-end feature ownership.

Preferred

Experience with model fine-tuning, embeddings or open-source model deployment; familiarity with Docker and Kubernetes; or open-source AI contributions or a portfolio of agent-based applications.

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

Skills for this role

AI agentsAgentic workflowsTool useFunction callingMulti-step reasoningPythonNode.jsGoReact.jsNext.jsVueLLMsLangChainLlamaIndexRAGPrompt EngineeringAI evaluationOpenAIAnthropicVector databasesPineconeWeaviatepgvectorSQLNoSQLAWSGCPAzureCI/CDDocker сутKubernetes

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

  • Build and deploy AI agents

    The role centers on agentic workflows using tool calls, function calling, multi-step reasoning and orchestration. Prepare to explain the design and deployment of an agent workflow you have worked on.

  • Ship AI features across the stack

    The posting calls for backend services, APIs and responsive front-end interfaces that bring AI capabilities into working products. Prepare to describe how a feature moves from the API to the user interface.

  • Develop and evaluate LLM features

    Responsibilities include RAG, prompt pipelines, evaluation systems, and integration with vector databases and model providers. Prepare to explain how you would test AI outputs, not just generate them.

  • Own production quality

    The role includes improving latency, cost, reliability and accuracy; collaborating with product and design; and writing testable, documented code through code review. Prepare an example of an engineering decision shaped by those constraints.

Likely challenges to think through

  • Keeping agent actions dependable

    Preparation hypothesis, not a confirmed Kodiva.ai problem: multi-step workflows with external tools can fail partway through or produce unexpected actions. Be ready to discuss how you would handle tool errors, limit actions and test complete workflows without making them too rigid.

  • Balancing AI quality against operating cost

    Preparation hypothesis: improving accuracy through more retrieval or model calls may increase latency and cost. Prepare to explain what you would measure and how you would compare alternatives before choosing a production approach.

  • Coordinating changes across the product

    Preparation hypothesis: owning an AI feature from concept to production means changes to prompts, APIs and interfaces may affect one another. Prepare an example of how you would align product requirements with implementation and verify the resulting user experience.

03

Practice your answers

Technical practice

Suggested practice: How would you design an agent that completes a multi-step task using tools?

What to coverThe role involves tool use, function calling, multi-step reasoning and orchestration. Explain how the agent would choose actions, track progress and stop or escalate when it cannot complete the task.

Suggested practice: How would you handle a failing or unreliable tool call in an agent workflow?

What to coverThe posting calls for tool integration and reliable production AI features. Discuss validation, timeouts, retries and safeguards against repeating an action that should run only once.

Suggested practice: How would you build an AI feature across the backend and front end?

What to coverThe role spans backend services, APIs and responsive interfaces. Describe the request flow, how the interface would handle a slow or failed response, and where you would test the integration.

Suggested practice: How would you design a retrieval-augmented generation pipeline?

What to coverThe posting names RAG, embeddings and vector databases. Explain document preparation, retrieval, use of retrieved context in a prompt, and how you would check whether the retrieved material supports the answer.

Suggested practice: How would you test a prompt pipeline whose outputs vary?

What to coverThe role calls for prompt pipelines and evaluation and testing of AI outputs. Suggest a representative test set, clear quality criteria and checks for regressions when prompts or models change.

Suggested practice: How would you integrate and compare model providers in a production feature?

What to coverThe posting mentions third-party APIs, OpenAI, Anthropic and open-source models. Discuss API boundaries, differences in capabilities and output formats, and how you would evaluate a provider change without assuming the models are interchangeable.

Suggested practice: How would you balance latency, cost, reliability and accuracy?

What to coverThe posting explicitly names all four as optimization goals. Walk through what you would measure, then explain a trade-off such as using a smaller model or fewer calls only if evaluation shows acceptable output quality.

Suggested practice: How would you divide application data between a conventional database and a vector store?

What to coverThe requirements mention SQL or NoSQL databases and familiarity with vector stores. Explain which data needs structured queries or application state, which needs similarity search, and how you would keep records and embeddings consistent.

Suggested practice: How would you ship and maintain an AI feature using cloud and CI/CD practices?

What to coverThe role requires comfort with a cloud platform and CI/CD, alongside testable, documented code. Describe deployment checks, configuration and secret handling, monitoring, and a rollback approach as preparation topics rather than a prescribed company process.

Suggested practice: When might fine-tuning be preferable to improving a prompt or RAG pipeline?

What to coverFine-tuning is listed as nice to have, while prompt pipelines and RAG are core duties. Compare the kinds of problems each approach could address, and discuss data, evaluation and maintenance costs before choosing one.

Behavioural practice

Suggested practice: Tell me about a feature you owned from concept to production.

What to coverThe posting emphasizes end-to-end feature ownership. Use a real situation, your specific actions and the result; explain how you decided the feature was ready to release.

Suggested practice: Tell me about a time you translated product or design needs into an implementation.

What to coverThe role involves collaboration with product and design teams. Describe the requirement, how you resolved uncertainty or competing priorities, what you built and the outcome.

Suggested practice: Tell me about a code review that improved the quality of a feature.

What to coverThe posting calls for code reviews and clean, testable, documented code. Give a real example of feedback you gave or received, the change you made and its result.

Suggested practice: Tell me about a difficult production issue you investigated.

What to coverThe role emphasizes problem-solving and the reliability of AI features. Describe the symptoms, how you narrowed down the cause, your action and the observed result without assuming a particular incident type.

Suggested practice: Tell me about a time you had to make an engineering trade-off under constraints.

What to coverThe posting calls for balancing latency, cost, reliability and accuracy. Use a real situation to explain the options, evidence behind your decision, action taken and outcome.

02

Sharpen your knowledge

Topics to prepare

  • Agent orchestration and tool use

    Posting: The role designs agents with tool use, function calling and multi-step reasoning. Revision exercise: diagram an agent workflow, then explain how it selects a tool, handles a failed call and decides when to stop.

  • RAG and retrieval design

    Posting: The role includes RAG, prompt pipelines, databases and vector stores. Revision exercise: sketch how documents move from storage through retrieval into an LLM response, and explain where irrelevant retrieval could affect accuracy.

  • LLM output evaluation

    Posting: Evaluation and testing of AI outputs are explicit requirements. Revision exercise: define a small set of test prompts, expected behaviors and failure categories for an agent feature; explain how you would compare changes.

  • Production AI tradeoffs

    Posting: AI features must be optimized for latency, cost, reliability and accuracy. Revision exercise: work through a scenario where an extra model or tool call improves an answer but slows it down; explain what you would measure before choosing.

  • End-to-end feature design

    Posting: The engineer owns features from concept to production across APIs, front-end interfaces, cloud platforms and CI/CD. Revision exercise: draw a high-level design for one AI-powered feature and trace a user request through its interface, backend and deployment path.

Skills to revise

  • Implement an agent workflow

    Posting: Hands-on agent development and tool integration are central. Preparation exercise: build a small agent that calls a defined tool, handles an error and records the steps it took. This is a practice exercise, not a specified employer project.

  • Build a retrieval-backed prompt pipeline

    Posting: The work includes RAG, prompt pipelines and vector databases. Preparation exercise: use a small document set to retrieve passages, pass them into a prompt and inspect answers when retrieval misses relevant content.

  • Connect a backend API to a front end

    Posting: The role requires a backend language and modern front-end framework for AI-enabled applications. Preparation exercise: create a simple API endpoint that invokes an LLM-powered feature and a responsive interface that displays its result and errors.

  • Test and refine AI outputs

    Posting: The engineer builds evaluation systems and writes testable code. Preparation exercise: run a fixed set of inputs against two prompt versions, record output quality and failures, and add tests for non-model API behavior.

  • Prepare a feature for deployment and review

    Posting: Cloud and CI/CD comfort, documentation and code reviews are expected. Preparation exercise: take a small feature through a CI/CD check, document its configuration and draft a review note covering reliability, latency and cost. Using one posting-listed cloud platform is a practice suggestion, not a requirement to know all three.

04

Your preparation checklist

  • Prepare an agent project walkthrough

    The role calls for demonstrated agent-building experience. If available, select one project and prepare a diagram and brief walkthrough of its orchestration, tool use or function calling, your contribution, and what reached production.

  • Practice a full-stack design exercise

    The posting spans backend services, APIs and responsive interfaces. Sketch how a user request would move through an AI-powered interface, backend, model provider and database; explain key design choices.

  • Show how you would evaluate AI output

    The role includes RAG, prompt pipelines and evaluation systems. Prepare a small example with retrieval steps, test inputs, expected behavior and a way to assess answer quality and failures.

  • Quantify an AI-feature trade-off

    The posting emphasizes latency, cost, reliability and accuracy. Prepare a before-and-after example if you have one; otherwise, practice explaining how you would measure and improve one of those dimensions without masking regressions in the others.

  • Gather end-to-end engineering evidence

    Prepare concise examples of backend and front-end work, SQL or NoSQL and vector-store use, cloud deployment and CI/CD. For each example, identify your decisions, tests, documentation and production responsibilities; distinguish hands-on experience from familiarity.

  • Rehearse production integration decisions

    Practice explaining how you would connect a third-party API, vector database and model provider in an agent workflow. Include how you would test failures and review the resulting code; this is a preparation exercise, not a stated interview format.

  • Bring focused questions for Kodiva.ai

    Ask which agent workflows and full-stack features this role would own, how the team evaluates AI outputs and production performance, and which cloud and model integrations it uses. You can also clarify the page’s 2–4-year badge versus its 2–5-year detailed requirement.

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

Availability last checked: 5 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…