New opportunity

Generative AI Developer

Broadridge · Bengaluru, India

About this role

Broadridge is seeking a Generative AI Developer in Bengaluru-EPIP Industrial Area, India. The full-time role centers on developing LLM-based, knowledge-driven applications, including retrieval-augmented generation (RAG) pipelines, chatbots, and enterprise Q&A assistants.

Requirements and technical focus:

  • A bachelor’s or master’s degree in Computer Science, Data Science, Artificial Intelligence, or a related field; 5+ years of overall IT experience, including at least 3+ years of hands-on AI/ML, Generative AI, or LLM-based solution development.
  • Strong Python proficiency, understanding of LLMs and prompt engineering, and experience designing and optimizing RAG pipelines.
  • Hands-on experience with vector databases such as Pinecone, Weaviate, FAISS, or Milvus; familiarity with agentic frameworks and orchestration tools such as LangChain, LangGraph, or LlamaIndex.
  • Expertise in chunking strategies and embeddings optimization, plus experience with chatbot development, conversational AI, and enterprise Q&A assistants. The posting also calls for exposure to Text-to-SQL and natural-language querying across structured and unstructured data; experience with PDF/document extraction and advanced context retrieval; and knowledge of query rewriting, multi-vector retrieval, and reranking.
  • Basic HTML, CSS, or React knowledge for simple GenAI UI integration. Knowledge of Java or similar technologies is an added advantage.

Broadridge describes a hybrid working model and offers professional-development opportunities, including training programs and access to LinkedIn Learning courses.

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

Skills for this role

PythonGenerative AIMachine LearningLarge Language ModelsPrompt EngineeringRetrieval-Augmented GenerationPineconeWeaviateFAISSMilvusLangChainLangGraphLlamaIndexChunking StrategiesEmbeddings OptimizationChatbot DevelopmentConversational AIText-to-SQLNatural Language QueryingPDF ExtractionDocument ExtractionContext RetrievalQuery RewritingMulti-Vector RetrievalRerankingHTMLCSSReactJava

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

  • Design and optimize RAG pipelines

    The posting explicitly calls for RAG design and optimization, strong Python, and hands-on vector-database experience. Prepare a concise walkthrough of how documents become retrievable context and how you would assess answer quality.

  • Improve document ingestion and retrieval

    The role specifies PDF/document extraction, chunking, embeddings optimization, advanced context retrieval, query rewriting, multi-vector retrieval, and reranking. Prepare to explain when each technique improves retrieval and how you would compare it with a simpler baseline.

  • Build conversational, knowledge-driven applications

    The posting names chatbots, conversational AI, and enterprise Q&A assistants, alongside LLMs, prompt engineering, and familiarity with orchestration frameworks. Prepare to describe how prompts, retrieved context, and conversation flow work together.

  • Connect structured queries and a basic interface

    The role calls for exposure to Text-to-SQL and natural-language queries across structured and unstructured data, plus basic HTML, CSS, or React for simple GenAI UI integration. Prepare to explain how a user request could be routed to the appropriate data source and presented clearly.

Likely challenges to think through

  • Noisy documents versus reliable answers

    Preparation hypothesis, not a stated Broadridge problem: PDF extraction and chunking can lose tables or context, weakening otherwise sound RAG answers. Prepare to discuss how you would inspect extracted content, test retrieval on representative questions, and adjust chunking or embeddings.

  • Retrieval gains versus pipeline complexity

    Preparation hypothesis: query rewriting, multi-vector retrieval, and reranking may improve relevance but add processing and latency. Prepare a comparison with a basic vector-search pipeline, including how you would decide whether the added steps justify their cost.

  • Natural-language queries across different data types

    Preparation hypothesis: Text-to-SQL and document retrieval require different ways to interpret a question and substantiate an answer. Prepare to explain how you would distinguish a structured-data question from a document question and check that the resulting answer reflects the returned data.

03

Practice your answers

Technical practice

