[D] USQL Joins Were Cool, But Now I Want to Join the GenAI Party
Our take
Hi Experts,
I have 1.5 years of experience in Data Engineering, and now I want to start learning AI, ML, and Generative AI. I already have some knowledge of AI and ML from my college days as a CSE (AI) student. I’ve also worked on a few image classification projects and explored the application of AI in real-life problems.
Currently, I want to dive deeper into Generative AI. However, before that, I’d like to strengthen my understanding of the core concepts behind it—such as neural networks and NLP—so that I can later focus on real-world applications.
If you have a roadmap or guidance that data scientists or other professionals usually follow, it would be very helpful for me as I want to switch from a Data Engineering role to a Data Scientist role.
[link] [comments]
Read on the original site
Open the publisher's page for the full experience
Related Articles
- [D]Trying to switch back to AI/ML — what skills are actually in demand right now?[R]I did my B.Tech in AI/ML where I learned core machine learning concepts like model training, evaluation, etc., and also completed an ML internship. However, my current job is in a different tech stack, and now I’m on the bench. [R] I want to switch back to my original path and aim for roles like ML Engineer / AI Engineer. But I’m confused about what to focus on right now. From what I see, many companies are now asking for GenAI skills (LLMs, LangChain, RAG, etc.), even for ML roles. So I’m unsure whether I should: - Go deep into core Machine Learning again - Focus more on Deep Learning - Or directly start learning GenAI tools and frameworks Given the current job market, what would be the best path to follow to become job-ready as an AI/ML or GenAI engineer? Would really appreciate guidance from people working in the field submitted by /u/iamshrey2 [link] [comments]
- Is the ds/ml slowly being morphed into an AI engineer? [D]Agents are amazing. Harnesses are cool. But the fundamental role of a data scientist is not to use a generalist model in an existing workflow; it's a completely different field. AI engineering is the body of the vehicle, whereas the actual brain/engine behind it is the data scientist's playground. I feel like I am not alone in this realisation that my role somehow got silently morphed into that of an AI engineer, with the engine's development becoming a complete afterthought. Based on industry requirements and ongoing research, most of the work has quietly shifted from building the engine to refining the body around it. Economically, this makes sense, as working with LLMs or other Deep Learning models is a capital-intensive task that not everyone can afford, but the fact that very little of a role's identity is preserved is concerning. Most of the time, when I speak to data scientists, the core reply I get is that they are fine-tuning models to preserve their "muscles". But fine-tuning is a very small part of a data scientist's role; heck, after a point, it's not even the most important part. Fine-tuning is a tool. Understanding, I believe, should be the fundamental block of the role. Realising that there are things other than "transformers" and finding where they fit into the picture. And don't even get me started on the lack of understanding of how important the data is for their systems. A data scientist's primary role is not the model itself. It's about developing the model, the data quality at hand, the appropriate problem framing, efficiency concerns, architectural literacy, evaluation design, and error analysis. Amid the AI hype, many have overlooked that much of their role is static and not considered important. AI engineering is an amazing field. The folks who love doing amazing things with the models always inspire me. But somehow, the same attention and respect are no longer paid to the foundational, scientific side of data and modeling in the current industry. I realise it's not always black and white, but it's kind of interesting how the grey is slowly becoming darker by the day. Do you feel the same way? Or is it just my own internal crisis bells ringing unnecessarily? For those of you who have recognized this shift, how are you handling your careers? Are you leaning into the engineering/systems side and abandoning traditional model development? Or have you found niche roles/companies that still value the fundamental data scientist role (data quality, architectural literacy, statistical rigor)? I'd love to hear how you are adapting submitted by /u/The-Silvervein [link] [comments]
- What has been people's experience with "full-stack" data roles?I started my career being a jack of all trades - hired as a data analyst but I had to extract, clean, and then analyze data and even sometimes train models for simple predictions and categorization. That actually led me to become a data engineer but I've spent most of my career working closely with data scientists and trying my best to make their jobs easier by taking away all the preprocessing tasks away from them so they can focus on training, inference MLops, etc. While I claim to have helped them, to be honest DE teams often become a bottleneck and an obstacle. Everything from not being able to provide the data needed to train on time, or how we processed the data was wrong and led to bad performance, or they went live with a model blindly because we couldn't get them the observation data on time for them to analyze accuracy. I'm wondering how much of the data engineering tasks can be automated/vibed away by data scientists. My guess is that in larger companies this won't be the case but I think startups and SMBs want to move fast so they'd rather have data scientists own the whole pipeline. What has been other's experience with this and where is it heading? submitted by /u/uncertainschrodinger [link] [comments]
- How are you all navigating job search as a data scientist?I feel ineligible for about 70% of the posted job advertisements since they all ask about Agentic/LLM stuff. I have worked with these tools and do use them at work. It's just that it's not my main job that I do on daily basis and I don't want to exaggerate my experience around these tools. I have about 10+ years of work ex and have actually worked from just data scientist to combination of ML and data engineer. submitted by /u/proof_required [link] [comments]