New opportunity

Data Scientist

Hashone Careers · Bangalore, India

About this role

Hashone Careers is seeking a Data Scientist or AI/Agent Engineer to design, develop, and deploy multi-agent systems and AI-driven solutions. The role is on-site in Bangalore, Karnataka, India. The posting describes the position as permanent and lists compensation of ₹ 5-17 Lacs PA.

Responsibilities

  • Design agentic systems and architect scalable multi-agent workflows.
  • Implement and optimize retrieval-augmented generation (RAG) pipelines; work with vector embeddings and vector databases.
  • Build and manage agent orchestration frameworks and end-to-end AI workflows covering data ingestion, processing, and inference.
  • Collaborate with cross-functional teams to deliver AI-powered solutions, and evaluate emerging AI tools and frameworks for potential integration.

Required qualifications

  • 3–6 years of experience in data science, machine learning, or AI engineering.
  • Strong expertise in agent engineering and agent-based system design, with hands-on experience in RAG pipelines, vector embeddings, semantic search, multi-agent orchestration, and workflow design.
  • Proficiency in Python and relevant AI/ML libraries. Experience with both LangChain and LangGraph is mandatory.
  • Solid understanding of large language models and prompt engineering, plus strong analytical, problem-solving, and system design skills.

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

Skills for this role

Data SciencePrompt EngineeringArtificial IntelligenceMachine LearningPythonLarge Language ModelsLangChainLangGraphRAGAgentic AIVector EmbeddingsVector DatabasesSemantic SearchMulti-agent OrchestrationSystem Design

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

  • Scalable multi-agent design

    The role calls for designing agentic systems and architecting scalable multi-agent workflows. Prepare to explain an architecture you built, including agent responsibilities, orchestration, and design trade-offs.

  • RAG and retrieval quality

    Implementing and optimizing RAG pipelines, embeddings, vector databases, and semantic search is central to the posting. Prepare to discuss how you would assess retrieval quality and improve a pipeline when results are weak.

  • End-to-end AI delivery

    The responsibilities span data ingestion, processing, inference, and deployment of AI-driven solutions. Prepare to trace one workflow from input data through inference, explaining the decisions at each stage.

  • Framework use and collaboration

    The posting requires experience with both LangChain and LangGraph and calls for cross-functional delivery and evaluation of emerging tools. Prepare to explain where you have used each framework and how you would assess a new tool for a specific workflow.

Likely challenges to think through

  • Balancing agent flexibility with control

    A likely design difficulty, not a confirmed employer issue, is deciding when multiple agents add value versus complexity. Prepare a concrete example showing how you would choose agent boundaries and make workflow behavior understandable.

  • Diagnosing weak RAG answers

    Because the role includes RAG optimization, a plausible challenge is separating retrieval failures from generation or prompting failures. Prepare a step-by-step diagnostic approach and the evidence you would use before changing the pipeline.

  • Choosing tools without disrupting delivery

    Evaluating emerging frameworks while delivering end-to-end solutions may require trading new capabilities against integration effort. Prepare to describe how you would test a tool against an existing workflow before recommending adoption.

03

Practice your answers

Technical practice

How would you design a scalable multi-agent workflow?

What to coverSuggested preparation: Explain how you would assign responsibilities to agents, coordinate their work, and define when the workflow is complete. Discuss trade-offs between adding specialized agents and keeping the system simpler.

How would you manage failures in agent orchestration?

What to coverSuggested preparation: Walk through how you would detect failed steps, prevent repeated actions, and recover or stop safely. Relate your approach to the posting’s responsibility for managing agent orchestration frameworks.

How would you build an end-to-end RAG pipeline?

What to coverSuggested preparation: Trace the path from ingested data through processing, retrieval, and LLM inference. Explain which stages you would inspect first if retrieved context did not support the answer.

How would you choose and assess embeddings for semantic search?

What to coverSuggested preparation: Explain how embeddings represent text for retrieval and how you would test whether relevant material is found. Discuss the trade-off between retrieval quality and processing cost without assuming a particular model.

What would you consider when using a vector database?

What to coverSuggested preparation: Describe how you would store and retrieve embeddings and keep them aligned with changing source data. Compare retrieval speed, relevance, and operational complexity as design considerations.

How would you evaluate and improve a RAG system?

What to coverSuggested preparation: Separate retrieval errors from generation errors, then describe how you would examine examples of each. Explain how changes to data processing, retrieval, or prompts could be evaluated rather than assumed to help.

How would you use prompts to guide an LLM within an agent workflow?

What to coverSuggested preparation: Explain how prompts can define an agent’s task, expected output, and boundaries. Discuss how you would test prompt changes for reliability across varied inputs.

How would you structure a Python-based AI workflow from ingestion to inference?

