> Markdown version of [/jobs/ext/3020717-ml-engineer-network-intelligence](https://www.wearedevelopers.com/jobs/ext/3020717-ml-engineer-network-intelligence). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # ML Engineer, Network Intelligence - **Company:** Colt Technologies, LLC - **Location:** United States (Remote available) - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, BigQuery, Cloud Computing, Cloud Storage, Information Engineering, Data Security, Python (Programming Language), Machine Learning, Network Control, Network Administration, Recommender Systems, Software Deployment, SQL Databases, Data Streaming, Workflow Management Systems, Computer Network Operations, Feature Engineering, Pytorch, Multi-Agent Systems, Deep Learning, Model Validation, AI Platforms, Scikit Learn, Kubernetes, Xgboost, Apache Kafka, Machine Learning Operations, Hardware Infrastructure, Software Version Control, Data Pipelines, Cisco, Unsupervised Learning - **Published:** September 21, 2026 - **Apply:** https://find.jobs/jobs-near-me/apply/ats-redirect/?id=2953249464-2 ## About the Role You do not need to be a deep learning researcher or a network engineer. You need enough network domain knowledge to make sense of the data, and strong ML fundamentals to build models that are trustworthy in a production environment. MLOps tooling experience is a plus but not a day-one requirement. You will have the opportunity to grow into ownership of the model lifecycle layer as the team matures., Classical ML * Time series analysis, anomaly detection, supervised/unsupervised learning; scikit-learn, XGBoost, PyTorch or equivalent; model evaluation and production deployment experience Data Engineering * SQL and BigQuery; data pipeline construction; feature engineering from raw telemetry; experience with real-world network data Cloud & Tooling * GCP (BigQuery, Vertex AI, Cloud Storage); Python; MLOps lifecycle tooling (MLflow, Weights & Biases, Vertex AI Pipelines or equivalent) is a growth expectation. Experience is a plus, ownership is where you are headed in six months Mindset * Comfortable working with ambiguous, incomplete data; understands that network operation requires high trust thresholds before autonomous action; can translate between network engineering and ML concepts Nice to Have * Experience with Cisco platforms, NSO, Itential, or similar network orchestration tools; streaming telemetry (Kafka, Pub/Sub); OpenTelemetry * Familiarity with network operations or network telemetry data is a plus; SDN experience is a significant advantage for the AI WAN closed-loop work but is not required for Phase 1 delivery ## Description As ML Engineer, Network Intelligence, you own the data and modeling layer that turns Colt's network telemetry into production ML systems. Your primary work is cleaning and structuring real-world network data, building classical ML models for anomaly detection, predictive maintenance, and traffic forecasting, and getting those models into production. You will work directly with network telemetry data in GCP BigQuery, build the data pipeline and feature engineering layer that makes ML possible on network data, and develop classical ML models for anomaly detection, predictive maintenance, traffic forecasting, and capacity planning. Longer term, you will be central to the AI WAN closed-loop architecture, defining what network state the model consumes and what control plane actions it is safe to initiate., * Build and operationalize ML models for anomaly detection on network time series data * Own root cause analysis (RCA) model development, identifying contributing factors and failure chains in network events, in addition to detecting that something is wrong * Develop predictive maintenance models to forecast hardware failures and network degradation before customer impact * Build traffic forecasting and capacity planning models to support proactive network management * Design model evaluation frameworks appropriate for network operations - precision/recall tradeoffs, false positive costs, operational trust-building Network Data & Feature Engineering * Assess, clean, and structure network telemetry data in GCP BigQuery - the foundational step before any ML is possible * Build data pipelines that transform raw network telemetry into ML-ready features * Work with Colt's NaaS and network operations teams to understand data semantics, quality gaps, and labeling challenges * Define the data access and enrichment roadmap for network AI use cases MLOps & Model Lifecycle * Own the full lifecycle of network ML models: experiment tracking, model versioning, retraining pipelines, and production drift monitoring * Define retraining triggers and model health thresholds appropriate for network operations, where a degraded model can have real service impact * Partner with the AI Platform Engineer, who owns the underlying infrastructure; you own the ML layer on top. The boundary is model serving (yours) versus Kubernetes and GPU infrastructure down (theirs) AI WAN Closed-Loop Architecture * Work with Cisco and Colt's NaaS team to understand what network state data are available and what control plane APIs exist for programmatic network actions * Define the closed-loop architecture: what inputs feed the model, what decisions it can make autonomously, what requires human confirmation * Build the initial recommendation layer (human-in-the-loop) before progressing to autonomous closed-loop actions * Design guardrails, rollback mechanisms, and confidence thresholds appropriate for production network control Cross-Team Collaboration * Partner with the Staff AI Engineer to connect ML model outputs to agent orchestration and recommendation systems * Work with the AI Platform Engineer on the handoff boundary: they own Kubernetes, GPU infrastructure, and model serving setup; you own what runs on top, including experiment tracking, retraining pipelines, and production model health * Engage directly with NaaS team and network operations stakeholders to ground use cases in real operational problems ## Related Videos - [MLOps - What’s the deal behind it?](https://www.wearedevelopers.com/videos/392-mlops-what-s-the-deal-behind-it) - [How Cisco embraced a DevOps culture within its network engineering team](https://www.wearedevelopers.com/videos/99-how-cisco-embraced-a-devops-culture-within-its-network-engineering-team) - [TikTok's Privacy Innovation](https://www.wearedevelopers.com/videos/1036-tiktok-s-privacy-innovation) - [Photonic Computing: Programming a New Class of AI Accelerators (incl. Live Coding)](https://www.wearedevelopers.com/videos/100196-photonic-computing-programming-a-new-class-of-ai-accelerators-incl-live-coding) - [Your Infrastructure Is Not a Playground: AI Agents for Infra Done Right](https://www.wearedevelopers.com/videos/2084-your-infrastructure-is-not-a-playground-ai-agents-for-infra-done-right) - [LLMOps-driven fine-tuning, evaluation, and inference with NVIDIA NIM & NeMo Microservices](https://www.wearedevelopers.com/videos/1582-llmops-driven-fine-tuning-evaluation-and-inference-with-nvidia-nim-nemo-microservices) ## Related Articles - [MLOps – What’s the deal behind it?](https://www.wearedevelopers.com/magazine/125-mlops-what-s-the-deal-behind-it) - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer) - [MLops – Deploying, Maintaining And Evolving Machine Learning Models in Production](https://www.wearedevelopers.com/magazine/115-mlops-deploying-maintaining-and-evolving-machine-learning-models-in-production) - [MLOps And AI Driven Development](https://www.wearedevelopers.com/magazine/82-mlops-and-ai-driven-development) - [What Are Large Language Models?](https://www.wearedevelopers.com/magazine/304-what-are-large-language-models) - [Graph and AI Trends 2026: Why Is AI Running but Not Yet Delivering?](https://www.wearedevelopers.com/magazine/680-graph-and-ai-trends-2026-why-is-ai-running-but-not-yet-delivering)