New opportunity

Data Scientist

Wi-Tronix · Bolingbrook, United States

About this role

Wi-Tronix is hiring a Data Scientist to own the full lifecycle of deep learning models deployed on locomotives across North America. The role uses real-time video and sensor data to support rail safety and reliability, with models running on edge hardware under variable lighting, weather, and equipment conditions.

Responsibilities

  • Design and train custom deep neural networks for computer vision, object detection, and time series problems. Build and refine data-labeling and training pipelines.
  • Optimize models for edge deployment using PyTorch, NVIDIA TensorRT, and ONNX. Develop APIs and automated tests to put models into production and monitor their health.
  • Work with ML engineers, data engineers, and product colleagues; explain model behavior to nontechnical stakeholders. Conduct careful experiments, maintain logs, and design ablations, prioritizing performance on real hardware.

Requirements

  • BS or MS in Computer Science, Mathematics, Statistics, or a related field; at least 3 years building and deploying deep learning models on real data, with strong Python and PyTorch skills.
  • Computer vision fundamentals; SQL; experience with regression, classification, and object detection; knowledge of memory models, CPU and GPU architectures, and modular software design; and familiarity with AWS S3 and Glue.
  • An agile approach to prototyping, incorporating feedback, and delivering usable work.

Preferred

NVIDIA TensorRT, ONNX, YOLO or Detectron2, C or C++ for edge integration, Docker, and an IoT or safety-critical background.

The role is hybrid in Bolingbrook, Illinois: Tuesday through Thursday in the office, with Monday and Friday remote or on-site as business needs require. Candidates must be able to board a locomotive for field research; occasional domestic and international travel may be required. Applicants must be authorized to work in the United States; employer-based visa sponsorship is not available now or in the future. The anticipated base salary range is $103,000 to $146,000. Benefits include medical, dental, and vision coverage with an employer HSA contribution; employer-paid life, AD&D, and disability coverage; telemedicine; an Employee Assistance Program; and financial wellness resources.

For full details about this role, click “Apply on company site” to view the employer’s original posting.

Skills for this role

PythonPyTorchDeep LearningComputer VisionObject DetectionTime Series AnalysisRegressionClassificationSQLNVIDIA TensorRTONNXAWS S3AWS GlueAPI DevelopmentAutomated TestingExperimental DesignEdge DeploymentYOLODetectron2CC++DockerIoTModular Software Design

Your skill match

Checking your profile…

YOUR NEXT STEP

Get interview-ready for this role

A focused preparation guide, built around this job’s responsibilities and requirements.

✦ AI-generated guide
Preparation suggestions, not the employer’s actual interview questions. Always check the original posting for current requirements.
01

Understand the role

What matters most

  • Own the model lifecycle

    The role spans designing and training deep learning models for computer vision, object detection, and time series problems through deployment on locomotives. Prepare to explain how you take a model from real data to a usable release.

  • Improve data and experimental rigor

    Wi-Tronix calls for refining labeling and training pipelines, keeping careful logs, and designing clean ablations. Prepare an example of how you tested whether a data or model change genuinely improved results.

  • Optimize for locomotive hardware

    Models must run in real time on edge hardware; the posting emphasizes performance on actual hardware over leaderboard results. Prepare to discuss how you evaluate accuracy alongside runtime and resource use, including PyTorch, ONNX, or TensorRT where relevant.

  • Ship and explain production models

    The role includes APIs, automated tests, model health, and collaboration with ML engineering, data engineering, and product. Prepare to describe production handoffs and how you communicate model behavior to nontechnical stakeholders.

Likely challenges to think through

  • Variable field conditions

    Likely preparation challenge, not a confirmed problem: lighting, weather, and equipment differences may make results on familiar data less reliable in service. Prepare to discuss representative labeling, condition-based evaluation, and how you would investigate failures.

  • Accuracy versus edge constraints

    Likely preparation challenge: a more accurate model may be too slow or demanding for real-time locomotive hardware. Prepare to explain how you would compare candidates on the target device and justify a smaller or optimized model.

  • Fast iteration versus dependable releases

    Likely preparation challenge: rapid prototyping and feedback must coexist with automated testing and ongoing model health. Prepare to explain what evidence and checks you would want before deployment, and how you would detect a regression afterward.

03

Practice your answers

Technical practice

How would you prepare locomotive video and sensor data for model training?

