New opportunity

Agentic Analytics Products Developer

eBay · Bengaluru, India

About this role

Build AI-first analytics products that help eBay’s business and product teams explore data, diagnose performance, understand the reasons behind results, and make evidence-based decisions. The role spans analytics, product, UX, and AI, turning human questions into data-grounded answers through interactive applications and analytical APIs.

Responsibilities

  • Build React interfaces for self-service data exploration, metric comparisons, and visualization of trends and causal drivers.
  • Connect front-end workflows to agentic pipelines that query, aggregate, and explain data. Develop FastAPI endpoints that deliver summaries, charts, and AI-powered diagnostics for human review or automation.
  • Define measures of analytical quality, including relevance and latency, and test and improve model-driven insights. Show the queries, data sources, and assumptions behind results so users can validate them.
  • Partner with data science, product management, and analytics teams to define metrics and evaluation frameworks and respond to user feedback. Write tests and monitor performance to improve speed, clarity, and analytical correctness.

Required skills:

  • Experience building self-serve analytics or decision-intelligence platforms; React for interactive data visualization; analytical APIs, data validation, and asynchronous retrieval.
  • SQL, data modeling, metrics computation, and time series analysis; LLM and agent analytics, including prompt design, RAG, evaluation, and grounding.
  • Data storytelling and visualization, experience measuring insight quality with evaluations, A/B tests, or golden datasets, and clear communication of analytical logic, trade-offs, and findings.

Preferred skills: Familiarity with databases, semantic layers, retrieval systems, experimentation frameworks, metrics stores, or statistical testing; UX for analytical workflows; software deployment such as Kubernetes; and DevOps workflows involving automated testing, secret management, and highly available cloud environments.

The intended outcome is a product that gives stakeholders grounded, visual answers to complex plain-English questions within seconds, increasing confidence in data and reducing time to decision. This is a full-time position in Bengaluru, India, listed as 40 hours per week.

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

Skills for this role

ReactData visualizationFastAPIAPI developmentData validationAsynchronous data retrievalSQLData modelingTime series analysisLarge language modelsAI agentsPrompt designRAGModel evaluationData groundingData storytellingA/B testingGolden datasetsCommunicationDatabasesSemantic layersRetrieval systemsUX designExperiment frameworksMetrics storesStatistical testingKubernetesDevOpsAutomated testingSecret management

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

  • Self-serve analytical experiences

    The role builds React interfaces for exploring data, comparing metrics, and visualizing trends and drivers. Prepare to explain how an interface helps users move from a question to a clear chart, table, or contextual narrative.

  • End-to-end AI-assisted insight delivery

    The posting calls for connecting front-end workflows to agentic pipelines that query, aggregate, and explain data, with FastAPI endpoints returning summaries, charts, and diagnostics. Prepare to describe the boundaries between retrieval, analytical computation, explanation, and human review.

  • Grounded, inspectable answers

    Users should be able to validate results through the underlying queries, data sources, and assumptions. Prepare an example of how SQL, data modeling, validation, and visible analytical logic support a trustworthy answer.

  • Measured insight quality

    The role defines measures such as relevance and latency, tests model-driven insights, and monitors speed and analytical correctness. Prepare to discuss an evaluation approach using measures named in the posting, such as golden datasets, A/B tests, or other evaluations.

  • Product and metrics collaboration

    The developer partners with data science, product management, and analytics to define metrics and evaluation frameworks and respond to feedback. Prepare to explain how differing stakeholder needs can be translated into a shared metric definition and an actionable product change.

Likely challenges to think through

  • Speed versus analytical correctness

    Likely trade-off, not a confirmed eBay problem: answering complex plain-English questions within seconds may conflict with data validation, asynchronous retrieval, and thorough diagnostics. Prepare to explain where to measure latency, when to return a partial or qualified answer, and how to test correctness.

  • Explaining drivers without overclaiming

    Likely difficulty: a persuasive visualization or AI explanation may imply causation that the available analysis does not establish. Prepare to distinguish observed trends from supported causal claims and show how sources, queries, and assumptions would remain inspectable without overwhelming users.

  • Evaluating open-ended answers

    Likely difficulty: many valid user questions and explanations make insight quality harder to assess than a fixed dashboard metric. Prepare to describe how a representative test set, relevance checks, stakeholder feedback, and monitoring could expose failures while keeping metric definitions consistent.

