New opportunity

Machine Learning Scientist II - Supply Chain AI

Wayfair · Boston, United States

About this role

Wayfair’s Supply Chain and Retail Technology Science team seeks a Machine Learning Scientist to develop and refine models for supply-chain and post-order customer-experience challenges. The team builds systems that predict delivery dates across the shopping journey while accounting for changes in the delivery network, customer trust, and operational performance. Other team projects include graph-neural-network policy-abuse detection, customer-service policy personalization, and vision-LLM product-refund diagnostics.

Responsibilities

  • Design, build, and deploy large-scale machine learning models that balance short- and long-term business value.
  • Analyze data to identify patterns, relationships, and features for model training.
  • Work with product managers, commercial stakeholders, and engineering partners to define problems and iteratively develop solutions that maximize business ROI.
  • Define success metrics and evaluation frameworks to assess model-output quality regularly.

Required qualifications

  • A PhD with 0–1+ years of experience, or a master’s degree in a STEM field—such as engineering, computer science, data science, machine learning, or a related quantitative field—with 2+ years of full-time industry experience in applied research.
  • A record of taking machine learning projects from conception to production, including deployment and maintenance, with strong problem-solving skills.
  • Professional Python coding expertise, SQL proficiency, experience with data-visualization tools, skill with TensorFlow or PyTorch, and version-control best practices. Strong written and verbal communication with technical and nontechnical audiences is required.

Preferred qualifications

  • Familiarity with GCP, AWS, or Azure; MLOps practices such as feature stores and MLflow; and orchestration tools such as Kubeflow or Airflow.
  • Experience with Docker, causal inference, multi-armed bandits, personalization, or hands-on LLM work.

Location and compensation: This hybrid role is based in Boston, MA, with office days Tuesday–Thursday and remote work Monday and Friday. Annual base pay is USD 176,000.00–184,250.00; the range may vary by location, knowledge, skills, and experience. Other compensation may be offered depending on the position. Listed benefits include paid time off, health coverage, retirement matching, tuition reimbursement, and parental leave.

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

Skills for this role

Machine LearningExploratory Data AnalysisModel DeploymentModel EvaluationPythonSQLData VisualizationTensorFlowPyTorchVersion ControlCommunicationCross-functional CollaborationGCPAWSAzureMLOpsFeature StoresMLflowKubeflowAirflowDockerCausal InferenceMulti-armed BanditsPersonalizationLarge Language Models

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

  • Delivery-date prediction and customer trust

    Source-backed: The team builds end-to-end delivery-date predictions at different points in the shopping funnel, accounting for network changes, customer trust, and operational KPIs. Preparation: Be ready to explain how you would frame prediction quality in that business context.

  • Models that reach and remain in production

    Source-backed: The role designs, builds, and deploys large-scale models; the posting also calls for experience taking projects from conception through deployment and maintenance. Preparation: Organize an end-to-end project account covering design decisions, engineering collaboration, launch, and upkeep.

  • Data investigation and ongoing evaluation

    Source-backed: Duties include exploratory analysis to identify training features, defining success metrics, and regularly assessing model-output quality. Preparation: Explain how exploratory findings informed a model and how its evaluation would continue after deployment.

  • Business-led, cross-functional iteration

    Source-backed: The scientist works with product managers, commercial stakeholders, and engineers to define problems and develop solutions that maximize ROI while balancing short- and long-term value. Preparation: Show how you would communicate technical trade-offs and revise a solution as business needs become clearer.

Likely challenges to think through

  • Accuracy amid delivery-network changes

    Potential challenge, not a confirmed problem: A delivery-date model could perform well on past data yet become less useful as the network changes; more aggressive estimates could also conflict with customer trust. Prepare to discuss time-aware evaluation, monitoring, and how you would compare accuracy with operational and trust measures.

  • Choosing the right approach across distinct projects

    Potential challenge, not an assignment to every project: The team describes delivery prediction, graph-based abuse detection, policy-effectiveness modeling, and vision-LLM refund diagnostics. Their data and evaluation needs differ. Prepare to explain how you would select a method and success measure for the problem rather than defaulting to one model family.

  • Balancing iteration speed with production reliability

    Potential challenge, not a stated employer issue: Iterative development for business ROI may compete with the time needed to deploy and maintain large-scale models reliably. Prepare an example of how you would scope an initial release, coordinate with engineers, and decide when further model complexity is worth maintaining.

03

Practice your answers

Technical practice