How would you design a Python-based RAG pipeline for an enterprise Q&A assistant?

What to coverSuggested answer focus: Walk through document ingestion, indexing, retrieval, prompt construction and response generation. Explain how you would check whether retrieved context supports an answer and where you would look first if answer quality declined.

How would you improve a prompt when an LLM gives answers that go beyond the retrieved context?

What to coverSuggested answer focus: Discuss instructions for using context, handling missing evidence and testing prompts against representative questions. Distinguish a prompt problem from a retrieval problem before changing either component.

How would you choose chunking and embedding strategies for a knowledge-driven application?

What to coverSuggested answer focus: Compare chunk boundaries, overlap and embedding choices in terms of retrieval relevance and context preservation. Describe how you would test those choices using questions whose answers span different parts of a document.

What would guide your choice of a vector database for a RAG application?

What to coverSuggested answer focus: Use the posting's examples—Pinecone, Weaviate, FAISS and Milvus—to discuss relevant differences without claiming one is required. Consider retrieval features, operational needs and how you would measure search quality for the application.

How would you troubleshoot poor answers traced to a PDF or document extraction pipeline?

What to coverSuggested answer focus: Check whether extraction preserved text, reading order and useful document structure before examining chunking or retrieval. Explain how you would trace a failed question back to the extracted source and its indexed content.

When would you try query rewriting, multi-vector retrieval or reranking?

What to coverSuggested answer focus: Explain the retrieval failure each approach might address and how the approaches could interact. Compare potential relevance gains with added complexity and latency, using an evaluation set to decide whether a change helps.

How would you evaluate and diagnose a RAG pipeline that retrieves relevant passages but still produces weak answers?

What to coverSuggested answer focus: Separate retrieval quality from answer quality by inspecting retrieved passages, prompts and generated responses. Suggest measures tied to the task, such as whether answers address the question and remain supported by the retrieved content.

How would you design a conversational Q&A assistant with a simple web UI?

What to coverSuggested answer focus: Cover how conversational context reaches the retrieval and generation steps, and how the interface presents answers or uncertainty. The posting calls for basic HTML, CSS or React integration, so keep the UI discussion at that level rather than assuming a particular frontend stack.

How would you approach natural-language questions spanning structured data and documents?

What to coverSuggested answer focus: Contrast Text-to-SQL with retrieval from unstructured content, and explain how you would decide which source a question needs. As a preparation suggestion, discuss checking a generated query and its result before using them in an answer; the posting does not prescribe an implementation.

When would an orchestration or agentic framework help this application?

What to coverSuggested answer focus: Describe how a framework such as LangChain, LangGraph or LlamaIndex might organize retrieval and generation steps. Compare that with a simpler Python implementation, including the debugging and complexity trade-offs; familiarity, not use of a specific framework, is stated.

Behavioural practice

Tell me about a time you improved a knowledge-driven application's answer quality.

What to coverSuggested answer focus: Give the situation, the quality problem you observed, your actions and the result. Make clear what evidence showed improvement and which part of the pipeline you changed.

Describe a time you had to choose between competing technical approaches under practical constraints.

What to coverSuggested answer focus: Use a real situation, your decision process, the action you took and the result. A retrieval or application-design trade-off would be relevant preparation, but the posting does not specify a particular project or constraint.

Tell me about a time you worked with others to turn a user question or need into a working application.

What to coverSuggested answer focus: Set out the situation, how you clarified the need and coordinated your contribution, and the result. An example involving a chatbot or Q&A application would connect closely to the stated technical focus.

Describe a time feedback changed your approach to a technical solution.

What to coverSuggested answer focus: Explain the situation, the feedback, what you changed and the outcome. As a preparation suggestion, choose an example that shows how you tested the change and worked constructively with others.

02

Sharpen your knowledge