What to coverSuggested answer focus: Discuss labeling consistency, data quality checks, and splits that avoid leakage between related recordings. Explain how you would examine coverage across the lighting, weather, and equipment variability named in the posting.

How would you design and evaluate an object-detection model for variable rail conditions?

What to coverSuggested answer focus: Describe relevant computer vision and detection choices, then explain how you would inspect errors across operating conditions rather than rely on one aggregate score. Relate model accuracy to the role’s need to run on edge hardware.

How would you approach a time-series problem using locomotive sensor data?

What to coverSuggested answer focus: Explain how you would define the prediction target and choose between regression and classification where appropriate. Discuss temporal validation, noisy or missing readings, and whether the result is useful in real time.

How would you improve a labeling and training pipeline after finding inconsistent model performance?

What to coverSuggested answer focus: Walk through checks for annotation quality, data coverage, preprocessing consistency, and reproducible training runs. Explain how you would determine whether new labels, pipeline changes, or model changes address the problem.

How would you design an ablation to test whether a model change genuinely helps?

What to coverSuggested answer focus: Describe a controlled comparison with a fixed evaluation set, clear metrics, and careful experiment logs. Include how you would check performance on real hardware, not just an offline benchmark.

What trade-offs would you consider when deploying a PyTorch model through ONNX or TensorRT?

What to coverSuggested answer focus: Discuss conversion compatibility, numerical or output differences, latency, memory use, and accuracy. Explain how you would compare the converted model with the PyTorch version on representative inputs and target hardware.

How would you diagnose a model that performs well offline but poorly on locomotive edge hardware?

What to coverSuggested answer focus: Separate data or model errors from preprocessing, conversion, and runtime bottlenecks. Discuss profiling CPU, GPU, and memory behavior, then testing changes on the actual hardware.

How would you structure an API and automated tests for a production model?

What to coverSuggested answer focus: Describe a modular boundary between input handling, inference, and outputs. Cover tests for expected behavior and failure cases, while distinguishing software checks from model-quality evaluation.

How would you monitor the health of a deployed vision model?

What to coverSuggested answer focus: Propose checks for inference failures, resource use, and changes in inputs or outputs under variable lighting, weather, and equipment conditions. Explain what evidence would prompt investigation or reevaluation without assuming ground-truth labels are immediately available.

How would you use SQL, S3, and Glue to support a reproducible model-development workflow?

What to coverSuggested answer focus: Explain how you would identify and access relevant data, track dataset versions or transformations, and make training inputs reproducible. Keep the proposed workflow conditional: the posting names these technologies but does not specify Wi-Tronix’s data architecture.

Behavioural practice

Tell me about a time you worked across ML, data engineering, and product roles to ship usable work.

What to coverSuggested answer focus: Use a real situation, the coordination and decisions you personally handled, and the resulting deliverable. Show how you resolved differing priorities without claiming a particular Wi-Tronix team process.

Describe a time you explained unexpected model behavior to nontechnical stakeholders.

What to coverSuggested answer focus: Give the situation, how you communicated the evidence and limitations, and what decision or follow-up resulted. Emphasize clarity without overstating model reliability.

Tell me about a time feedback changed a prototype before delivery.

What to coverSuggested answer focus: Identify the original goal, the feedback you received, your specific adjustment, and the result. The posting values rapid prototyping, feedback loops, and work the team can act on.

Describe a time real-world conditions changed how you evaluated a model.

What to coverSuggested answer focus: Use a real example of the conditions encountered, the evaluation or troubleshooting actions you took, and the outcome. If applicable, distinguish lab metrics from behavior on deployed hardware; the posting prioritizes performance on real hardware.

Tell me about a time a careful experiment challenged your preferred approach.

What to coverSuggested answer focus: Describe the hypothesis, the logs or ablation that tested it, your response to the evidence, and the result. Focus on a genuine trade-off rather than presenting an unverified improvement as a success.

02

Sharpen your knowledge