How would you design a system to predict delivery dates at different points in the shopping journey?

What to coverThe posting identifies delivery-date prediction under changing network conditions as a team challenge. Suggested preparation: discuss what information is available at each prediction point, how to avoid using future information, and how you would balance accuracy with customer trust and operational KPIs.

How would you use SQL, Python, and visualization to find useful training features?

What to coverExploratory data analysis and proficiency with these tools are stated in the posting. Suggested preparation: explain how you would examine missing data, changing patterns, and feature relationships, then check whether promising features remain available when the model makes predictions.

How would you evaluate the quality of delivery-date predictions over time?

What to coverThe role includes defining success metrics and regularly assessing model outputs. Suggested preparation: distinguish prediction error from the effects of early or late estimates on customer trust, and explain how you would inspect performance as the delivery network changes.

What would you consider when taking a large-scale ML model from research to production?

What to coverThe posting calls for model design, deployment, and maintenance, with collaboration from engineering partners. Suggested preparation: cover reproducible training, version control, deployment checks, ongoing monitoring, and the trade-off between model complexity and operational reliability.

How might a graph neural network help detect policy abuse despite identity manipulation?

What to coverGraph-neural-network-based policy-abuse detection is listed as a team project. Suggested preparation: explain what relationships a graph could represent, why connected evidence might complement individual records, and how you would evaluate false positives and robustness without assuming the team's implementation.

How would you estimate which customer-service policy is most effective for a particular customer?

What to coverThe posting names uplift modeling for customer-service policy personalization and lists causal inference as preferred familiarity. Suggested preparation: distinguish predicting an outcome from estimating a policy's incremental effect, and discuss comparison groups, selection bias, and evaluation.

How would you assess a vision-LLM system for product-refund diagnostics and resolution?

What to coverThe posting lists visual diagnostics and resolution for product refunds as a team project, while hands-on LLM experience is a preference. Suggested preparation: discuss how you would assess diagnostic accuracy, unsupported outputs, and the consequences of an incorrect resolution; avoid assuming a particular model or workflow.

When would you consider a multi-armed bandit rather than a fixed policy comparison?

What to coverMulti-armed bandits are listed as preferred familiarity, and the role involves balancing short- and long-term business value. Suggested preparation: explain exploration versus exploitation, when adaptive allocation could be useful, and why measuring longer-term effects may complicate the choice.

How would you make a model-training and evaluation workflow reproducible?

What to coverVersion-control practices are required; feature stores, MLflow, orchestration tools, cloud platforms, and Docker are listed as nice-to-haves. Suggested preparation: describe how you would track data and model versions, rerun evaluations, and choose workflow components based on the problem rather than assuming Wayfair uses a specific stack.

How would you decide whether a more complex model delivers enough business value?

What to coverThe role calls for large-scale models that maximize ROI while balancing short- and long-term value. Suggested preparation: compare a simpler baseline with a more complex approach using output quality, maintenance effort, operational costs, and effects on the stated customer and business goals.

Behavioural practice

Tell me about a time you defined an ML problem with product or commercial stakeholders.

What to coverThe posting emphasizes cross-functional problem definition and iterative solutions. Suggested preparation: use a real situation, explain how you translated stakeholder goals into a tractable question and revised the approach, then state the result.

Describe a time you worked with engineers to deploy and maintain a model.

What to coverEngineering collaboration and delivery from conception through production are stated expectations. Suggested preparation: describe the situation, your specific contribution to a deployment or maintenance decision, and the observable result.

Tell me about a time data analysis changed your modeling plan.

What to coverThe role includes uncovering patterns, relationships, and training features through exploratory analysis. Suggested preparation: give a real situation, the analysis and decision you made, and what happened afterward.

Describe a time you explained a model-quality concern to a nontechnical audience.

What to coverThe posting requires communication with technical and nontechnical audiences and regular assessment of model-output quality. Suggested preparation: outline the situation, how you conveyed the concern and its trade-offs, and the resulting decision or action.

Tell me about a time you balanced an immediate result against a longer-term ML outcome.

What to coverBalancing short- and long-term business value is an explicit responsibility. Suggested preparation: use a real situation, explain the options and your action, and report the result without claiming an impact you could not verify.

02

Sharpen your knowledge

