ML case: port waiting-time forecasting

Выводы и как готовиться

• The interviewer pushes target and aggregation choices from a business-latency perspective, not only a modeling perspective.
• Port-level historical aggregates are useful but can leak future information if train/test time boundaries are ignored.
• The case tests practical ML judgment: anomaly handling, categorical encoding, horizon design and interpretability.