Topics to prepare

  • LLMs and prompt engineering

    The posting calls for a strong understanding of LLMs and prompt engineering. Revise by explaining how a prompt can constrain an enterprise Q&A answer to retrieved context and what should happen when that context is insufficient.

  • RAG design and optimization

    The posting requires experience designing and optimizing RAG pipelines. Sketch the path from a user question through retrieval to an answer, and explain where chunking and embedding choices affect results.

  • Advanced retrieval approaches

    The posting names query rewriting, multi-vector retrieval, reranking, and advanced context retrieval. Compare when each might improve a missed or poorly ranked result; treat the comparison as interview practice, not a prescribed company design.

  • Conversational AI and orchestration

    The posting asks for chatbot and enterprise Q&A experience plus familiarity with agentic frameworks such as LangChain, LangGraph, or LlamaIndex. Explain how a follow-up question would retain useful context without carrying forward an incorrect answer.

  • Structured and unstructured querying

    The posting mentions exposure to Text-to-SQL and natural-language querying across structured and unstructured data. Classify a few example questions by whether they need a database query, document retrieval, or both, and explain your choice.

Skills to revise

  • Build a Python document-to-answer flow

    Practice extracting text from a sample PDF, chunking it, retrieving relevant passages, and producing an answer grounded in those passages. This combines the posting’s Python, document extraction, and RAG requirements; the sample exercise is a preparation suggestion.

  • Index and search embeddings

    Using one listed option—Pinecone, Weaviate, FAISS, or Milvus—practice indexing sample chunks and inspecting the passages returned for several questions. The posting specifically requests hands-on vector-database experience.

  • Tune retrieval results

    On the same sample questions, compare two chunking or embedding choices, then try query rewriting or reranking and record which passages move into the results. This rehearses the posting’s emphasis on embedding optimization and advanced RAG.

  • Implement a conversational Q&A turn

    Practice handling a follow-up question in a small chatbot flow, optionally using one framework named in the posting, and check whether the retrieved context supports the answer. This relates to conversational AI and orchestration familiarity.

  • Prototype a Text-to-SQL query

    Given a small sample table and natural-language questions, practice producing SQL, checking the returned rows, and distinguishing questions that instead require document retrieval. Text-to-SQL is listed as exposure, not as a stated specialist requirement.

  • Connect a basic UI

    Practice connecting a simple HTML/CSS or React question-and-answer view to a sample GenAI flow. The posting asks only for basic UI knowledge for integration, so keep this exercise lightweight.

04

Your preparation checklist

  • Map the stated qualifications to evidence

    Prepare a one-page, factual record of education, overall IT experience, AI/ML or LLM development experience, and Python work. The posting specifies a related bachelor’s or master’s degree, 5+ years in IT, and 3+ years of hands-on AI/ML, Generative AI, or LLM development.

  • Rehearse a RAG project walkthrough

    If you have a relevant project, prepare a diagram and a concise account of your decisions, contributions, results, and trade-offs. Address the posting’s focus on RAG pipelines, vector databases, chunking, embeddings, and prompt engineering; do not claim work you did not do.

  • Practice a document-to-answer design exercise

    Sketch a proposed pipeline from PDF extraction through indexing, retrieval, and an enterprise Q&A response. Explain how you would compare query rewriting, multi-vector retrieval, and reranking; these are practice choices, not a stated Broadridge architecture.

  • Prepare a chatbot implementation example

    Bring a small code excerpt or architecture sketch showing Python orchestration, conversational behavior, and a simple UI connection. Be ready to explain where a tool such as LangChain, LangGraph, or LlamaIndex would help, and where it would add complexity.

  • Work through a structured-data query scenario

    Draft an example natural-language question that needs both documents and structured data. Walk through a possible Text-to-SQL approach, how results would be combined, and how you would check the generated query and answer.

  • Prepare focused questions for Broadridge

    Write three or four questions about the team’s knowledge sources, how it evaluates retrieval and answers, its approach to chatbot integration, and which advanced RAG techniques matter most in this role. Treat the answers as unknown; the posting lists skills but does not specify the team’s implementation.

AI-generated from the job information · Prepared Sep 29, 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…