03

Practice your answers

Technical practice

How would you design a React experience for exploring metrics and comparing trends?

What to coverThe posting calls for intuitive, self-service exploration and visualization. Suggested answer focus: explain how users would refine a question, compare consistent metrics, and move between a chart, a table, and the underlying context without losing track of what each view represents.

How would you model and compute a business metric in SQL so different users get consistent results?

What to coverSQL, data modeling, and metrics computation are listed as must-have skills. Suggested answer focus: define the metric’s grain, filters, and time window; then describe validation checks and how you would communicate assumptions.

How would you investigate a change in a time series without overstating its cause?

What to coverThe role involves time series analysis and visualizing trends and causal drivers. Suggested answer focus: discuss baselines, segmentation, and possible confounders, while distinguishing an observed association from evidence of causation.

How would you turn a plain-English question into a grounded agent-assisted analysis?

What to coverThe posting describes pipelines that query, aggregate, and explain data, and lists prompt design, RAG, evaluation, and grounding. Suggested answer focus: outline how you would resolve ambiguity, retrieve relevant definitions or data, check the resulting query and calculations, and limit unsupported claims.

How would you design a FastAPI endpoint for an analytical summary and chart?

What to coverThe role calls for insight APIs, data validation, and asynchronous retrieval. Suggested answer focus: describe request and response contracts, validation, handling slow or failed retrieval, and how the response would remain useful for human review or automation.

What would you expose so a user can validate an AI-generated insight?

What to coverThe posting explicitly asks for underlying queries, data sources, and assumptions to be visible. Suggested answer focus: explain how to present that evidence alongside the answer and what you would do when sources conflict or an assumption cannot be verified.

How would you evaluate whether model-driven insights are analytically correct and useful?

What to coverThe role calls for quality measures such as relevance and latency and mentions evaluations and golden datasets. Suggested answer focus: propose representative questions with expected evidence, checks for numerical correctness and grounding, and a way to review failure cases.

How would you test whether an analytics experience improves decisions rather than just generating answers?

What to coverThe posting names A/B tests as an insight-quality method and describes reduced time-to-decision and greater data confidence as intended outcomes. Suggested answer focus: distinguish product-use measures from answer-quality measures, discuss an appropriate comparison, and note the limits of interpreting either alone.

How would you improve response speed without sacrificing analytical correctness?

What to coverThe intended experience delivers grounded answers within seconds, and the role includes testing and performance monitoring. Suggested answer focus: identify where query, retrieval, API, and model latency arise; explain what you would measure and which optimizations would require correctness checks.

How would you present a complex result as a clear, trustworthy data story?

What to coverThe posting emphasizes charts, tables, contextual narratives, and communication of analytical logic and trade-offs. Suggested answer focus: choose views suited to the question, make comparisons and uncertainty legible, and give users a path from the headline finding to its supporting evidence.

Behavioural practice

Tell me about a time you aligned different teams on a metric or evaluation approach.

What to coverThe role involves partnering with data science, product management, and analytics on metrics and evaluation. Suggested practice: use a real situation, your actions to resolve differing definitions or priorities, and the resulting decision or measurable outcome.

Describe a time user feedback changed an analytical product or workflow.

What to coverThe posting calls for iterating on user feedback in self-service analytics. Suggested practice: describe the original user difficulty, how you investigated and acted on it, and what changed for users afterward.

Tell me about a time you found that an apparently convincing analysis was misleading.

What to coverThe role emphasizes analytical correctness, visible assumptions, and trust in insights. Suggested practice: explain the situation, how you checked the evidence and communicated the issue, and the result without claiming certainty you did not have.

Describe a time you balanced speed of delivery against quality or interpretability.

What to coverThe posting seeks answers within seconds while also calling for tests, monitoring, and clear analytical logic. Suggested practice: give a real example of the trade-off, the safeguards or scope choices you made, and the outcome.

Tell me about a time you turned a recurring analysis request into a reusable experience.

What to coverThe role focuses on moving beyond individual analyses toward AI-first, self-service analytics products. Suggested practice: describe the recurring need, your contribution to making it reusable, and evidence of how the resulting workflow was used or improved.