Topics to prepare

  • Computer vision and object detection

    Review how detection errors change with lighting, weather, and equipment variation; as a preparation exercise, explain how you would compare performance across those conditions. The posting names object detection and these variations as central to locomotive video.

  • Time series, regression, and classification

    Review when each approach fits sensor-data problems; as a preparation exercise, outline a plausible prediction task for each and how you would evaluate it. The posting explicitly calls for time series work and experience with regression and classification; the example tasks are suggestions, not stated projects.

  • Edge compute and memory constraints

    Review CPU and GPU architectures and memory models; as a preparation exercise, reason through why a smaller model might outperform a larger one on constrained hardware. The posting emphasizes real-hardware performance and names these foundations.

  • Experimental design and ablations

    Review how to isolate one model or data-pipeline change at a time; as a preparation exercise, draft an ablation table with metrics and a log of decisions. The posting explicitly values careful logs, clean ablations, and usable results.

  • Production model lifecycle

    Review how labeling, training, deployment, and model-health checks connect; as a preparation exercise, sketch the handoffs and likely failure points. The posting assigns full-lifecycle ownership, including labeling pipelines, APIs, and automated testing.

Skills to revise

  • Python and PyTorch model development

    As a preparation exercise, implement a small training and evaluation loop for a vision or sensor-data task, keeping the code modular. Strong Python and PyTorch fluency and deep-learning deployment experience are stated requirements.

  • Labeling and training pipelines

    As a preparation exercise, define label checks and trace how corrected labels reach a retrained model. Building and refining labeling and training pipelines is an explicit responsibility.

  • SQL and AWS data access

    As a preparation exercise, write SQL to select and summarize records, then diagram where S3 storage and Glue would fit in a data-access workflow. The posting requires SQL and comfort with S3 and Glue; the diagram is a suggested exercise, not a stated architecture.

  • Edge deployment workflow

    As a preparation exercise, walk through exporting a PyTorch model with ONNX and benchmarking an optimized version against the original on edge hardware, if available. The role explicitly involves edge optimization using PyTorch, ONNX, and NVIDIA TensorRT; ONNX and TensorRT experience is listed as a bonus.

  • APIs and automated tests

    As a preparation exercise, design a model-inference API and tests for input handling, output consistency, and failure cases. Creating APIs and automated testing to move models into production and keep them healthy is an explicit responsibility.

  • Explaining model behavior

    As a preparation exercise, summarize an experiment’s trade-offs and failure cases in plain language for a product colleague. The posting calls for collaboration across teams and explanations to nontechnical stakeholders.

04

Your preparation checklist

  • Prepare a deployed-model walkthrough

    The role calls for 3+ years building and deploying deep learning models on real data. Prepare one project walkthrough, if available, covering your Python/PyTorch choices, computer vision or time-series task, deployment, and measured results; distinguish your own contributions.

  • Sketch a data and labeling pipeline

    Wi-Tronix builds labeling and training pipelines for locomotive video and sensor data. Prepare a diagram showing how you would access data, define labels, check quality, and handle lighting, weather, and equipment variation. Include where SQL and AWS S3 or Glue might fit; this is a proposed design, not a stated company workflow.

  • Practice an edge-deployment design exercise

    The models run on locomotive hardware, and the posting emphasizes real-hardware performance. Prepare a design that compares model size, latency, memory, and accuracy, and explains how you would validate PyTorch-to-ONNX or TensorRT optimization. Identify CPU/GPU and memory considerations and label any hardware assumptions.

  • Bring an experiment and ablation plan

    The role values careful logs and clean ablations. Prepare a one-page plan for an object-detection or time-series problem with baselines, metrics, controlled changes, failure-case analysis, and a decision rule based on hardware results.

  • Outline a production health check

    Wi-Tronix calls for APIs and automated tests that move models into production and keep them healthy. Prepare a sample API contract, a few test cases, and proposed monitoring signals; present the monitoring choices as suggestions rather than existing company practice.

  • Rehearse a cross-functional explanation

    The role partners with ML engineers, data engineers, and product and explains model behavior to nontechnical stakeholders. Prepare a short explanation of a model's result, limitations, and trade-offs, plus an example of how feedback would change the next prototype.

  • Draft targeted employer questions

    Prepare questions about available edge hardware, how field data is labeled and evaluated, what model-health signals matter, and how field research informs priorities. If relevant, clarify the stated Bolingbrook hybrid schedule, locomotive boarding, and occasional travel.

AI-generated from the job information · Prepared Oct 1, 2026 (UTC)Useful preparation, not a guarantee of eligibility or an offer.

Availability last checked: Sep 30, 2026. Status can change after a check; confirm on the employer’s website. Report an issue · Our checking policy

KEEP EXPLORING

Similar AI jobs

Related skills and specializations in United States. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…