New opportunity

GenAI Developer

Eazygurus · Hyderabad, India

About this role

Eazygurus seeks a GenAI Developer in Hyderabad to design, build and deploy applications powered by large language models and other generative AI technologies, including chatbots, copilots, content generation and intelligent automation. This is a full-time role.

Responsibilities

  • Develop applications using LLM services such as OpenAI, Azure OpenAI and Anthropic; create prompt engineering and optimization strategies.
  • Implement retrieval-augmented generation (RAG) pipelines and integrate vector databases such as FAISS, Pinecone and Weaviate for semantic search.
  • Fine-tune and evaluate LLMs where needed; develop APIs and microservices for GenAI solutions.
  • Work with AI/ML, data and product teams to ensure system scalability, security and performance.

Required qualifications

  • 2–5 years of experience in AI/ML, NLP or software development, with strong Python programming skills.
  • Hands-on experience with LLM frameworks such as LangChain, LlamaIndex or Haystack, and experience using OpenAI or Azure OpenAI APIs or similar services.
  • Understanding of NLP concepts and transformer models; experience with vector databases and embeddings; knowledge of REST APIs and backend development.

Preferred qualifications

  • Experience fine-tuning open-source models such as LLaMA, Mistral or Falcon; familiarity with AWS, Azure or GCP; exposure to MLOps or LLMOps; experience with Docker and Kubernetes; and understanding of data privacy and AI security.

The employer offers work on real-world GenAI products and opportunities to explore new AI technologies in a collaborative team.

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

Skills for this role

Generative AILarge Language ModelsPythonOpenAIAzure OpenAIAnthropicPrompt EngineeringPrompt OptimizationRAGFAISSPineconeWeaviateSemantic SearchLLM Fine-tuningLLM EvaluationAPIsMicroservicesLangChainLlamaIndexHaystackNatural Language ProcessingTransformer ModelsVector DatabasesEmbeddingsREST APIsBackend DevelopmentLLaMAMistralFalconAWS

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 LLM-powered applications

    The role designs, builds and deploys applications such as chatbots, copilots, content generation and intelligent automation, using LLM services including OpenAI, Azure OpenAI and Anthropic.

  • Improve prompts

    Prompt engineering and optimization are explicit responsibilities. Prepare to explain how a prompt change would be tested against a defined application task.

  • Deliver RAG and semantic search

    The role implements RAG pipelines and integrates vector databases such as FAISS, Pinecone and Weaviate. Embeddings and vector-database experience are required.

  • Evaluate models and fine-tune when warranted

    LLM evaluation is a stated duty; fine-tuning is specified where required. Fine-tuning open-source models is listed as good to have, not required.

  • Turn solutions into dependable services

    The role develops APIs and microservices and works with AI/ML, data and product teams to ensure scalability, security and performance. Python and REST/backend knowledge are required.

Likely challenges to think through

  • Retrieval quality versus response speed

    Preparation hypothesis, not a reported Eazygurus issue: a RAG application may need more thorough retrieval without making responses too slow. Prepare to explain how you would assess retrieved results alongside answer quality and latency.

  • Choosing the least complex improvement

    Preparation hypothesis: prompt changes, retrieval changes and fine-tuning can address different failures, but add different effort and operational complexity. Prepare a decision framework based on observed errors and evaluation results; the posting calls for fine-tuning only where required.

  • Balancing reliability with safeguards

    Preparation hypothesis: deploying an LLM through an API may require trade-offs among throughput, performance and protection of sensitive data. Prepare to describe how you would test those trade-offs with the AI/ML, data and product teams, without assuming a particular infrastructure or company policy.

03

Practice your answers

Technical practice

How would you design an LLM-powered chatbot or copilot from request to response?

What to coverPreparation suggestion: Explain how you would connect an application to an LLM service, manage conversation context, and expose the result to users. Discuss when retrieval or other application logic would be needed rather than relying on the model alone.

How would you improve prompts for a content-generation task?

What to coverPreparation suggestion: Describe an iterative approach using clear instructions, representative test cases, and checks for output quality. Explain how you would compare prompt changes while watching for regressions.

How would you build and troubleshoot a retrieval-augmented generation pipeline?

What to coverPreparation suggestion: Walk through preparing source content, retrieving relevant passages, and supplying them as context to the model. Distinguish retrieval failures from generation failures when an answer is inaccurate or unsupported.

What choices affect embedding-based semantic search?

What to coverPreparation suggestion: Explain what embeddings represent and how content preparation and similarity search affect retrieval quality. Discuss practical trade-offs when integrating a vector database such as FAISS, Pinecone, or Weaviate, without assuming one is required.

How would you evaluate an LLM application before and after a change?

What to coverPreparation suggestion: Propose task-relevant test cases and criteria for answer quality, including whether answers use retrieved context appropriately. Explain how you would compare results and examine failures rather than relying on a single score.

When would you consider fine-tuning instead of prompt optimization or RAG?

What to coverPreparation suggestion: Compare the problems each approach can address and the data, evaluation, and maintenance effort involved. Fine-tuning open-source models is listed as good to have, so treat model-specific experience as optional.

How would you implement a Python REST API for a GenAI service?

What to coverPreparation suggestion: Cover request validation, calls to an LLM service, error handling, and a clear response contract. Explain how you would separate API and application logic in a maintainable backend or microservice.

Which transformer and NLP concepts help explain LLM application behavior?

