← UiPath Interview Insights

UiPath·Machine Learning Engineer·Technical Phone Screen·Senior

Senior
May 2026

Summary

Technical screen for an MLE role at UiPath, basically one big case study on feature engineering for a house price model. Pretty thorough for a single question but it covered a lot of ground fast.

Questions Asked (1)

Q1

You're given a dataset with only two features, numeric area and categorical neighborhood, to predict house prices. Walk through all the feature engineering and preprocessing you'd do, then justify your model choice and evaluation metric.

Technical Trade-offsData ModelingProduct Analytics & Metrics
Author's notes

This one sprawled in a way I didn't expect from what looked like a simple setup.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by outlining the preprocessing steps for both numeric and categorical features, then discuss feature engineering opportunities like interactions and target encoding. Justify your model choice based on the data characteristics and explain why your chosen evaluation metric aligns with the business problem.

Pro tip: Always tie your choices back to the business context—for house price prediction, asymmetric loss (e.g., overpredicting is worse than underpredicting) often matters more than pure statistical performance.

1. Preprocess numeric feature

Handle missing values, outliers, and scaling for the area feature. Consider transformations like log scaling if the distribution is skewed.

2. Encode categorical feature

Choose an encoding method for neighborhood (e.g., one-hot, target, or frequency encoding) based on cardinality and risk of overfitting.

3. Engineer new features

Create interactions (e.g., area * neighborhood average price) or aggregate statistics (e.g., neighborhood median area) to capture combined effects.

4. Select and justify model

Pick a model that handles mixed data types and nonlinearity (e.g., gradient boosting) and explain why it suits the problem.

5. Choose evaluation metric

Select a metric like RMSE or MAE, and justify it based on the business cost of errors (e.g., asymmetric loss).

Key Points to Mention

  • Handling missing values and outliers in area (e.g., imputation, clipping)
  • Encoding neighborhood with target encoding or one-hot, and addressing high cardinality
  • Creating interaction features like area per neighborhood average
  • Using tree-based models (e.g., XGBoost) for mixed data and nonlinearity
  • Choosing RMSE for large errors or MAE for robustness, and considering asymmetric loss
  • Validating with cross-validation and monitoring for overfitting

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.