Generative AI for Engineering Students/ Working Professionals

Sudherson Jagannathan PIPING ENGINEER

A lot of the material tracked issues in our current sprint, framing AI as something that fits into an existing arch instead of a side experiment. The Chapter 3 walkthrough on predictive maintenance for rotating shafts, especially the FFT-to-classifier sketch, stuck; mapping that to our automotive brake wear data was straightforward. It's beginner-level so some math wasn't there, and I wished for more on infra/CI getting to prod, but the risk-scoring example helped close a PR—saved me from a couple arch debates.

Harit Naik Director - Global Innovation & Knowledge Management

Initially, I wasn’t sure what to expect from this course. Coming from a production engineering background, AI always felt a bit abstract, but the way it was tied to real industrial problems made it click. Topics like predictive maintenance using machine learning and computer vision for defect detection were especially relevant, since similar issues show up on our shop floor. The section on data preprocessing and feature selection was something I didn’t realize I was missing, and it filled a clear knowledge gap from my earlier, more theory-heavy exposure to AI. One challenge was wrapping my head around model selection trade-offs, especially when comparing neural networks versus simpler models for limited datasets. The course didn’t hide those limitations, which I appreciated. A practical takeaway was learning how to structure an end-to-end AI workflow, from collecting sensor data to validating model outputs before deployment. That directly helped on a small pilot we’re running for anomaly detection on rotating equipment. The content felt grounded in real constraints like data quality and compute limits, not ideal scenarios. It definitely strengthened my technical clarity.

Ikram Ul Haq

Coming into this course, I had some prior exposure to the subject, mainly around basic machine learning concepts, but not much on applying them in an engineering setting. What stood out was how the course connected supervised learning and neural networks to real industrial problems like predictive maintenance and process optimization. The sections on feature engineering for sensor data and model validation in noisy environments were especially relevant to work I’m doing on equipment health monitoring. One challenge was keeping up with the math behind model tuning while also understanding the practical trade‑offs. The jump from theory to implementation, particularly when covering computer vision for defect detection, took some effort and a bit of extra practice outside the lectures. A practical takeaway was learning how to frame an engineering problem as an AI problem, including when not to use deep learning and stick with simpler models. That alone helped fill a knowledge gap around model selection and deployment constraints. Difficulty felt moderate but fair, especially for someone working full time. The content felt aligned with practical engineering demands.

Ved Naik Engineering

Initially, I wasn’t sure what to expect from this course. Coming from a production engineering background, there was a gap between knowing basic AI concepts and actually applying them on real projects. The modules on data preprocessing and supervised machine learning helped close that gap, especially when they tied feature engineering and model selection to engineering datasets like sensor data. Coverage of neural networks and predictive maintenance was also useful, since that’s directly relevant to the reliability work happening on my current project. One challenge was keeping up with the pace when the course moved from theory into implementation. Translating algorithms into working Python code, particularly when tuning models in scikit-learn and evaluating performance beyond accuracy, took some effort. The examples weren’t always clean, which honestly reflected real-world conditions and forced some problem-solving. A practical takeaway was learning how to build a simple end-to-end AI workflow—from defining the engineering problem, cleaning data, training a baseline model, and validating results before deployment. That structure is something already being reused at work for a small anomaly detection use case. The content felt aligned with practical engineering demands.