New opportunity

Data Scientist II, International Machine Learning

Amazon · Gurugram, India

About this role

Join Amazon’s International Machine Learning team to develop and deploy scalable machine learning solutions for consumer-business problems in India and other emerging markets across MENA and Latin America. The team uses large-scale business data to improve customer experience, automate processes and support business performance. Application areas include product recommendations, transaction risk, catalog quality and address suggestions.

Responsibilities

  • Analyze large volumes of historical business data and use machine learning and analytical techniques to solve business problems and optimize processes.
  • Design, develop, evaluate, deploy and maintain scalable ML models. Establish efficient, automated processes for data analysis, model development and validation.
  • Partner with business stakeholders to identify problems and propose solutions; work with software engineers and product managers to implement complex models in production, including real-time applications.
  • Lead projects and mentor scientists and engineers in ML techniques.

Basic qualifications: At least 2 years of data scientist experience; at least 3 years of experience with data-querying languages such as SQL, scripting languages such as Python, or statistical and mathematical software such as R, SAS or Matlab; and at least 3 years of experience with machine learning or statistical-modeling analysis tools, techniques and performance parameters. Candidates need experience applying theoretical models in practice, using quantitative analysis for business decisions, and communicating complex concepts effectively. Experience developing ML models across the credit lifecycle, including pre-underwriting, underwriting, post-underwriting and collections, is listed among the basic qualifications. Fintech, lending or credit-risk experience is highly preferred.

Preferred qualifications

A Ph.D. in a STEM field; knowledge of ML concepts for reasoning and problem-solving; ML or data scientist experience at a large technology company; and the ability to turn insights into strategy and communicate them clearly in writing. The posting also prefers at least 3 years of credit-lifecycle ML model development and at least 3 years in fintech, lending or credit risk.

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

Skills for this role

Machine LearningStatistical ModelingData AnalysisQuantitative AnalysisSQLPythonRSASMATLABBig DataModel DevelopmentModel ValidationCredit RiskFintechCommunicationMentoring

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

  • Own business outcomes with quantitative analysis

    The role calls for analyzing large volumes of historical business data, identifying problems with business partners, and using models to automate or optimize processes. The posting emphasizes ownership of business problems and metrics affecting customer experience and India business performance.

  • Build models through production and maintenance

    Responsibilities span model design, evaluation, deployment and maintenance, plus automated data analysis and validation. The role also works with software engineers on real-time implementations and large-scale production models.

  • Apply credit-lifecycle modeling experience

    The basic qualifications list experience developing ML models across pre-underwriting, underwriting, post-underwriting and collections. Fintech, lending or credit-risk experience is described as highly preferred; the posting also lists broader consumer-business applications.

  • Lead projects and communicate across teams

    The role includes leading projects, mentoring scientists and engineers, and working with business partners, product managers and engineers. Qualifications emphasize explaining complex concepts clearly and turning quantitative analysis into business decisions.

Likely challenges to think through

  • Balancing model quality with production constraints

    Preparation hypothesis: a model that performs well in analysis may be difficult to deploy at scale or in real time. Prepare to explain how you would evaluate performance alongside implementation, validation and maintenance needs; the posting does not specify its infrastructure.

  • Choosing metrics across different business applications

    Preparation hypothesis: recommendations, transaction risk, catalog quality and address suggestions may call for different measures of success and different trade-offs. Prepare to describe how you would define a business metric with stakeholders and connect model evaluation to it, without assuming one metric fits every application.

  • Translating credit-risk depth to a broad international remit

    Preparation hypothesis: credit-lifecycle modeling is explicitly requested, while the team also targets varied India-first and emerging-market problems. Prepare to explain which modeling principles transfer across applications and where data or business context would require a different approach.

03

Practice your answers

Technical practice

How would you turn a business problem into an ML objective and success metric?

What to coverSuggested preparation (inference): Start with the customer or business outcome, then define a measurable target and a simpler baseline. Explain how you would check whether model improvements also improve the process or metric the business partner cares about.

