Agent Stack for ML Training Lifecycle: Generation, Validation, and Optimization
Organizations: LinkedIn
Abstract
Production model development requires repeated architecture design, platform integration, debugging, training, and evaluation. We present an agent stack deployed at LinkedIn with two independently usable agent loops: AutoTorch for model generation and migration, and AutoResearch for model optimization. AutoTorch generates PyTorch models and training pipelines for TensorFlow migration, XGBoost replacement, and new-model development. Executable validation hooks check platform API compliance, trainability, and conversion fidelity on sampled data, guiding iterative repair before engineer review and full-scale distributed training. AutoResearch explores architecture and training-configuration changes through expert-steered or autonomous experimentation. An external orchestrator manages parallel trials, experiment history, candidate selection, and wall-clock budgets across agent sessions. A shared runtime preserves execution state independently of agent reasoning and allocates GPUs separately from agent execution. Across ranking, content understanding, and recommendation workloads, AutoTorch completed generation and full-scale training in 92 of 115 workflow runs (80%). Of these, 77 (83.7%) produced models meeting post-training quality requirements. In a separate cohort, AutoResearch improved the primary task metric on held-out data for 28 of 100 production pipelines. Engineering teams estimate that the stack reduced elapsed end-to-end migration time from approximately eight weeks to two weeks, a 4x speedup.
Figures & tables
| 1. Deployment outcomes | Result | Scope | |
| 1.1 | AutoTorch generation runs | 115 | Workflow executions; not necessarily distinct models |
| 1.2 | Operational completion | 92 of 115 (80%) | Generation and full training; denominator: all attempted runs |
| 1.3 | Post-training quality pass | 77 of 92 (83.7%) | Evaluated model artifacts from completed runs; TF clones also require a conversion score |
| 1.4 | Offline primary-metric difference | Typically within 1–5% | Relative to reference after full training; initialization modes not disaggregated; not a deployment gate |
| 1.5 | AutoResearch improvements | 28 of 100 (28%) | Improved original baseline on final held-out evaluation |
| 2. Measured AutoTorch execution | p50 / p90 | Range | |
| Case | Model / use case | Agent action | Primary task metric |
| AutoTorch — generation and migration | |||
| AT-1 | Two-tower video retrieval | Delivered PyTorch model and training pipeline based on source model | Recall@200 matched source model |
| AT-2 | XGBoost TabM; job-posting classification | Changed loss to per-example binary cross-entropy | AUC matched |
| AT-3 | TensorFlow Ranking-based CTR model | Ported to PyTorch with weight transfer; fixed data and evaluation mismatches | AUC matched |
| AT-4 | TensorFlow multi-task model (200M embedding parameters) | Ported to PyTorch; repaired preprocessing, sparse gradients, and task-output handling | Embedding outputs matched (output-parity check) |
| AT-5 | TensorFlow graph neural network | Ported to a PyTorch GNN; restored node encoder and concatenation combiner | Downstream classifier AUC matched |
Automated Machine Learning
Automated machine learning (AutoML) builds and tunes data-to-model pipelines with minimal manual effort, balancing predictive quality, compute, and deployment constraints.
See all 99 papers