Question for MLEs: How often are you writing your models from scratch in TF/PyTorch?
Our take
I have about 8 years of experience mostly in the NLP space although i've done a little bit of vision modeling work. I was recently let go so I'm in the midst of interview prep hell. As i'm moving further along in the journey, i'm feeling i have some gaps modeling wise but I'm just trying to see how others are doing their work.
Most of my work the last year was around developing MCP servers/back end stuff for LLMs, context management, creating safety guardrails, prompt engineering, etc. My work before that was using some off the shelf models for image tasks, mostly using models I found on github via papers or pre-trained models on HuggingFace. And before that I spent most of my time around feature engineering/data prep and/or tuning hyperparamters on lighter weight models (think XGBoost for classification, or BERTopic for topic modeling).
I've certainly read books/seen code that involves hand-coding a transformer model from scratch but I've never actually needed to do something like this. Or when papers talk about early/late fusion layers or anything more complex than a few layers, I'd probably have to look up how to do it for a day or two before getting it going.
Am i the anomaly here? I feel like half my time has been doing DS work and the other half plain old engineering work, but people are expecting more NN coding knowledge than i have and frankly it feels bad, man. How often are y'all just looking for the latest and greatest model on UnSloth/HF instead of building it yourself?
Brought to you from the depths of unemployment depression....
[link] [comments]
Read on the original site
Open the publisher's page for the full experience
Related Articles
- 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]
- Do MLEs actually reduce your workload in your job?Maybe I’m wrong, but I feel like in the bigger companies I have worked for, the “client - provider” kind of setup for MLEs / MLOps people and Data Scientists is broken. Not having an MLE in the pod for a new model means that invariably when something is off with the serving, I end up debugging it because they have no context on what’s happening and if it is something that challenges the current stack, the update to account for it will only come months down the road when eventually our roadmaps align. I don’t feel like they take a lot of weight off my shoulders. The best relationship I ever had with MLEs was in a small company where I basically handed off the trained model to them for deployment and monitoring, and I would advise only on what features were used and where they come from (to prevent a distribution mismatch in their feature serving pipelines online). Discuss submitted by /u/yaksnowball [link] [comments]
- Are teams still using Pytorch/Tensorflow, or is most ML work just calling LLM endpoints and prompt engineering now?I've been looking for a new job lately (brutal market, btw), and a lot of the ML/AI engineering work now seems pretty LLM-dominated. I still see a few jobs that seem to be doing more "classical", pre-ChatGPT era type of work with Pytorth or Tensorflow, but it seems that a lot of the work now is working with LLMs, doing RAG, prompt engineering, etc. with Langchain or what have you, and calling Anthropic or OpenAI model endpoints. Is this an accurate take on the market? And if so, what happened to all the Pytorch/Tensorflow work? Why did it shift so heavily towards just using LLM providers in some package/endpoint? submitted by /u/Illustrious-Pound266 [link] [comments]
- How do you keep up without burnout?DS sometimes feels like there's infinite amount of things to learn. Most recent trend has been AI engineering And it's not like AI came in so you can deprioritize something else, but instead it just gets added to the heap. So you already had this massive amount of content to know from stats & product, trad. ML, deployment, ops, engineering, cloud, etc. and then you add the new thing on and the new thing. And when you read the job descriptions they literally list of all of this. I just had an interview for a random gaming company that wanted cloud, snowflake, stats, ML, ops, and AI experience in 1 person and it was for like 3-5 years of experience. And I wish that this was a one off thing but it seems to get more common. It actually feels like FAANG is easier to interview for because they silo people and not expect you to know and do everything What is your strategy for learning these skills without getting exhausted, or do you feel companies expectations are overflated? Is this a by product of AI where people are expected to do a lot more with less? submitted by /u/LeaguePrototype [link] [comments]