How would you build a reliable modeling dataset from large volumes of historical business data?

What to coverSuggested preparation (inference): Discuss querying and joining data, checking completeness and time boundaries, and avoiding information that would not be available when a prediction is made. Explain the trade-off between richer features and scalable, repeatable data preparation.

How would you evaluate a model intended to safeguard financial transactions?

What to coverSuggested preparation (inference): Compare errors that miss risky transactions with errors that affect legitimate customers, rather than relying on one aggregate score. Describe how you would choose an operating threshold against the stated business objective.

How would you assess product bundle recommendations at a large product scale?

What to coverSuggested preparation (inference): Explain how you would establish a baseline, evaluate recommendation relevance, and check whether gains translate into customer or business value. Address the trade-off between model quality and the cost of generating recommendations for millions of products.

How would you extract and validate product attributes from structured and unstructured catalog data?

What to coverSuggested preparation (inference): Describe how you would handle inconsistent inputs and measure attribute accuracy across product types. Explain when automated extraction should yield to additional validation to protect catalog quality.

How would you evaluate address-quality suggestions?

What to coverSuggested preparation (inference): Define what a useful suggestion should improve and how you would detect suggestions that incorrectly change a valid address. Discuss the trade-off between offering more suggestions and maintaining customer trust.

How might modeling choices differ across pre-underwriting, underwriting, post-underwriting and collections?

What to coverSuggested preparation (inference): Distinguish the decision, available information and outcome at each credit-lifecycle stage, as the posting explicitly names these stages. Explain why a model and validation approach suitable for one stage may not transfer unchanged to another.

What would you consider when moving a model into a real-time application?

What to coverSuggested preparation (inference): Discuss prediction-time feature availability, latency, reliability and coordination with software engineers. Explain how you would balance model complexity against the needs of a production application.

How would you automate model validation and maintenance after deployment?

What to coverSuggested preparation (inference): Describe repeatable checks for data quality, model performance and changes over time, with a clear response when a check fails. Distinguish validation before deployment from monitoring an operating model.

How would you test whether an ML solution built for India applies to another emerging market?

What to coverSuggested preparation (inference): Compare data availability, customer behavior and the business objective before assuming a model transfers across markets. Propose local evaluation and explain the trade-off between reusing a scalable solution and adapting it to a different setting.

Behavioural practice

Tell me about a time you worked with a business partner to define an ambiguous problem.

What to coverSuggested preparation (inference): Use a real situation, your actions to clarify the decision and success metric, and the result. Focus on how quantitative analysis changed or sharpened the proposed solution.

Tell me about a time you worked with engineers to put a complex model into use.

What to coverSuggested preparation (inference): Describe the situation, your contribution to resolving implementation trade-offs, and the result. Make clear how you communicated model behavior or constraints to the engineering team.

Tell me about a project you led from analysis through evaluation or deployment.

What to coverSuggested preparation (inference): Give the situation, decisions you owned, actions you coordinated and the result. Explain a substantive trade-off between model performance, scalability or business impact.

Tell me about a time you helped another scientist or engineer apply an ML technique.

What to coverSuggested preparation (inference): Describe the situation, how you mentored or reviewed their approach, and the result. Focus on the technical judgment they needed to develop rather than simply naming the technique.

Tell me about a time you turned a complex analysis into a clear recommendation.

What to coverSuggested preparation (inference): Use a real situation, how you explained the evidence and uncertainty in writing or conversation, and the resulting decision. Distinguish what the analysis showed from the strategy you recommended.

02

Sharpen your knowledge