Topics to prepare

  • Delivery-date prediction under network change

    The team builds end-to-end predictions at different points in the shopping funnel while accounting for a changing delivery network. As a revision exercise, sketch what information is available at each prediction point and how you would test performance before and after a network change.

  • Model quality and business trade-offs

    The role defines success metrics and regularly evaluates output quality while balancing customer trust, operational KPIs, and short- and long-term value. Draft a metric framework for delivery-date predictions, distinguishing prediction quality from business outcomes and explaining possible trade-offs.

  • Exploratory analysis and feature reasoning

    Exploratory data analysis to find patterns, relationships, and training features is an explicit responsibility. Given a hypothetical order-and-delivery dataset, list plausible features, when each becomes available, and checks for missing data or information leakage.

  • Production ML lifecycle

    The posting requires taking ML projects from conception through deployment and maintenance at scale. Rehearse a project walkthrough covering problem definition, modeling decisions, deployment, recurring quality checks, and a response to degraded performance.

  • Cross-functional problem framing

    The scientist works with product managers, commercial stakeholders, and engineering partners to maximize business ROI. Practice turning an ambiguous post-order customer-experience problem into a model objective, measurable outcome, and set of questions for each partner group.

  • Other team project approaches

    The posting also names GNN-based policy-abuse detection, customer-service policy uplift modeling, and vision-LLM refund diagnostics; it does not say every scientist works on all three. For breadth, choose one and explain its prediction target, a likely evaluation challenge, and how you would investigate failure cases. Causal inference, personalization, and hands-on LLM experience are listed as nice to have, not core requirements.

Skills to revise

  • SQL exploration and data visualization

    SQL proficiency and experience with visualization tools are required. Practice querying hypothetical order and delivery records for missingness and segment-level patterns, then make a chart that communicates one finding and its implications for model training.

  • Python modeling with an advertised framework

    Professional Python coding and skill with TensorFlow or PyTorch are required. Implement a small delivery-date prediction example in one of those frameworks, compare it with a simple baseline, and explain your code structure and modeling choices.

  • Build a repeatable evaluation check

    The role calls for evaluation frameworks that regularly assess model-output quality. Write a Python check that reports prediction quality by shopping-funnel stage and time period, and specify what change would prompt investigation. The particular checks are preparation suggestions, not prescribed Wayfair metrics.

  • Deployment and maintenance walkthrough

    Deployment, maintenance, and version-control best practices are explicit requirements. Practice describing how you would version a model change, validate it before release, monitor its outputs, and investigate a regression. If useful, relate the walkthrough to the posting’s optional MLOps or orchestration tools without treating them as required.

  • Technical and nontechnical explanation

    Strong written and verbal communication across technical and nontechnical audiences is required. Prepare two brief explanations of the same delivery-date model decision: one for an engineering partner covering implementation and evaluation, and one for a commercial stakeholder covering customer trust and business trade-offs.

04

Your preparation checklist

  • Prepare an end-to-end ML project walkthrough

    The role calls for projects delivered from conception through deployment and maintenance. Prepare one real example covering the problem, your decisions, production handoff, monitoring, results, and lessons learned.

  • Sketch a delivery-date prediction design

    Wayfair describes predictions at different points in the shopping journey amid delivery-network changes. As a practice exercise, outline available inputs, a baseline, model choices, serving approach, and how you would handle changing conditions.

  • Assemble evidence of data and coding work

    Prepare a concise example of SQL analysis, Python feature development, and a visualization that revealed a useful pattern. Be ready to explain your use of TensorFlow or PyTorch and version-control practices; these are stated qualifications.

  • Draft a model evaluation plan

    The role develops success metrics and regularly assesses output quality. For the delivery-date exercise, propose prediction-quality measures alongside customer-trust and operational measures, explaining trade-offs and how you would check performance over time.

  • Rehearse a cross-functional decision story

    Prepare an example of working with product, commercial, or engineering partners to refine an ML problem. Explain the competing short- and long-term considerations, iterations, and how you communicated the outcome to technical and nontechnical audiences.

  • Review one adjacent team problem

    Choose the posting’s GNN policy-abuse detection, customer-service policy uplift, or vision-LLM refund diagnostics example. Prepare a brief, explicitly hypothetical approach and its main evaluation challenge; related methods and tools are not all required qualifications.

  • Write targeted questions for the team

    Bring questions about where delivery-date predictions are used, how customer trust and operational KPIs are balanced, who owns production maintenance, and which of the listed team problems this role would prioritize.

AI-generated from the job information · Prepared Sep 30, 2026 (UTC)Useful preparation, not a guarantee of eligibility or an offer.

Availability last checked: Nov 4, 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 United States. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…