What to coverPreparation suggestion: Explain tokens, context limits, and the role of transformer attention at a practical level. Connect those concepts to choices about input length, retrieved context, and output quality.

How would you choose what to handle in an LLM framework versus application code?

What to coverPreparation suggestion: Use LangChain, LlamaIndex, or Haystack as an example of a framework named in the posting. Discuss the benefits of reusable retrieval or orchestration components against the need for transparent, testable application logic.

How would you improve the scalability, security, and performance of a deployed GenAI application?

What to coverPreparation suggestion: Consider response latency, service capacity, access to data, and handling of sensitive inputs or outputs. Explain how you would measure the issue and weigh improvements; cloud platforms, containers, and LLMOps are good-to-have topics, not assumed requirements.

Behavioural practice

Tell me about a time you coordinated with product, data, or AI/ML colleagues to deliver a technical feature.

What to coverPreparation suggestion: Use a real situation, your specific actions to resolve differing needs, and the result. Make the collaboration concrete without claiming a GenAI project if your example came from another area.

Describe a time you investigated a quality or performance problem in an application.

What to coverPreparation suggestion: State what users or measurements revealed, how you isolated the cause, and what changed as a result. An example from software or ML work can show a troubleshooting approach relevant to this role.

Tell me about a time feedback caused you to revise a technical solution.

What to coverPreparation suggestion: Explain the original goal, the feedback you received, and the changes you made. End with the observed result or what you learned if the outcome was mixed.

Describe a time you balanced delivery speed with a security or reliability concern.

What to coverPreparation suggestion: Give the situation, the trade-off you identified, the action you took, and the result. Keep the example grounded in your actual work rather than implying experience with a particular GenAI deployment.

02

Sharpen your knowledge

Topics to prepare

  • NLP and transformer fundamentals

    Required: understanding of NLP concepts and transformer models. Exercise: explain how tokens, context and transformer attention affect an LLM’s response to a long document.

  • RAG and semantic search design

    The role calls for RAG pipelines, embeddings and vector databases. Exercise: diagram a question-answering flow from document ingestion through retrieval to generation, and explain where irrelevant results could enter.

  • Prompt engineering and optimization

    Building prompt strategies is a stated responsibility. Exercise: compare two prompts for a chatbot task and explain how you would judge whether the revision improved the response.

  • LLM evaluation and fine-tuning decisions

    The posting calls for evaluation and fine-tuning where required; open-source model fine-tuning is good to have. Exercise: outline an evaluation set for a content-generation task and explain when prompt changes or RAG might be preferable to fine-tuning.

  • GenAI service design

    The role includes APIs and microservices, with attention to scalability, security and performance. Exercise: sketch an LLM-backed API and identify how you would handle slow responses, request failures and sensitive input.

Skills to revise

  • Python LLM API integration

    Strong Python and experience with OpenAI, Azure OpenAI or similar APIs are required. Practice writing a small Python function that submits a prompt, handles an API failure and returns a structured result.

  • LLM framework implementation

    Hands-on experience with frameworks such as LangChain, LlamaIndex or Haystack is required. Practice building a short retrieval-to-answer workflow in one named framework and be ready to explain what each component does.

  • Embedding and vector-index workflow

    The posting requires experience with embeddings and vector databases and names FAISS, Pinecone and Weaviate. Practice embedding a small document set, indexing it in one named option and inspecting the results of several semantic queries.

  • Prompt testing

    Prompt optimization is a stated responsibility. Practice running a fixed set of chatbot questions against two prompt versions, recording response quality and failure cases, and explaining the change you would keep.

  • REST endpoint for a GenAI feature

    REST and backend knowledge are required, and developing GenAI APIs is part of the role. Practice exposing a simple Python endpoint for an LLM-backed feature, validating its input and returning a clear error when the LLM call fails.

04

Your preparation checklist

  • Select a relevant project walkthrough

    Prepare a brief walkthrough of an LLM application you have built, if available: the use case, your contribution, Python implementation, LLM service or framework used, deployment approach, and results. The role calls for building and deploying GenAI applications.

  • Practice a RAG design exercise

    Sketch a chatbot or copilot that ingests documents, creates embeddings, retrieves from a vector database, and generates answers. Explain how you would assess retrieval quality and choose between options such as FAISS, Pinecone, and Weaviate; these are examples named in the posting.

  • Show how you improve prompts and outputs

    Prepare a before-and-after prompt example and a small evaluation plan with test inputs, failure cases, and quality measures. Be ready to explain when fine-tuning might be warranted; the posting says to fine-tune models where required.

  • Review Python and backend evidence

    Choose a code sample or architecture diagram, if available, that demonstrates Python, an LLM API or framework, and a REST API or microservice. Note your specific decisions rather than implying experience with every tool listed.

  • Rehearse production trade-offs

    For your design, outline how you would address latency, scalability, security, and performance, and how you would work with AI/ML, data, and product teams. These are stated responsibilities; your proposed approach is preparation, not an employer-specified process.

  • Prepare evidence for optional experience

    If applicable, gather concise examples of open-source model fine-tuning, cloud deployment, MLOps or LLMOps, Docker or Kubernetes, and data privacy or AI security. The posting labels these good-to-have, not required.

  • Draft questions for Eazygurus

    Ask which GenAI use cases the role will prioritize, how LLM and RAG solutions are evaluated, what deployment constraints matter most, and how the AI/ML, data, and product teams collaborate.

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…