What to coverSuggested preparation: Describe how you would separate ingestion, processing, orchestration, and inference so each stage can be tested and changed. The posting specifies Python and relevant AI/ML libraries but does not name a required library beyond LangChain and LangGraph.

How would you use LangChain and LangGraph in an agentic system?

What to coverSuggested preparation: Explain the roles each could play in implementing the workflow and when an explicit graph of steps would be useful. Ground the answer in a concrete design, since the posting specifically requires experience with both.

How would you evaluate an emerging AI framework for integration?

What to coverSuggested preparation: Propose a small comparison against the existing workflow’s needs, such as orchestration fit, maintainability, and performance. Explain what evidence would justify integration rather than adopting a tool solely because it is new.

Behavioural practice

Tell me about a time you collaborated across functions to deliver an AI solution.

What to coverSuggested preparation: Set out the situation, the different teams’ needs, and the actions you took to align the work. State the result and what you learned about coordinating delivery.

Tell me about a difficult problem you diagnosed in an AI workflow.

What to coverSuggested preparation: Describe the symptoms and how you narrowed the issue to a particular stage or component. Explain your actions, the result, and how you verified the fix.

Tell me about a time you assessed a new AI tool or framework.

What to coverSuggested preparation: Explain the need that prompted the evaluation, the criteria you used, and your role in testing it. Give the resulting decision and its effect, whether or not the tool was adopted.

Tell me about a time you made a system-design trade-off.

What to coverSuggested preparation: Describe the constraints, the options you considered, and how you reached a decision. Explain the result, including any limitation you accepted or later revisited.

Tell me about a time you took an AI workflow from design toward deployment.

What to coverSuggested preparation: Identify your responsibilities across the stages you worked on and the obstacles you encountered. Describe your actions and the outcome without claiming ownership of stages you did not handle.

02

Sharpen your knowledge

Topics to prepare

  • Multi-agent system design

    Practice: sketch a workflow with two agents, showing their responsibilities, handoffs, failure paths, and how it could scale. The posting explicitly calls for agent-based system design and scalable multi-agent workflows.

  • RAG and semantic search concepts

    Practice: explain how ingestion, embeddings, vector-database retrieval, and generation fit together; identify where retrieval quality can degrade. These are explicit parts of the role.

  • LLMs and prompt engineering

    Practice: compare two prompt designs for the same task and explain how you would judge their outputs. The posting requires a solid understanding of LLMs and prompt engineering; the comparison is a preparation suggestion.

  • End-to-end AI workflow design

    Practice: draw the path from data ingestion through processing to inference, noting where agents and retrieval interact. The posting names these workflow stages and emphasizes system design.

Skills to revise

  • Python implementation

    Practice: write a small Python workflow that ingests text, processes it, and passes it to an inference step. Python proficiency and end-to-end AI workflows are explicit requirements; the small example is a preparation suggestion.

  • LangChain and LangGraph

    Practice: build a minimal agent workflow using both LangChain and LangGraph, then explain what each contributes. The posting marks experience with both as mandatory.

  • RAG pipeline construction

    Practice: implement a small retrieval-and-generation flow using embeddings, semantic search, and a vector database; inspect retrieved results before generation. The posting explicitly requires hands-on RAG and vector-search experience.

  • Multi-agent orchestration

    Practice: configure agents to pass work between steps and handle an unsuccessful step, then trace one execution. This rehearses the explicitly stated work of building agent orchestration frameworks and managing multi-agent workflows.

04

Your preparation checklist

  • Map the requirements to evidence

    Prepare a one-page table linking the posting’s 3–6 years of relevant experience, Python, agent design, RAG, and mandatory LangChain and LangGraph experience to examples you can discuss. Mark any gaps rather than inventing examples.

  • Prepare an agent-system walkthrough

    If you have a relevant project, diagram its agents, orchestration, workflow decisions, and deployment. Be ready to explain your own contribution and how the design addressed scale; the posting calls for scalable multi-agent systems.

  • Work through a RAG design exercise

    Sketch a hypothetical pipeline from ingestion and processing through embeddings, vector search, retrieval, and inference. Explain how you would assess retrieval quality and improve the pipeline; this is preparation for the stated RAG responsibilities, not a specified interview exercise.

  • Demonstrate framework and Python choices

    Prepare a concise code example or architecture sketch showing how you have used LangChain and LangGraph, if applicable. Explain their respective roles, relevant Python libraries, and a design trade-off without claiming experience you do not have.

  • Prepare an LLM and collaboration example

    Choose a real example, if available, that shows prompt-engineering decisions, analytical problem-solving, and work with other teams. Summarize the objective, your decisions, the evidence used to assess results, and what changed.

  • Draft questions about delivery expectations

    Ask how the team defines success for its AI workflows, which parts of ingestion-to-inference the role owns, how agents and RAG are evaluated, and how emerging tools are selected. These are questions to clarify the posting, not stated company processes.

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…