Topics to prepare

  • Credit-lifecycle modeling

    The basic qualifications call for ML model development across pre-underwriting, underwriting, post-underwriting and collections. Sketch a hypothetical prediction task for each stage, specifying the decision it supports, available information and how you would evaluate it. Treat the task designs as preparation examples, not stated projects.

  • Model evaluation and performance drivers

    The posting asks for ML or statistical-modeling techniques and knowledge of parameters affecting performance. Compare two model approaches for a hypothetical transaction-risk problem; explain the evaluation measures, error trade-offs and conditions under which performance might change. The approaches and measures you choose are revision suggestions, not prescribed by Amazon.

  • Large-scale model lifecycle

    The role includes developing, evaluating, deploying and maintaining scalable models, with automated analysis and validation. Draw an end-to-end workflow from historical data to production monitoring, and explain where you would check data and model quality. Specific checks are your proposed approach, not listed requirements.

  • Business problem formulation

    The team works on India-first and other emerging-market problems, including product bundles, transaction risk, catalog attributes and address suggestions. Choose one listed application and outline its target decision, useful historical data and a business outcome to assess; these choices are a practice exercise, not a specified assignment.

  • Quantitative decisions and communication

    The qualifications call for quantitative analysis that informs business decisions and clear written and verbal explanations. Practice interpreting a hypothetical model result: state what decision it supports, its limitations and what evidence would change your recommendation.

Skills to revise

  • Query historical data

    The posting cites data-querying languages such as SQL and analysis of large volumes of historical business data. As practice, write a SQL query that builds a time-bounded, aggregated dataset from hypothetical transaction tables, then explain how you would check the result. SQL is an example named in the posting, not a requirement to use a particular database.

  • Prototype a model

    The posting cites scripting languages such as Python and statistical software such as R, SAS or Matlab, alongside applied ML experience. In a language you use, prototype a model on a small synthetic dataset, evaluate it and explain which choices could affect performance. No particular language is mandated by this exercise.

  • Plan validation and maintenance

    The responsibilities include automated model development, validation and maintenance. Draft a repeatable validation plan for a hypothetical credit-lifecycle or transaction-risk model, including what you would measure before release and revisit afterward. The plan is a preparation suggestion, not an Amazon process.

  • Present a production handoff

    The role works with software engineers and product managers on complex models, including real-time implementations. Practice a short handoff that states a hypothetical model’s inputs, outputs, expected use and failure cases, plus questions for engineering. These details are suggested discussion points, not specified interface requirements.

  • Explain and mentor

    The posting calls for leading projects, mentoring scientists and engineers, and communicating complex ideas clearly. Prepare a brief written explanation of one modeling trade-off, then rehearse explaining it to both a business partner and a technical colleague.

04

Your preparation checklist

  • Map evidence to the qualifications

    Prepare a one-page map of examples for data science, SQL or another listed language, ML modeling, applied quantitative decisions, and written and verbal communication. Note separately the posting’s credit-lifecycle qualification and preferred fintech, lending, or credit-risk experience.

  • Build a large-data project walkthrough

    Select one project involving substantial historical data. Be ready to explain the business problem, data extraction, modeling choices, validation, business metric, and decision informed by the analysis.

  • Prepare a credit-lifecycle example

    If you have relevant work, trace one model through pre-underwriting, underwriting, post-underwriting, or collections and explain its evaluation. Otherwise, prepare a clearly labeled hypothetical discussion rather than presenting it as experience.

  • Practice a production ML design

    As a practice exercise, design a scalable, real-time transaction-risk model—one application named in the posting. Sketch inputs, evaluation, deployment with engineers, automation, and ongoing validation and maintenance.

  • Rehearse a data and modeling exercise

    Prepare a short SQL and Python or other listed-tool example showing how you would extract useful signals from historical data, check data quality, compare models, and explain performance trade-offs.

  • Document project leadership and collaboration

    Prepare one concise account of identifying a problem with business partners, working with engineers or product managers on implementation, and leading a project or mentoring others, where applicable.

  • Draft a written recommendation

    Write a brief example that turns a model result into a business recommendation, stating the metric, uncertainty, trade-offs, and proposed next step. The posting emphasizes clear written communication and translating insights into strategy.

  • Prepare targeted questions

    Ask which India-first or emerging-market problems are priorities, how the team evaluates customer and business impact, and how scientists partner with engineers on real-time deployment and model maintenance.

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…