> Markdown version of [/jobs/ext/4702485-data_scientist-with-core-ml-onsite-interview-in-san-jose-ca](https://www.wearedevelopers.com/jobs/ext/4702485-data_scientist-with-core-ml-onsite-interview-in-san-jose-ca). 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). --- # Data_Scientist with Core ML (Onsite interview in San jose,CA) - **Company:** EdgeAll Inc - **Location:** San Jose, CA, United States - **Experience:** Expert - **Contract:** Contract - **Skills:** Artificial Intelligence, BigQuery, Continuous Integration, Distributed Computing Environment, Apache Hadoop, Monitoring of Systems, Python (Programming Language), NumPy, Tensorflow, Azure Machine Learning, SQL Databases, Feature Engineering, Pytorch, Apache Spark, Pandas, Pyspark, Scikit Learn, Kubernetes, Machine Learning Operations, Docker - **Published:** November 13, 2026 - **Apply:** https://www.dice.com/job-detail/7ebeaf7d-30b9-4b13-81d7-53dc7b98a149 ## About the Role Bachelor's or Master's in CS, Statistics, Mathematics or a related quantitative discipline; PhD a plus. * 8+ years applied ML / data science with a verifiable record of models sustained in production. * Strong mathematical foundations - linear algebra, probability, statistics, optimization. * Demonstrated depth in feature engineering and model architecture design, explainable on a whiteboard for models personally built. * Proven end-to-end pipeline ownership, not notebook-stage experimentation. * Expert Python and SQL; pandas, NumPy, scikit-learn and PyTorch or TensorFlow. * Distributed processing (Spark/PySpark, Hadoop, BigQuery) and a cloud ML platform (SageMaker, Azure ML or Vertex AI). * MLOps working knowledge - MLflow, Docker, Kubernetes, CI/CD, model monitoring. * Production model observability and drift management - threshold definition, automated alerting, kill- switches and retraining/rollback triggers. * Experience designing model routing or fallback logic across multiple models, including the validation applied when a switch occurs.