02

Sharpen your knowledge

Topics to prepare

  • Self-serve analytics as a product

    The posting emphasizes decision-intelligence platforms and turning plain-English questions into useful answers. Suggested exercise: sketch a user journey from a performance question to a decision, noting where users need to explore further, review evidence, or give feedback.

  • Metric definitions and time-series reasoning

    SQL, data modeling, metrics computation, and time-series analysis are must-haves. Suggested exercise: define a metric's grain, numerator, denominator, and comparison period; then explain how missing data or a changed definition could mislead a trend comparison.

  • Grounding and interpretability in agent analytics

    The role calls for LLM and agent analytics, including RAG, and for showing queries, sources, and assumptions behind results. Suggested exercise: diagram how a question becomes a query, aggregation, and explanation, marking where each claim must be checked against data.

  • Analytical quality and evaluation

    The posting names relevance, latency, evaluations, A/B tests, and golden datasets. Suggested exercise: propose a small evaluation rubric for answer correctness, relevance, traceability, and response time, and explain a trade-off between speed and analytical depth.

  • Visualization and analytical claims

    The role calls for clear charts, tables, contextual narratives, and views of trends and causal drivers. Suggested exercise: choose displays for a metric comparison and a trend, then distinguish an observed association from a supported causal explanation.

Skills to revise

  • Compute and validate metrics with SQL

    SQL-based metrics computation is a must-have. Suggested exercise: write queries over a small practice dataset to calculate a metric by period and segment, then check joins, duplicates, nulls, and totals before interpreting changes.

  • Build an exploratory React view

    The posting explicitly calls for React interfaces for data exploration, comparisons, and trends. Suggested exercise: make a small interactive view that filters a metric, compares two periods, and presents a chart alongside its definition and caveats.

  • Design a FastAPI insight endpoint

    The role includes analytical APIs, validation, and asynchronous retrieval. Suggested exercise: implement a practice endpoint that validates a question or metric request and returns a summary, chart-ready values, and the underlying query and assumptions; test invalid inputs and response time.

  • Connect an agentic analysis workflow

    The posting calls for pipelines that query, aggregate, and explain data, with prompt design and grounding. Suggested exercise: use a small practice dataset to take a plain-English question through those steps, and revise the prompt when an explanation makes a claim the data cannot support.

  • Test insight quality and performance

    Writing tests, monitoring performance, and measuring insight quality are explicit responsibilities. Suggested exercise: assemble a few question-and-expected-answer cases as a golden dataset, test numerical and source attribution errors, and record relevance and latency before and after a change.

  • Explain analytical trade-offs

    The posting requires clear communication and collaboration with data science, product management, and analytics teams. Suggested exercise: give a brief walkthrough of a practice insight covering the metric definition, evidence, uncertainty, and what user feedback would prompt a revision.

04

Your preparation checklist

  • Prepare a self-serve analytics walkthrough

    If you have a relevant project, outline the user question, your contribution, the interface and data flow, and how you measured usefulness. Distinguish your work from the team’s.

  • Sketch a plain-English-to-insight experience

    As a practice exercise, draw a React exploration flow connected to an agentic pipeline and FastAPI endpoints. Show how users compare metrics, view trends, and review summaries, charts, and diagnostics.

  • Work through a metric and time-series example

    Prepare a small SQL and data-modeling exercise with a metric definition, validation checks, a trend comparison, and an explanation of assumptions or possible confounders.

  • Show how an insight stays grounded

    Draft one example answer that exposes its query, data sources, and assumptions. Explain how prompt design or retrieval would avoid unsupported claims and let a user check the result.

  • Design an insight-quality evaluation

    Propose a compact test set and measures for relevance, analytical correctness, and latency. Include how you would use failed cases and user feedback to improve the experience.

  • Prepare a product trade-off story

    Use a real collaboration example, if available, to explain how you aligned stakeholders on a metric or analytical workflow. Be ready to discuss trade-offs between speed, clarity, and correctness.

  • Write questions for the employer

    Ask how data science, product management, and analytics define metrics together; what evidence users need to trust an answer; and how the team measures time-to-decision and data confidence.

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…