Idea to Startup

Team OG Oil & Gas Domain

At first glance, the topics looked familiar, but the depth surprised me. Coming from an aerospace systems engineering background with recent automotive platform work, the session helped connect design thinking to things like requirements trade studies and HMI decisions, not just sticky notes. The walkthrough of problem framing and user empathy filled a gap I’ve had when moving from technical specs to early concept discussions, especially on cross‑functional programs. One challenge was compressing the exercises into a one‑hour format. Translating empathy maps into something usable for a regulated aerospace or automotive environment isn’t trivial, and it took a bit of mental effort to see how this fits alongside DFMEA and certification constraints. Still, the examples made it workable. A practical takeaway was the emphasis on writing clearer problem statements before jumping into solutions. That’s already been applied on a current automotive subsystem project to reset a design review that was stuck on premature architecture choices. Difficulty-wise, it felt accessible but not watered down, which helped keep it relevant for someone already in industry. The content felt aligned with practical engineering demands.

edward pappoe Deputy Director engineering

Initially, I wasn’t sure what to expect from this course, especially given it was only an hour and I already use ChatGPT casually at work. Coming from an automotive background with some exposure to aerospace systems, I was curious whether it would actually add value beyond basic prompts. What worked well was the explanation of how large language models reason and where they break down. That helped me rethink how to use ChatGPT for tasks like drafting requirements for an automotive ECU update and summarizing aerospace-style verification documents. One challenge was translating the generic examples into engineering-specific workflows; the course doesn’t fully walk you through domain-heavy use cases like thermal analysis notes or failure mode discussions. Still, it highlighted the importance of structured prompts and iteration, which was a gap in my understanding. A practical takeaway was learning how to constrain outputs so they’re more usable for real projects—like asking for assumptions, limitations, or step-by-step logic instead of a polished answer. I’ve already applied this while reviewing design trade-offs and preparing internal technical summaries. The course isn’t deep, but it’s grounded enough to be useful for working engineers. It definitely strengthened my technical clarity.

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.

Chesta Patel

This course turned out to be more technical than I anticipated. The sections on supervised vs. unsupervised learning went beyond theory and actually dug into how algorithms like random forests and k-means behave with noisy, imbalanced engineering data. There was also solid coverage of time-series forecasting for equipment data and basic anomaly detection, which maps well to predictive maintenance use cases seen in industry. One challenge was keeping up with the model evaluation discussions, especially around precision–recall tradeoffs and false positives. In real plants, edge cases matter, and the course did a decent job showing how a “good” accuracy score can still fail at the system level. Compared to how AI is often pitched in vendors’ demos, this was more honest about data leakage, model drift, and the limits of small datasets. A practical takeaway was learning how to frame an end-to-end pipeline, from data collection to deployment considerations, instead of stopping at model training. The MLOps discussion was lighter than what’s used in mature teams, but it set the right direction. I can see this being useful in long-term project work.